Hi,
I really need help on that question.
Does any one has experience on having a JAXP 1.0 application running on
Orion?
Thanks in advance
Etienne
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Etienne
Giraudy
Sent: vendredi 7 decembre 2001 08
I searched the list, and people have experienced this problem (like myself),
but no word from Orion. Ideas?
If you try to get Orion working with this latest release from Sun, Orion
won't
start:
G:\orionjava -jar orion.jar
java.lang.NoSuchMethodError
at
I did enter a request for support of JAXP 1.1 in Bugzilla yesterday (ID
369).
Magnus Stenman declared it soon thereafter as an invalid request as their
latest internal builds already use JAXP 1.1.
It will be released with the next version (1.4.8).
Karl Avedal mailed me yesterday that this release
orion.jar's classpath manifest attribute) will be used. Even if you
create a lib entry to jaxp in server.xml or orion-application.xml the jxap
that ships with orion will be used.
Andre
-Original Message-
From: Conrad Chan [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 27, 2001 4:25 PM
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
the
JAXP code that Sun has recently released. There are different versions of
parser.jar, xalan.jar and jaxp.jar distributed with Orion. Older ones. I
have tried replacing the older ones with the newer ones because my code
requires the newer ones and I guess that my code will be running in the same
related to JAXP, but I do not know if they will address your specific question.
tim.
I have been working on this problem all day. I have posted once before and
no one responded. I will try again.
I'm no Java expert and this is just my ignorance, but can anyone tell me if
I'm correct in my
, jaxp.jar and xalan.jar
from JAXP 1.1. After a thorough analysis of these jar files, I found that
xalan.jar and crimson.jar have most of what jaxp.jar and parser.jar have
plus a lot more.
One of the problems I have is that ant, jdk1.3, orion, and jaxp1.1 each come
with a different version of jaxp.jar
-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.
11 matches
Mail list logo