[ https://issues.jboss.org/browse/AS7-3940?page=com.atlassian.jira.plugin.s... ] David Lloyd updated AS7-3940: ----------------------------- Assignee: Stan Silvert Component/s: JSF (was: Web) The alternative implementation in the deployment should either be completely used or completely ignored. Throwing errors is not an ideal outcome. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-3940?page=com.atlassian.jira.plugin.s... ] Oleg Varaksin commented on AS7-3940: ------------------------------------ This is a "must to have" issue. The most important one in my opinion. Stick with Mojarra is not quite nice because last Mojarra impl. has huge performance problems. E.g. this one http://java.net/jira/browse/JAVASERVERFACES-2334 I know many people (incl. me and my company) looking for a possiblity to add MyFaces as JSF-impl. to JBoss 7.1.1 final. Please take a look into this issue! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-3940?page=com.atlassian.jira.plugin.s... ] Karsten Wutzke commented on AS7-3940: ------------------------------------- Ugh. I don't even manage to exchange Mojarra 2.1.7 with Mojarra 2.1.9 because of that. Too bad to hear there's no way to get MyFaces to work on JBAS 7. Plus noting that the JBAS 7.1.2 community version will not be released to the public (at least in binary) is another problem. We'd have to wait until mid July to get our hands on JBAS 7.2.0.Alpha and a newer integrated JSF version. We have to wait too long to try other JSF versions IMO. Big problem. It should be possible to install/use any JSF version - including JSF 2.2 - on JBAS ASAP. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-3940?page=com.atlassian.jira.plugin.s... ] Stuart Douglas commented on AS7-3940: ------------------------------------- I think the best way to fix this is to move the JSF service provider files to their own module. This can then be excluded automatically when WAR_BUNDLES_JSF is specified. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-3940?page=com.atlassian.jira.plugin.s... ] Stuart Douglas edited comment on AS7-3940 at 6/30/12 10:28 PM: --------------------------------------------------------------- I have submitted a PR that breaks JSF off into its own subsystem. When the version is set to WAR_BUNDLES_JSF_IMPL no JSF classes or META-INF/services entries should be exposed to the deployment. This means it is now possible to completely remove JSF from the configuration, or exlucde it via jboss-deployment-structure.xml: {code:xml} <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> <deployment> <exclude-subsystems> <subsystem name="ejb3" /> </exclude-subsystems> </deployment> </jboss-deployment-structure> {code} This also opens the possibility of providing a myfaces subsystem (probably as a 3rd party project) that will allow people to use myfaces with full container integration. was (Author: swd847): I have submitted a PR that breaks JSF off into its own subsystem. When the version is set to WAR_BUNDLES_JSF_IMPL no JSF classes or META-INF/services entries should be exposed to the deployment. This means it is now possible to completely remove JSF from the configuration, or exlucde it via jboss-deployment-structure.xml: {code|XML} <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> <deployment> <exclude-subsystems> <subsystem name="ejb3" /> </exclude-subsystems> </deployment> </jboss-deployment-structure> {code} This also opens the possibility of providing a myfaces subsystem (probably as a 3rd party project) that will allow people to use myfaces with full container integration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-3940?page=com.atlassian.jira.plugin.s... ] Stuart Douglas updated AS7-3940: -------------------------------- Fix Version/s: 7.1.3.Final (EAP) 7.2.0.Alpha1 (was: Open To Community) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-3940?page=com.atlassian.jira.plugin.s... ] Serge Emmanuel Pagop commented on AS7-3940: ------------------------------------------- I love the agile mind and open choice, customers will love that . Thanks Stuart! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira