On 4/13/07, ant elder <[EMAIL PROTECTED]> wrote:
Right now the Axis2 binding needs the WSDL4J Definition object to create an AxisService but the definition object isn't available to it anywhere. The Definition is read by the contribution service which creates a WSDLDefinition, so as a bypass around this I've add a WSDLDefinition field to the WebServiceBinding and populate that in the WebServiceBindingProcessor resolve method, but this adds a dependency on tuscany-interface-wsdl to tuscany-binding-ws and tuscany-binding-ws-xml which doesn't seem ideal. Any comments on what to do about this? I guess the WSDLDefinition needs to be pulled out of tuscany-interface-wsdl into a separate module.
No replies to this so for the sake of expediency to bring up the Axis2 binding I've just add the WSDLDefinition field and dependency on tuscany-interface-wsdl to tuscany-binding-ws and tuscany-binding-ws-xml. I'll try to sort something better our next week if no one else does before then. ...ant
