XML Registry

Question

I'm still trying to run Xalan from the server side...
I tried to set up an XML Registry to use the org.apache.xerces.jaxp
classes. Though it is selected by the server on the XML Services tab,
and it is the only registry I have, I print out the factory and parser
classes that get created, and they are still
weblogic.xml.jaxp.RegistryBlahblahblah classes. The config.xml has the
right class names as shown on the console. Why aren't they used?
The other question I have is that since the Xerces classes that I want
to use have the same names as the ones included but are a different
version, how do I get the server to use the new classes and not the ones
bundled with WebLogic?
Any help would be greatly appreciated!
Michelle

Answer 1

Try to define XML Registry Entry for your specific DTD.
WL compares PublicId, SystemId and RootElement between XML and DTD to find
specific Parser class name for your XML. In this case you must create
xml/registry directory in your domain directory and put there your DTD file.
If it still not working - write this code:
public SAXParser getParser() {
// Return the parser we already created (if any)
if(parser!=null) {
return (parser);
// Create and return a new parser
try {
SAXParserFactory factory= new
org.apache.xerces.jaxp.SAXParserFactoryImpl();
factory.setNamespaceAware(false);
factory.setValidating(false);
parser=factory.newSAXParser();
return (parser);
} catch(Exception e) {
System.out.println("getParser: "+e.getMessage());
return (null);
"Michelle Baxter" <[email protected]> wrote in message
news:[email protected]...
Ok, thanks. I suspected it might be wrapping it, but I wasn't sure how
to tell. I have not figured out how to get the server to run as a
JBuilder run configuration to debug it. It's looking for ".\config",
even though I've given it weblogic.system.home. So I can't look at the
stack trace, at least not that way.
Whatever parser it's getting, it's still the wrong one because I still
get the AbstractMethodError. I don't see how it's possible to have the
wrong version with xmlx.jar out of the way. But I have to keep looking.
Thanks for all your help.
Sandeep Shrivastava wrote:
The parser is weblogic.xml.jaxp.RegistrySAXParser, but it wraps the
org.apache.xerces.parser.SAXParser. the actual parse will be done by the
xerces parser ( whatever is configured in the xml registry )
look at the stack trace in one of your sax callback methods to verify
this.
>>
sandeep
Michelle Baxter wrote in message <[email protected]>...
If that is true, then why when I print out the class name of a parser
that I created do I get weblogic.xml.jaxp.RegistrySAXParser instead of
org.apache.xerces.parsers.SAXParser, which is what is configured in the
config.xml file?
Sandeep Shrivastava wrote:
the weblogic.xml.jaxp package contains classes which implement JAXP
inside
weblogic server. The parser configured in the registry will be invoked
by
the server's jaxp implementation. You can verify this by examining thestack
trace inside one of your sax handler callback methods.
Michelle Baxter wrote in message <[email protected]>...
I'm trying to use Xalan 2J D05. The config.xml is attached.
Xalan is the first thing in my classpath when I run the server.
Xerces
is the second. I tried renaming xmlx.jar to something else, but it
doesn't make a difference.
Sandeep Shrivastava wrote:
Which version of Xalan are you trying to use?
Can you post the config.xml?
The weblogic 6.0 install contains Xerces 1.2 in
weblogic.apache.xerces.parsers package and Xalan 1.2 in the
weblogic.apache.xalan.xslt package ( These are the built-in sax and
dom
parser and xslt engine, bundled in weblogic.jar )
The install also includes Xerces 1.2 in theorg.apache.xerces.parsers
package and Xalan 1.2 in the org.apache.xalan.xslt package ( Theseare
>>>>>
the
XML module's parser and xslt engine, bundled in xmlx.jar )
If you want to use another version of xalan rename the xmlx.jar to
xmlx.jar.bak in the lib directory of the install. You may lose on
the
>>>>>
other
goodies that come with the XML module, i.e. the parser generator and
the
jsp
tag library though.
thanks
Sandeep
"Michelle Baxter" <[email protected]> wrote in message
news:[email protected]...
I'm still trying to run Xalan from the server side...
I tried to set up an XML Registry to use the org.apache.xerces.jaxp
classes. Though it is selected by the server on the XML Services
tab,
and it is the only registry I have, I print out the factory andparser
classes that get created, and they are still
weblogic.xml.jaxp.RegistryBlahblahblah classes. The config.xml hasthe
right class names as shown on the console. Why aren't they used?
The other question I have is that since the Xerces classes that Iwant
to use have the same names as the ones included but are a different
version, how do I get the server to use the new classes and not theones
bundled with WebLogic?
Any help would be greatly appreciated!
Michelle