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 > >
