Return-Path: Delivered-To: apmail-ws-axis-c-user-archive@www.apache.org Received: (qmail 94712 invoked from network); 10 Aug 2009 16:36:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Aug 2009 16:36:02 -0000 Received: (qmail 34192 invoked by uid 500); 10 Aug 2009 16:36:09 -0000 Delivered-To: apmail-ws-axis-c-user-archive@ws.apache.org Received: (qmail 34163 invoked by uid 500); 10 Aug 2009 16:36:09 -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 34154 invoked by uid 99); 10 Aug 2009 16:36:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Aug 2009 16:36:09 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [165.251.13.90] (HELO corp-msg3.ps-dmz-corp.easylink.com) (165.251.13.90) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Aug 2009 16:36:01 +0000 Received: from MSGSRV1.netmaster.corp.easylink.com ([10.40.40.21]) by corp-msg3.ps-dmz-corp.easylink.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 10 Aug 2009 12:35:39 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA19D8.8DFFD38E" Subject: Logging Requests and responses sent by axis2c client Date: Mon, 10 Aug 2009 12:35:21 -0400 Message-ID: <759627BF6F2B53419569F8B24182BD8F05D4B2E4@MSGSRV1.netmaster.corp.easylink.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Logging Requests and responses sent by axis2c client Thread-Index: AcoZ2I7TAs+Kt8M8RpqHl6Pi0PFI+Q== From: "Raghu Udupa" To: X-OriginalArrivalTime: 10 Aug 2009 16:35:39.0808 (UTC) FILETIME=[98A54A00:01CA19D8] X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. ------_=_NextPart_001_01CA19D8.8DFFD38E Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I am using axis2c client to communicate with an external web service. I am trying to use logging module (libaxis2_mod_log.so) =20 I want to capture outbound message sent by the axis2c client as well inbound successful as well as error responses received from the external service by the client. =20 Here is the XML excerpt in axis2c.xml. I am not sure whether these settings are correct for client sending messages to the server. =20 =20 =20 =20 My other problem is that, even though I am configuring the client to engage logging module, logging module is not being engaged. I do see rampart and addressing modules being engaged in the log. But I do not see anything about logging module. =20 I appreciate your response regarding this problem. =20 Regards, Raghu ------_=_NextPart_001_01CA19D8.8DFFD38E Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I am using axis2c client to communicate with an = external web service. I am trying to use logging module = (libaxis2_mod_log.so)

 

I want to capture outbound message sent by the axis2c = client as well inbound successful as well as error responses received from the = external service by the client.

 

Here is the XML excerpt in axis2c.xml. I am not sure whether these settings are = correct for client sending messages to the = server.

 

   <module name=3D"logging" class=3D"axis2_mod_log">

         =        <inflow>

         =             &= nbsp;  <handler name=3D"LoggingInHandler" class=3D"axis2_mod_log">

         =             &= nbsp;          <order = phase=3D"PreDispatch"/>

         =             &= nbsp;  </handler>

         =        </inflow>

         =        <outflow>

         =             &= nbsp;  <handler name=3D"LoggingOutHandler" class=3D"axis2_mod_log">

         =             &= nbsp;      <order = phase=3D"MessageOut"/>

         =             &= nbsp;  </handler>

         =        </outflow>

 

         =        <outfaultflow>

         =             &= nbsp;  <handler name=3D"LoggingOutHandle" class=3D"axis2_mod_log">

         =             &= nbsp;          <order = phase=3D"MessageOut"/>

         =             &= nbsp;  </handler>

         =        </outfaultflow>

 

    = </module>

 

My other problem is that, even = though I am configuring the client to engage logging module, logging module is not = being engaged. I do see rampart and addressing modules being engaged in the = log. But I do not see anything about logging module.

 

I appreciate your response regarding this = problem.

 

Regards,

Raghu

------_=_NextPart_001_01CA19D8.8DFFD38E--