On Fri, Aug 7, 2009 at 2:09 PM, Dimuthu Gamage 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...
> paramete
+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 wrote:
> +1. Only prob
+1
Nandika
On Fri, Aug 7, 2009 at 11:12 AM, Samisa Abeysinghe wrote:
> +1. Only problem is backward compatibility, how can we handle that?
> Samisa...
>
>
> On Fri, Aug 7, 2009 at 10:25 AM, Uthaiyashankar wrote:
>
>> Hi,
>>
>> Currently, Skeleton generated does not include message context as pa
+1. Only problem is backward compatibility, how can we handle that?
Samisa...
On Fri, Aug 7, 2009 at 10:25 AM, Uthaiyashankar wrote:
> Hi,
>
> Currently, Skeleton generated does not include message context as part
> of the method signature. For example, following is an operation
> generated in t
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,
ad
