[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Broken SAX parser after app server port
Consider one more thing. Moving from JDK 1.3 to 1.4, the good old crimson parser ships with the JDK and you might be using this by mistake. Double check which parser you are actually instantiating.. Good luck, Christian > Thank you everybody for your help!! > J. Eric Hamacher > Wisconsin Department of Justice > 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().
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|