[
https://jira.jboss.org/jira/browse/JBAS-6638?page=com.atlassian.jira.plug...
]
Stan Silvert commented on JBAS-6638:
------------------------------------
The JSFDeployer provides a comprehensive solution to several issues we've had with
previous releases.
* Non-JSF applications will no longer have JSF jars in the classpath and will no longer
run any part of the JBossJSFConfigureListener.
* JSF declarations will be moved out of the shared web.xml in jbossweb.deployer.
* You can easily upgrade to a newer JSF version and assign as the default JSF
implementation.
* You can create JSF configurations including its own component libraries, listeners,
servlets, and context params.
* Each JSF configuration can be individually assigned to one or more WARs.
* We will have the option of shipping more than one JSF implementation with AS. This
includes not only multiple versions, but multiple implementations (i.e. both Mojarra and
MyFaces) if desired.
Move JSF integration into a deployer
------------------------------------
Key: JBAS-6638
URL:
https://jira.jboss.org/jira/browse/JBAS-6638
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: JSF
Affects Versions: JBossAS-5.1.0.Beta1
Reporter: Stan Silvert
Assignee: Stan Silvert
Fix For: 6.0.0.M4
We need to create a JSF Deployer to replace the current JSF integration code. This will
allow different versions of JSF to run for different web apps. It will also allow any web
app to use the WAR_BUNDLES_JSF_IMPL flag. Previously, this only worked if you were
bundling MyFaces 1.1.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira