RE: What actually happens when you deploy a service

[Glen Daniels]

Hi Mark, Jonathan:   Mark is mostly right, except that you do not have to restart the server to get access to the new service.  It is both added to the current in-memory engine configuration and the persistent server-config.wsdd file.   You can see a list by running "java org.apache.axis.client.AdminClient list" (this returns the server-config.wsdd XML), and when a deployment is undeployed all the components within it (I'm assuming you're talking about a WSDD <undeployment> here) are removed from both the internal and the persistent engine configuraitons.   --Glen -----Original Message----- From: Mark Volkmann [mailto:[EMAIL PROTECTED]] Sent: Sunday, April 14, 2002 1:11 PM To: [EMAIL PROTECTED]; Jonathan Subject: Re: What actually happens when you deploy a service I could be wrong, but I think the only thing that happens is that server-config.wsdd in the bin directory of your server (such as Tomcat) is modified. If you are deploying a service for the first time, the server must be restarted to pickup those changes. After doing this, your service will be deployed every time the server is started because the change to server-config.wsdd is only undone if you run AdminClient on undeploy.wsdd or edit server-config.wsdd manually to remove the service description.   ----- Original Message ----- From: Jonathan To: [EMAIL PROTECTED] Sent: Sunday, April 14, 2002 10:28 AM Subject: What actually happens when you deploy a service We use: "java org.apache.axis.client.AdminClient deploy.wsdd"   Does this command create some kind of binary file? How do you see a list of what has been deployed? What technically happens when a deployment is undeployed?