Hi Pete, what version of Xerces are you using? I had problems with previous ones, but using 1.4.4 I get no errors anymore (the server doesn't complain in startup).
Maybe you also need to add xml-apis.jar to the classpath (if not using
jdk1.4)
and place the patch of Weblogic 6.1 I attach, before weblogic.jar (at least
in
sp1) or you'll get a NullPointerException everytime you access a service in
SOAP.
hope it works,
Ruben
(See attached file: patchCR058220.jar)
|---------+---------------------------->
| | "Pete Sheill" |
| | <Pete.Sheill@arib|
| | a.com> |
| | |
| | 04/24/2002 02:59 |
| | AM |
| | Please respond to|
| | soap-user |
| | |
|---------+---------------------------->
>--------------------------------------------------------------------------------------------------------------|
|
|
| To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
|
| cc:
|
| Subject: weblogic 6.1 and Apache soap 2.2
|
>--------------------------------------------------------------------------------------------------------------|
I've seen directions for swapping in Xerces 1.4 in Weblogic by putting it
in the front of the classpath and configuring JAXP. However, it appears
that Weblogic discourages this practice (see below). Has anyone ran into
difficulties doing this? Does anyone use SOAP 2.1 to work around this
issue?
Thanks.
http://edocs.bea.com/wls/docs61/faq/xml.html#740643
Can I plug in a version of Apache's Xerces XML parser that is different to
the one that is built-in with WebLogic Serve 6.1 (Xerces 1.3.1)?
(Embedded image moved to file: pic27446.gif)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.1 of WebLogic Server includes the version of DOM
needed for Xerces 1.3.1 because the built-in parser of WebLogic Server 6.1
is based on Xerces 1.3.1. 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.3.1 is
used internally and requires the Xerces 1.3.1 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
patchCR058220.jar
Description: Binary data
pic27446.gif
Description: GIF image
