JSF 2.0 aims to improve the JavaServer Faces framework by focusing on four main goals: 1) introducing a new page declaration language called Facelets, 2) making custom component development easier, 3) adding support for Ajax interactions, and 4) reducing configuration requirements. Key changes include support for annotations to replace XML configuration, and new tags and APIs to enable Ajax functionality without JavaScript. The specification was developed based on feedback from the JSF community.
2. JSF 2.0 – What We Heard
• Top Goals
1)Page Declaration Language (PDL)
2)Make custom components much easier to develop
3)Ajax Support
4)Reduce the configuration burden
3. Page Declaration Language
• Based on Facelets
• Facelets:
> first non-JSP PDL designed for JSF
> Some differences from JSP:
> Pages compiled to abstract structure - when executed builds
JSF component view
> Don't need TLD for tag attributes
> Page templating
9. Ajax Support
• JavaScript namespace registered with OpenAjax
• JavaScript API for performing Ajax interations with
JSF
> collecting/encoding view state
> sending requests
> processing Ajax response and Dom updates
10. Ajax Support
Ajaxification Capability
• A way to give ajax capability to existing JSF
components without writing any JavaScript
• Specification will define core tag
<h:commandButton value=”submit”>
<f:ajaxRequest render=”myOutput” />
</h:commandButton>
...
<h:outputText id=”myOutput” />
11. Reduce Configuration Burden
Annotation Support
• An alternative to XML configuration
• @FacesComponent, @FacesConverter, @ManagedBean
• “Scope” Annotations:
> @RequestScope, @SessionScope, @ApplicationScope
12. Summary
• Collected feedback from community and EG members
• Defined top goals for specification
• Diverse set of EG members