Bugs item #928024, was opened at 2004-04-02 05:30
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=928024&group_id=22866
Category: JBossSOAP
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Jula (julajula)
Assigned to: Nobody/Anonymous (nobody)
Summary: Class Loader Classpath Conflict
Initial Comment:
The JDOM jar which is being used by JBoss is newer to
what is used in my web service. So I explicitly gave the
following command to avoid looking at the 3.2.2 servers
jar.
<jboss-web>
<class-loading java2ClassLoadingCompliance="false">
<loader-repository>
jboss.test:war=oldxerces.war
<loader-repository-config>
java2ParentDelegation=false
</loader-repository-config>
</loader-repository>
</class-loading>
</jboss-web>
It solved JDOM error but now I get another error. The
stack trace is attached here with.
I am simply trying to use FOP to generate a PDF using
the fop.jar, batik.jar, xalan-2.4.1.jar components in
addition to using JDOM. These 4 jars are inside my EAR.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=928024&group_id=22866
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
