[ 
https://issues.apache.org/jira/browse/WSCOMMONS-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rich Scheuerle resolved WSCOMMONS-194.
--------------------------------------

    Resolution: Fixed

This problem is fixed.  

> SOAPEnvelope getHeader processing
> ---------------------------------
>
>                 Key: WSCOMMONS-194
>                 URL: https://issues.apache.org/jira/browse/WSCOMMONS-194
>             Project: WS-Commons
>          Issue Type: Bug
>            Reporter: Rich Scheuerle
>
> There are a few fundamental problems in the header processing in 
> SOAPEnvelopeImpl
> 1) The getHeader method sometimes adds missing header elements and sometimes 
> it does not.  This violates the javadoc for the method and is the kind of 
> random behavior that should be avoided.  (In addition, when the current code 
> adds a header it causes a full expansion of the om tree.)
> 2)  The SOAPEnvelopeImpl.addChild method is improved to consider the parser 
> state when adding the header.  In the current code it is possible that this 
> method will add the header twice, or add the header after the body.  
> (!) I also discovered that searching for missing headers can also cause the 
> full expansion of the om tree.  The culprit in such cases was the misuse of 
> the getElementByName method.  But I see that these errors have already been 
> fixed in the current version of the code.  (Thank you to the kind soul who 
> discovered this already !) 
> I have run all of the axiom and axis2 tests with my new changes, which I will 
> be adding shortly.
> These changes were found by the IBM Performance Analysist team.   Special 
> thanks to David Strite for detecting the om expansion problem!
> Thanks,
> Rich

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to