On Thursday 20 December 2007 11:25:17 [EMAIL PROTECTED] wrote: > Hi Peter, > > I think this problem is beyond Axis and Axis2 and is more on project > base. I know that maven has built-in support for different environments > using profiles to support this. For ant there are alternatives but I > don't exactly know how to deal with this. I think they make use of extra > tasks for different environments. I'm only asking how to handle different versions or how to change the name, so I'd rather not have to go for a big solution.
I can manage the ant scripting if just knew what needed to be changed within my application. Thanks for the tips anyway - I'll take a look at Maven. Pete.H. > > Good luck! > > Sietse > > -----Original Message----- > From: Peter Hargreaves [mailto:[EMAIL PROTECTED] > Sent: 20 December 2007 11:16 > 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]
