axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nandika Jayawardana <jayaw...@gmail.com>
Subject Re: Including message context as a parameter in code generated skeleton.
Date Fri, 07 Aug 2009 06:14:27 GMT
+1
Nandika

On Fri, Aug 7, 2009 at 11:12 AM, Samisa Abeysinghe <samisa@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 <shankar@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

Mime
View raw message