Return-Path: Delivered-To: apmail-ws-axis-c-user-archive@www.apache.org Received: (qmail 35555 invoked from network); 24 Sep 2007 09:22:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 24 Sep 2007 09:22:27 -0000 Received: (qmail 94839 invoked by uid 500); 24 Sep 2007 09:22:16 -0000 Delivered-To: apmail-ws-axis-c-user-archive@ws.apache.org Received: (qmail 94819 invoked by uid 500); 24 Sep 2007 09:22:16 -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 94798 invoked by uid 99); 24 Sep 2007 09:22:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Sep 2007 02:22:16 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [203.200.205.130] (HELO blrironp1.india.altair.com) (203.200.205.130) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Sep 2007 09:24:29 +0000 X-IronPort-AV: E=Sophos;i="4.20,290,1186338600"; d="scan'208,217";a="67503" Received: from unknown (HELO blrnms.india.altair.com) ([192.168.0.8]) by blrironp1.india.altair.com with ESMTP; 24 Sep 2007 14:51:32 +0530 Received: from blrex.prog.altair.com (blrex [192.168.0.100]) by blrnms.india.altair.com (Postfix) with ESMTP id B330427C76; Mon, 24 Sep 2007 14:51:30 +0530 (IST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C7FE8C.090F3D7E" X-MimeOLE: Produced By Microsoft Exchange V6.5 Subject: RE: How to develop a HTTPs-based webservice client Date: Mon, 24 Sep 2007 14:49:40 +0530 Message-ID: <21581D39FA3BDF40904D75AF9653CE263CC767@blrex.prog.altair.com> In-Reply-To: <21581D39FA3BDF40904D75AF9653CE263CC764@blrex.prog.altair.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: How to develop a HTTPs-based webservice client Thread-Index: Acf+iy/nLM5g2knhS8aqRK3SkKUhdAAAWWQg References: <21581D39FA3BDF40904D75AF9653CE263CC762@blrex.prog.altair.com><21581D39FA3BDF40904D75AF9653CE263CC763@blrex.prog.altair.com> <21581D39FA3BDF40904D75AF9653CE263CC764@blrex.prog.altair.com> From: "Murali Konnipati" To: "Dumindu Pallewela " , "Apache AXIS C User List " X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C7FE8C.090F3D7E Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Pallewela, Thank you very much for the reply. I have a small doubt, I need to modify the SOAP envelope and send = some custom messages in the SOAP request. For this, i am planning to use = the OperationClient. I am sending the sample SOAP request message, i need to send it to = my webservice. Please check the same and let me know, which method is = suitable for the webservice invocation. = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D SOAP Request message = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D Bert Ernie http://schemas.ggf.org/bes/2006/08/bes-factory/CreateActivity http://www.bes.org/BESFactory {Any valid JSDL document} Thanks & Regards, Murali Krishna K =20 =20 -----Original Message----- From: Dumindu Pallewela To: Apache AXIS C User List Sent: 9/24/07 2:42 PM Subject: Re: How to develop a HTTPs-based webservice client 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. >=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 <>=20 ------_=_NextPart_001_01C7FE8C.090F3D7E Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: How to develop a HTTPs-based webservice client

Hi Pallewela,

       Thank you very much for the = reply.
       I have a small doubt, I need to = modify the SOAP envelope and send some custom messages in the SOAP = request. For this, i am planning to use the OperationClient.

      I am sending the sample SOAP request = message, i need to send it to my  webservice. Please check the same = and let me know, which method is suitable for the webservice = invocation.

    = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D
     SOAP Request message
    = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D

<s11:Envelope
  xmlns:s11=3D"http://schemas.xmlsoap.= org/soap/envelope"
  xmlns:wsa=3D"http://www.w3.org/2005/08/a= ddressing"
  xmlns:bes-factory=3D"http://schemas.gg= f.org/bes/2006/08/bes-factory"
  xmlns:wsse=3D"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss= -wssecurity-secext-1.0.xsd"
  xmlns:wsu=3D"http://docs.oasis-open.org/wss/2004/01/oasis-200401-ws= s-wssecurity-utility-1.0.xsd" >
  <s11:Header>
    <wsse:Security>
      <wsse:UsernameToken = xmlns:wsse=3D"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss= -wssecurity-secext-1.0.xsd" >
        = <wsse:Username>Bert</wsse:Username>
        <wsse:Password  = Type=3D"http://docs.oasis-open.org/wss/2004/01/oa= sis-200401-wss-username-token-profile-1.0#PasswordText">Ernie= </wsse:Password>
      </wsse:UsernameToken>
    </wsse:Security>
    <wsa:Action>
       ht= tp://schemas.ggf.org/bes/2006/08/bes-factory/CreateActivity
    </wsa:Action>
    <wsa:To s11:mustUnderstand=3D1>
        http://www.bes.org/BESFactory<= BR>     </wsa:To>
  </s11:Header>
  <s11:Body wsu:Id=3D"TheBody">
        = <bes-factory:CreateActivity>
            = <bes-factory:ActivityDocument>
            &= nbsp;   <jsdl:JobDefinition>
            &= nbsp;       {Any valid JSDL document}
            &= nbsp;   </jsdl:JobDefiniton>
            = </bes-factory:ActivityDocument>
        = </bes-factory:CreateActivity>
  </s11:Body>
</s11:Envelope>


Thanks & Regards,

Murali Krishna K



 

-----Original Message-----
From: Dumindu Pallewela
To: Apache AXIS C User List
Sent: 9/24/07 2:42 PM
Subject: Re: How to develop a HTTPs-based webservice client

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.
>
> I will try to submit a small job and let you know, if i face = any
issues.
>
>
> Thanks & Regards,
>
> Murali Krishna K
>
> -----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
>
> Murali,
> "Murali Konnipati" <murali.konnipati@altair.com> = 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.
>
> thanks,
> Dinesh
>
> --
> Dinesh Premalal
> http://xydinesh.wordpress.com/
> GPG ID : A255955C
> GPG Key Finger Print : C481 E5D4 C27E DC34 9257  0229 4F44 = 266E A255
> 955C
>
> = ---------------------------------------------------------------------
= > To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-user-help@ws.apache.org
>


 <<SMIME.txt>>

------_=_NextPart_001_01C7FE8C.090F3D7E--