Log In | Sign Up   View a printable version of the current page.
  Dashboard > [fleXive] > ... > Developer Info > JSF2 development status

Added by Daniel Lichtenberger, last edited by Daniel Lichtenberger on Jul 30, 2010  (view change)
Labels: 
(None)

JSF2 development status

JSF2 compatibility

Flexive 3.1.0+ is compatible with JSF 2.0, i.e. it works with JSF2, but still uses the Facelets 1.x implementation. This means that you cannot use the new JSF2 templating features (f:ajax, ...).

JSF2 native support

Release 3.1.4 contains an initial set of JSF2 components (most code is actually shared with the JSF1 components, so the attributes and functionality is almost completely the same).

When you use Maven, you can decide whether to use the new flexive-plugin-jsf2-core artifact or the JSF1 components. Note that you currently cannot use the backend in a JSF2 EAR due to packaging issues. For an example check src/examples/jsf2-test from trunk:

svn co http://svn.flexive.org/repository/flexive/trunk/src/examples/jsf2-test
  • Basic components that should work in 3.1.4+:
    • fx:content
    • fx:contentList
    • fx:fxValueInput
    • fx:includes
    • fx:navigation
    • fx:resultValue
    • fx:yuiSetup (no longer required)
  • JSF2 components cannot use JSF1.x libraries. I.e. no Tomahawk file upload at the moment.
  • We cannot use the templated components from the JSF1 library. This means that the following components will not be available for some time:
    • fx:contentEditor
    • fx:queryEditor
    • And some minor components, like fx:formRow or fx:fieldSet.

Also on the TODO list is the support of client behaviours, e.g. supporting the f:ajax tag in our input component (bug FX-934).

Site running on a free Atlassian Confluence Open Source Project License granted to [fleXive] . Evaluate Confluence today.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.6.1 Build:#916 Nov 09, 2007) - Bug/feature request - Contact Administrators