[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xmlrpc-user
Subject:    [jira] [Commented] (AXIOM-255) The sequence of events produced by
From:       "Hudson (Commented) (JIRA)" <jira () apache ! org>
Date:       2011-11-28 23:41:41
Message-ID: 1777360958.20250.1322523701099.JavaMail.tomcat () hel ! zones ! apache ! org
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/AXIOM-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158942#comment-13158942 \
] 

Hudson commented on AXIOM-255:
------------------------------

Integrated in ws-axiom-trunk #725 (See \
[https://builds.apache.org/job/ws-axiom-trunk/725/])  Removed some code that has \
become obsolete with the changes in AXIOM-255 and AXIOM-335.

veithen : 
Files : 
* /webservices/commons/trunk/modules/axiom/modules/axiom-dom/src/main/java/org/apache/axiom/om/impl/dom/TextNodeImpl.java
                
* /webservices/commons/trunk/modules/axiom/modules/axiom-impl/src/main/java/org/apache/axiom/om/impl/llom/OMTextImpl.java


                
> The sequence of events produced by OMStAXWrapper for XOP:Include is inconsistent
> --------------------------------------------------------------------------------
> 
> Key: AXIOM-255
> URL: https://issues.apache.org/jira/browse/AXIOM-255
> Project: Axiom
> Issue Type: Bug
> Affects Versions: 1.2.8
> Reporter: Andreas Veithen
> Assignee: Andreas Veithen
> Fix For: 1.2.9
> 
> 
> For an Axiom tree built by MTOMStAXSOAPModelBuilder (or XOPAwareStAXOMBuilder) the \
> sequence of events produced by OMStAXWrapper (i.e. the reader returned by \
> getXMLStreamReader and getXMLStreamReaderWithoutCaching) for an XOP:Include element \
> in the underlying stream depends on the state of the tree and on whether caching is \
> enabled or not: Scenario 1: The tree has already been built. In this case \
> OMStAXWrapper produces a CHARACTER event on which the OMConstants.DATA_HANDLER \
> property can be queried. This is true both for caching enabled and disabled. \
> Scenario 2: The tree has not been built and caching is enabled. In this case \
> OMStAXWrapper produces an invalid sequence of events: namely, there is a spurious \
> END_DOCUMENT event. Except for this bug, in this case OMStAXWrapper behaves as \
> described in scenario 1. Scenario 3: The tree has not been built and caching is \
> disabled. In this case OMStAXWrapper delegates to the raw StAX stream and produces \
> START_ELEMENT and END_ELEMENT events for the XOP:Include element, leaving it up to \
> the client code to decode XOP. Conclusion:
> - When caching is disabled, the sequence of events depends on the state of the tree \
>                 (built or not).
> - The sequence of events produced by getXMLStreamReader and \
> getXMLStreamReaderWithoutCaching is not the same. Since aspects such as caching and \
> the state of the tree should be transparent to the client code, Axiom should be \
> fixed so that OMStAXWrapper produces the same sequence of events in all cases. The \
> correct sequence is the one described in scenario 1, because it is Axiom's \
> responsibility to decode XOP.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: \
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more \
information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]