Raymond Feng wrote:
binding.ws allows the configuration of @wsdlElement to point to the above models in the WSDL using QNames. I think the JIRA complains that if the QName cannot be resolved a model defintion in the WSDL, we should have meaningful messages to report that. For example, if we have:

<binding.ws wsdlElement="http://ns1#wsdl.port(service1/port1)"/>

If there is no WSDL defines a port "port1" under a service "service1" with "http://ns1"; namespace, we should report the problem instead of NPE.


Agreed. Do any of the components or their test cases demonstrate validation of a wsdlElement? I see various method calls for reading or writing a composite to/from XML, do you recall any methods for validating? (I guess my question is, does the existing code have a validation framework, and perhaps this wsdlElement validation is missing from the framework, or does a validation framework currently not exist?)
--
Thanks, Dan Becker

Reply via email to