svn commit: r154998 - webservices/axis/trunk/java/xdocs/OMTutorial.html

[ch...@apache.org]

Author: chinthaka
Date: Wed Feb 23 02:15:52 2005
New Revision: 154998

URL: http://svn.apache.org/viewcvs?view=rev&rev=154998
Log: (empty)


Modified:
    webservices/axis/trunk/java/xdocs/OMTutorial.html

Modified: webservices/axis/trunk/java/xdocs/OMTutorial.html
URL: http://svn.apache.org/viewcvs/webservices/axis/trunk/java/xdocs/OMTutorial.html?view=diff&r1=154997&r2=154998
==============================================================================
--- webservices/axis/trunk/java/xdocs/OMTutorial.html (original)
+++ webservices/axis/trunk/java/xdocs/OMTutorial.html Wed Feb 23 02:15:52 2005
@@ -334,7 +334,7 @@
 
 <h3>Building OM from Objects - Use of ObjectToOMBuilder</h3>
 <p>
-There is a requirement to build an OM with a given object structure. A Typical scenario will be to build OM from an object structure that is returned from a data binding tool. So when the need arises to generate an OM from an object, a special builder class is to be used. The ObjectToOMBuilder class implements the XMLParserWrapper  (which is effectively the builder interface), but unlike the other builders such a conversion cannot be pull based. It is “push based” which means that the builder should have access to a content handler in order to push events. Hence the ObjectToOmBuilder implements the registerContentHandler method which accepts an instance of the SAX ContentHandler.interface.
+There is a requirement to build an OM with a given object structure. A Typical scenario will be to build OM from an object structure that is returned from a data binding tool. So when the need arises to generate an OM from an object, a special builder class is to be used. The ObjectToOMBuilder class implements the XMLParserWrapper  (which is effectively the builder interface), but unlike the other builders such a conversion cannot be pull based. It is “push based&quot; which means that the builder should have access to a content handler in order to push events. Hence the ObjectToOmBuilder implements the registerContentHandler method which accepts an instance of the SAX ContentHandler.interface.
 In serializing however the user need not worry whether the inner parts of the OM tree consists of Object builders which are push based. The serializing mechanism automatically registers a StreamToContentHandlerConverter which effectively redirects all the ContentHandler events into the relevant XMLStreamWriter. 
 The ObjectToOMBuilder expects an org.apache.axis.om.OutObject interface from the third party for registering a SAX ContentHandler. The ObjctToOMBuilder should also be supplied with the parent element which the supplied object should be serialized under. When the ObjectToOMBuilder is asked to proceed the call is in turn passed to the OutObject to fire SAX events. The ObjectToOMBuilder will take care of building the structure (if needed).</p>