On Thursday 20 December 2007 11:24:02 Lositski Vadim wrote: > Hi, > > You can install multiple Axis2 distributions (WARs) under different context > roots, and install each version of the service in a separate Axis2 > application. Yes, this is my fallback option - but not really satisfactory. The services and wars would all have the same name! - very confusing, easy to make mistakes, etc. I'd like to manage all within one Axis application for the obvious advantages.
I can change the name of the aar file and the <service name="newname"> tag in services.xml. Everything works fine, except for the wsdl request. Any ideas how to fix that? Peter. > > BR, > Vadim > > -----Original Message----- > From: Peter Hargreaves [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 20, 2007 1:16 PM > To: [email protected] > Subject: Name Changes For Development Test and Production Deployments > > We would like to deploy our service under different names within the Axis2 > application: > > 1) DevWebService connected to a development database. > 2) TestWebService connected to a test database. > 3) ProdWebService connected to a production database. > > The problem is that renaming a service seems to have many consequences, so > these different versions of the same service have many differences other > than just the database connection. > > How do other people run different versions of the same service? > > Is there a simple way to do renaming for this purpose? > > Any ideas please? > > Pete.H. > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
