When we create the WSDL interface contract in the WebServicesBinding the 
Definitions that lead to it being created is left null
-------------------------------------------------------------------------------------------------------------------------------

                 Key: TUSCANY-3917
                 URL: https://issues.apache.org/jira/browse/TUSCANY-3917
             Project: Tuscany
          Issue Type: Bug
          Components: Java SCA Axis Binding Extension
    Affects Versions: Java-SCA-2.0
         Environment: All
            Reporter: Simon Laws
             Fix For: Java-SCA-2.0


When the interface contract is created from a WSDLDefinition using the 
following piece of code from WebServiceBIndingProcessor

            PortType portType = getPortType(model);
            if (portType != null) {
                WSDLInterfaceContract interfaceContract = 
wsdlFactory.createWSDLInterfaceContract();
                WSDLInterface wsdlInterface = null;
                try {
                    wsdlInterface = wsdlFactory.createWSDLInterface(portType, 
wsdlDefinition, resolver, context.getMonitor());
                } catch (InvalidInterfaceException e) {
                        warning(monitor, "InvalidInterfaceException", 
wsdlFactory, model.getName(), e.getMessage()); 
                }
                interfaceContract.setInterface(wsdlInterface);
                
interfaceContract.setCallbackInterface(wsdlInterface.getCallbackInterface());
                model.setBindingInterfaceContract(interfaceContract);
            }

The wsdlDefinition is not set on the newly created wsdlInterface. This hasn't 
mattered until now but, due to TUSCANY-3915, we're looking to retrieve the 
binding interface contract and serialize out the WSDL that's found. If could be 
useful to be able to use the wsdlDefinition if one already exists rather than 
trying to generate a new one. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to