Assuming that your are using Axis, you would use the AdminClient tool. The details are in the Axis documentation. Being a Java class, running AdminClient can also be started through Ant.
I want to pack the webservice as part of web application. i have created .wsdl file and webservices.xml file also.w where to place deploy.wsdd file. server-config.wsdd is must in war file. mapping.xml is must?
Which SOAP engine are you using? To my knowledge, Axis does not use files called mapping.xml and webservices.xml.
But if it is Axis, you need to add the Axis jar files to your WEB-INF/lib directory, add the Axis servlet to your web.xml, and put server-config.wsdd into WEB-INF. deploy.wsdd is not needed, assuming that server-config.wsdd already contains that information. The WSDL file isn't needed either. [ January 04, 2006: Message edited by: Ulf Dittmer ]
Why would a .wsdd file be a servlet - what are you trying to do with it?
server-config.wsdd contains configuration data for Axis, as well as information about the web services you have deployed. After deploying your web services on your development machine, you should take the file as it is and add it to the war file you're building.
To say anything about that error message, one would need to know the URL you're trying to access and the relevant contents of the web.xml file (servlet declaration and mapping).
What do you mean by "i want my wsdl file to be taken"? Once the WS is developed and deployed, you don't need the WSDL any more. Your users might, but you can let Axis serve it to them dynamically. I wouldn't recommend that for a production service, though. Better to put the file somewhere on the server, and add a link to it on some page, so that the users can download it.
with it's own naming conventions and giving error that the deserializer not found while accessing that service. But i have defined the deserializer mapping with existing naming conventions
please don't hijack an existing thread by adding unrelated questions. It's perfectly OK to start a new thread, and if you give it a meaningful topic name, it's much more likely that you'll get an answer that way. [ January 05, 2006: Message edited by: Ulf Dittmer ]
By deploying, do you mean the initial deployment of the WS into the WS engine, or the deployment of the complete war file that already includes the WS? Axis does not create WSDL files; it can only serve the information dynamically. So, without knowing what exactly you're doing, and what errors or exceptions you're getting, it's hard to guess what might be going wrong.
I'll repeat once more what I said earlier: without knowing which URL you're trying to access, and seeing the relevant excerpts from the web.xml (servlet and mapping), and the exact error message, one won't be able to guess what might be going wrong.
I also don't fully understand the architecture -e.g., why are you creating your own endpoint servlet when you also include Axis, and could just use its servlet?-, or why -within the same web app- you have a page accessing a WS and the WS itself. That seems a rather roundabout way to access functionality.
If you integrate Axis into your web app, you can map the Axis servlet to any directory you like.
this is slightly different from the handwritten one.
Then I would tweak the WS until the automatically generated WSDL matches what you are trying to achieve manually (if the differences even matter to you).
if we dont go for Specific End point servlet, we have to access the operation from the jsp directly.
This makes no sense. Whether you use the Axis servlet as endpoint, or create your own, has no bearing whatsoever on how you access the WS.
not able to download the wsdl file(manual) file from the specified location
There's nothing to download. You simple save the web page that gets displayed when you click on the "WSDL" link. [ January 05, 2006: Message edited by: Ulf Dittmer ]
Post by:autobot
I brought this back from the farm where they grow the tiny ads:
a bit of art, as a gift, the permaculture playing cards