It's been a couple days and the odds are you've figured it out already, but
since no one has responded I'll take the chance that it is still hanging.
You need to override the default classloading behavior for jboss, which
essentially means you have to define a classloader for your ear. Rather than
cut and paste the whoel thing, here are a couple of links that explain it:
Check for the section isolation w/server override.
http://www.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration
Here's one on Raible's site. He hits so much of this kind of thing with app
fuse, I've always found it's a good idea to search his entries early on in any
sort of issue like this because he very often hits it early and is good about
posting fixes and links to fixes.
http://raibledesigns.com/rd/entry/jboss_classloader_logic
hth,
gn
---- Edward Sumerfield <esumerfd@xxxxxxxxxxxxxx> wrote:
> I am using jdom in my app and have the 1.0 jar declared as a common
> jar in application.xml
>
> JDom is dependent on jaxen.jar which is delivered as a jboss jar
> already in server/default/lib.
>
> So when the Jaxen code does an instanceof org.jdom.Document it fails
> with class loader problems.
>
> Is there a simple anwser to this? Anything shipped with JBoss in the
> server/default/lib is likely to cause me problems right?
>
> --
> Ed
>
> ---------
> You may unsubscribe from this mailing list
> by sending a blank email addressed to:
> users-unsubscribe@xxxxxxxxxx
>
> --
> Find additional help by sending a blank email
> addressed to:
> users-help@xxxxxxxxxx
>
|