[
https://issues.jboss.org/browse/WFLY-976?page=com.atlassian.jira.plugin.s...
]
Stan Silvert commented on WFLY-976:
-----------------------------------
I've attached the CLI install file for WildFly Alpha1 and MyFaces 2.1.11. Here are
detailed instructions:
Download or build the latest AS8/WildFly
Copy install-myfaces-2.1.11.cli to wildfly-8.0.0.Alpha1-SNAPSHOT/bin
start AS8/WildFly
cd to wildfly-8.0.0.Alpha1-SNAPSHOT/bin
run cli and do these two commands:
[standalone@localhost:9999 /] deploy install-myfaces-2.1.11.cli
[standalone@localhost:9999 /]
/subsystem=jsf/:write-attribute(name=default-jsf-impl-slot,value=myfaces-2.1.11)
Edit modules/system/layers/base/org/jboss/weld/core/main/modules.xml and change the JSF
API slot to MyFaces:
<module name="javax.faces.api" slot="myfaces-2.1.11"/>
Do the same for modules/system/layers/base/org/jboss/as/weld/main/modules.xml
restart AS8/WildFly
Let me know how it goes!
Multi-JSF doesn't understand new modules structure
--------------------------------------------------
Key: WFLY-976
URL:
https://issues.jboss.org/browse/WFLY-976
Project: WildFly
Issue Type: Bug
Components: JSF
Reporter: Stan Silvert
Assignee: Stan Silvert
Attachments: install-myfaces-2.1.11.cli
With the new modules structure, Multi-JSF is looking for JSF implementations in the root
of the modules directory instead of in modules/system/layers/base. The reason is that
Multi-JSF relies on the module.path property which points to the root by default.
The workaround is to go ahead and install the new JSF impl wherever you wish and add that
directory to JBOSS_MODULEPATH in the startup script.
See
https://community.jboss.org/wiki/DesignOfAS7Multi-JSFFeature#comment-11789
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira