axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Manjula Peiris <manj...@wso2.com>
Subject Re: Changing service client API for Neethi/C
Date Tue, 05 Jun 2007 11:10:22 GMT
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?

> axis2_svc_client_set_policy(svc_client, env, policy_obj );
So inside this function we can set the policy object to the description
hierarchy.
> 
> I think even PHP developers can be get benefited from this approach.
> Thoughts?
> Cheers,
> Kaushalye
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


Mime
View raw message