Generating Stubs and Analyzing Binding Extension Tags 

Use

The Web service proxy implementation classes are generated and for each binding WSDL component, an implementation stub is generated. Initially, the binding must be recognized by some of the available binding implementations. This is performed by passing the WSDL binding component to the recognizeBinding()method of the ClientTransportBinding interface (see the diagram in the Proxy Generation). If the method returns the value true, this means that this implementation supports this binding and it can process these binding extension elements.

Once the binding is recognized, binding contents are passed to the binding implementation to recognize the common binding options. An object, PropertyContext, is also passed. This object is used by the TransportBinding implementation to store the properties it requires. This class acts as a double Hashtable. It enables both Object-s and PropertyContext-s to be mapped to it.

Activities

When generating stubs for every binding, the generator invokes ClientTransportBindingmethod:

·        void getMainBindingConfig(WSDLBinding binding, PropertyContext context)

And for each operation it invokes:

·        void getOperationBindingConfig(WSDLBindingOperation obinding, WSDLOperation operation, PropertyContext context, WSDLDefinitions definitions)

Furthermore, to get the endpoint address from the extension element in the wsdl:port component, the proxy generator invokes:

·        String loadAddress(WSDLExtension extension)

Note that these methods are available in all binding implementations, and that for each stub, one specific binding implementation is used.