Pid-2 wrote: > > > Actually, I disagree. I have deployed the Axis and support jars in a > shared classloader (shared/lib for TC5.5) and then deployed a .war for > each webapp. > > In your case you could do: > > /app1/axis/services/xxxx > /app2/axis/services/xxxx > > You're both correct. There's no technical problem with Axis, but Rashmi > is right in that you may find suggestions and assistance on the Axis > mailing list - which may help improve your deployment methodology and > avoid this type of problem. > > This would avoid you having to try and subvert the Tomcat classloader(s). > >
Hi Thanks for your message. Well, I've been working with Axis on the last two years and never hear about such kind of configuration, but if it works, it could be a good solution. I' ll try to test it. (and I' ll ask in axis list too). Thank you very much. J -- View this message in context: http://www.nabble.com/Organizing-WEB-INF-lib-tf3643789.html#a10196388 Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
