JAXB: Exception thrown during Unmarshalling ! HELP !

Question

Hi, my JAXB works fine when the input XML conforms with the schema. But sometimes the input XML contains some extra non-business related fields (populated by the client application) that are absent from my schema definitions and cannot be predicted. In such scenarios JAXB fails during unmarshalling. Is there a way round this ? I have tried Unmarshaller.setValidating( false), but still fails ! Ideally I would want the parser to ignore such fields. Do I need to write a custom EventHandler as means of a way out? Kindly suggest
Raj

Answer 1

I found the following in JAXB specification 1.0, Section 5.9.5
Bind wildcard schema component:
A wildcard is mapped to a simple content-property with:
● Content-property name set to the constant �any�. A binding schema customization could provide a more semantically meaningful contentproperty name.
● Content-property base type set to java.lang.Object by default. Wildcard content encountering during unmarshalling is supported if global XML element tags occurring in �strict� or �lax� wildcard context
are known to the instance of javax.xml.bind.JAXBContext, meaning that the schema(s) describing the element content occurring in the wildcard context is registered with the JAXBContext instance, see
Section 3.2, �JAXBContext,� on page 24 on how bindings are registered with a JAXBContext instance. A JAXB implementation is only required to be able to marshall and unmarshal global element content to/
from �strict�/�lax� wildcard context that is registered and valid5 according to the schema(s) registered to JAXBContext. The specification does not specify how a JAXB implementation handles element content that it does not know how to map to a Java representation.
● See content-property predicate for a wildcard.
● If the maxOccurs is greater than one, the content property is mapped
to a collection property. The default collection property is a List
property.
● These is no default value.
Does anyone know how to go about setting Content-property name & Content-property base type as the specification suggests ?