[Wsf-general] WSRequest.options.useSOAP

[Thilina Gunarathne]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> 1) Use the WSRequest object as an "open socket" and have the stub do the
> heavy lifting of generating "raw" content (payload) and headers (options).
> 2) Encapsulate the behavior of the HTTP binding (and other bindings!) within
> the WSRequest object.  By copying a set of options that correspond fairly
> directly to the attributes in the HTTP binding, the WSRequest can formulate
> the message accordingly.
IMHO 2nd method adds much value to the WSRequest itself... +1 for that..

>   var wsr = new WSRequest();  //environment specific
>   var payload = <wrapper><param1>a</param1><param2>b</param2></wrapper>;
>   var options = new Array();
>   options.useSOAP = false;
Thought we had plans to change the name of "useSOAP" property :)...
+1 for that too..

> I have not thought much about how to handle WSDL extensions in this way.
> WS-Addressing is straightforward, WS-Security might not be so (have to look
> at the PHP solutions).  
http://www.wso2.org/wiki/display/wsfphp/WS-Security+API
http://www.wso2.org/wiki/display/wsfphp/RM+API

My only concern would be whether these things would complicate the
WSRequest...
Adding Security with the use of policies as they have done in PHP seems
to be straight forward.. But RM seems to require addition of more
methods to the API..

Thanks,
Thilina


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFGLvcSTt0cKycFPQgRArHjAJ0XQe/pGtUh6s8qbo8A85Ihy+57pACeJYCQ
nrxreAOrnGBaTrL2rsUuWo0=
=V11Z
-----END PGP SIGNATURE-----