Question

Is there any way to use soap-rpc web services such that the client is generated via a shared interface? Restful web services do it this way, but what about soap based? Do you always have to use a tool like Axis or CXF to generate your stubs and proxies, or is there something out there that will set it up dynamically?

Thanks.

EDIT #1:

To clarify, I’m looking to do something like this:

Common interface:

@WebService
public interface MyWebService {

   @WebMethod
   String helloWorld();
}

This common interface can already be used to create the server side component. My question is: can this type of common interface be used on the client side to generate dynamic proxies? Restful web services do it this way (Restlets & CXF) and it seems the .Net world has this type of functionality too.

Answer 1

I would see this tutorial of JAX-WS useful for your purposes:

In the example code the Web Services Client is configured by adding an annotation @WebServiceRef with a property pointing to the WSDL location to the client implementation class and no tools are needed to access the stuff from the Web Service that is referenced.

Was this the way you would like to have it, or did this even answer to right question?