Bring out your JSF Extensions
In order to solve issue [
rel="nofollow" target="_top">121-JarOrdering], EG member Alexander
Smirnov from Exadel suggested we research the current practice of how
JSF extension points are used.
If you’re reading my blog, it’s likely you are a computer
professional, so you know how error-prone large scale software systems
can be. (You also know they are less-error prone if they are built with
:^)) There have been many stories in reputable news
sources regarding apparently error-prone purges of voter registration
roles in the U.S..
I discovered that Vanguard is using JSF via Backbase
When signing up for paperless statements on my 401(k), I stumbled
upon another JSF user: The Vanguard Group.
At JSFOne, someone suggested modifying the navigation rule system such
that if the to-view-id is absent from a navigation-case, the to-view-id
value be inferred from the outcome.
This would mean the following is valid:
The JSF Expert Group has just released another draft of the JSF 2.0
Draft Review 2. There are many new features in this draft,
including early implementations of composite components and Ajax.
Please read the preface of the spec prose document to see the list
I received a tip from
that Apple is using JSF for its online rebate site, which you can see at
A quick View Source shows the presence of our javax.faces.ViewState
Our current schedule for JSF 2.0 has us handing off the spec
artifacts to the JCP on 15 December 2008. That’s 62 business days
One of the worst things about Java is the lack of a language level
solution to the href="http://en.wikipedia.org/wiki/Fragile_base_class_problem">fragile
base class problem. In the absence of a solution, the JSF EG has
resorted to creating subclasses of interfaces, appending a digit to the
interface name, and adding the methods there.
We had an expert group meeting for JSR-314-EG today.