[
Lists Home |
Date Index |
Thread Index
]
Hello!
First off, congratulations on moving away from an increasingly unnecessary, expensive, slow-moving, and bloated app server! (although, maybe it has changed in the last year?)
I won't comment on the spec conformance of SAX here - Elliotte is far more qualified :) . But what I can comment on is that we too had difficulties with WebSphere vs. Tomcat in the past. It's worth noting that WebSphere was the offender every time. Tomcat has proven to my teams to be far more reliable, performant, and specs-compliant than the analogous features in WebSphere.
If it turns out that you need to investigate the jar conflicts route again: I seem to remember that there are two places to deal with classpaths in WAS, one is the "normal" one, and one is the system CP, which takes precedence. We had to swap in our own more current version of xerces.jar in the system CP to get our application running correctly.
Some of the other issues you may encounter when porting away from IBM are with other library interdependencies (JNDI, others?) Build it with the Sun JDK and see what happens - if you don't have any issues, the rest of the effort will probably go pretty smoothly.
Sorry if the beginning of this message is a bit inflammatory, I *swear* I'm not trolling. YMMV :)
Take care, and good luck!
Rick
// -------------------------------------------------------
Rick Cochrane
ObjectZen Consulting - <be_the_object/>
"Industrial-Strength Object-Oriented Software Development"
mobile) 612.414.1024 / mailto:rick@objectzen.net
---------- Original Message ----------------------------------
From: Elliotte Harold <elharo@metalab.unc.edu>
Date: Mon, 31 Jan 2005 12:05:20 -0500
>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
>
>-----------------------------------------------------------------
>The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
>initiative of OASIS <http://www.oasis-open.org>
>
>The list archives are at http://lists.xml.org/archives/xml-dev/
>
>To subscribe or unsubscribe from this list use the subscription
>manager: <http://www.oasis-open.org/mlmanage/index.php>
>
>
___________________________________________________________
$0 Web Hosting with up to 120MB web space, 1000 MB Transfer
10 Personalized POP and Web E-mail Accounts, and much more.
Signup at www.doteasy.com
|
