• To: "Hamacher, John E." <HamacherJE@D...>
• Subject: Re: Broken SAX parser after app server port
• From: Elliotte Harold <elharo@m...>
• Date: Mon, 31 Jan 2005 12:49:53 -0500
• Cc: xml-dev@l...
• In-reply-to: <275E1ED78371D511B0050001026A0D8B08E10848@d...>
• References: <275E1ED78371D511B0050001026A0D8B08E10848@d...>
• User-agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041217

Hamacher, John E. wrote:

> 
> Garsh, I've read that before.  Oh well, so I need to except SAX reality.
> Does anyone know why Xerces might behave differently under WebSphere 4 with
> Java 1.3 and Tomcat 5 with Java 1.4?  Why would it change?
> 

It's not clear what's breaking; but if I had to guess I'd say look to 
see whether you used to have a DOCTYPE in your servlet.xml and no longer 
do, or vice versa. That would at least explain the shift between 
characters() and ignorableWhitespace().

-- 
Elliotte Rusty Harold  elharo@m...
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim

• References:
  • RE: Broken SAX parser after app server port
    • From: "Hamacher, John E." <HamacherJE@D...>

• Prev by Date: Re: Broken SAX parser after app server port
• Next by Date: html posts
• Previous by thread: RE: Broken SAX parser after app server port
• Next by thread: Re: Broken SAX parser after app server port
• Index(es):
  • Date
  • Thread