Xalan-j_2_0_1 xerces-1_3_1 and jdom-b6

Question

I know that people have already posted message regarding xalan, xerces compatability
with weblogic 6.0sp1 but all the fixes suggested don't work when I use jdom!
When using JDOM, if i put xerces before the weblogic_sp.jar then Hotspot will
die with the following error when i start using jdom.
# HotSpot Virtual Machine Error, EXCEPTION_ACCESS_VIOLATION
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
# Error ID: 4F533F57494E13120E43505002D4
if I put xerces after weblogic_sp.jar and before weblogic.jar then xalan gets
a method not found error when I try a to execute transform() on a document. Also,
I tried my transformation outside of weblogic and it worked just fine.
here is the exception when i try to do the transform in weblogic
java.lang.NoSuchMethodError
at org.apache.xpath.patterns.NodeTest.execute(NodeTest.java:403)
at org.apache.xpath.axes.PredicatedNodeTest.acceptNode(PredicatedNodeTest.java:388)
at org.apache.xpath.axes.ChildTestIterator.nextNode(ChildTestIterator.java:193)
at org.apache.xalan.templates.ElemForEach.transformSelectedNodes(ElemForEach.java:428)
at org.apache.xalan.templates.ElemApplyTemplates.execute(ElemApplyTemplates.java:193)
at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2202)
at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:739)
at org.apache.xalan.templates.ElemForEach.transformSelectedNodes(ElemForEach.java:498)
at org.apache.xalan.templates.ElemApplyTemplates.execute(ElemApplyTemplates.java:193)
at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2202)
at org.apache.xalan.transformer.TransformerImpl.applyTemplateToNode(TransformerImpl.java:2085)
at org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.java:1219)
at org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:2942)
at java.lang.Thread.run(Thread.java:484)

Answer 1

I could see how that would fail if Weblogic was using the default registry
values of:
DocumentBuilderFactory="weblogic.apache.xerces.jaxp.DocumentBuilderFactoryIm
pl"
SAXParserFactory="weblogic.apache.xerces.jaxp.SAXParserFactoryImpl"
it would find weblogic's internal classes.
But if Weblogic is using an xml registry such as:
DocumentBuilderFactory="org.apache.xerces.jaxp.DocumentBuilderFactoryImpl"
SAXParserFactory="org.apache.xerces.jaxp.SAXParserFactoryImpl"
and was starting with the system property of:
..-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.Transf
ormerFactoryImpl ...
Wouldn't JDOM correctly find the org.apache factories instead?
I seem to be having a very similar problem to yours with 6.0 sp2; I'm not
invoking JDOM directly, but I'm using Syslog from protomatter to handle
logging; and Syslog DOES invoke the new SAXBuilder() that you cite. I'm
using xalan 2.1.0 and xerces 1.3.1 placed after the weblogic jars. I also
get a NoSuchMethodError during the transformer.transform, but the same
document is successfully transformed at the command line
TransformerFactory tFactory = TransformerFactory.newInstance();
String xString = xmlDoc.toString() ;
StringReader xmlReader = new StringReader( xString );
StreamSource streamSource = new StreamSource( xmlReader ) ;
Source stylesheet = tFactory.getAssociatedStylesheet( streamSource,
media, title, charset);
Transformer transformer = tFactory.newTransformer(stylesheet);
StreamResult streamResult = new StreamResult( outWriter ) ;
transformer.transform( new StreamSource( new StringReader( xString ) ),
streamResult ) ;
"Eric Van" <[email protected]> wrote in message
news:[email protected]...
>
FIGURED IT OUT!
The problem is that JDOM's SAXBuilder, when used with weblogic, loadsweblogic's
jaxp sax parser, which for some reason doesn't work if the newest xercesis placed
in the classpath before weblogic_sp.jar.
So, to get around this all you have to do is tell JDOM's SAXBuilder to useanother
parser when you create it, preferable one that WORKS!!
I used the one that comes with xerces
new SAXBuilder("org.apache.xerces.parsers.SAXParser")
and it worked fine.
Hope this helps everyone else out.
"Steve Liles" <[email protected]> wrote:
Eric's solution works great if you can get away with always using a
DOMBuilder.
>>
However, I can't always use a DOMBuilder - I need to use the SAXBuilder
in one particular
case where I need to specify the SystemId dynamically as in:
.. SAXBuilder builder = new SAXBuilder(reader, _systemId); ..
There is no DOMBuilder equivalent. Anyone have any suggestions?
cheers,
Steve Liles
"Eric Van" <[email protected]> wrote:
Looks like if you avoid using the org.jdom.input.SAXBuilder and usethe
org.jdom.input.DOMBuilder
instead that the Hotspot error can be avoided. I have a feeling thatthere
is
something else going on here, but OH WELL, NOW IT WORKS.
"Eric Van" <[email protected]> wrote:
I know that people have already posted message regarding xalan, xerces
compatability
with weblogic 6.0sp1 but all the fixes suggested don't work when I
use
jdom!
When using JDOM, if i put xerces before the weblogic_sp.jar then
Hotspot
will
die with the following error when i start using jdom.
# HotSpot Virtual Machine Error, EXCEPTION_ACCESS_VIOLATION
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
# Error ID: 4F533F57494E13120E43505002D4
if I put xerces after weblogic_sp.jar and before weblogic.jar thenxalan
gets
a method not found error when I try a to execute transform() on a
document.
Also,
I tried my transformation outside of weblogic and it worked just fine.
here is the exception when i try to do the transform in weblogic
java.lang.NoSuchMethodError
atorg.apache.xpath.patterns.NodeTest.execute(NodeTest.java:403)
atorg.apache.xpath.axes.PredicatedNodeTest.acceptNode(PredicatedNodeTest.java:
388)
atorg.apache.xpath.axes.ChildTestIterator.nextNode(ChildTestIterator.java:193)
atorg.apache.xalan.templates.ElemForEach.transformSelectedNodes(ElemForEach.ja
va:428)
atorg.apache.xalan.templates.ElemApplyTemplates.execute(ElemApplyTemplates.jav
a:193)
atorg.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform
erImpl.java:2202)
atorg.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:
739)
atorg.apache.xalan.templates.ElemForEach.transformSelectedNodes(ElemForEach.ja
va:498)
atorg.apache.xalan.templates.ElemApplyTemplates.execute(ElemApplyTemplates.jav
a:193)
atorg.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform
erImpl.java:2202)
atorg.apache.xalan.transformer.TransformerImpl.applyTemplateToNode(Transformer
Impl.java:2085)
atorg.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.j
ava:1219)
atorg.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:2942)
at java.lang.Thread.run(Thread.java:484)