I have attached an updated patch to the jira http://issues.apache.org/activemq/secure/ManageAttachments.jspa?id=24443
I still have some questions, now that I have a better understanding of what the patch do. Mainly, I'm questionning the need to the wsdl 1.1 jbi wrapper. If all services exposed and invoked by servicemix are ws-i basic profile compliant, there is only one child in the soap body. Other parts that may be included in the normalized message may come from soap headers. So we are in the same case as for WSDL 2.0: only one element in the soap body, and additioanl soap headers. However, for WSDL 2, soap headers won't be mapped inside the xml content, but should be put as properties on the message. So i'm not quite sure if headers should be put inside the content for WSDL 1.1, as it will not be consistent. I don't really see the point of the wrapper here. Thoughts ? On 8/31/06, Alex Boisvert <[EMAIL PROTECTED]> wrote:
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
-- Cheers, Guillaume Nodet
