Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>
Received-SPF: pass (nike.apache.org: domain of amra@us.ibm.com designates
 32.97.182.139 as permitted sender)
In-Reply-To: <27518586.post@talk.nabble.com>
References: <27518586.post@talk.nabble.com>
To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>
Cc: axis-c-user@ws.apache.org
MIME-Version: 1.0
Subject: Re: Need suggestions on Axis/c client stub
Message-ID: 
 <OF72D0D3FB.AD358040-ON862576C6.0003DC65-862576C6.000432AD@us.ibm.com>
From: Nadir Amra <amra@us.ibm.com>
Date: Tue, 9 Feb 2010 18:45:23 -0600
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

As far as the Axis-C++ client, it is recommended for production use....as=20
long as you build the client from the latest code in SVN.

But ensure that it supports what you need supported, which is WSDL 1.1 and =

SOAP 1.1.=20

Nadir Amra


Ashok P <ashvitech@gmail.com> wrote on 02/09/2010 11:09:09 AM:

> [image removed]=20
>=20
> Need suggestions on Axis/c client stub
>=20
> Ashok P=20
>=20
> to:
>=20
> axis-c-user
>=20
> 02/09/2010 11:09 AM
>=20
> Please respond to "Apache AXIS C User List"
>=20
>=20
> I want to clear my understandings about axis-c/c++. I got few answers in
> email archives and like to understand thoroughly.  Newbie to Axis-c.. :) =

 I
> apologize for any repeated  questions.=20
>=20
> 1) Can I provide custom mappings for C/C++ data types for code=20
generation
> tool?
> Wsdl2c/wsd2ws generates the code for xs:string as ?char* (axis-char)?=20
and
> ?std::string? respectively. Is there any way to mention mapping like
> ?wchar*?  or std::wstring (c++) to toolkit considering Unicode enabled
> project?   Does char* processing problematic in case of Unicode string?=20
>=20
> 2) My requirement is to generate the clients for non-axis web services=20
like
> .net, JBOSS-WS, etc. So Is there any limitations for such clients? I=20
believe
> all web services can easily consumed with axis/c client considering they
> adhere with WSDL specifications.=20
>=20
> 3) As per the  documentation, axis-c supports ?ADB? binding for client=20
code
> generations and ?none? option for raw xml in/out. Is ADB is efficient to
> consume non-axis web services?=20
>=20
> 4) As per analysis, wsdl2c can generate client code for RPC/document=20
literal
> styles only. Am I correct? Is there any support available for=20
RPC-encoded
> style in near feature?
>=20
> 5) Does it mandatory to use axis2.xml? I like all these settings through
> code by settings the options ? like settings the protocol ?http? or=20
https
> (ssl), port , ssl certificate, client timeout and more. Does such=20
provision
> is available in both C/C++ client generated code?
>=20
> 6)  From the other posting on forum, it?s not clear that ?AXIS2C=5FHOME?
> deplorer folder is mandatory or not for client side. Can anybody confirm
> this? I agree few Dlls are required for client distribution. I like my
> client application (along with client stub) should have small footprint=20
for
> distribution, so can I build stub statically for depended libraries like
> axiom.dll, axis2=5Fhttp=5Fsender.dll etc?
>=20
> 7) Axis-C++ is not recommended for production use. Does I need to test
> client generated (stub) for stability considering the recommendation?=20
Any
> suggestions on axis-c++ clients to be used on production? Otherwise I=20
need
> go with axis-c only.
>=20
>=20
> Thanks in advance and appreciate your help.
>=20
>=20
> --=20
> View this message in context: http://old.nabble.com/Need-
> suggestions-on-Axis-c-client-stub-tp27518586p27518586.html
> Sent from the Axis - C++ - User mailing list archive at Nabble.com.
>=20