As long as you use Xerces/Xalan at the web-app or server level and don't try
to override the parser and xslt engine that JRun uses, you'll be fine.
The only time I've seen problems is when someone puts their XML libraries in
a system-wide location (i.e., in the classpath prior to JRun's XML jars).
I've had troubles trying to get JRun to use JAXP 1.1, but have not had
troubles when trying to use other parsers or XSLT engines at the web-app
level.
If you run into any specific problems, I'll try to help.
Scott Stirling
Macromedia
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 04, 2001 1:02 AM
> To: JRun-Talk
> Subject: XML Processing with Xerces and JRun 3 sp2a
>
>
>
> Hi,
>
> I have run into weird problems with XML processing since I
> upgraded to JRun
> 3sp2a. From what I read, there seem to be problems with
> using a DOM levle 2
> parser with JRun 3 sp 2a (on more that one JRun server).
>
> What libraries are other people using to parse XML from their
> JSP pages?
>
> --
> m John J. Lehmann, [EMAIL PROTECTED]
> e Consiciousness is a "benign user illusion". Is it possible to live
> m life without the illusion?
> e
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
