axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Supun Kamburugamuva <supu...@gmail.com>
Subject Re: Operation and message level policies in client side
Date Thu, 29 Jan 2009 10:45:42 GMT
How about adding another method with a name like
axis2_svc_client_set_policy_with_type. We can have a default value for
axis2_policy_types in the first method.

Supun.


On Thu, Jan 29, 2009 at 2:49 PM, Manjula Peiris <manjula@wso2.com> wrote:

> Hi devs,
>
> In order to fix https://issues.apache.org/jira/browse/AXIS2C-619 we need
> to change the following function signature in the svc_client API.
>
> AXIS2_EXTERN axis2_status_t AXIS2_CALL
> axis2_svc_client_set_policy(
>    axis2_svc_client_t * svc_client,
>    const axutil_env_t * env,
>    neethi_policy_t * policy)
>
> I am proposing to add the policy_type defined in axis2_policy_include.h
> as a parameter.
>
> So the function signature will become,
>
> AXIS2_EXTERN axis2_status_t AXIS2_CALL
> axis2_svc_client_set_policy(
>    axis2_svc_client_t * svc_client,
>    const axutil_env_t * env,
>    neethi_policy_t * policy,
>    axis2_policy_types type)
>
> WDYT ?
>
> Thanks,
> -Manjula.
>
>
> --
> Manjula Peiris
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
> Blog: http://manjula-peiris.blogspot.com/
>
>

Mime
View raw message