It turns out, the answer is that what I’m seeing is a Byte Order Mark, which is a character that tells whatever is loading the document what it is encoded in. In my case, it’s encoded in utf-8, so the corresponding BOM was EF BB BF, as shown below. To remove it, I opened it … Read more
I have had the same problem. I resolved it by disabling the proxy in the SoapUI preferences. (source : http://www.eviware.com/forum/viewtopic.php?f=13&t=12460)
You made two errors: one in the schema file and another in the syntax of the value of the xsi:schemaLocation attribute of the XML file. The main error is that your employee.xsd file is only a fragment of the XML Schema. You should complete the contain of the employee.xsd. For example, <?xml version=”1.0″ encoding=”utf-8″?> <xs:schema … Read more
You should qualify your autowired variable to say which one should be injected @Autowired @Qualifier(“A1Unmarshaller”) private Jaxb2Marshaller A1Unmarshaller; The default autowiring is by type, not by name, so when there is more than one bean of the same type, you have to use the @Qualifier annotation.
xsd and xsi Similarities Both are XML namespace prefixes, abbreviations for an XML namespace. Both are, as are all namespace prefixes, arbitrarily named; other namespace prefix abbreviations could equally well be used. However, both prefixes are conventional and therefore recommended. (An also-conventional alternative to xsd is xs.) xsd and xsi Differences The xsd (or xs) … Read more
You need to create a simple type like so: <xs:simpleType name=”LimitedString”> <xs:restriction base=”xs:string”> <xs:maxLength value=”50″ /> </xs:restriction> </xs:simpleType> and then use this new type in your schema: <xs:complexType name=”test”> <xs:sequence> <xs:element name=”abc” type=”xs:String” /> </xs:sequence> <xs:attribute type=”LimitedString” name=”myattr” /> </xs:complexType> Marc
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
Answered quite well over here: targetNamespace and xmlns without prefix, what is the difference? To restate: targetNamespace=”” – As the current XML document is a schema this attribute defines the namespace that this schema is intended to target, or validate. xmlns=”” – Defines the default namespace within the current document for all non-prefixed elements (i.e … Read more
Returns simply true or false (also you don’t need any external library): static boolean validateAgainstXSD(InputStream xml, InputStream xsd) { try { SchemaFactory factory = SchemaFactory.newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI); Schema schema = factory.newSchema(new StreamSource(xsd)); Validator validator = schema.newValidator(); validator.validate(new StreamSource(xml)); return true; } catch(Exception ex) { return false; } }
One general (but important!) recommendation is never to store multiple logical pieces of data in a single node (be it a text node or an attribute node). Otherwise, you end up needing your own parsing logic on top of the XML parsing logic you normally get for free from your framework. So in your coordinate … Read more