[
Lists Home |
Date Index |
Thread Index
]
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?
J. Eric Hamacher
Wisconsin Department of Justice
Hamacher, John E. wrote:
> I recently ported a WebSphere 4 application to Tomcat 5. The
> schema-validated SAX parser (Xerces) in the program broke down. It is now
> firing characters() when encountering whitespace after each end tag. I
have
> noticed some other unusual behavior such as the enormous size of the ch
> arrays being passed to characters(). The ch arrays are almost always of
> size 2048 and contain my entire XML document from beginning to wherever
the
> 2048th character is. I have tried adjusting the buffer size of the
> XMLReader to no avail. I have looked for jar conflicts but haven't found
> any yet. Anybody relate to this?
>
This is all as it should be. Nothing surprising here. To the extent you
are being surprised, it is by what the SAX spec requires and allows,
rather than what Xerces is doing. See
http://www.cafeconleche.org/books/xmljava/chapters/ch06s07.html
and
http://www.cafeconleche.org/books/xmljava/chapters/ch06s10.html
--
Elliotte Rusty Harold elharo@metalab.unc.edu
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
|
