Marius Bogoevici wrote:
Hi Robert,
Thanks for using AS6 and sorry for missing this question.
You're not doing the Spring integration incorrectly, but due to the way the JSF integration works, it's relatively hard (if not impossible) to use the deployer (which adds the JSF API+implementation classes at the WAR level) and use shared JSF utility classes (which load in the global classloader).
You have a few options:
1. disable the deployer *and* share the JSF API+Implementation classes globally (as Ales says)
2. Keep the current structure and include only the Spring JSF classes in your deployment (not shared)
3. Use your own JSF implementation bundled in the WAR as shown here: http://docs.jboss.org/jbossas/6/JSF_Guide/en-US/html/jsf.deployer.config.html#bundling.jsf.with.war
Option #4 is in the JSF Deployer documentation that you reference in #3 above. Instead of bundling JSF with your WAR, look at sections 3.7 and 3.8 of that document. This describes a feature where you create your own JSF configuration. You can include any combination of JSF implementation and supporting libraries in that configuration. Note that the JSF configuration contains its own "shared" web.xml that allows you to configure these libraries. Then when you are done with the configuration you use a setting in the application's web.xml to tell that JSF Deployer that you want to use that configuration.
I don't know the particulars of the libraries you are trying to use, but it sounds to me like option #4 might be exactly what you are trying to do. It makes the JSF configuration look like it would if you bundled it with each WAR.
Stan