I just noticed a good Tapestry nugget on Howard's blog. With Tapestry 3.0, one of the things I complained about was the need to throw an exception when redirecting. With 4.0, it looks like you can plug-in this flash component and get exactly the flash message functionality I try to put in all the web frameworks that AppFuse supports. Now I just need to figure out how to do
@InjectObject("engine-service:page") without using annotations.
I'm hoping to upgrade AppFuse to WebWork 2.2 and Tapestry 4.0 in the next few days.
Ed Burns (JSP Spec Lead) points out there's New Drafts of Java EE Web Tier: JSF 1.2, JSP 2.1, Servlet 2.5
I'm pleased to announce another revision of the Java EE Web Tier. In
Jan Luehe's blog
you can find out what's new in JSP 2.1 Proposed Final Draft 2 (PFD2).
Log for Servlet 2.5 will give you the scoop on the Servlet spec.
This blog entry will show what's new in the JSF spec.
In JSF, the most visible new feature since the last draft of the spec
is the addition of the
invokeOnComponent() method on
UIComponent. See below for more details.
This revision of the Java Web Tier is fully implemented in glassfish
build 37, Sun's open source Java EE 5 Application Server, and the
basis for the upcoming Java EE SDK.
I changed the link to Jan Luehe's blog because Ed's link seems to be incorrect. My guess is Java EE will be finalized and released before JavaOne. This is how Sun usually does things: work like mad until JavaOne, then take a week or two off to celebrate the release. Other rumors I've heard are that JBoss and Geronimo hope to release Java EE 5 compliant releases by or at JavaOne.
2006 is shaping up to be quite a year for the popular Java web frameworks. Tapestry 4.0, WebWork 2.2, JSF 1.2 and Spring MVC 2.0 (with form tag libraries and smart defaults). The question is, how long will it take for MyFaces to implement JSF 1.2? And when will we see a large-scale site deployed with JSF?
Why isn't Struts or your favorite framework in this list? Struts is being replaced by WebWork and the rest simply don't have the market share.
No one has heard of RIFE or Wicket. However, that didn't stop me from encouraging SourceBeat to publish a Wicket book. Having good (published) documentation about a project is the first step to corporate adoption IMO.