[ 
http://issues.apache.org/jira/browse/WSCOMMONS-32?page=comments#action_12415930 
] 

Dennis Sosnoski commented on WSCOMMONS-32:
------------------------------------------

This doesn't really show much, but my guess is that something is causing the 
expansion of the tree through the OMSourcedElementImpl.forceExpand() method 
before the call to getXMLStreamReaderWithoutCaching(). It is possible for this 
to occur without a full build of the tree, though, so the 
getXMLStreamReaderWithoutCaching() should pass on the flag setting as 
originally suggested. I'll change the code to match.

They might want to look into what's triggering the call to 
OMSourcedElementImpl.forceExpand(), though. This doesn't occur in the normal 
sequence of events I've seen when using Axis2.

> 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
>     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.
-
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]

Reply via email to