I read on an earlier string of emails that the plan was for artifact processors to pass WSDLDefinition objects to be resolved into a WSDLModelResolver. If I'm understanding this correctly, this was to replace the overwritten equals() method in the WSDLDefinitionImpl class that was being used by HashMaps to match the dummy WSDLDefinition to the one defined from the WSDL file (and correctly since you really shouldn't say two WSDLDefinitions are the same based on namespace alone).
The equals() method was recently commented out, but (and notably in the WebServiceBindingProcessor class) I'm not seeing the mechanism to pass WSDL resolutions to the WSDLResolver. I'm in fact hitting this issue where the WS Binding can't resolve the WSDLDefinition because it is using ModelResolverImpl instead of WSDLModelResolver. Instead, it resolves to a generated WSDL Definition from the Java Interface and fails to match the WSDLInterface to defined connections. Is there something I'm missing or do I need to open a JIRA here? Kapish Aggarwal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
