|
|
|
|
| |
Which XML parser comes with WebLogic Server 6.0?
We bundle a parser, based on Apache's Xerces 1.2.0 parser, in WebLogic Server
6.0. In addition, we include a parser generator that enables you to build a custom parser
based on a specific DTD for optimized performance. The WebLogic XML Registry
allows you to configure the parser you want to use for specific DTDs.
Is an XSLT processor bundled in WebLogic Server?
Yes, we bundle an XSLT processor, based on Apache's Xalan 1.2 processor, in
WebLogic Server 6.0.
Can I use SAX version 2.0 parsing with WebLogic Server 6.0?
Yes, but you must use the parser specific API, instead of the Java API for XML
Parsing (JAXP).
Can I use the getAttribute() and setAttribute() methods of Version 2.2 of the Java
Servlet API to parse XML documents?
Yes. Use the setAttribute() method for SAX mode parsing and the
getAttribute() method for DOM mode parsing. Using these methods in a Servlet,
however, is a WebLogic-specific feature. This means that the Servlet may not be fully
portable to other Servlet engines, so use the feature with caution.
Does WebLogic Server 6.0 support SOAP?
WebLogic Server 6.0 does not support SOAP; however, BEA provides an
alpha-quality SOAP implementation at
http://developer.bea.com:80/techtracks/xml/index.jsp.
Can I plug in a version of Apache's Xerces XML parser that is different to the one
that is built-in with WebLogic Server 6.0 (Xerces 1.2.0)?
No. Each version of Apache's Xerces XML parser requires a different version of
the DOM interfaces and there can be only one copy of the DOM interfaces in the
WebLogic Server environment. Version 6.0 of WebLogic Server includes the version
of DOM needed for Xerces 1.2.0 because the built-in parser of WebLogic Server 6.0
is based on Xerces 1.2.0. If you try to plug in a different version, say 1.X of Xerces,
you will get an error when you parse XML documents because Xerces version 1.X is
expecting the version 1.X of the DOM interfaces. If you try to put version 1.X of the
DOM interfaces in front of weblogic.jar in the CLASSPATH environment variable
before you start WebLogic Server, you will cause WebLogic Server not to work
correctly because Xerces 1.2.0 is used internally and requires the Xerces 1.2.0 version
of the DOM interfaces.
The real cause of this problem is that Xerces ships new versions of interfaces in each release. Unfortunately, this prevents mulitiple versions of Xerces from co-existing in the same CLASSPATH environment.
The problem only affects Xerces or other parsers that support the non-final features of DOM Level 2. It does not affect the Sun Project X or Crimson parsers because those parsers support DOM Level 1 whose portion of the DOM interfaces is the same in all versions.
I plugged in a version of Apache Xalan that I downloaded from the Apache Web
site, and now I get errors when I try to transform documents. What is the problem?
You must ensure that the version of Apache Xalan you download from the Apache
Web site is compatible with Apache Xerces version 1.2.0. Because you cannot plug
in a different version of Apache Xerces (see the preceding question), the only version
of Apache Xerces that is compatible with WebLogic Server 6.0 is 1.2.0.
The built-in parser (based on version 1.2.0 of Apache Xerces) and transformer (based on version 1.2 of Apache Xalan) have been modified by BEA to be compatible with each other.
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|