This sample aims to demonstrate the invocation of a service that offers multiple bindings. We use the familiar stock quote service, and expose the functionality via a SOAP binding (implemented by the remotely hosted service on XMethods, as in the simplesoap sample) and also via a local java class binding. WSIF allows the client to defer selection of the actual port used for invocation until runtime. To demonstrate this, both the clients in this sample allow specification of a preferred port at runtime. If you choose the port that uses the java binding, the local class is called. If you choose the SOAP port, the SOAP service is called. The high level view of the service remains uniform.
The WSDL file is in this sample directory.
The SOAP implementation is hosted by the good folks at XMethods. The service URL, where you can find details on the service implementation, etc. is here.
Here's how the local java class that implements the service functionality is implemented.
Here's how to invoke this service dynamically using WSIF's dynamic invocation interface (DII).
Here's how to invoke this service by first generating the stub interface and using this directly through WSIF's dynamic proxy, thus hiding all WSIF specifics from the client code. Note that the stub interface used is the the service interface as defined by the JAX-RPC specification.