Sam, this is the bug you found. Matt, we have an import scenario where a binding's portType is undefined when it shouldn't be: (See attached file: import.problem.zip).
tutorial.wsdl --------------- <import ... location="portType.wsdl"> <import ... location="binding.wsdl"> <service...> portType.wsdl ----------------- <portType ...> binding.wsdl --------------- <binding ...> When I run "java Test tutorial.wsdl" I get: Retrieving document at 'tutorial.wsdl'. Retrieving document at 'porttype.wsdl', relative to 'file:tutorial.wsdl'. Retrieving document at 'binding.wsdl', relative to 'file:tutorial.wsdl'. definition = uri:diy:tutorial.wsdl Binding portType isUndefined? true PortType isUndefined? false definition = uri:diy:portType.wsdl PortType isUndefined? false definition = uri:diy:binding.wsdl Binding portType isUndefined? true PortType isUndefined? true Notice that whereever the binding refers to a portType, that portType is undefined, even though that portType DOES exist. I can understand that the binding.wsdl's definition's binding's portType is undefined, but the tutorial.wsdl's definition's binding's portType should not be undefined. If I change the wsdl files slightly, the portType isn't undefined: tutorial.wsdl --------------- <import ... location="binding.wsdl"> <service...> portType.wsdl ----------------- <portType ...> binding.wsdl --------------- <import ... location="portType.wsdl"> <binding ...> > java Test tutorial.wsdl Retrieving document at 'tutorial.wsdl'. Retrieving document at 'binding.wsdl', relative to 'file:tutorial.wsdl'. Retrieving document at 'porttype.wsdl', relative to 'file:binding.wsdl'. definition = uri:diy:tutorial.wsdl Binding portType isUndefined? false PortType isUndefined? false definition = uri:diy:binding.wsdl Binding portType isUndefined? false PortType isUndefined? false definition = uri:diy:portType.wsdl PortType isUndefined? false Russell Butek [EMAIL PROTECTED]
import.problem.zip
Description: Zip archive
