[
https://issues.apache.org/jira/browse/SYNAPSE-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227844#comment-13227844
]
Udayanga Wickramasinghe edited comment on SYNAPSE-745 at 3/12/12 8:13 PM:
--------------------------------------------------------------------------
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
to 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 http://www.eaipatterns.com
Regards,
udayanga
[1] http://synapse.apache.org/userguide/config.html#Templates
[2] http://synapse.apache.org/userguide/config.html#TemplateConfig
[3] http://synapse.apache.org/userguide/samples/sample750.html
was (Author: [email protected]):
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 http://www.eaipatterns.com
Regards,
udayanga
[1] http://synapse.apache.org/userguide/config.html#Templates
[2] http://synapse.apache.org/userguide/config.html#TemplateConfig
[3] http://synapse.apache.org/userguide/samples/sample750.html
> Implement a Collection of Integration Patterns for Synapse
> ----------------------------------------------------------
>
> Key: SYNAPSE-745
> URL: https://issues.apache.org/jira/browse/SYNAPSE-745
> 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 http://www.eaipatterns.com - 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
