Guillaume Nodet wrote:
The binding model should only be built on top of the wsdl for the current
HttpEndpoint (either consumer or provider). This WSDL can be
explicitely set, or may be auto-generated using the target endpoint
WSDL. If the WSDL is provided, there is nothing to do, but if the WSDL
is generated, we have to:
* check if there is any existing binding infos (for example, if the
target
endpoint is a soap provider). In this case, we should use the
binding
informations
* else, we need a flag on the http endpoint to set the binding style
(rpc / doc). If the user need to provide a more detailed binding,
then he has to provide it in the wsdl.
Ok, that clarifies it.
I'm trying to abstract the SoapBindingModel a bit more to be able to
easily handle a plain HTTP binding.
WSDL 2.0 bindings will require another reformat later i guess.
Cool! I might be able to help with WSDL 2.0 as well.
thanks,
alex
