Return-Path: Delivered-To: apmail-axis-c-user-archive@www.apache.org Received: (qmail 34251 invoked from network); 21 Jul 2010 10:40:27 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 21 Jul 2010 10:40:27 -0000 Received: (qmail 5395 invoked by uid 500); 21 Jul 2010 10:40:27 -0000 Delivered-To: apmail-axis-c-user-archive@axis.apache.org Received: (qmail 5221 invoked by uid 500); 21 Jul 2010 10:40:24 -0000 Mailing-List: contact c-user-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache AXIS C User List" Delivered-To: mailing list c-user@axis.apache.org Received: (qmail 5205 invoked by uid 99); 21 Jul 2010 10:40:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Jul 2010 10:40:23 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rickomuer@gmail.com designates 74.125.82.51 as permitted sender) Received: from [74.125.82.51] (HELO mail-ww0-f51.google.com) (74.125.82.51) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Jul 2010 10:40:15 +0000 Received: by wwb22 with SMTP id 22so627753wwb.32 for ; Wed, 21 Jul 2010 03:39:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=sYrskgDi+2+/g1hiktc7DLI+vDvHOlKor8cG6SGeiNg=; b=cIV0zc8x/Z7N86gCWYvCPwGRINLgbhUOmO0kGm6YKoh8+SRLZXfKEURFWxCQZUJlaU djguTYIlKKLibQvHgEM0mnYq+DPWuuJ/iMN5uNTkRJvQ6QrdH9JXIdTBwh9eaOFcQijK Kf07AfUwCgdA9TLrWqK1I5hJ31ba+guf0PzCw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=M/a9E7YzxQAve5r81Ey0aRewHSOlHZlVXrxoS7r45ESaP/GztaX44Ens62ZZHKJyQg xwjUwFvM4Ow52L8ReU4eaglHKmGvU+hA2zxGRvgtwI6iWR9Y3IVfmHO4G77lmd+TALK8 scyYLB91RBjV/EHTN/78h3IHnEtVW01f4Ppls= MIME-Version: 1.0 Received: by 10.227.94.138 with SMTP id z10mr6824746wbm.166.1279708746437; Wed, 21 Jul 2010 03:39:06 -0700 (PDT) Received: by 10.216.176.146 with HTTP; Wed, 21 Jul 2010 03:39:06 -0700 (PDT) Date: Wed, 21 Jul 2010 11:39:06 +0100 Message-ID: Subject: Retriving value from Soap Header From: Rico M To: Apache AXIS C User List Content-Type: multipart/alternative; boundary=000e0cd217563f562b048be36921 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd217563f562b048be36921 Content-Type: text/plain; charset=ISO-8859-1 Assuming my message is as follows: 100 Hello Server! How can one retirve transaction ID value.? I did read there was a work around for this , but i have not come across it. I can see the following API's playing a role. - AXIS2_EXTERN struct axiom_soap_header *AXIS2_CALL axiom_soap_envelope_get_header( axiom_soap_envelope_t * envelope, const axutil_env_t * env); - AXIS2_EXTERN axiom_children_qname_iterator_t *AXIS2_CALL axiom_soap_header_examine_all_header_blocks(axiom_soap_header_t * header, const axutil_env_t * env); How is the envelope of a response payload found? Offtopic: I seem to be running into trivial yet time consuming issues with doing simpler things. I wanted to know if i can use my own API' ( or something like libxml2 ) to create/read soap messsages and the underlying framework of axis2/c to send/recieve them? Is there an example of the same available ? Cheers! --000e0cd217563f562b048be36921 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Assuming my message is as follows:

&= lt;soap:Envelope xmlns:soap=3D"http= ://www.w3.org/2003/05/soap-envelope" xmlns:xsi=3D"htt= p://www.w3.org/1999/XMLSchema-instance" xmlns:xsd=3D"http://www.w= 3.org/2001/XMLSchema">

<= soap:Header>

=20 <TransactionId>100</TransactionId>

</MyHeader>

<soap:Body>

<greet>Hello Server!</greet>

</soap:Body></soap:Envelope>= ;

How can one retirve transaction ID value.?

I= did read there was a work around for this , but i have not come across it.= =A0

I can see the following API= 9;s playing a role.

- =A0=A0 AXIS2_EXTERN struct axiom_soa= p_header *AXIS2_CALL=A0=A0=A0=20 axiom_soap_envelope_get_header( axiom_soap_envelope_t * envelope, const=20 axutil_env_t * env);

-=A0 =A0=A0 AXIS2_EXTERN axiom_children_qname_iterator_t= *AXIS2_CALL axiom_soap_header_examine_all_header_blocks(axiom_soap_header_= t * header, const axutil_env_t * env);

How i= s the envelope of a response payload found?

Offtopic: I seem to be running into trivial yet time consuming issues with = doing simpler things. I wanted to know if i can use my own API' ( or so= mething like libxml2 ) to create/read soap messsages and the underlying fra= mework of axis2/c to send/recieve them? Is there an example of the same ava= ilable ?

C= heers!

--000e0cd217563f562b048be36921--