Return-Path: Delivered-To: apmail-synapse-dev-archive@www.apache.org Received: (qmail 48374 invoked from network); 9 Nov 2009 05:45:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 9 Nov 2009 05:45:38 -0000 Received: (qmail 43622 invoked by uid 500); 9 Nov 2009 05:45:38 -0000 Delivered-To: apmail-synapse-dev-archive@synapse.apache.org Received: (qmail 43548 invoked by uid 500); 9 Nov 2009 05:45:38 -0000 Mailing-List: contact dev-help@synapse.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@synapse.apache.org Delivered-To: mailing list dev@synapse.apache.org Received: (qmail 43538 invoked by uid 99); 9 Nov 2009 05:45:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Nov 2009 05:45:38 +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 (nike.apache.org: domain of supun06@gmail.com designates 209.85.160.52 as permitted sender) Received: from [209.85.160.52] (HELO mail-pw0-f52.google.com) (209.85.160.52) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Nov 2009 05:45:27 +0000 Received: by pwj9 with SMTP id 9so255423pwj.11 for ; Sun, 08 Nov 2009 21:45:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=UJLQwJytgi8Dp4ijLPI415G3UawxO5gnmQIc4cItLGI=; b=LvqECwmsXkH4PX+FZUJ5a684Drhn58bvlw61k5EQ/beW2RjZbvMURuz/i39iwy5k6P 6jTV5rJrnBCpdtlCSifW4XDgepeZrm/EpAkMZVt2c2SNa+txEyfzDbtpxqEvOjZXaMPO uwR+vvk/SS31fl71He4nw2QSkqsS/kE/eyj4M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=HnZJr1UuA0VYfyRGNQWkyrNvFgr9Hys94AhzJweVuEB1RFTxl7AfNjEOPd3aXVIkSS B+SHU+Xx6gNkxBHGL0cjDrLAxBMJrIaWt0dzpekI7ICSj/C/j8Cp4YTVDwG/Ju4em/Ik OPRFZqqF/JSbWsx/8v35eeMCzkV2SqRgwUbRg= MIME-Version: 1.0 Received: by 10.143.26.39 with SMTP id d39mr706489wfj.223.1257745505722; Sun, 08 Nov 2009 21:45:05 -0800 (PST) In-Reply-To: References: Date: Mon, 9 Nov 2009 11:15:05 +0530 Message-ID: Subject: Re: Service chaining From: Supun Kamburugamuva To: dev@synapse.apache.org Content-Type: multipart/alternative; boundary=001636e0ae4d1621fe0477e9b29d X-Virus-Checked: Checked by ClamAV on apache.org --001636e0ae4d1621fe0477e9b29d Content-Type: text/plain; charset=ISO-8859-1 Hi Indika, Thanks for the feedback. Actually I thought about your suggested approach as well. But if we want to do something complex, this approach can become pretty hard to implement and maintain. Or it can be very difficult to implement in some cases. But with my approach the Synapse configuration become logical and easy. Thanks, Supun.. On Mon, Nov 9, 2009 at 10:39 AM, indika kumara wrote: > Spun we can do the service chaining with synapse . one resource is [1] > which does the message chaining with a proxy service. You should be > able to do same thing even with the main sequence (put response true > property and call the new service endpoint within the out mediator). > > Could you please critically evaluate the existing approaches and your > suggestions? > > And... +1 For keeping and retrieving non string properties. > Thanks > Indika > > [1] > http://adroitlogic.org/knowledge-base-synapse/11-message-chaining-with-synapse.html > > On Mon, Nov 9, 2009 at 2:28 AM, Supun Kamburugamuva > wrote: > > Hi all, > > > > Ability to call one service, then use that result to call another service > > and so on is a very important feature in any ESB. But this is hard to > > implement in the current Synapse configuration language unless we are > using > > something like callout mediator. > > > > But with a simple improvement we can get close to achieving full message > > mediation. The improvement is to allow the user to specify a receiving > > sequence to the send mediator. When the response comes to this send, it > will > > be directed to the receiving sequence instead of a predefined sequence > like > > main or outSequence. > > > > send (response to sequence 1) --------> sequence 1 (do some > > transformations), send (response to sequence 2) --------> sequence 2, > send > > the response back. > > > > Just having this functionality does not complete the whole service > chaining > > requirements. We need a way to store the request and responses and access > > them from different mediators. To do this we may need to improve the > > property mediator and improve the xpath functions. > > > > I have created a Jira for the first requirement and attached a patch [1]. > > That is to send with a receiving sequence. Please have a look at it and > > provide your feedback. I'm always open to improvements :). > > > > [1] https://issues.apache.org/jira/browse/SYNAPSE-593 > > > > Thanks, > > Supun.. > > > > -- > > Software Engineer, WSO2 Inc > > http://wso2.org > > supunk.blogspot.com > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org > For additional commands, e-mail: dev-help@synapse.apache.org > > -- Software Engineer, WSO2 Inc http://wso2.org supunk.blogspot.com --001636e0ae4d1621fe0477e9b29d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Indika,

Thanks for the feedback. Actually I thought about your su= ggested approach as well. But if we want to do something complex, this appr= oach can become pretty hard to implement and maintain. Or it can be very di= fficult to implement in some cases. But with my approach the Synapse config= uration become logical and easy.

Thanks,
Supun..

On Mon, Nov 9, 200= 9 at 10:39 AM, indika kumara <indika.kuma@gmail.com> wrote:
Spun we can do the service chaining with synapse . one resource is [1]
which does the message chaining with a proxy service. You should be
able to do same thing even with the main sequence (put response true
property and call the new service endpoint within the out mediator).

Could you please critically evaluate the existing approaches and your
suggestions?

And... +1 For keeping and retrieving non string properties.
=A0
Thanks
Indika

[1] http://adroitlogic.org/knowledge= -base-synapse/11-message-chaining-with-synapse.html

On Mon, Nov 9, 2009 at 2:28 AM, Supun Kamburugamuva <supun06@gmail.com> wrote:
> Hi all,
>
> Ability to call one service, then use that result to call another serv= ice
> and so on is a very important feature in any ESB. But this is hard to<= br> > implement in the current Synapse configuration language unless we are = using
> something like callout mediator.
>
> But with a simple improvement we can get close to achieving full messa= ge
> mediation. The improvement is to allow the user to specify a receiving=
> sequence to the send mediator. When the response comes to this send, i= t will
> be directed to the receiving sequence instead of a predefined sequence= like
> main or outSequence.
>
> send (response to sequence 1) --------> sequence 1 (do some
> transformations), send (response to sequence 2) --------> sequence = 2, send
> the response back.
>
> Just having this functionality does not complete the whole service cha= ining
> requirements. We need a way to store the request and responses and acc= ess
> them from different mediators. To do this we may need to improve the > property mediator and improve the xpath functions.
>
> I have created a Jira for the first requirement and attached a patch [= 1].
> That is to send with a receiving sequence. Please have a look at it an= d
> provide your feedback. I'm always open to improvements :).
>
> [1] https://issues.apache.org/jira/browse/SYNAPSE-593
>
> Thanks,
> Supun..
>
> --
> Software Engineer, WSO2 Inc
> http://wso2.org
> supunk.blogsp= ot.com
>
>
>

---------------------------------------------------------------= ------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org




--
Software Engineer, WSO2= Inc
http://wso2.org
supunk.blogspot.com


--001636e0ae4d1621fe0477e9b29d--