axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Senaka Fernando" <>
Subject Re: [Axis2C] Client with xml declaration
Date Thu, 17 Jan 2008 05:10:22 GMT
Hi Samisa, Atanacio,

I see a valid point here in including the xml declaration in the
soap_envelope_serialize() method. However, after querying various
developers it was decided that the addition of the xml declaration was
the responsibility of the authority who does the
soap_envelope_serialize() and therefore has been added at transport
sender level. Another reason to why we took this approach is the ability
for the user to specify in the axis2.xml whether or whether not the xml
declaration has to be sent with the SOAP message. I think it is much
cleaner. One more reason was the flexibility we gain in interop
scenarios which meets the WS-I specification that the xml declaration is
optional, when it comes to sending.


On Thu, 2008-01-17 at 06:09 +0530, Samisa Abeysinghe wrote:
> Senaka Fernando wrote:
> > Hi Antonio,
> > This might work. But, I don't believe that writing the XML declaration is
> > necessarily a part of axiom_soap_envelope_serialize(). This is because,
> > logically speaking, the XML declaration is not a part of the SOAP
> > envelope.
> Logically speaking, a SOAP envelope is an XML document.
> > By doing this tweak, you are violating the concept of a SOAP
> > envelope. And, therefore this is not correct according to my personal
> > belief. Devs, please correct me if I've made any mistake.
> >
> It is nt possible to include this in OM layer, as we cannot afford to
> keep state of the start point of serialization. That would restrict our
> ability to serioalize a given node as we wish when we wish.
> Hence for me, the solution by Atanacio looks fine.
> Samisa...
> > Regards,
> > Senaka
> >

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message