Hi,
Comments in-line.
-Kau
Manjula Peiris wrote:
Hi Kau,
+1 for changing the service_client API. Please see my comments
reguarding the two functions you have introduced.
On Tue, 2007-06-05 at 16:06 +0530, Kaushalye Kapuruge wrote:
Hi Devs,
Since we have Neethi/C now as the configuration model for Axis2/C and
it's modules, it might be necessary to change the service client API.
For the time being, the user has to write a lengthy code to add a policy
object. This includes FileIO, XML parsing etc. (See :
http://svn.apache.org/repos/asf/webservices/rampart/trunk/c/samples/client/sec_echo/echo_helper.c)
This logic can be hidden from user by providing a function do all this
in the service client API.
Something like this...
policy_obj = axis2_svc_client_load_policy_from_file(svc_client, env.
file_name);
Why are we passing the svc_client here? Is it just to maintain the
pattern in the service_client API?
Yes.
axis2_svc_client_set_policy(svc_client, env, policy_obj );
So inside this function we can set the policy object to the description
hierarchy.
Whatever you do here is insignificant for the user, who writes the
client. Idea is to allow user to set policies with a minimum number of
code lines.
I think even PHP developers can be get benefited from this approach.
Thoughts?
Cheers,
Kaushalye
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
