[
https://issues.jboss.org/browse/RFPL-1494?page=com.atlassian.jira.plugin....
]
Ján Jamrich commented on RFPL-1494:
-----------------------------------
Since richfaces-3.3.1.SP3 are not supposed to be run on JSF2, the valid way how to get
them working on AS7 are following steps (to activate JSF1.2 slot with RF-3.3.1.SP3 based
application):
1. remove jboss-web.xml from WEB-INF lib
2. add jboss-deployment-structure.xml int WEB-INF lib with following configuration:
<jboss-deployment-structure>
<deployment>
<exclusions>
<module name="javax.faces.api" slot="main"/>
<module name="com.sun.jsf-impl" slot="main"/>
</exclusions>
<dependencies>
<module name="javax.faces.api" slot="1.2"/>
<module name="com.sun.jsf-impl" slot="1.2"/>
</dependencies>
</deployment>
</jboss-deployment-structure>
Configuration is quite self-explaining since in javax.faces.api module are slots
"main" and "1.2" and for com.sun.jsf-impl the same.
See
https://docs.jboss.org/author/display/AS7/How+do+I+migrate+my+application...
for more information about how to manage slot in AS7
Test deployment, and execution of RichFaces 3.3.1.SP3 component demo
on the latest release of AS7
-------------------------------------------------------------------------------------------------
Key: RFPL-1494
URL:
https://issues.jboss.org/browse/RFPL-1494
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: examples, QE
Reporter: Jay Balunas
Assignee: Ján Jamrich
Priority: Critical
Fix For: 4.1.0.Milestone2
We need to test what issue come up when deploying a 3.3.1.SP3 version of the component
demo to AS7. Since AS7 only ships with JSF2, and RichFaces 3.3.1 has known issues with
JSF 2 we do not expect this to be clean. However we need to make sure to understand where
we stand with this.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira