To: Orion-Interest
Subject: RE: JAXP
Have you try to package your version of JAXP files inside your application
archive (ear, war)? This idea comes from the fact that every class is
identified not only its class name but also which class loader it is loaded
from. Since Orion supports dynamic
Have you try to package your version of JAXP files inside your application
archive (ear, war)? This idea comes from the fact that every class is
identified not only its class name but also which class loader it is loaded
from. Since Orion supports dynamic loading of application files, it should
Richard Doust schrieb:
have tried replacing the older ones with the newer ones because my code
Hi Richard,
to me it seems that what You do makes perfect sense and that Orion *must
not* impose any restriction on which libraries/versions You are going to
use in your EJB code.
That Orion uses
Hi Rich,
Could you narrow it down? Specifically which JAR breaks Orion. We have replaced
the xalan.jar and xerces.jar files with version 1.2.2 and Orion is happy. Is it
just the jaxp.jar file that is the issue?
Also, I believe that somewhere in the mailing list archives, you will find posts
Sent: Friday, February 23, 2001 8:33 PM
To: Orion-Interest
Subject: Re: JAXP
Hi Rich,
Could you narrow it down? Specifically which JAR breaks Orion. We have
replaced
the xalan.jar and xerces.jar files with version 1.2.2 and Orion is happy. Is
it
just the jaxp.jar file that is the issue?
Also, I
-Interest
Subject: Re: JAXP
Hi Rich,
Could you narrow it down? Specifically which JAR breaks Orion. We have
replaced
the xalan.jar and xerces.jar files with version 1.2.2 and Orion is happy. Is
it
just the jaxp.jar file that is the issue?
Also, I believe that somewhere in the mailing list
[Loaded java.lang.NoSuchMethodError from C:\Program
Files\JavaSoft\JRE\1.3\lib\r
t.jar]
java.lang.NoSuchMethodError
at
org.apache.crimson.tree.AttributeSet.init(AttributeSet.java:139)
Richard, do you have the source code for that line it is croaking on?
tim.
