Is this what people are doing in a production world? I've been wondering what folks are doing in a complex environment with multiple web services. (i.e. 20+) There are also the questions related to where a an applications jar has to be. Currently the \lib dir. There's always the possiblity a web service application jar could be named the same as another jar. Yes, standards fixes this, but... So the separation could prevent this issue. But the duplication of axis jars is unpleasant. And the very similar URLs might be confusing to an organization.
Is there a semblance of a 'production' environment out there that has lessons learned which could be shared? chris -----Original Message----- From: Steve Loughran [mailto:steve_l@;iseran.com] Sent: Thursday, October 31, 2002 3:56 PM To: [EMAIL PROTECTED] Subject: Re: isolation of web services deployed on axis ----- Original Message ----- From: "Len Takeuchi" <[EMAIL PROTECTED]> To: "Axis User" <[EMAIL PROTECTED]> Sent: Wednesday, October 30, 2002 4:21 PM Subject: isolation of web services deployed on axis > Hello, > > Is there any mechanism available in axis to achieve some level of isolation > between web service implementations? If two web services depend on using > different versions of classes with the same name how can each web service > get the right version, given that the implementations go in the classes or > lib directory of the axis web application. What I'm looking for is > something like the way each web application deployed on a servlet engine > gets its own classloading space. the trick is to stop having multiple apps in the axis webapp, and move to one webapp per app, each with the axis libs (and servlets in web.xml)
