Thanks to all for suggestions and inputs.
Any suggestions on point-1 - data type mapping? for example if you check typemap.dat in case of gsoap which gives us a easy way to map data types. I am planning to take a look on code generation source code. Will it work if I change for data types?
I will update on point 5 and 6 as I started investigations on it.
/// Ashok
Nadir Amra wrote:
Axis-C++ client-side is not broken or buggy. It is perfectly functional
and in some cases much easier to use than axis2/C.
Nadir Amra
Olivier Mengué <omengue@oxymel.com> wrote on 02/10/2010 04:41:51 AM:
> [image removed]
>
> RE : Need suggestions on Axis/c client stub
>
> Olivier Mengué
>
> to:
>
> Apache AXIS C User List
>
> 02/10/2010 04:42 AM
>
> Please respond to "Apache AXIS C User List"
>
> Hi
>
> I'm a recent Axis2/C user. I don't know about Axis-C/C++.
>
> Ashok P wrote:
>
.
.
.
>
> >7) Axis-C++ is not recommended for production use. Does I need to test
> >client generated (stub) for stability considering the recommendation?
Any
> >suggestions on axis-c++ clients to be used on production? Otherwise I
need
> >go with axis-c only.
>
> The recommandation is to use Axis2/C (which is not axis-c).
> I understood it as "Axis-C++ is buggy and is broken by design, we
> choose to rewrite everything as Axis2/C". Is it really the case? I
> don't know. That is just the feeling I got by reading the site.
>
> Olivier Mengué
