Skip to main content

Blog Archive for edburns during September 2008

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. I see that they're using JSF via Backbase on their paperless signup page at: <https://personal.vanguard.com/us/JSP/RegLogOn/Regis/RegActivityContent.jsf>. I've added them to the RealWorldJSFLinks wiki at <http://wiki.java.net/...
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: <pre>&lt;navigation-rule&gt;     &lt;from-view-id&gt;/pages/inputname.jsp&lt;/from-view-id&gt;     &lt;navigation-...
The JSF Expert Group has just released another draft of the JSF 2.0 specification, Early 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 changes. This draft of the specification is fully implemented (though the TCK is not yet finished) and can be...
I received a tip from Matthias Weflendorf that Apple is using JSF for its online rebate site, which you can see at <https://rebate.apple.com/art-web/pages/newAccountCreationPage.faces>. A quick View Source shows the presence of our javax.faces.ViewState hidden field. Inspection of the value of that field leads me to believe they are using Mojarra, but I am not certain. If someone can...
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 from today. We have 37 open spec issues, not including some ones floating around on the EG list that I need to put into the issue tracker. Of those 37, there are 20 that I’ve classified as “hard”, with help from FOJSF Yara Senger. If you care...
One of the worst things about Java is the lack of a language level solution to the 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. For example, we created <ahref="http://java.sun.com/javaee/javaserverfaces/1.2_MR1/docs/api/javax/faces/component/...