Subject:schema validation Author:(Deleted User) Date:18 Sep 2008 06:06 AM
Hi Brightman,
this schema doesn't follow the guideline that suggests having a single entry point for each namespace (as enforced by the Xerces-C++ schema validator). For instance, OrderLogisticalInformation.xsd (that implements the namespace urn:ean.ucc:order:2) has these lines
but the schema specs warns against this practice because "given that the schemaLocation [attribute] is only a hint, it is open to applications to ignore all but the first <import> for a given namespace, regardless of the actual value of schemaLocation". The proper way to import the urn:ean.ucc:2 namespace is by using a single
Subject:schema validation Author:Brightman Mkhwanazi Date:18 Sep 2008 10:35 AM
Thanks Alberto
It works if I use InvoiceProxy.
I imported the schema to my integration system successfully, created mappings and generated the wsdl file based on this schema. I am getting the following errors when calling the webservice from stylus studio :
Ref element ds:Signature not found in the Schema
Base type could not be found: eanucc:LineItemType
Namespace urn:ean.ucc.:pay:vat:2 is referenced without <import> declaration
The same wsdl works in XMLSpy.
I have attached the wsdl file.
Subject:schema validation Author:(Deleted User) Date:19 Sep 2008 03:53 AM
Hi Brightman,
the version you are using had an issue with multiple xs:schema defined inside a WSDL using xs:import to import each other; to workaround this problem you should use external files for the support schemas, keeping only the main one inside the WSDL, like in the attached files.