public interface DomHandler<ElementT,ResultT extends Result>
Implementations of this interface will be used in conjunction with
XmlAnyElement annotation to map an element of XML into a representation
of infoset such as W3C DOM.
Implementations hide how a portion of XML is converted into/from such DOM-like representation, allowing JAXB providers to work with arbitrary such library.
This interface is intended to be implemented by library writers and consumed by JAXB providers. None of those methods are intended to be called from applications.
|Modifier and Type||Method and Description|
When a JAXB provider needs to unmarshal a part of a document into an infoset representation, it first calls this method to create a
Once the portion is sent to the
This method is called when a JAXB provider needs to marshal an element to XML.
ResultT createUnmarshaller(ValidationEventHandler errorHandler)
A JAXB provider will then send a portion of the XML into the given result. Such a portion always form a subtree of the whole XML document rooted at an element.
errorHandler- if any error happens between the invocation of this method and the invocation of
getElement(Result), they must be reported to this handler. The caller must provide a non-null error handler. The
Resultobject created from this method may hold a reference to this error handler.
Result. This method is called by a JAXB provider to obtain the unmarshalled element representation.
Multiple invocations of this method may return different objects.
This method can be invoked only when the whole sub-tree are fed
Source marshal(ElementT n, ValidationEventHandler errorHandler)
If non-null, the returned
Source must contain a whole document
rooted at one element, which will then be weaved into a bigger document
that the JAXB provider is marshalling.
errorHandler- Receives any errors happened during the process of converting an element into a
Source. The caller must provide a non-null error handler.
For further API reference and developer documentation, see Java SE Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.
Copyright © 1993, 2013, Oracle and/or its affiliates. All rights reserved.