Return-Path: Delivered-To: apmail-ws-axis-c-user-archive@www.apache.org Received: (qmail 33503 invoked from network); 24 Sep 2007 09:15:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 24 Sep 2007 09:15:32 -0000 Received: (qmail 85130 invoked by uid 500); 24 Sep 2007 09:15:22 -0000 Delivered-To: apmail-ws-axis-c-user-archive@ws.apache.org Received: (qmail 85117 invoked by uid 500); 24 Sep 2007 09:15:22 -0000 Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C User List" Reply-To: "Apache AXIS C User List" Delivered-To: mailing list axis-c-user@ws.apache.org Received: (qmail 85106 invoked by uid 99); 24 Sep 2007 09:15:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Sep 2007 02:15:22 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.68.5.15] (HELO relay01.pair.com) (209.68.5.15) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 24 Sep 2007 09:15:22 +0000 Received: (qmail 68253 invoked from network); 24 Sep 2007 09:15:00 -0000 Received: from unknown (HELO ?10.100.1.142?) (unknown) by unknown with SMTP; 24 Sep 2007 09:15:00 -0000 X-pair-Authenticated: 222.165.132.170 Message-ID: <46F77F91.5040101@wso2.com> Date: Mon, 24 Sep 2007 14:42:49 +0530 From: Dumindu Pallewela User-Agent: Thunderbird 2.0.0.6 (X11/20070907) MIME-Version: 1.0 To: Apache AXIS C User List Subject: Re: How to develop a HTTPs-based webservice client References: <21581D39FA3BDF40904D75AF9653CE263CC762@blrex.prog.altair.com><21581D39FA3BDF40904D75AF9653CE263CC763@blrex.prog.altair.com> <21581D39FA3BDF40904D75AF9653CE263CC764@blrex.prog.altair.com> In-Reply-To: <21581D39FA3BDF40904D75AF9653CE263CC764@blrex.prog.altair.com> X-Enigmail-Version: 0.95.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig49740EABC510078CA514A2A1" X-Virus-Checked: Checked by ClamAV on apache.org --------------enig49740EABC510078CA514A2A1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Murali, If you want to set the properties required for HTTPS transport, in your client code, please do the following: axutil_property_t *prop_sc =3D axutil_property_create(env); axutil_property_set_value(prop_sc, env, axutil_strdup(env, "/path/to/server/cert")); axis2_options_set_property(options, env, "SERVER_CERT", prop_sc); where *options* is the *axis2_options_t* structure that you set to the service client using *axis2_svc_client_set_options* function, or to the operation client using *axis2_op_client_set_options* function. Refer to the echo sample client's http authentication section for a sample on similar code fragment [echo.c lines 115-125]. Note that it does not depend on whether the service client or operation client is used to send the request. Other properties, if necessary, can be set in an identical manner. Property names are KEY_FILE and SSL_PASSPHRASE as described in axis2c manual [1]. HTH, -Dumindu. [1] http://ws.apache.org/axis2/c/docs/axis2c_manual.html#ssl_client Murali Konnipati wrote: > Thank you Dinesh. >=20 > I will try to submit a small job and let you know, if i face any issues= =2E >=20 >=20 > Thanks & Regards, >=20 > Murali Krishna K >=20 > -----Original Message----- > From: Dinesh Premalal > To: axis-c-user@ws.apache.org > Cc: Dinesh Premalal ; Dinesh Premalal > Sent: 9/23/07 1:32 AM > Subject: Re: How to develop a HTTPs-based webservice client >=20 > Murali, > "Murali Konnipati" writes: >> As i have to modify the SOAP envelope, i am planning to use the > Operation >> Client instead of Service Client. Can you please send me any document > with some >> examples on https web service client, which can provide some useful >> information. > It doesn't matter whether you use svc_client or op_client to send your > request. HTTPS handled by Axis2/C transport layer which is independent > from the client api that you use. I'm afraid that I don't have any > examples in my hand. I think axis2c manual's description is > descriptive enough. >=20 > thanks, > Dinesh >=20 > -- > Dinesh Premalal > http://xydinesh.wordpress.com/ > GPG ID : A255955C > GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255 > 955C >=20 > --------------------------------------------------------------------- > To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org > For additional commands, e-mail: axis-c-user-help@ws.apache.org >=20 --------------enig49740EABC510078CA514A2A1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG93+Rzt8Ztp4TFnIRAkXrAJ9V4kAwlFfgl6HE0tuOdWLGzMePCACeMbWY jDkX3Yl3FM0Tr3GNx0wIAhE= =Be7J -----END PGP SIGNATURE----- --------------enig49740EABC510078CA514A2A1--