Ulf Dittmer wrote:As I said, the WSDL isn't deployed by you, it's deployed by the SOAP engine. But you only need it for development, not for production use (unless you want other people to access it so that they can build client code for the service).
As to the endpoint URL, that's determined by where the SOAP engine is deployed, and how the relevant classes and methods are named (and possibly by some of the annotations if you're using JAX-WS). Beyond that, you don't have control over it, and it's only relevant for the client side, not the server side to begin with.
Ulf Dittmer wrote:Welcome to JavaRanch.
I'm not sure I understand all your questions, but I'll give it a shot.
#1 - The WSDL is only needed by someone creating a client for the WS. If you have done that, then there's no further need for it. What's more, it isn't so much "deployed" as it is generated automatically by the WS stack.
#2 - If by "locator" you mean something that's part of the client, then you're right - the client obviously needs to know which server to go to. If you want to keep that configurable (like for test and production), then the client should read the server name from a config file that you can change without having to change the code.
#3 - I don't understand what you're asking. Can you rephrase that and provide more detail?