|
|
|
|
Now that JSF 2.0 is Final and is is easily accessible in GFv3 Preview, it is a good time to learn more about it, so here is a set of useful links:
|
•
The
JSR 314 site (EG) has a link to the spec, the votes, etc.
|
Also, all related TA entries are tagged JSF... And, please send us feedback on the spec or the implementation to help us with the Fit and Finish.
Three brief but important JCP news:
|
The first
JavaEE 6 |
The JCP also approved additional transparency for JCP 2.7, which I believe is a very important part in running an Expert group for a number of reasons, including balancing the role of the EG lead.
The final news is the submission of JSR 330, Dependency Injection for Java. The relationship to JSR 299 is unclear to me at this point.
|
JSF 2.0 is arguably one of the most awaited update to the Java EE 6 specification. IceFaces, the well-known provider of Ajax-enabled JSF components, is now building its 2.0 version on top of the Ajax support now built into the JSF 2.0 specification. Co-specification lead Roger Kitain has a recent blog entry discussing how ICEFaces uses JSF 2.0 to send Ajax requests from the client and how it processes them on the server. |
In other recent JSF news, Ryan Lubke discusses bookmark-ability in JSF 2.0 (with the reference Mojarra implementation). Previous entries regarding JSF 2.0 can be found using the jsf2 tag.
In a few days time you'll be able to use the Preview version of GlassFish v3 which supports JSF 2.0. The adventurous can grab a recent GlassFish v3 promoted build here.
JSR 314, JSF 2.0, is Now in Final Vote. To celebrate that, here is a pass through JSF 2.0 news:
|
•
From Ed, the
Slides and Feedback
on his recent
Online Webinar
|
Ryan's latest installement in his JSF 2.0 Preview series shows how to implement
Custom Managed Beans
through the new custom scope view
and the
managed-bean-scope
element in
faces-config.xml
or via the
@CustomScoped
annotation.
The full series is:
PS. The picture is that of the Tuxtla Statuette, which is from the La Mojarra; used here as Mojarra is the project name of the GlassFish JSF implementation.
|
|
Dan had previously made Seam work with GlassFish but he now has woven the changes back (with extra functionality) into the Seam Project. Thanks, Dan! Specially appreciated is the support for RH (JBoss 5/RichFaces) and non-RH technologies (GlassFish Server/ICEfaces). Also newsworthy is the First Beta of JSR299, with a promised Seam bridge. |
Related Webinars and Blog Entries:
• Seam, WebBeans and GlassFish, Dan Allen, Nov 20th, 2009.
• Short intro to ICEfaces, Ted Goddard, Feb 10th, 2009.
• From Ajax Push to JSF 2.0: ICEfaces on GlassFish, Ted Goddard, March 12th, 2009.
• Entries tagged Seam
,
ICEfaces
,
JSF
.
• Arun's TOTD-77
|
The presenter at tomorrow's webinar is Ted Goddard; he will detail how to write rich interface applications using Ajax and Comet using JSF and ICEfaces and will also describe how these relate to the new JSF 2.0 specification in JavaEE 6. Presentation at 11am US Pacific, at TheAquarium Channel. Full details (and recordings) at the Show Page. |
|
Last summer Ryan wrote a very nice JSF 2.0 Preview Series but then he got pretty busy; today he came by my office and said he will start posting again. As a first installment, check his note on Implicit Navigation in JSF 2.0; this means that faces-config.xml is not needed in many cases. I think bookmarkable pages is next in Ryan's agenda - that has been a very recent addition to the spec. JavaOne 2009 is around the corner, so we should expect more Java EE 6 activity; the spec is shaping up very nicely... |
BTW, on a somewhat related note, check out Ed's writeup regarding improving transparency on the JSF 2.0 expert group. Baby steps, in the right direction.
|
The JSF team has released a
New Version of JSF 2.0
(release notes,
changelog,
JSF You can install the ZIP manually or the IPS repositories automatically using either the admin console or the update tool. The repositories are very convenient but check what is your preferred repository and remember to set your "View All Versions!" - see ScreenShot. |
We are working on improving the experience of using the repositories; your feedback is very appreciated.
As promised in yesterday's note here are the details on the UpdateCenter (2.0) bug and "update logic" ...
|
The story starts with Ryan releasing new JSF packages in December; updates that my update tool didn't see. Several JSF team folks I contacted reported success so I assumed I was affected by a new bug and later wrote an entry. But last week I finally had some time and there are two different issues: • The first one is a usability issue: the Update Tool checks for updates from multiple repositories one of which is preferred. The community and the Sun distributions of GFv3 Prelude have different configurations and our observed behavior reflected which distro we were testing. • After we realized the first, the second issue was easy: just a simple bug, 1075. The result is that we are going to fix 1075, and, we are going to look at how we define the search through the repositories, and how we report on possible updates - the current arrangement is just too error-prone. If you have experiences with similar mechanisms that you want to contribute please let us know. |
A quick update: the JCP SE/EE EC has approved all the Java EE 6 specs in the first batch of votes mentioned in our Jan 6th Report:
|
•
Vote results
for JSF 2.0
(Ed Burns & Roger Kitain,
JSR 314,
@TA
|
EJB 3.1 (results) and JPA 2.0 (results), were approved previously; Bean Validation, WebBeans will go to vote on Feb 3rd.
|
The JSF 2.0 team last month released an implementation of the new JSF 2.0 PRD (see JCP vote) and an updated JSF 1.2.11. The releases are available at the GFv3 Update Center (see, e.g., Mac) and can be installed using the stand-alone UpdateTool or the Admin Console. Let us know if you encounter any problems. |
This implementation has all PRD features including the Declarative Events described by Jason, but the EG is still working on additional features like state management. A few others, like bookmarkable URLs, are still being discussed and may or not make it.
During the break, I noticed that the Bean Validation spec had gone into Public Review Draft. That spec is the last of the batch being considered for JavaEE 6. Below is a full list based on a pass through JCP (will adjust if I missed any); all of them are either in PRD or past it; the only exception is Java EE 6 itself (JSR 316) which, by definition, lags them all.
|
•
WebBeans
(Gavin King,
JSR 299,
@TA
|
Some of these specs have already been voted on: EJB 3.1 (results) and JPA 2.0 (results); for some others the vote starts on Jan 6th: JCA 1.6, Servlet 3.0, JSF 2.0, and a last batch starts on Feb 3rd: Bean Validation, WebBeans.
If you are a Woodstock user you may have seen the announcement from November 3rd where the NetBeans team announced they would stop development of new features in Woodstock. The full context was provided in a subsequent event (Archive - check slide 11-13 in slide deck).
|
The outcome was that Sun would work on two fronts: adding support for FireFox 3 on Woodstock 4.2 and a partner-based strategy. On the first front, check today's email and this wiki page; on the second, today we are announcing a relationship with ICEfaces. Check: John's post, Migration page at ICEfaces and Migration Doc at NetBeans. |
The ICEfaces NetBeans plugin can be obtained at ICEfaces.org or from the NB's Update Center, see under tools->plugins. And, as John says, stay tuned for more details in these areas.
Most migrations to GlassFish are straight-forward, a testimony to the value of the JavaEE specification (and to the extra care to the user in the GF community!). The only area that sometimes requires non-trivial changes are dependencies on implementation details in MyFaces.
The GlassFish JSF implementation (Mojarra) is Used in Many Containers and the new JSF 2.0 spec should improve portability but GF supports a useMyFaces Property for this use case. Arun just published a note showing how to use the property when Using Apache Tomahawk but I'm extracting here the configuration table for ease of reference:
|
• On GlassFish v2 - Set "useMyFaces" in "sun-web.xml"
|
Note that you also need to disable Facelets 2.0 in "web.xml" if you have Facelets 1.1.x dependencies.