[
https://issues.apache.org/jira/browse/AXIOM-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227623#comment-14227623
]
Jayashankar edited comment on AXIOM-465 at 11/27/14 12:59 PM:
--------------------------------------------------------------
Let me brief my issue further..
I have an xml that needs to go as soap header which is as follows.
<ns2:serviceRequestContextHeader xmlns:ns1="http://common.***.***.com/";
xmlns:ns2="http://ods.***.***.com/";>
<ns1:messageId>0</ns1:messageId>
<ns1:requestorDN>****</ns1:requestorDN>
</ns2:serviceRequestContextHeader>
When I sniff the soap envelope with a TCP Mon, the soap header is as follows.
<soapenv:Header>
<ns2:serviceRequestContextHeader xmlns:ns2="http://ods.**.***.com/";>
<ns1:messageId xmlns:ns1="http://common.**.***.com/";>0</ns1:messageId>
</ns2:serviceRequestContextHeader>
</soapenv:Header>
requestorDN is skipped. This used to work fine in Axiom 1.2.10
was (Author: karnj):
Let me brief my issue further..
I have an xml that needs to go as soap header which is as follows.
<ns2:serviceRequestContextHeader xmlns:ns1="http://common.***.***.com/";
xmlns:ns2="http://ods.***.***.com/";>
<ns1:messageId>0</ns1:messageId>
<ns1:requestorDN>****</ns1:requestorDN>
</ns2:serviceRequestContextHeader>
When I sniff the soap envelope with a TCP Mon, the soap header is as follows.
<soapenv:Header>
<ns2:serviceRequestContextHeader xmlns:ns2="http://ods.ing.emeldi.com/";>
<ns1:messageId xmlns:ns1="http://common.ing.emeldi.com/";>0</ns1:messageId>
</ns2:serviceRequestContextHeader>
</soapenv:Header>
requestorDN is skipped. This used to work fine in Axiom 1.2.10
> Axiom not adding child elements in soap header.
> -----------------------------------------------
>
> Key: AXIOM-465
> URL: https://issues.apache.org/jira/browse/AXIOM-465
> Project: Axiom
> Issue Type: Bug
> Components: API
> Affects Versions: 1.2.13
> Environment: Tomcat Java 6/7
> Reporter: Jayashankar
> Priority: Critical
> Fix For: 1.2.13
>
>
> Axiom not honouring the sibling nodes.
> Crazy stuff is happening in OMAbstractIterator.java in hasNext() and next()
> methods.
> used to work pretty well in 1.2.10!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
