Frank,
I went
through the same scenario as yourself recently.
Officially, BEA have a disclaimer saying that you may have problems if
you use another parser such as version 1.4.4. Basically, they
won't provide support if you use a different parser and start
having problems as a result.
I
tried adding it to the classpath for my managed server and it worked ok.
(Remember to put it before the weblogic.jar!)
The
real issue is with the implementation of the DOM interfaces in various
parsers. If Weblogic is calling a particular DOM method that doesn't
happen to be implemented by your parser, you've got a problem. On the face
of it, it looks like there isn't a difference between the DOM interfaces
implemented by 1.2 and 1.4.4.
If you
do decide to go with 1.4.4 make sure you test your app thoroughly......just in
case ;)
Rash
-----Original Message-----
From: Leemans, Frank [JanBe] [mailto:[EMAIL PROTECTED]
Sent: 04 February 2002 10:44
To: '[EMAIL PROTECTED]'
Subject: Xerces backward Compatibility
From: Leemans, Frank [JanBe] [mailto:[EMAIL PROTECTED]
Sent: 04 February 2002 10:44
To: '[EMAIL PROTECTED]'
Subject: Xerces backward Compatibility
Can anyone confirm me that the later versions of Xerces are backward compatible with the previous ones. More specific, is Xerces 1.4.4 backwards compatible with Xerces 1.2.
We are using Weblogic 6.1, in which Xerces 1.2 is included. Validating XML Schema's does not work properly. It is with Xerces 1.4.4. Now I want to know if there is any possibility Weblogic got any problems with including Xerces 1.4.4 in the classpath.
Thx,
Frank
[EMAIL PROTECTED]
