Validating schema jaxb
Thanks to this extensibility framework, vendors are free to go beyond the baseline functionality in the specification.Similarly, the JAXB specification can extend the supported subset of W3C XML Schema in the future or even support other schema languages.
Thus, in this article, I'll iintroduce the JAXB API.We'll examine the design of the API and discuss its shortcomings; consider JAXB in the context of the Java-XML universe; and, finally, we'll learn if JAXB can evolve to meet expected future needs.While you can use JAXB without knowing how a schema is mapped to Java or how to use customizations, you cannot use JAXB if you don't know the API. The way a JAXB binding compiler maps W3C XML Schema to Java can be changed more drastically and easily by utilizing the version attribute and through the extensibility framework.In this way, the unmarshaller will look at a document and figure out which package to use.This makes it easy to read in different types of documents without knowing their type in advance.This API hides provider-specific implementation code from applications and also provides a uniform way to do basic operations, such as marshalling or unmarshalling.
The compiler has caused some concern (see JAXB or W3C XML Schema "a la carte"?
This method takes a list of package names as a parameter.
Each schema is compiled into a single package, which means that you can assemble them at run-time by providing multiple package names.
These three aspects of JAXB are covered by three separate interfaces.
Instances of those interfaces can be created from a method.
Another possibility is to set up a SAX pipeline in such a way that your XML parser does the validation; alternately, you could install a stand-alone validator in the pipeline (such as JARV: validation API).