Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 81429 invoked from network); 21 Apr 2006 13:14:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 21 Apr 2006 13:14:08 -0000 Received: (qmail 41645 invoked by uid 500); 21 Apr 2006 13:13:49 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 41415 invoked by uid 500); 21 Apr 2006 13:13:48 -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 41404 invoked by uid 99); 21 Apr 2006 13:13:48 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Apr 2006 06:13:48 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of robertlazarski@gmail.com designates 64.233.166.178 as permitted sender) Received: from [64.233.166.178] (HELO pproxy.gmail.com) (64.233.166.178) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Apr 2006 06:13:45 -0700 Received: by pproxy.gmail.com with SMTP id b29so455234pya for ; Fri, 21 Apr 2006 06:13:25 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=jg4mR+0ShkTZrVE+QSLuwHfc72/kH0yFx45YWuj7gEsAhKe+80OpIOvUnKkCXdft3nnyRgqpvniNgLR3Y9LQefxvRBZnymWphhJDN3QOFraH5x/EUvrVDz84jXN2TxMCzVERa0HKnuvliYcgOH9vlNJZHJjTUBiavKOxaKMGnFY= Received: by 10.35.15.11 with SMTP id s11mr2634335pyi; Fri, 21 Apr 2006 06:13:25 -0700 (PDT) Received: by 10.35.46.12 with HTTP; Fri, 21 Apr 2006 06:13:25 -0700 (PDT) Message-ID: Date: Fri, 21 Apr 2006 10:13:25 -0300 From: "robert lazarski" To: axis-user@ws.apache.org Subject: Re: SOAP Intermediary with Axis In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_5044_24862546.1145625205272" References: X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_5044_24862546.1145625205272 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Not sure I quite get what you're after yet - but there is the soap monitor that does the abstraction you seem to be looking for. It uses handlers. HTH, Robert http://www.braziloutsource.com On 4/21/06, Rishikesh.Mallesh@atradius.com wrote: > > >> Use a Handler ? > > OK but how? Not sure exactly how this works out. > > > > I have used handlers when they are part of the request/response flow > within the ultimate receiver node. But say if my intermediary is on a > different network node and I want to forward all messages that come to my > intermediary to the ultimate receiver, then what I require is the SOAP > intermediary to forward the request on to the ultimate receiver. Say > something like the TCP monitor but at a SOAP level message level of > abstraction rather than a TCP level. > > > > Cheers > > > > > > > > > ------------------------------ > > *From:* robert lazarski [mailto:robertlazarski@gmail.com] > *Sent:* 21 April 2006 13:53 > *To:* axis-user@ws.apache.org > *Subject:* Re: SOAP Intermediary with Axis > > > > Use a Handler ? > > HTH, > Robert > http://www.braziloutsource.com > > > On 4/21/06, *Rishikesh.Mallesh@atradius.com* > wrote: > > Hi Everyone, > > > > I have a question regarding writing SOAP intermediaries. I wanted to writ= e > a SOAP node that sits between the sender and ultimate receiver of a SOAP > message. > > > > Question is how can I do this in Axis? > > > > Cheers > > Rishi > > > > > > > -------------------------------------------------------------------------= ----------------------------------- > This message is intended for the addressee or its representative only. > Any form of unauthorized use, publication, reproduction, copying or > disclosure of the content of this e-mail is not permitted. If you are > not the intended recipient of this e-mail message and its contents, > please notify the sender immediately and delete this message and > all its attachments subsequently. > > > ------=_Part_5044_24862546.1145625205272 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Not sure I quite get what you're after yet - but there is the soap monitor that does the abstraction you seem to be looking for. It uses handlers.

HTH,
Robert
http://www.braziloutsource.com

On 4/21/06, Rishikesh.Malle= sh@atradius.com <Rishikesh.Ma= llesh@atradius.com> wrote:

>> Use a Handl= er ?

OK but how? Not sure exactly how t= his works out.

 

I have used handlers when they are= part of the request/response flow within the ultimate receiver node. But say if my = intermediary is on a different network node and I want to forward all messages that come= to my intermediary to the ultimate receiver, then what I require is the SOAP i= ntermediary to forward the request on to the ultimate receiver. Say something like the = TCP monitor but at a SOAP level message level of abstraction rather than a TCP level.

 

Cheers

 

 

 

 

From:= robert lazarski [mailto:robert= lazarski@gmail.com]
Sent: 21 April 2006 13:53<= br> To: axis-user@ws.apache.org
Subject: Re: SOAP Intermed= iary with Axis

 

Use a Handler ?

HTH,
Robert
http://www.braziloutsource.com
 

On 4/21/06, Rishikesh.Mallesh@atradius.com <Rishikesh.Mallesh@atr= adius.com > wrote:

Hi Everyone,

 

I have a question regarding writing SOAP intermediaries. I wanted to write a SOAP node that sits between the sender = and ultimate receiver of a SOAP message.

 

Question is how can I do this in Axis?

 

Cheers

Rishi

 



---------------------------------------------------------------------------= ---------------------------------
This message is intended for the addressee or its representative only.
Any form of unauthorized use, publication, reproduction, copying or
disclosure of the content of this e-mail is not permitted. If you are
not the intended recipient of this e-mail message and its contents,
please notify the sender immediately and delete this message and
all its attachments subsequently.

 


------=_Part_5044_24862546.1145625205272--