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 "korz, david" <ko...@emc.com> on 2002/11/14 05:24:02 UTC

How to deploy permanently?

What is the preferred method of deploying a service permanently? I don't
want to have to run AdminClient every time my app server (tomcat) is
started.

Re: How to deploy permanently?

Posted by Benjamin Tomasini <bt...@neteverything.com>.

I have seen this same problem running Axis 1.0 under Resin 2.1.6.  Seems
the server-config.wsdd doesn't save config state.  Tomcat did not have
this problem for me.

Every restart I have to rerun AdminClient.  Probably a parser problem.

Ben

On Thu, 2002-11-14 at 09:31, Steven Gollery wrote:
> David,
> 
> Deployment through the AdminClient should be permanent -- at least it 
> always has been for us. If you have to re-deploy every time you restart 
> Tomcat, there might be something with your setup -- file permissions, maybe?
> 
> Steven Gollery
> 
> korz, david wrote:
> 
> >What is the preferred method of deploying a service permanently? I don't
> >want to have to run AdminClient every time my app server (tomcat) is
> >started.
> >
> 
>

Re: How to deploy permanently?

Posted by Steven Gollery <sg...@cadrc.calpoly.edu>.

David,

Deployment through the AdminClient should be permanent -- at least it 
always has been for us. If you have to re-deploy every time you restart 
Tomcat, there might be something with your setup -- file permissions, maybe?

Steven Gollery

korz, david wrote:

>What is the preferred method of deploying a service permanently? I don't
>want to have to run AdminClient every time my app server (tomcat) is
>started.
>