From: Martin K. <mar...@fe...> - 2008-03-24 09:58:27
|
Hi, I just commited a fix to SOAP-Lite/trunk adressing https://sourceforge.net/tracker/index.php?func=detail&aid=1604320&group_id=66000&atid=513017 As Mikhail Gusarov correctly states, the WS-I basic profile does not allow a part of a rpc/literal operation message to contain xsi:nil="true". However, this attribute may be required by document/literal webservices, and might be required (I don't know) by rpc/encoded webservices. For document/literal, I think that stubmaker should set up the parameters to be encoded with the nil attribute when required. Does anyone know how rpc/encoded webservices behave? Martin Am Montag, den 24.03.2008, 02:01 -0700 schrieb kut...@us...: > Revision: 218 > http://soaplite.svn.sourceforge.net/soaplite/?rev=218&view=rev > Author: kutterma > Date: 2008-03-24 02:01:27 -0700 (Mon, 24 Mar 2008) > > Log Message: > ----------- > - fixes [ 1604320 ] xsi:nil on part accessor in argless message > This needs discussion: The removal of the xsi:nil="true" attribute on an empty method may break document/literal and rpc/encoded webservices. > > Modified Paths: > -------------- > trunk/Changes > trunk/lib/SOAP/Serializer.pm > trunk/t/SOAP/Serializer.t > > > This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > soaplite-commit mailing list > soa...@li... > https://lists.sourceforge.net/lists/listinfo/soaplite-commit > |