The most common practice is to provide access to the WSDL and let consuming users implement their own clients. But if the service will be used internally, and you want to increase consistency in the way people use it, you could provide a pre-generated client package. I think it's up to you whether you tar it up or distribute jars.
If you're using a registry or repository, you can use it to enable access to any artifacts that you might provide. (wsdl, schema, policies, code, tests, documentation, SLAs, etc.) Anne On 3/31/07, Gul Onural <[EMAIL PROTECTED]> wrote:
Hi, I just wanted to ask how people are distributing the web services stubs. For example, let say you generated your stubs using xmlbeans databinding option. The wsdl2java tool generates the following files/directories for a web service : - src - resources - build.xml What is the common practice ? A.) tar the files listed above and distribute the tar file, OR B.) build them first and distribute the jar files (<web-service-name>-test-client.jar and XBeans-packaged.jar) OR C.) just define a way to get access to the wsdl files and let the clients do the rest I know all the options listed are viable options, but I just want to see if there are different opinions/practices people follow. Thanks, Gul
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
