java.lang.Objectjavax.xml.transform.sax.SAXResult
javax.xml.bind.util.JAXBResult
All Implemented Interfaces:
Result
This utility class is useful to combine JAXB with other Java/XML technologies.
The following example shows how to use JAXB to unmarshal a document resulting from an XSLT transformation.
JAXBResult result = new JAXBResult(
JAXBContext.newInstance("org.acme.foo") );
// set up XSLT transformation
TransformerFactory tf = TransformerFactory.newInstance();
Transformer t = tf.newTransformer(new StreamSource("test.xsl"));
// run transformation
t.transform(new StreamSource("document.xml"),result);
// obtain the unmarshalled content tree
Object o = result.getResult();
The fact that JAXBResult derives from SAXResult is an implementation detail. Thus in general applications are strongly discouraged from accessing methods defined on SAXResult.
In particular it shall never attempt to call the setHandler, setLexicalHandler, and setSystemId methods.
Kohsuke - Kawaguchi (kohsuke.kawaguchi@sun.com)| Fields inherited from javax.xml.transform.sax.SAXResult: |
|---|
| FEATURE |
| Constructor: |
|---|
|
This JAXBResult object will use the specified Unmarshaller instance. It is the caller's responsibility not to use the same Unmarshaller for other purposes while it is being used by this object. The primary purpose of this method is to allow the client to configure Unmarshaller. Unless you know what you are doing, it's easier and safer to pass a JAXBContext.
|
| Method from javax.xml.bind.util.JAXBResult Summary: |
|---|
| getResult |
| Methods from javax.xml.transform.sax.SAXResult: |
|---|
| getHandler, getLexicalHandler, getSystemId, setHandler, setLexicalHandler, setSystemId |
| Methods from java.lang.Object: |
|---|
| clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
| Method from javax.xml.bind.util.JAXBResult Detail: |
|---|
|