[
https://issues.jboss.org/browse/WFLY-976?page=com.atlassian.jira.plugin.s...
]
Glenn Kastrinos commented on WFLY-976:
--------------------------------------
I did deploy the .cli and can see in my wildfly directory that myfaces has been laced
throughout the modules via a .cli, however if I don't have the libraries in the /lib,
it errors out saying they can't be found. It first threw:
JBAS018733: Failed to process phase INSTALL of deployment "Localization.war"
...
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException:
java.lang.ClassNotFoundException: javax.faces.webapp.FacesServlet
so I added the myfaces bundle-2.1.11, but then it errored out asking for the collections
predicate, after I added collections-3.2, then it goes a little farther and needs the
digester. When I finally add all the things it asks for (getting farther in the deployment
process everytime) it goes back to the original error:
WeldApplicationFactory is no javax.faces.application.ApplicationFactory.
I'll remove the current war and upload mine without the libraries. If it works on
yours then it must be something with my AS even though I deployed the .cli? Could using XP
have any impact? Thank you
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, Localization.war, Localization.war
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