Some of these are: This tip demonstrates two of these improvements: validation (as a part of marshalling and unmarshalling) using the JAXP validation APIs, and Java-to-Schema binding.You'll find the example code for this tip in a downloadable archive.Validation is explained in more detail in More about Validation.JAXB est une spécification qui permet de faire correspondre un document XML à un ensemble de classes et vice versa au moyen d'opérations de sérialisation/désérialisation nommées marshalling/unmarshalling.
This makes it easy to read in different types of documents without knowing their type in advance. JAXBContext jaxb Context = Instance(package Name); Unmarshaller unmarshaller = jaxb Context.create Unmarshaller(); Validating(true); Item item = (Item) unmarshaller.unmarshal(new File("item.xml")); ...Rather than creating a general validating mechanism it might be better to have a general mechanism you inherit from for specific validating purposes i.e. Our Validation Event Collector throws an unchecked exception (JAXBParser Exception) which we then handle with Exception Mapper. Hi Andrew, Validating is indeed deprecated and you need to set the Schema object to validate against.In this respect i am unsure how you can create a general validating mechanism unless you keep a map of known JAXB class to Schema instance.The Unmarshal Validate example demonstrates how to enable validation during unmarshalling.Note that JAXB provides functions for validation during unmarshalling but not during marshalling.