Tony Anecito wrote:
> Hi All,
>
> While tracking down a startup warning for a web service I ran into something I had not expected.
> I have several web services bundled into a single war and each one has it's own wsdl. I decided to create a separate war for a single service and got to the point where it deployed. Then I removed the references from the old war and without changing the client side jar containing the classes for talking to the services I got an error about not being able to connect to the service. In my client side code I specify the path to the service.
>
> I suspect what is happening that since I did not change the client side classes for interfacing with the service (the method/args did not change for the service) that in the generated artifacts wsgen for the client it hardcodes the url for the wsdl for example.
>
> How do I work around this problem? I do not want to change the client side classes everytime I change the location of the service. Is there some way when creating the port or service class in the client code to overide what might be embedded in the wsgen artifacts for the client?
>
In 2.2, the service code lazily evaluates the wsdl locations. If you use
the constructor XXXService(wsdl) and explicitly pass the new wsdl
location, you shouldn't see any exception(even though the client code
still has the older wsdl location)
Jitu
> Thanks,
> -Tony
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_jax-ws.dev.java.net
> For additional commands, e-mail: dev-help_at_jax-ws.dev.java.net
>
>