Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 3013 invoked from network); 26 Dec 2007 23:10:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Dec 2007 23:10:04 -0000 Received: (qmail 51734 invoked by uid 500); 26 Dec 2007 23:09:47 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 50708 invoked by uid 500); 26 Dec 2007 23:09:45 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 50697 invoked by uid 99); 26 Dec 2007 23:09:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Dec 2007 15:09:45 -0800 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 (athena.apache.org: domain of amahmood@serena.com designates 199.201.227.27 as permitted sender) Received: from [199.201.227.27] (HELO SMX-MX.serena.dmz) (199.201.227.27) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Dec 2007 23:09:20 +0000 Received: from ord-mail.serena.com (unverified) by SMX-MX.serena.dmz (Clearswift SMTPRS 5.2.5) with ESMTP id for ; Wed, 26 Dec 2007 15:09:24 -0800 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_01C84814.5B223EB8" Subject: Can I configure Axis2 (out-of-box) to work as Proxy via WS_ADDRESING / WS_TRANSFER Date: Wed, 26 Dec 2007 15:09:23 -0800 Message-ID: <0CD5E28A763C8D4D84C690F5C463F94A4A559B@ord-mail.serena.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Can I configure Axis2 (out-of-box) to work as Proxy via WS_ADDRESING / WS_TRANSFER Thread-Index: AchIFFq3L1Eo57YKTwuwd9r/MBguqQ== From: "Aftab Mahmood" To: X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C84814.5B223EB8 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable HI =20 Is there any way in Axis2 that I can configure it to work as PROXY for routing the web service messages? Can WS_ADDRESSING module be used for this purpose? =20 For experimentation, I deployed a test web service on two instances of Tomcat and engaged them Axis2 Addressing modules. Using SOAPUI I created a sample request with end-point referring to instance-1. I modified SOAP:Header by adding TO (pointing to instance-2 URI) and ACTION as per WS_ADDRESSING specifications. I was hopping that message sent to instance-1 could route to instance-2 by axis2, but it did not. Any change in Addressing handler location in "axis2.xml" was ineffective also. =20 What does really WS_ADDRESSING handler do in Axis2?. =20 Here are some of the articles I read but could not get clear picture. =20 http://dev2dev.bea.com/pub/a/2005/01/ws_addressing_intro.html http://wso2.org/library/176 http://ws.apache.org/axis2/1_3/Axis2ArchitectureGuide.html http://www.w3.org/TR/2006/REC-ws-addr-core-20060509/ =20 I will highly appreciate few words / pointers on this topic. -- Aftab =20 ********************************************************************** This email and any files transmitted with it are confidential and intended = solely for the use of the individual or entity to whom they are addressed. = Any unauthorized review, use, disclosure or distribution is prohibited. If = you are not the intended recipient, please contact the sender by reply e-ma= il and destroy all copies of the original message.=20 ********************************************************************** ------_=_NextPart_001_01C84814.5B223EB8 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
HI
 
Is there = any way in=20 Axis2 that I can configure it to work as PROXY for routing the web service= =20 messages? Can WS_ADDRESSING module be used for this purpose?<= /DIV>
 
For exper= imentation,=20 I deployed a test web service on two instances of Tomcat and enga= ged=20 them Axis2 Addressing modules. Using SOAPUI I created a sample request with= =20 end-point referring to instance-1. I modified SOAP:Header by adding=20 TO  (pointing to instance-2 URI) and ACTION as per WS_ADDRESSING=20 specifications.  I was hopping that message sent to instance-1 could r= oute=20 to instance-2 by axis2, but it did not. Any change in  Addre= ssing=20 handler location in "axis2.xml" was ineffective also.
 
What does= really=20 WS_ADDRESSING handler do in Axis2?.
 
Here are = some of the=20 articles I read but could not get clear picture.
 
http= ://dev2dev.bea.com/pub/a/2005/01/ws_addressing_intro.html=
http://wso2.org/library/176=
http://= ws.apache.org/axis2/1_3/Axis2ArchitectureGuide.html
http://www.w3= .org/TR/2006/REC-ws-addr-core-20060509/
 
I will hi= ghly=20 appreciate few words / pointers on this topic.
--
Aftab
 

*********************= *************************************************

This email and any fi= les transmitted with it are confidential and intended solely for the use of= the individual or entity to whom they are addressed. Any unauthorized revi= ew, use, disclosure or distribution is prohibited. If you are not the inten= ded recipient, please contact the sender by reply e-mail and destroy all co= pies of the original message.

*********************= *************************************************

 

------_=_NextPart_001_01C84814.5B223EB8--