You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-dev@ws.apache.org by "Dennis Sosnoski (JIRA)" <ji...@apache.org> on 2007/07/08 03:37:04 UTC
[jira] Closed: (WSCOMMONS-32) Call to
OMSourcedElementImpl.getXMLStreamReaderWithoutCaching() returns an
XMLStreamReader WITH caching
[ https://issues.apache.org/jira/browse/WSCOMMONS-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Sosnoski closed WSCOMMONS-32.
------------------------------------
> Call to OMSourcedElementImpl.getXMLStreamReaderWithoutCaching() returns an XMLStreamReader WITH caching
> -------------------------------------------------------------------------------------------------------
>
> Key: WSCOMMONS-32
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-32
> Project: WS-Commons
> Issue Type: Bug
> Components: AXIOM
> Environment: Windows XP, JBOSS4.0.3 SP1
> Reporter: Lakshmi Chaparala
> Assignee: Dennis Sosnoski
> Attachments: DataObjectOMDataSource.java
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org