You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by Manjula Peiris <ma...@wso2.com> on 2009/01/29 10:49:56 UTC
Operation and message level policies in client side
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/
Re: Operation and message level policies in client side
Posted by Uthaiyashankar <sh...@wso2.com>.
On Thu, Jan 29, 2009 at 11:23 PM, Manjula Peiris <ma...@wso2.com> wrote:
> On Thu, 2009-01-29 at 15:45 +0500, Supun Kamburugamuva wrote:
> > 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.
>
> +1. So this will be an API addition rather than an API change. And most
> users are using axis2_svc_client_set_policy.
+1
Regards,
Shankar
>
>
> >
> > Supun.
> >
> >
> > On Thu, Jan 29, 2009 at 2:49 PM, Manjula Peiris <ma...@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/
> >
>
>
--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"
Re: Operation and message level policies in client side
Posted by Manjula Peiris <ma...@wso2.com>.
On Thu, 2009-01-29 at 15:45 +0500, Supun Kamburugamuva wrote:
> 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.
+1. So this will be an API addition rather than an API change. And most
users are using axis2_svc_client_set_policy.
>
> Supun.
>
>
> On Thu, Jan 29, 2009 at 2:49 PM, Manjula Peiris <ma...@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/
>
Re: Operation and message level policies in client side
Posted by Supun Kamburugamuva <su...@gmail.com>.
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 <ma...@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/
>
>