Thanks Petr, this is very useful! -----Original Message----- From: Petr Kozelka [mailto:[EMAIL PROTECTED] Sent: Thursday, January 22, 2004 4:52 AM To: [EMAIL PROTECTED] Subject: Re: How to create the server-config.wsdd file in a script (without any running server) - SOLVED!
Hi Bill and anybody intrrested, I found the solution, and it's quite simple! It is based on the observation that the file "server-config.wsdd" contains all the elements from deploy.wsdd as-is, so the only task is to copy the content from the deploy.wsdd to an existing server-config.wsdd or to a template. To make this easier, I created a XSL stylesheet that can be used to either generate a fresh new server-config.wsdd, or to properly modify an existing one. The latter variant, as I guess, might be useful for you - if you want to keep your configuration in manualy edited file, and add the services during the war build process. Just specify the XSL parameter "original.server.config". The stylesheet is available at: http://kozelka.hyperlink.cz/ws/axis/axis-server-config.wsdd.xsl The default server-config.wsdd, containing standard AXIS services, is at: http://kozelka.hyperlink.cz/ws/axis/axis-server-config-default.wsdd Regards, Petr Heitzeg, Bill wrote: > Sorry Petr, I haven't had to do this. I hope you get it solved though. > > -----Original Message----- > From: Petr Kozelka [mailto:[EMAIL PROTECTED] > Sent: Friday, January 16, 2004 4:39 AM > To: [EMAIL PROTECTED] > Subject: Re: How to create the server-config.wsdd file in a script > (without any running server) > > > Hi Bill, > > thanks for the hint. > I forgot to note that the primary source for my client code is WSDL > (iow., I generate client code from WSDL, not vice versa). > This makes my situation slightly harder, because server-config.wsdd is > (as I understand it) just an internal AXIS representation of the WSDL. > > So I have these entities: > -(external input) My.wsdl > | > +--(generated) client stubs generated by Axis wsdl2java > | > +--(manually edited) client code > > > Now I need to somehow generate the server-config.wsdd; having it edited > as you suggest would mean that I would have to reflect any changes that > happen to the WSDL during development to this one, too. > > In the ideal case, the only thing I would have to adjust when WSDL > changes is the client code. > Any ideas ? > > Thanks, > Petr > > > Heitzeg, Bill wrote: > > >>Petr, >> I believe I'm doing what you're asking. I'm just placing everything directly >> in the server-config.wsdd and then kicking off Ant to build it all into a war. In >> other words, I have a server-config.wsdd file as part of my build project, I place >> all my config information in this file (what would normally be passed in as part of >> deploy.wsdd) and then add it to the war when I build. I don't use deploy.wsdd at >> all. >> >>If that doesn't help, I can send you what I have in a zip file. >> >>Bill >> >>-----Original Message----- >>From: Petr Kozelka [mailto:[EMAIL PROTECTED] >>Sent: Thursday, January 15, 2004 12:50 PM >>To: [EMAIL PROTECTED] >>Subject: How to create the server-config.wsdd file in a script (without >>any running server) >> >> >>Hello, >> >>I need to create a WAR file containing whole AXIS + my webservice, in >>order to make the deployment of my webservice same as deploying any >>other WAR. >> >>The problem is that I did found no way to create the server-config.xml >>file without having any server running. I need to do this in an ANT >>script, because the whole process will be reproduced many times at >>several machines, typically disconnected from the corporate network. >>But it seems that the AdminClient utility >> a) always tries to connect a server >> b) never returns the server-config.wsdd file to a caller-accessible >>location; instead, it is created just on the server. >> >>Is there a way to convince the AdminClient or other utility to produce >>the wsdd file at the clientside, without connecting webserver ? >> >>Thanks, >>Petr >> >> >> > > > >
