[
https://issues.jboss.org/browse/AS7-6790?page=com.atlassian.jira.plugin.s...
]
Stan Silvert updated AS7-6790:
------------------------------
Git Pull Request:
https://github.com/jbossas/jboss-as/pull/4425
Instead of installing JSF impls wherever you wish, it is recommended that you install into
the root of the modules directory. However, if you do this then "main", which
ships with AS, will no longer get added as a valid JSF configuration.
Submitted
https://github.com/jbossas/jboss-as/pull/4425 to make sure that "main"
is always one of the valid JSF impl slots.
A couple of updates are needed to the tool that creates the *.cli JSF impl install files.
But since that tool is not part of the AS code base, I'm going to go ahead and close
this jira once the PR is merged.
Multi-JSF doesn't understand new modules structure
--------------------------------------------------
Key: AS7-6790
URL:
https://issues.jboss.org/browse/AS7-6790
Project: Application Server 7
Issue Type: Bug
Components: JSF
Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
Reporter: Stan Silvert
Assignee: Stan Silvert
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