So whats the deal with XML parsers? For example lets say I need my web app to use xerces-1.4.3 as later versions have various bugs with some of the things Im trying to do (for example xerces-1.4.4's Document.cloneNode() is screwed, and 2.something's EntityResolver gets fed incorrect info, etc... (and the other parsers like crimson are even worse and slow too!))
Rather than hope with crossed fingers that my app will play nice with whatever unknown and untested parser the customer has in their appserver (& if it doesnt we all know who gets blamed) I'd like to be able to include the xerces jar in WEB-INF/lib and have it used instead of the shared one - yet this isn't what happens. What gives? -----Original Message----- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED] Sent: Wednesday, 3 September 2003 00:26 To: Struts Users Mailing List Subject: Re: Commons Versions bundled with Struts 1.1 On Tue, 2 Sep 2003, Adam Hardy wrote: > > On a related subject, what criteria does one use to decide whether to > put these in tomcat's commons/lib directory, or in the webapp's own lib > directory when deploying? > http://jakarta.apache.org/struts/userGuide/configuration.html#config_add Craig --------------------------------------------------------------------- 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]
