This behavior is by design: The xs:integer type is specified as a number with no upper or lower bound on its size. For this reason, neither XML serialization nor validation map it to the System.Int32 type. Instead, XML serialization maps the xs:integer to a string while validation maps it to the Decimal type that is … Read more
So just in case anybody else runs into the same issue here, I needed to load a parent schema (and implicit child schemas) from a unit test – as a resource – to validate an XML String. I used the Xerces XMLSchemFactory to do this along with the Java 6 validator. In order to load … Read more
There is a command-line tool called XSD2DB, that generates database from xsd-files, available at sourceforge.
I tell you you can go to the shops at least once and at most twice, and each time you have a choice of what to buy: you can buy apples (either one apple or two apples), or you can buy oranges (either no oranges or one orange). It’s entirely possible that you will choose … Read more
I did some research on this a while ago and the only solution I found was to used the mixed attribute: <xs:element name=”field”> <xs:complexType mixed=”true”> <xs:sequence> <xs:element ref=”subfield” minOccurs=”0″ maxOccurs=”unbounded” /> </xs:sequence> <xs:attribute name=”name” type=”xs:string” /> </xs:complexType> </xs:element> This sadly also allows <field name=”test_field_0″> Some text I’m sure you don’t want. <subfield>Some text.</subfield> More text … Read more
Between Validator validator = schema.newValidator(); and StreamSource xmlFile = new StreamSource(xml); add this fragment: final List<SAXParseException> exceptions = new LinkedList<SAXParseException>(); validator.setErrorHandler(new ErrorHandler() { @Override public void warning(SAXParseException exception) throws SAXException { exceptions.add(exception); } @Override public void fatalError(SAXParseException exception) throws SAXException { exceptions.add(exception); } @Override public void error(SAXParseException exception) throws SAXException { exceptions.add(exception); } }); This … Read more
You can try turning Check-constraints off on the DataSet (it’s in its properties), or altering the properties of that relationship, and change the key to a simple reference – up to you.
Setting nillable=”true” means that the <birthDate> tag can appear as follows: <birthDate xsi:nil=”true”/> However, since you also set minOccurs=”0″, you could also omit the <birthDate> tag completely from the XML and it would also still validate against your XSD. Note that <birthDate/> or <birthDate></birthDate> is not considered null according to XSD rules. Have a look … Read more
Right click on an XSD file, choose “Open with…” and select the appropriate option – then click on “Set as Default” before you actually open it.
There are two methods for this. <xsd:include schemaLocation=”pathToFile” /> should be used for including files of the same namespace. <xsd:import namespace=”namespace” schemaLocation=”pathToFile” /> should be used for include files in a different namespace. Usually you will specify the namespace given as the targetNamespace of the imported schema.