We ended up doing exactly that. If you deploy your apps as a servlet the JavaXML framework is not even loaded by the servlet container because it contains servlet classes like HTTPRequest. The J2EE spec that any jar that contains those classes will be ignored by the classloader. Which means all of the other things that you thought you were using were also not being loaded from that jar.
Dov On 7/1/09 8:48 AM, "David Avendasora" <[email protected]> wrote: > Hi all, > > I am trying to figure out the best way to replace any jars required by > projects that in the past were provided by the JavaXML.framework. > > Should I simply download the latest versions of the needed jars from > their original sources and put them in my Libraries directory? > > While I'm sure Maven would be a possible solution for this, right now > I'm looking for the non-maven (Fluffy Bunny Layout) solution. > > Thanks! > > Dave > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/webobjects-dev/drosenberg%40inquira.com > > This email sent to [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
