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 foll
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
>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. Th
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 fr
Make sure you have classloading isolation set up for both apps
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038065#4038065
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038065
I'd guess that this has to do with the scoping of servlet filters within ears.
If two wars are published within the same ear what happens? I suppose you have
your answer. Don't know if this is a bug or a feature of JEE deployment.
This could also be a scoping problem with the JSF context. Wi