Posted by norbi
on February 4, 2008 at 1:14 PM PST
We use JAX-WS for our Java client to access the WebService interface of our server-application. Recently we added a new operation to server's WSDL file and recompiled also the JAX-WS based client (we use the option to retrieve the wsdl file from the server during startup). But now we have a problem that the "new" JAX-WS based client doesn't work with the "old" server as we get an exception "undefined operation name" (pointing to the new operation's name) during the service.GetMyPort method call
(the idea was to retrieve WS interface version through one of the "older" operations and thus determine whether the "new" operation is already supported or not).
Is there a way with JAX-WS to say somehow that the particular operation is optional or so ? The only problem seems to be the "old" wsdl file without new operation name, as if I exchange it on the server ("old" wsdl -> "new" wsdl) everything works fine (apparently I could workaround this by using the local wsdl file within our client, but then I would have to deploy also the wsdl file with the client, right ?)
Thanks in advance for any advices