JSF 2.0 so far, in depth Blog
We all know that Ryan Lubke is a top notch engineer, but did you also know he's a solid technical writer? Ryan has been posting plenty of really useful content on his blog about JSF 2.0, including the series on new features in JSF 2.0. This entry summarizes the series thus far and gives links to each entry.
Part 1: ProjectStage
If you're a fan of Ruby on Rails, and let's face it, who isn't?, this blog entry coves a simple tip-o-the-hat to RoR found in JSF 2.0.
http://blogs.sun.com/rlubke/entry/jsf_2_0_new_feature2
Part 2: Resources in JSF
If you've ever used Shale remoting or weblets with JSF and wished such a feature was in the core spec, your wish has come true. We've also gone a few steps further, thanks to the EG, and added full localization, versioning and libries.
http://blogs.sun.com/rlubke/entry/jsf_2_0_new_feature5
Part 3: The Resources Java API
Once we have you hooked on the idea of resources, and perhaps on our implementation of it in JSF, you might want to go deeper into how it works. Here's your chance.
http://blogs.sun.com/rlubke/entry/jsf_2_0_new_feature
Part 4: Resources from EL
I love this one because it talks about a totally powerful use of the EL: to inline references to resources. You get all the localized, versioned goodness of the resource system, straight from the EL.
http://blogs.sun.com/rlubke/entry/jsf_2_0_new_feature3
Part 5: System Events
The JSF EDR has extended the JSF event system to include a publish/subscribe event bus for application events. This blog entry shows how to use it.
http://blogs.sun.com/rlubke/entry/jsf_2_0_new_feature1
Part 6: Pulling it all together: resource annotations
Now that we've established system events and resources, we have an example that pulls it all together: resource annotations. If you've ever developed a JSF component and wished for a way for that component to declare dependencies on specific JavaScript, CSS or image files, this is the way it works!
http://blogs.sun.com/rlubke/entry/jsf_2_0_new_feature4
I hope you find this content useful, I sure did because it gave me a high level view of the stuff I've been so closely working on for so long.
Technorati Tags: edburns6 Comments
-
-
This blog stuff is all very well, but where is the *real* JSF2.0 design discussion going on? As described here: http://jcp.org/en/jsr/detail?id=314 I have sent an email to the spec lead (you) requesting to "receive email updates" and got no response. I've sent an email to jsr-314-comments@jcp.org and got no response. I have found no trace of a wiki or public email list. There is an email list for mojarra development, but I sure hope that's not where the *specification* is being discussed. The "monitored forum" for this project is full of newbie questions about JSF, and is not useful for any specification-related discussion. I have seen the bugtracker for this project. Ok, that's a start. But it's not a great format for discussions. And there appears to be no way to search it, or to receive notifications of issue creation/modification. Commenting on blog sites doesn't seem to be the right approach for specification development. What *is* the way to see what is happening in this project, and get involved? //
-
-
Thank you very much for your prompt and informative reply. EB> It appears you are active in the MyFaces Tomahawk project, and appear to EB> be on the PMC for the Apache Commons project. I'm also on the MyFaces PMC, an active contributor to the MyFaces JSF1.1/1.2 implementation and an ASF member (though am speaking only for myself here). And am employed to develop JSF applications all day. So I have a definite interest in a quality JSF2.0 specification, and hopefully have something to contribute - if the JCP process makes that possible. EB> As a corporate entity member of JCP, Martin is entitled to share EG EB> private communications with others within that same corporate entity. Unfortunately, as an open source community, we Apache people do not just want *access* to secret information for ourselves. We want that information to be freely available. So this option is IMO not acceptable. And if this information were available on an ASF-only group, then it is very likely that someone would simply republish it in public; we have no interest in preserving technical secrets. I fail to see why discussions on the specification need to be secret. I will follow this up in a posting on the brand new "JSF2.0 Discussion" thread in the forum.. We do seem to have an internal lack of communication from Martin to the rest of the Apache MyFaces project; I will poke him a little :-) EB> Unfortunately, there is no way for me to add links to the top of the EB> JSR-314 public page. We all understand about limitations like that. But it looks like you can add links to any download you want. So perhaps as a workaround there could be a "download" file that lists these useful resources? The JCP page is the primary result returned for a web search on "jsf 2.0", so it's a shame that it doesn't point to any of the important websites. The wiki doesn't seem terribly useful. Just one page, and last edited in Dec 2007. Do changes to it get posted as an email to the expert group list? If not, then will anyone actually notice if someone modifies it? EB> Thanks for your interest and I hope this hasn't soured your impression EB> of the JSF community beyond repair. The JSF community is bigger than just the JCP Expert Group, or Sun. I still find this JCP process to be unnecessarily closed and secret, and hope to persuade you all to open things up. But I do appreciate the hard work that has gone into JSF2.0 so far, and hope to be able to contribute something. I'll repost the issues I raised in the email to the jsr-314-comments address on the forum or bugtracker. Regards, Simon //
-
As Ed mentioned, this blog will be up this week. I think it'll be a good starting point, and also a good place to keep up-to-date. // -
This will be at http://www.jsfcentral.com, btw. //
392 Guest Jun 26, 2008 11:08 PM