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

List:       xmlrpc-user
Subject:    [jira] [Commented] (AXIOM-282) Get Payload QName information without building OMElement
From:       "Hudson (Commented) (JIRA)" <jira () apache ! org>
Date:       2012-02-25 10:53:48
Message-ID: 1545271614.19365.1330167228697.JavaMail.tomcat () hel ! zones ! apache ! org
[Download RAW message or body]


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

Hudson commented on AXIOM-282:
------------------------------

Integrated in ws-axiom-trunk #797 (See \
[https://builds.apache.org/job/ws-axiom-trunk/797/])  Implemented a regression test \
for r631687 (AXIOM-282). (Revision 1293553)

     Result = SUCCESS
veithen : 
Files : 
* /webservices/commons/trunk/modules/axiom/modules/axiom-impl/src/main/java/org/apache/axiom/om/impl/llom/OMContainerHelper.java
                
* /webservices/commons/trunk/modules/axiom/modules/axiom-testsuite/src/main/java/org/a \
pache/axiom/ts/soap/envelope/TestGetSOAPBodyFirstElementLocalNameAndNSWithParser.java

                
> Get Payload QName information without building OMElement
> --------------------------------------------------------
> 
> Key: AXIOM-282
> URL: https://issues.apache.org/jira/browse/AXIOM-282
> Project: Axiom
> Issue Type: Improvement
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> 
> Problem:
> The Axis2 code invokes MessageContext.isFault() before starting the phases.  This \
> causes an Axiom tree to be built up to and including the first child element \
> (payload) in the soap body.   The problem is that the phases might have special \
> CustomBuilders.  Building the Axiom tree past the payload can defeat these kinds of \
> optimizations. Solution1:
> The first solution is tactical and will work with all parsers.  The proposal is to \
> add some simple, protected "look ahead" code in the StaXOMBuilder.   The Axiom \
> SOAPBody can use this information to determine whether the payload is a fault, \
> without actually building the object.    I am working on the tests and code for \
> this first solution, and will have it ready in the next day or two. Solution 2:
> The second solution is support a custom property on the parser.  The SOAPEnvelope \
> can then call the custom property on the backing parser to get the soap body \
> payload qname.   The idea is that the parser (woodstox or ibm, etc.) may have \
> already looked ahead in the text before the StAX events are fully pulled. The \
> benefit of this solution is that calls, like MessageContext.isFault(), will not \
> cause the expansion of the header elements.    I will work on this solution after \
> solution 1 is done.  I don't have a proposed name for the property yet. (Note that \
> both of these solutions will require some minor changes to the Axis2 code.) P.S. I \
> am working with Takahide Nogayama on these changes. Thanks,
> Rich Scheuerle

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