The reality of your file’s encoding appears to conflict with that specified by your XML declaration. If your file actually uses one-byte characters, declaring encoding=”utf-16″ won’t change it to use two-byte characters, for example. Try removing the conflicting encoding from the XML declaration. Replace <?xml version=”1.0″ encoding=”utf-16″?> with <?xml version=”1.0″?> You may also be able … Read more
targetNamespace is an XML Schema “artifact”; its purpose: to indicate what particular XML namespace the schema file describes. xmlns – because the XML Schema is an XML document, it is then possible to define a default XML namespace for the XML file itself (this is what xmlns attribute does); the implications are multiple: authoring, and … Read more
According to the documentation javax.xml.validation is supported since API level 8. (I will test that and report asap) Update Ok, the problem is not that simple: SchemaFactory factory = SchemaFactory.newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI); failed on both level 8 and level 9 API with an IllegalArgumentException as described here Google doesn’t help on that matter except to find the … Read more
First, you must add a targetNamespace=”http://tempuri.org/” to the xs:schema element of your XSD in order for your XSD to apply to the namespace used in your XML payload. Then you can take either of the following approaches: Change the XML or Change the XSD. Choose according to which files you control. Change the XML Add … Read more
This is not pretty – but it gets the job done (hopefully ;). I based this code partly on the link you provided, and then added some recursion to parse out the different types included in the schema, as well as the inner elements and their data types. This definitely does not take into account … Read more
from the XML specification at http://www.w3.org/TR/REC-xml/ (fifth edition) chapter 2 This says “Each XML document has both a logical and a physical structure. Physically, the document is composed of units called entities. An entity may refer to other entities to cause their inclusion in the document. A document begins in a “root” or document entity.” … Read more
You should try it that way XmlDocument doc = new XmlDocument(); XmlSchema schema = new XmlSchema(); schema.Namespaces.Add(“xmlns”, “http://www.sample.com/file”); doc.Schemas.Add(schema); Do not forget to include the following namespaces: using System.Xml.Schema; using System.Xml;
What you can do is to create another new file called file.xsd containing all the schema names in it and then the trick is to name the last schema file with .\ as prefix. File.xsd <xsd xmlns=”http://microsoft.com/dotnet/tools/xsd/”> <generateClasses language=”CS” namespace=”MyNamespace”> <schema>First.xsd</schema> <schema>Second.xsd</schema> <!– more schema files here –> <schema>.\Third.xsd</schema> </generateClasses> </xsd> Now run the command … Read more
I’ll quote from the most official unofficial guide on JAXB on the net. When schemas contain similar looking element/type names, they can result in “Two declarations cause a collision in the ObjectFactory class” errors. To be more precise, for each of all types and many elements (exactly what elements get a factory and what doesn’t … Read more
I want to comment that the script in current accepted answer doesn’t validate errors about incorrect orders of elements of xs:sequence. For example: test.xml <addresses xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xsi:noNamespaceSchemaLocation=’test.xsd’> <address> <street>Baker street 5</street> <name>Joe Tester</name> </address> </addresses> test.xsd <xs:schema xmlns:xs=”http://www.w3.org/2001/XMLSchema”> <xs:element name=”addresses”> <xs:complexType> <xs:sequence> <xs:element ref=”address” minOccurs=”1″ maxOccurs=”unbounded”/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name=”address”> <xs:complexType> <xs:sequence> <xs:element ref=”name” … Read more