[ http://issues.apache.org/jira/browse/WSCOMMONS-32?page=comments#action_12414063 ]
Lakshmi Chaparala commented on WSCOMMONS-32: -------------------------------------------- CORRECTION: I eliminated the OMSourcedElementImpl.getXMLStreamReaderWithoutCaching() method. This caused the superclass OMElementImpl.getXMLStreamReaderWithoutCaching() method to be executed, which properly returns the an XMLStreamReader without caching and allows the OMSourcedElementImpl to be serialized correctly. Recommend this code correction be included in the next Axiom release. Jim Peterson > Call to OMSourcedElementImpl.getXMLStreamReaderWithoutCaching() returns an > XMLStreamReader WITH caching > ------------------------------------------------------------------------------------------------------- > > Key: WSCOMMONS-32 > URL: http://issues.apache.org/jira/browse/WSCOMMONS-32 > Project: WS-Commons > Type: Bug > Components: AXIOM > Environment: Windows XP, JBOSS4.0.3 SP1 > Reporter: Lakshmi Chaparala > > I used Axis2's OMSourcedElementTest.java as an example of how to use a > custom OMDataSource. In this case you construct an OMSourcedElementImpl > class and give it your custom OMDataSource. When the service implementation > class the constructed OMSourcedElementImpl and Axiom streams it out, the > OMSerializerUtil class makes a call to > OMSourcedElementImpl.getXMLStreamReaderWithoutCaching(), which returns an > XMLStreamReader WITH caching. This sends the code down an execution path > that fails to stream the OMSourcedElementImpl because it looks for OMElement > objects that aren't there. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
