[jboss-jira] [JBoss JIRA] Commented: (JBAS-6638) Move JSF integration into a deployer

Wed May 19 16:17:06 EDT 2010

    [ https://jira.jboss.org/browse/JBAS-6638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12531572#action_12531572 ] 

Stan Silvert commented on JBAS-6638:
------------------------------------

It looks like I've fixed the Seam tests.  The EARs were being bundled with classes that depend on JSF at the EAR level rather than the WAR level.  While I think this is probably wrong, I know that Seam apps have been built like this for a long time.  So for backward compatibility, I've changed the JSF Deployer to add JSF jars to all ancestor deployments of the WAR.  I put out a new snapshot of the JSF Deployer that should get picked up by Hudson soon.

It looks like fixing the Weld failures is going to require some coordination with the Weld deployer.  I'll have to dig further.

> Move JSF integration into a deployer
> ------------------------------------
>
>                 Key: JBAS-6638
>                 URL: https://jira.jboss.org/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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira