You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Peter Hargreaves <p....@bedsearcher.co.uk> on 2007/12/20 12:16:25 UTC
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: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Name Changes For Development Test and Production Deployments
Posted by Peter Hargreaves <p....@bedsearcher.co.uk>.
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:p.d.hargreaves@bedsearcher.co.uk]
> Sent: Thursday, December 20, 2007 1:16 PM
> To: axis-user@ws.apache.org
> 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: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: Name Changes For Development Test and Production Deployments
Posted by Lositski Vadim <Va...@profitsoftware.com>.
Hi,
You can install multiple Axis2 distributions (WARs) under different context roots, and install each version of the service in a separate Axis2 application.
BR,
Vadim
-----Original Message-----
From: Peter Hargreaves [mailto:p.d.hargreaves@bedsearcher.co.uk]
Sent: Thursday, December 20, 2007 1:16 PM
To: axis-user@ws.apache.org
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: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Name Changes For Development Test and Production Deployments
Posted by Martin Gainty <mg...@hotmail.com>.
ANT accomplishes the objective by reading separate properties file for each
environment
http://ant.apache.org/manual/CoreTasks/property.html
<property environment="env"/>
<echo message="ANT_HOME is set to = ${env.ANT_HOME}"/>
and then use the environment variable ANT_HOME as the arbiter of which
property file to use e.g.
<property file="${env.ANT_HOME}/.ant-global.properties"/>
ping user@ant.apache.org
for follow-up questions..
Martin--
----- Original Message -----
From: <si...@bt.com>
To: <ax...@ws.apache.org>
Sent: Thursday, December 20, 2007 6:25 AM
Subject: RE: Name Changes For Development Test and Production Deployments
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.
Good luck!
Sietse
-----Original Message-----
From: Peter Hargreaves [mailto:p.d.hargreaves@bedsearcher.co.uk]
Sent: 20 December 2007 11:16
To: axis-user@ws.apache.org
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: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Name Changes For Development Test and Production Deployments
Posted by Peter Hargreaves <p....@bedsearcher.co.uk>.
On Thursday 20 December 2007 11:25:17 sietsenicolaas.tenhoeve@bt.com 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:p.d.hargreaves@bedsearcher.co.uk]
> Sent: 20 December 2007 11:16
> To: axis-user@ws.apache.org
> 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: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: Name Changes For Development Test and Production Deployments
Posted by si...@bt.com.
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.
Good luck!
Sietse
-----Original Message-----
From: Peter Hargreaves [mailto:p.d.hargreaves@bedsearcher.co.uk]
Sent: 20 December 2007 11:16
To: axis-user@ws.apache.org
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: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org