Skip to main content

Add Your JSF 2 Content to Sun Java Certification Exam

Posted by edburns on December 18, 2009 at 7:44 AM PST

In November, Servlet 3.0
Specification Lead Rajiv Mordani
, and I started providing technical
advice to the team at Sun developing the successor to the href="">Sun

Certified Web Component (SCWD) certification exam. This new exam
covers Java EE 6, including JSF 2. All this week, the work will
continue in the form of an offsite workshop at href="">the

To help ensure the highest quality exam possible (and thus make the
certification as href="">meaningful as
possible), I'm asking you to post comments on this blog about what
you think should be in the exam. I'll be href="">tweeting from the event all week
and continually monitoring the comments.

Thanks for your help!

Technorati Tags:



YOU GUYS REALLY DO NEED TO DO SOMETHING ABOUT THE DOCUMENTATION FOR JSF. AND I'M NOT TALKING ABOUT JAVADOCS. I'M TALKING ABOUT DOCUMENTATION THAT EXPLAINS HOW TO USE IT. For example, how to port a pre-JSF 2.0 custom component that uses JSP to JSF 2.0 with Facelets. Unless I'm missing something, the current documentation flat out sucks and is basically non-existent. Unless you have good documentation to go along with it, it doesn't matter how much you improve JSF. People are not going to use it. You need to do something about the web site also. Will you at least fix the idiotic fact that you have the content mixed between HTTP and HTTPS so that it doesn't prompt on every damn page whether you want to load everything? The site has been doggedly slow from day one and something needs to be done about it. Everytime I come to this site, it just frustrates the hell out of me. Furthermore, what's up with the stupid bug tracker. It looks like it's in read-only mode now and you have to request to be able to submit bugs. There are so many bugs that have been out there for years and have never been fixed. The new JSF looks a lot better than the old one, but, again HIRE SOME DOCUMENTATION WRITERS AND PUT UP SOME GOOD DOCUMENTATION.

doc writers

I'm sorry to say that I've seen many doc writers be let go from Sun due to the current economic situation.  I hear that Oracle has more writers.  For what it's worth, I have a book about JSF2 that might answer your questions


Ed Burns JSF spec lead.

JSF 2 Documentation

Looks like it will be available on January 19:

"rendered" and "binding" attributes misunderstanding.

The most popular questions about JSF on forums and support are : 1) unexpected behavior of component that binds "rendered" ( "disabled" ) attribute to a request scope bean that has a different value during render and execute phases. Therefore, JSF does not process these component on form submit. 2) binding component to session/application scope beans that messed up component instances between views and requests. I guess exam has to pay more attention to these cases.

Since JSP is no longer the

Since JSP is no longer the primary PDL/VDL of JSF, I think it needs deemphasized in favor of Facelets. Also, since the Java 6 EE Virtual Conference I've been getting into JAX-RS as a replacement for many of my servlets - ones that generate xls's, iText PDF's, KML's, etc. It seems to be making things much easier and I think it needs included. Personally, since I'm not consulting or looking for a job, you won't see me paying $300 for the Sunacle seal of approval. It's much more economical to spend my time working on my black... err... brown belt. ;)

Since JSP is no longer the

The software applications are developed on platforms like .Net, PHP, Perl, Zend, Python, Silverlight, SharePoint, Ajax and others. The team of development experts work on an application through analysis and evaluation of the exact requirement. They build the plan after consulting the client. They elaborate the strategy before commencing on the software development process. These services develop projects for mobile, desktop and Internet based applications. This allows you to develop projects with far broader reach than your competitors without the need to use multiple developers.