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 Samisa Abeysinghe <sa...@wso2.com> on 2009/08/07 07:42:05 UTC
Re: Including message context as a parameter in code generated
skeleton.
+1. Only problem is backward compatibility, how can we handle that?
Samisa...
On Fri, Aug 7, 2009 at 10:25 AM, Uthaiyashankar <sh...@wso2.com> wrote:
> Hi,
>
> Currently, Skeleton generated does not include message context as part
> of the method signature. For example, following is an operation
> generated in the skeleton.
>
> adb_divResponse_t* axis2_skel_Calculator_div (const axutil_env_t *env,
> adb_div_t *_div1);
>
>
> However, for some services, we need msg_ctx. Specially, if our service
> logic depends on the user name from rampart, we need to access
> msg_ctx. Can we add it as an additional parameter? Like given below:
>
> adb_divResponse_t* axis2_skel_Calculator_div (const axutil_env_t *env,
> axis2_msg_ctx_t *msg_ctx,
> adb_div_t *_div1);
>
> Thoughts?
>
> Regards,
> Shankar
>
> --
> S.Uthaiyashankar
> Software Architect
> WSO2 Inc.
> http://wso2.com/ - "The Open Source SOA Company"
>
--
Samisa Abeysinghe
Director, Engineering - WSO2 Inc.
http://www.wso2.com/ - "The Open Source SOA Company"
Re: Including message context as a parameter in code generated
skeleton.
Posted by Samisa Abeysinghe <sa...@wso2.com>.
On Fri, Aug 7, 2009 at 2:09 PM, Dimuthu Gamage <di...@gmail.com> wrote:
> +1.
>
> To keep the backward compatibility, we can given an option (or system
> property) at the code generation to set if a user want the old style code to
> generate, so by default it generate msg_ctx
Sounds good.
Samisa...
> parameter.
>
> Thanks
> Dimuthu
>
> On Fri, Aug 7, 2009 at 11:12 AM, Samisa Abeysinghe <sa...@wso2.com>wrote:
>
>> +1. Only problem is backward compatibility, how can we handle that?
>> Samisa...
>>
>>
>> On Fri, Aug 7, 2009 at 10:25 AM, Uthaiyashankar <sh...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> Currently, Skeleton generated does not include message context as part
>>> of the method signature. For example, following is an operation
>>> generated in the skeleton.
>>>
>>> adb_divResponse_t* axis2_skel_Calculator_div (const axutil_env_t *env,
>>> adb_div_t
>>> *_div1);
>>>
>>>
>>> However, for some services, we need msg_ctx. Specially, if our service
>>> logic depends on the user name from rampart, we need to access
>>> msg_ctx. Can we add it as an additional parameter? Like given below:
>>>
>>> adb_divResponse_t* axis2_skel_Calculator_div (const axutil_env_t *env,
>>> axis2_msg_ctx_t *msg_ctx,
>>> adb_div_t
>>> *_div1);
>>>
>>> Thoughts?
>>>
>>> Regards,
>>> Shankar
>>>
>>> --
>>> S.Uthaiyashankar
>>> Software Architect
>>> WSO2 Inc.
>>> http://wso2.com/ - "The Open Source SOA Company"
>>>
>>
>>
>>
>> --
>> Samisa Abeysinghe
>> Director, Engineering - WSO2 Inc.
>>
>> http://www.wso2.com/ - "The Open Source SOA Company"
>>
>
>
>
> --
> Thanks,
> Dimuthu Gamage
>
> http://www.dimuthu.org
> http://www.wso2.org
>
--
Samisa Abeysinghe
Director, Engineering - WSO2 Inc.
http://www.wso2.com/ - "The Open Source SOA Company"
Re: Including message context as a parameter in code generated
skeleton.
Posted by Dimuthu Gamage <di...@gmail.com>.
+1.
To keep the backward compatibility, we can given an option (or system
property) at the code generation to set if a user want the old style code to
generate, so by default it generate msg_ctx parameter.
Thanks
Dimuthu
On Fri, Aug 7, 2009 at 11:12 AM, Samisa Abeysinghe <sa...@wso2.com> wrote:
> +1. Only problem is backward compatibility, how can we handle that?
> Samisa...
>
>
> On Fri, Aug 7, 2009 at 10:25 AM, Uthaiyashankar <sh...@wso2.com> wrote:
>
>> Hi,
>>
>> Currently, Skeleton generated does not include message context as part
>> of the method signature. For example, following is an operation
>> generated in the skeleton.
>>
>> adb_divResponse_t* axis2_skel_Calculator_div (const axutil_env_t *env,
>> adb_div_t
>> *_div1);
>>
>>
>> However, for some services, we need msg_ctx. Specially, if our service
>> logic depends on the user name from rampart, we need to access
>> msg_ctx. Can we add it as an additional parameter? Like given below:
>>
>> adb_divResponse_t* axis2_skel_Calculator_div (const axutil_env_t *env,
>> axis2_msg_ctx_t *msg_ctx,
>> adb_div_t
>> *_div1);
>>
>> Thoughts?
>>
>> Regards,
>> Shankar
>>
>> --
>> S.Uthaiyashankar
>> Software Architect
>> WSO2 Inc.
>> http://wso2.com/ - "The Open Source SOA Company"
>>
>
>
>
> --
> Samisa Abeysinghe
> Director, Engineering - WSO2 Inc.
>
> http://www.wso2.com/ - "The Open Source SOA Company"
>
--
Thanks,
Dimuthu Gamage
http://www.dimuthu.org
http://www.wso2.org
Re: Including message context as a parameter in code generated
skeleton.
Posted by Nandika Jayawardana <ja...@gmail.com>.
+1
Nandika
On Fri, Aug 7, 2009 at 11:12 AM, Samisa Abeysinghe <sa...@wso2.com> wrote:
> +1. Only problem is backward compatibility, how can we handle that?
> Samisa...
>
>
> On Fri, Aug 7, 2009 at 10:25 AM, Uthaiyashankar <sh...@wso2.com> wrote:
>
>> Hi,
>>
>> Currently, Skeleton generated does not include message context as part
>> of the method signature. For example, following is an operation
>> generated in the skeleton.
>>
>> adb_divResponse_t* axis2_skel_Calculator_div (const axutil_env_t *env,
>> adb_div_t
>> *_div1);
>>
>>
>> However, for some services, we need msg_ctx. Specially, if our service
>> logic depends on the user name from rampart, we need to access
>> msg_ctx. Can we add it as an additional parameter? Like given below:
>>
>> adb_divResponse_t* axis2_skel_Calculator_div (const axutil_env_t *env,
>> axis2_msg_ctx_t *msg_ctx,
>> adb_div_t
>> *_div1);
>>
>> Thoughts?
>>
>> Regards,
>> Shankar
>>
>> --
>> S.Uthaiyashankar
>> Software Architect
>> WSO2 Inc.
>> http://wso2.com/ - "The Open Source SOA Company"
>>
>
>
>
> --
> Samisa Abeysinghe
> Director, Engineering - WSO2 Inc.
>
> http://www.wso2.com/ - "The Open Source SOA Company"
>
--
http://nandikajayawardana.blogspot.com/
WSO2 Inc: http://www.wso2.com