synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Udayanga Wickramasinghe (Commented) (JIRA)" <>
Subject [jira] [Commented] (SYNAPSE-745) Implement a Collection of Integration Patterns for Synapse
Date Mon, 12 Mar 2012 20:14:38 GMT


Udayanga Wickramasinghe commented on SYNAPSE-745:

Hi Malith,
To give you an introduction , function templates are a mechanism to prototype mediation flows
in Synapse..Idea is to group commonly used integration patterns as a set of functions (or
  templates)..By doing so Synapse users would be able reuse this functions easily within their
mediation flow / sequence by calling up the function as required..Good starting point would
be to go through some of the existing documentation and samples on templates in [1] , [2]
and [3].. 
Also we are intending to utilize the recently introduced template libraries to implement this
collection of reusable patterns..For example it can be a "synapse.lang.eip" library to be
deployed on synapse and various eips's can be exposed via the library as function/template
modules (ie:- "Split aggregate" , "clone aggregate" , "message filter" , "recipient list"
,etc ). And more of these patterns can be found in 


I would
> Implement a Collection of Integration Patterns for Synapse
> ----------------------------------------------------------
>                 Key: SYNAPSE-745
>                 URL:
>             Project: Synapse
>          Issue Type: New Feature
>          Components: Core, Deployment
>         Environment: Any
>            Reporter: Hiranya Jayathilaka
>              Labels: gsoc2012
>             Fix For: FUTURE
> Currently there's an ongoing effort to implement the concept of functions/templates for
the Synapse configuration language (SYNAPSE-738). This provides a simple approach for implementing
support for various enterprise integration patterns (EIP) in Synapse. One could implement
a pattern as a function and then reuse it in various services and message flows in Synapse.
To make most out of this, following action items need to be completed:
> 1. Make it possible to define any Synapse component (sequences, services, endpoints,
local entries) as a reusable function
> 2. Implement a library of built-in integration patterns for Synapse (Some of the well
known patterns are documented at - It would be great to support
most of these in Synapse out of the box)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message