I was recently very surprised to find that jars in the JBOSS_DIST/lib are
available on the classloader to WARS (jboss version 4.0.2). Specifically,
dom4j.jar was the culprit in the issue we were tracking down. I have always
worked under the assumption that only jars in
Thanks - that is a great resource.
Brian
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3926215#3926215
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3926215
---
This
Would there be any way to scope the ear with the jboss-app.xml and then somehow make
it's loader repository visible to a WAR with a setting in the jboss-web.xml ? I know
I'm starting to grasp at straws on this - maybe I'm making this more complicated than
it should be
View the original
Thanks for the reply - I actually do have the 'for pay' documentation, but I have not
found it helpful in this instance.
I do want to share resources from my EAR - and that is working well. Currently my
WAR's WEB-INF is isolated and the contents of the EAR is available to the other WARS.
Thanks -
I did try that - both with jboss-app and the jboss-service - and in both instances I
got
2004-10-15 09:56:41,804 ERROR [org.jboss.ejb.StatelessSessionContainer] Initialization
failed jboss.j2ee:jndiName=ejb/service/remote/EmployeeService,service=EJB
java.lang.ClassCastException
I have looked at the Wikis forum on Classloader scoping and cant find an appropriate
solution.
I have an EAR deployed along side a couple WARS. I have UseJBossWebLoader set to
false to keep my WARS seperated. I'm having a problem with the jar's in
jbossweb-tomcat50.sar conflicting with jars
I have an EAR in which I have an application that uses Cayenne. Cayenne needs
commons-collections3.x to work properly. I am deploying the EAR in exploded format.
app.EAR
|
core.jar
|
lib
|
commons-collections-3.1.jar
cayenne-no-deps.jar
Cayenne, however, is
