The issue here is related to customers using web services. WSDL 1.1 has a
psychotic facade in front of W3C XML Schema, whereby the element-name of a node
must be determined very late, and may not be unique in the WSDL (in particular,
soap:body may be associated with multiple @type-s).
What we need to do is to provide a validation API that looks approximately like
this:
N validate(N element, QName sourceNodeType)
(there may be additional parameters, but the change here is from getting
started by looking at the supplied element's name, seeking a schema Element
definition as the starting point, and instead going to validating the content
using the type indicated by the supplied QName)
Original issue reported on code.google.com by aale...@gmail.com on 11 Jun 2013 at 5:23
Original issue reported on code.google.com by
aale...@gmail.com
on 11 Jun 2013 at 5:23