Re: Re: Ksoap: xmlns request parameter = " "

[email protected] wrote:
> Hi,
> Have you implement the option 1 ?

Yes, meanwhile it is implemented....
but it is completely untested and only available for the
experimental ksoap 2 version, see http://ksoap.org.

Best,
Stefan



> 
> Thanks.
> 
> 
> 
> 
>>A new node should assume its parent's name space if not told otherwise.
> 
> To
> 
>>make it worse, the current PropertyInfo does not support name spaces. So,
>>there is no way to add custom name spaces for child nodes. We HAVE TO
>>accept the "" name spaces in non-root elements in any SOAP request unless
>>we assemble the SOAP message directly from Strings ...
> 
> 
> kXML 2.1 (including the serilaizer) seems to pass
> all XmlPull conformance tests except from one, which will
> hopefully be resolved today, so I hope I can spend
> some more time on kSOAP now....
> 
> For property namespaces, there are two options:
> 
> 1. Provide a switch between inheriting namespaces from
>     the outer element, like used in MS .NET and
>     "no namespaces for properties", like in the official
>     SOAP standard
> 
> 2. Add full namespace support to PropertyInfo and/or
>     the (de)serializer
> 
>     2a) via "{namespace}name"
>     2b) using an additional namespace attribute in
>         PropertyInfo
> 
> Pro 1: Seems simpler
> Pro 2: May allow usage of SoapObject in error messages
>         etc.??
> 
> Pro 2a): No API changes needed except from internal
>           changes in the (de)serializer
> 
> Pro 2b): May be more efficient for (de)serialization
>           since some string operations may be avoided
> 
> Does anybody see additional (dis)advantages of any
> of the options...?
> 
> Best,
> Stefan
> 
> _______________________________________________
> Ksoap mailing list
> [email protected]
> http://www.enhydra.org/mailman/listinfo.cgi/ksoap