Here's some verbose output from java on the attempt to start Orion:
[Loaded org.apache.crimson.tree.DomEx]
[Loaded org.w3c.dom.DocumentType]
[Loaded org.apache.crimson.tree.XmlWriteContext]
[Loaded org.apache.crimson.tree.XmlDocument$ExtWriteContext]
[Loaded org.w3c.dom.ProcessingInstruction]
[Loaded org.apache.crimson.tree.PINode]
[Loaded org.w3c.dom.EntityReference]
[Loaded org.apache.crimson.tree.XmlDocument$EntityRefNode]
[Loaded org.w3c.dom.DocumentFragment]
[Loaded org.apache.crimson.tree.XmlDocument$DocFragNode]
[Loaded org.w3c.dom.Comment]
[Loaded org.apache.crimson.tree.CommentNode]
[Loaded org.w3c.dom.CDATASection]
[Loaded org.apache.crimson.tree.CDataNode]
[Loaded org.w3c.dom.Attr]
[Loaded org.apache.crimson.tree.AttributeNode]
[Loaded org.apache.crimson.tree.XmlDocument$Catalog]
[Loaded org.apache.crimson.tree.DataNode$NodeListImpl]
[Loaded org.apache.crimson.util.XmlChars]
[Loaded org.w3c.dom.DOMImplementation]
[Loaded org.apache.crimson.tree.DOMImplementationImpl]
[Loaded org.apache.crimson.tree.Doctype]
[Loaded org.w3c.dom.NamedNodeMap]
[Loaded org.w3c.dom.Notation]
[Loaded org.apache.crimson.tree.Doctype$NotationNode]
[Loaded org.w3c.dom.Entity]
[Loaded org.apache.crimson.tree.Doctype$EntityNode]
[Loaded org.apache.crimson.tree.Doctype$Nodemap]
[Loaded org.apache.crimson.tree.AttributeSet]
[Loaded java.lang.IncompatibleClassChangeError from C:\Program
Files\JavaSoft\JR
E\1.3\lib\rt.jar]
[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)
at
org.apache.crimson.tree.XmlDocumentBuilder.startElement(XmlDocumentBu
ilder.java:463)
at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1449)
at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:499)
at org.apache.crimson.parser.Parser2.parse(Parser2.java:304)
at
org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
at
org.apache.crimson.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl
.java:179)
at com.evermind.xml.e.getJavaxDocument(JAX)
at com.evermind.xml.XMLUtils.getDocument(JAX)
at com.evermind.xml.XMLConfig.ay(JAX)
at com.evermind.xml.XMLConfig.ay(JAX)
at com.evermind.server.hg.run(JAX)
at java.lang.Thread.run(Unknown Source)
at com.evermind.util.f.run(JAX)
[Loaded java.lang.Shutdown$Lock from C:\Program
Files\JavaSoft\JRE\1.3\lib\rt.ja
r]
Thanks 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
>
>
