Configuring Xerces 1.4.1 in WL 6.0SP2

Question

Greetings.
We have developed a pilot application to get familiar with WebLogic. We
need to validate XML input and output against .xsd schemas. I have this
working for the DOM parser but the SAX parser (which we use to validate
the XML string before sending back to the client) is not working. It
seems like WebLogic is not finding the implementation class. Here's the
stack trace:
java.lang.AbstractMethodError
at javax.xml.parsers.SAXParser.parse(SAXParser.java:367)
at net.verizon.xml.XMLHelper.validate(XMLHelper.java:178)
at net.verizon.xml.XMLHelper.stringValue(XMLHelper.java:154)
at
net.verizon.xml.DescriptorHelper.stringValue(DescriptorHelper.java:99)
at
net.verizon.xml.DocumentDescriptor.toXML(DocumentDescriptor.java:44)
at net.verizon.pilot.Gateway.processRequest(Gateway.java:126)
I have the XML Registry set for both DOM and SAX to use the Xerces
package which I included first in the classpath.
The SAXParserFactory is set
to: org.apache.xerces.jaxp.SAXParserFactoryImpl
Perhaps this is incorrect...
Ed

Answer 1

Charlie,
I appreciate your response, but there must be something else. I tried
adding the definition for Syslog to my startup but no change. I don't use the
transforms so I didn't define that. Here's my startup:
CLASSPATH=$USER_LIB/xerces.jar
CLASSPATH=$CLASSPATH:$WL_HOME:$WL_HOME/lib/weblogic_sp.jar:$WL_HOME/lib/weblogic.jar
CLASSPATH=$CLASSPATH:$USER_LIB/classes12.zip:$USER_LIB:
PATH=$WL_HOME/bin:$JAVA_HOME/jre/bin:$JAVA_HOME/bin:$PATH
java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=myDomain
-Dweblogic.Name=adminServer -Dbea.home=$BEA_HOME
-Djava.security.policy==$WL_HOME/lib/weblogic.policy
-Dweblogic.management.password=weblogic
-DSyslog.xml.parser=org.apache.xerces.parsers.SAXParser weblogic.Server
And my Sax code snippet:
SAXParserFactory factory = SAXParserFactory.newInstance();
factory.setValidating(true);
factory.setNamespaceAware(true);
SAXParser parser = factory.newSAXParser();
InputSource input = new InputSource(new
ByteArrayInputStream(xmlString.getBytes()));
parser.parse(input, new XMLErrorHandler());
I believe this is JAXP 1.0 compliant. The last line throws the exception.
Note that this worked fine under WL 5.1 with the same xerces.jar file. And the
DOM parser is working - I use it on request strings coming in but then I build
a response string and attempt to parse it with SAX before sending it back out.
Do you have code similar to above, or do you mind testing the above code in
your environment? Are you using 6.0 sp2?
Thanks,
Ed
Charlie Crook wrote:
I use:
-DSyslog.xml.parser=org.apache.xerces.parsers.SAXParser -Djavax.xml.transfor
m.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl
as a parameter in the java startup command for weblogic
and for the XML registry
DocumentBuilderFactory="org.apache.xerces.jaxp.DocumentBuilderFactoryImpl"
SAXParserFactory="org.apache.xerces.jaxp.SAXParserFactoryImpl"/>
Make sure the server is using the external XML registry, not the built-in
one...
I use the xerces that came with xalan 2.1, putting xerces.jar ahead of
weblogic jars
If we are using JAXP with something like:
new SAXBuilder()
instead of
new SAXBuilder( "some parser class" )
we get an immediate core dump; otherwise all works fine.
"Edward Dunkle" <[email protected]> wrote in message
news:[email protected]...
Greetings.
We have developed a pilot application to get familiar with WebLogic. We
need to validate XML input and output against .xsd schemas. I have this
working for the DOM parser but the SAX parser (which we use to validate
the XML string before sending back to the client) is not working. It
seems like WebLogic is not finding the implementation class. Here's the
stack trace:
java.lang.AbstractMethodError
at javax.xml.parsers.SAXParser.parse(SAXParser.java:367)
at net.verizon.xml.XMLHelper.validate(XMLHelper.java:178)
at net.verizon.xml.XMLHelper.stringValue(XMLHelper.java:154)
at
net.verizon.xml.DescriptorHelper.stringValue(DescriptorHelper.java:99)
at
net.verizon.xml.DocumentDescriptor.toXML(DocumentDescriptor.java:44)
at net.verizon.pilot.Gateway.processRequest(Gateway.java:126)
I have the XML Registry set for both DOM and SAX to use the Xerces
package which I included first in the classpath.
The SAXParserFactory is set
to: org.apache.xerces.jaxp.SAXParserFactoryImpl
Perhaps this is incorrect...
Ed