Tim, Thanks for trying to help. I'll take a look in the mailing list archives. I looked through the first set and didn't find anything, but I can look at older stuff. In the meantime, I'm replacing the jaxp.jar, parser.jar, and xalan.jar that came with Orion (latest version) with crimson.jar, 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. Orion, jdk1.3 and jaxp1.1 each comes with a different version of xalan.jar. Orion and ant come with different versions of parser.jar. (I have all four of these installed.) ant worked okay after replacing its jaxp.jar and parser.jar with jaxp1.1's xalan.jar and crimson.jar. I start Orion with a classpath that includes the crimson.jar and xalan.jar from jaxp 1.1. During the startup, when its trying to parse its config files (I guess) I get a NoSuchMethodError at org.apache.crimson.tree.AttributeSet.<init>(AttributeSet.java:139). I guess I can't tell from this what method it's trying to call. It would be helpful if I could. Somehow, it sounds internal to JAXP, and not like it's really a problem of Orion. Any more ideas now that I've given all these details? Love to hear from you again! Rich -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Tim Endres 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 believe that somewhere in the mailing list archives, you will find posts 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 assumptions on this. > I am trying to develop server side code that runs under Orion that 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 > image as Orion. Orion fails to start due to an exception while trying to > parse its configuration files. Putting the old .jar files back, it works > again. So, now it occurs to me that I'm basically stuck running with > whatever version of support code the tools I'm using are dependent on. > If I'm right, that means I can't use the latest version of JAXP until Orion > does? Is that right? > Anyone? > Thanks, > Rich > >
