cc:
08/06/2003 09:05 Subject: RE: cannot persist
server-config.wsdd file in a war
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 sugges
uk> cc:
Subject: RE: cannot persist
server-config.wsdd file in a war
> IMHO, I still think that Axis should provide this facility in a future
> release.
Good stuff! Why not submit your code to the axis folks for consideration?
Jim
o: <[EMAIL PROTECTED]>
nder.co.uk> cc:
Subject: RE: cannot persist
server-config.wsdd file in a war
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,
> 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.
For more complicated services thats exactly what I do Stuart - you are
right, it does seem to work very well and I find is much easier than using
the
