[jboss-user] [JBoss Seam] - Re: Deploying seam app along side standard jsf app problem
In case anyone has the same problem, I couldn't come up with a proper solution so have had to hack one in. A sort of if you can't beat em join em answer. I still don't know if the problem is happening because of a bug or feature. I had to wire Seam into the JSF app, so the web.xml had the following added to it. listener-classorg.jboss.seam.servlet.SeamListener/listener-class and the faces-config.xml file had the following added. phase-listenerorg.jboss.seam.jsf.SeamPhaseListener/phase-listener just like a regular Seam project. So far everything in the JSF app still works and hopefully will stay that way. Thank you for all the replies. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4039822#4039822 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4039822 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Deploying seam app along side standard jsf app problem
From http://wiki.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration anonymous wrote : | With nested modules, only the top level file may specify class loader scoping. If you have a .ear file containing other modules, only scoping specified in the .ear's META-INF/jboss-app.xml is used. This also applies for any other deployment which contains sub-deployments. For example, if a .sar contains a .war deployment, only the .sar META-INF/jboss-service.xml scoping has effect. | I took this as meaning that if you specify a loader at the ear level, any loader specified in a nested war or sar will be ignored. If you specified the loader in jboss-app, then all of contents of the ear should be loaded within the same classloader. You can see what jars are loaded within your specified classloader by checking the jmx-console; just search for your unique-archive-name. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4038880#4038880 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038880 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Deploying seam app along side standard jsf app problem
Thank you for that. I read the same thing and was trying to set the classloading in the war files as a desperate measure. Upon startup I get warnings saying that JBoss is going to ignore the loader in the war files because only the root deployment can set it. It must be a classloading issue I just don't know a way around it. I tried removing the seam jar from the application.xml file hoping this would stop the jar from being seen by all the components. That worked and of course stopped the seam app from working as well. I then set the Class-Path in the MANIFEST.MF file of the Seam EJB jar which brought up the same problem again. It looks like adding the jar to any artifacts classpath makes it visible to all. I don't know of any way in a jar/war to say exclude from class path (of course thats assuming that it would solve the problem). View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4038935#4038935 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038935 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Deploying seam app along side standard jsf app problem
Thank you for the quick responses. It looks like classpath isolation can only be done per deployment, the ear file in my case which contains both the wars. I don't know if this means that each war file in the ear will use classpath isolation or just the ear file as a whole will be isolated from other deployments. Anyway I tried setting the isolation level at both the ear and war level (just in case) but still end up with the same problem. I have never done it before so hopefully I set it up correctly by placing jboss-app.xml in the META-INF directory of the ear with the following content jboss-app loader-repository com.example:loader=unique-archive-name /loader-repository /jboss-app And placed a jboss-web.xml file in the WEB-INF directory of both my wars with the following content. jboss-web class-loading loader-repository com.example:loader=unique-archive-name /loader-repository /class-loading /jboss-web Please let me know if you have any other ideas, I am trying to avoid deploying them separately. Thanks again. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4038346#4038346 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038346 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Deploying seam app along side standard jsf app problem
Make sure you have classloading isolation set up for both apps View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4038065#4038065 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038065 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
