Hi Daniel, Thanks! Schema is coming from a 3rd party. I doubt they'll fix it any time soon if ever. As a workaround I've already done what you suggest (as I haven't find any other way to make it work), i.e. created another XSD that includes all others (that use the same namespace) and then import this new into WSDL. However, I don't want to make this changes with each new version of schema (which I don't control).
On Thu, May 2, 2019 at 5:13 PM Daniel Kulp <[email protected]> wrote: > > > > On Apr 30, 2019, at 7:05 AM, Miljenko Brkic <[email protected]> wrote: > > > > I have a SOAP endpoint and want to validate incoming requests against the > > WSDL. The problem is that WSDL imports multiple XSDs using the same > > namespace > > I would fix that problem, not try to hack the parser to accept it. > > The WSDL should be set to import only a single XSD with the given > namespace, but that XSD could them “xsd:include” the other XSD’s in the > same namespace. Thus, only a single schema for the namespace is created, > it just happens to include the other xsd fragments. > > -- > Daniel Kulp > [email protected] <mailto:[email protected]> - http://dankulp.com/blog < > http://dankulp.com/blog> > Talend Community Coder - http://talend.com <http://coders.talend.com/> >
