[ http://issues.apache.org/jira/browse/AXIS2-55?page=comments#action_12317484 ]
Eran Chinthaka commented on AXIS2-55: ------------------------------------- Dims, this has a small problem. If the first child of the SOAPEnvelope is a Text, then setting the SOAPHeader as the first child is not correct, IMO. This text may be just set of spaces or /n, but I think we have to preserve it. Plus, what do we do if user is trying to add SOAPHeader, when alreadt there is a SOAPHeader. The same argument is there for the body. So IMO, there is a limit, we can interfere with this. So I agree with the first option of what Srinath has suggested to have a SOAPEnvelope already filled with a SOAPHeader and SOAPBody. There is another idea for this, but this works only for the serialization. When we serialise we can override the serialize method of the SOAPEnvelope, so that it will first serialise the Header and then the body. But then again there is a problem with Text nodes. And this approach will not preserve the memory model. What do you all think about this issue ? We better agree on something before we go to the next release. > Children order in SOAPElements > ------------------------------ > > Key: AXIS2-55 > URL: http://issues.apache.org/jira/browse/AXIS2-55 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: om > Reporter: Eran Chinthaka 2 > Assignee: Eran Chinthaka > > All the SOAPElements uses the children methods of the OMElement. So ordering > of elements are not according to the spec, if they are not added properly. > For example, if one add a body and then a header to the soap envelope, the > serialisation and the chidlren order within the envelope is the order it was > added. Not header first and then body. -- 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
