I am running up against this issue as well. Did you determine if this is the
only workaround for jboss 4.0.3?
With classloader logging and JMX inspection, I can see that it will load a
dom4j jar stashed in the WAR (only, however, if it appears in the manifest
class-path). However it seems
I did not find a work-a-round that I felt comfortable with, so we, and our
customers, will not upgrade to the new version of JBoss. Instead we will be
moving on to Geronimo.
I have for a long time been very unhappy with the less than logical class
loader system in JBoss, but this was the last
I am having the exact same problem. I am trying to upgrade from 4.0.1 to 4.0.3
but this is kinda holding me back.
Anyone has a solution for this?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3937899#3937899
Reply to the post :
130g wrote : I am having the exact same problem. I am trying to upgrade from
4.0.1 to 4.0.3 but this is kinda holding me back.
| Anyone has a solution for this?
See technically dom4j is a platform required jar and as such this behavior
really doesn't violate the J2EE spec. With that said,
Anybody?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3937695#3937695
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3937695
---
This SF.Net email is sponsored by xPML,
