org.apache.axis.utils.Admin client|server <xml-file> On 6/13/05, Ephemeris Lappis <[EMAIL PROTECTED]> wrote: > > Hello again. > Just for your information, i do it, currently, using the xmltask to merge > the axis default server-config.wsdd with the generated deploy.wsdd. > It seems to work, but it's a bit 'heavy' ! > Any other suggestion is welcome ! > > > > -- > Ephemeris Lappis > > > -----Original Message----- > From: Amiel, Meir [mailto:[EMAIL PROTECTED] > Sent: Monday, June 13, 2005 9:07 AM > To: 'Ephemeris Lappis '; 'Axis-User ' > Subject: RE: Automated server-config.wsdd generation using ant > > > > I took a different approach in solving the same issue. I have a servlet that > inits on server startup; it then iterates the war file, looks for all > deploy.wsdd files and deploys the new services. > > > -----Original Message----- > From: Ephemeris Lappis > To: Axis-User > Sent: 6/12/2005 11:40 PM > Subject: Automated server-config.wsdd generation using ant > > Hello. > > Does anyone know a simple way to automate the generation of a deployable > server wsdd. Indeed, to build a deployable war, the default > server-config.wsdd must be extended with the application's services > descriptors, and, to achieve this, we have to either copy/paste the > generated services elements, or code a DOM program to add them... > > I imagine a wsdl2java ant task (or command) extension could generate a > deployable server-config.wsdd instead of the simple deploy.wsdd, based, > either on the default axis one, or a task custom one, for those who need > specific handlers... > > Some idea ? > Thanks... > > -- > Ephemeris Lappis
-- Davanum Srinivas -http://blogs.cocoondev.org/dims/
