I run the WSDL2Java tool and then cut and paste the service entry from the deploy.wsdd file into the server-config.wsdd file. Seems to work.
Unless you know all the details of service specification and type mappings then its safer to leave it to the AXIS tools.
Ta. Stuart.
Jim Harris wrote:
Junaid, Instead of using the AdminClient tool to deploy your services you could always just edit the server-config.wsdd file by hand. I realise this is a fudge but I don't know of any other way of doing what you want at the moment apart from adding the functionality yourself as you suggest.
At least if you edit by hand you know exactly what is being added and can make sure the changes stay persistant.
HTH Jim -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 06 August 2003 05:19 To: [EMAIL PROTECTED] Subject: cannot persist server-config.wsdd file in a war
Hi all,
I'm running axis as a war in WebLogic. I'm able to deploy/undeploy, as well as execute my webservices without any problems. However the services that I deploy using the admin client tool are not persisted in the server-config.wsdd file, so whenever I re-start the app server, I have to re-deploy the services again!
Looking through the code in EngineConfigurationFactoryServlet it seems to me that the property 'axis.ServerConfigFile' isn't of much help either if you are running in a war/ear mode, since servletContext.getRealPath() returns null, and Axis defaults to using the server-config.wsdd in a read-only mode from the war. I guess if I were running in an exploded directory format things would work fine, but I have to package my application in a war file.
Is there any way to persist the services that I deploy in a war mode? I know I can always write my own version of EngineConfigurationFactoryServlet and use it by specifying some system property, but I would hate to do that unless absolutely necessary. Can Axis provide a way (probably by modifying the behavior of the default EngineConfigurationFactoryServlet) so as to persist services when running in a war mode? I can even volunteer to make the required change if need be :-)
I can only imagine that a majority of folks trying to run Axis in a production environment (like us) would do so by packaging it up in a war, and this issue would be a serious one if not addressed.
