A couple of comments inline... On 5/9/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
<snip/>
5. The following line was in Axis2BindingBuilder before the SPI > changes: > TODO: if <binding.ws> specifies the wsdl service then should > create a service for every port > Is this remoider still needed? I just checked the WebService spec and couldn't find a statement confirming this behavior. I don't understand why we would create an (Axis2) service for every WSDL port...
I could be reading mis-reading it, but line 39, section 2.1 page 2 of the WS binding spec, http://www.osoa.org/download/attachments/35/SCA_AssemblyModel_V100.pdf?version=1 : 39 <WSDL-namespace-URI>#wsdl.service(<service-name>) In this case, all the endpoints in the WSDL Service that have equivalent PortTypes with the SCA service or reference must be available to the SCA service or reference.
8. Should Http chunking be on or off? There's code to turn it off, > but I've seen it tunred on when reading wire traces. In general I think it's better to have it on. Why would we turn it off?
A lot of older (and not so old) SOAP stacks don't support it. There's also a few other things like this where we may want to customise the request it ways not defined by the WS binding spec. The WS binding schema is extensible so we could add these as extensions to <binding.ws>. Alternatively, for chunking we could do something like say chunking is always on for SOAP 1.2as that is newer so likely a stack that supports chunking, but off for SOAP 1.1, but thats not as flexible as extending the schema. ...ant
