Hi,
Thanks for the tip ;)  We're well aware of package-renaming approach,
and in fact do it with DBCP for Tomcat 5.5.  But for XML parses after
JAXP that's really hardly ever necessary.

Yoav Shapira http://www.yoavshapira.com


>-----Original Message-----
>From: David Stevenson [mailto:[EMAIL PROTECTED]
>Sent: Friday, December 03, 2004 8:14 PM
>To: Tomcat Users List
>Subject: RE: xercesImpl.jar xerces.jar TC 5.0.19
>
>One thing I've seen done is that third party software (Documentum Web
>Development Kit(WDK)/Content Management Software) takes the open source
>Xerces source code, and renames all the package names. The WDK is then
>coded using the new package names. This allows a customer's version of
>Xerces to peacefully co-exist with the the third party's software, and
>saves the customer the problem of doing that to allow both versions of
>Xerces to co-exist in a web server. This might be something for Tomcat
>to consider doing, to better serve customers who want to choose the
>version of Xerces/Xalan to use with their software.
>
>David Stevenson
>
>On Fri, 2004-12-03 at 11:58, Shapira, Yoav wrote:
>> Hi,
>>
>> >I'm working with Apache Tomcat/5.0.19.
>> >In the \Tomcat 5.0\common\endorsed\ directory,
>> >I've got 2 libraries : xerces.jar (I think it's an old Xerces, I
didn't
>> put
>> >myself
>> >there : someone else need it) and xercesImpl.jar (a newer version of
>> >xerces).
>>
>> It's either or, not both.  If you put them both there, you're asking
for
>> trouble.
>>
>> >I coded a class that need xerces2, but when I launch it (via a
servlet)
>> in
>> >my Tomcat, it throws a NoSuchMethoError cause it doesn't take the
good
>> jar
>> >!
>> >How can I "force" Tomcat to take the librairy  j want ?
>>
>> The best option is to only have one (the one that ships with Tomcat)
>> xerces in common/endorsed.
>>
>> Consider having two Tomcat instances, one for "someone else" with the
>> old xerces, and one with the default Tomcat parser for other
>> applications.
>>
>> Yoav Shapira http://www.yoavshapira.com
>>
>>
>>
>>
>> This e-mail, including any attachments, is a confidential business
>communication, and may contain information that is confidential,
>proprietary and/or privileged.  This e-mail is intended only for the
>individual(s) to whom it is addressed, and may not be saved, copied,
>printed, disclosed or used by anyone else.  If you are not the(an)
intended
>recipient, please immediately delete this e-mail from your computer
system
>and notify the sender.  Thank you.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business 
communication, and may contain information that is confidential, proprietary 
and/or privileged.  This e-mail is intended only for the individual(s) to whom 
it is addressed, and may not be saved, copied, printed, disclosed or used by 
anyone else.  If you are not the(an) intended recipient, please immediately 
delete this e-mail from your computer system and notify the sender.  Thank you.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to