[
https://issues.apache.org/jira/browse/SYNAPSE-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475947#comment-13475947
]
Malith Dhanushka commented on SYNAPSE-745:
------------------------------------------
Hi Udayanga,
It's with great pleasure i continue my contribution in future. I really
appreciate and thankful for your great support throughout the project.
If i bit elaborate more about newly introduced parameter syntax of,
- Content Based Router
parameters - routing_exp
match_content ( syntax -
"IBM:cnd1_seq,MSFT:cnd2_seq;cnd3_seq"
User can define multiple matching conditions using "," splitter. regular
expressions and target sequence should be separated by inserting":". And
finally default sequence needs to be defined after inserting ";". If there is
no any target sequence defined for a particular regular expression , default it
will be mediated to the main sequence)
- Dynamic Router
parameters - conditions ( syntax -
"header=foo:bar.*{AND}url=/services/;seq=seq1,header=header1:bar.*{OR}header=header1:foo.*;seq=seq2,header=header2:foo.*;seq=seq3"
User can define multiple routing rules by using "," splitter. To match
HTTP headers use "header=regEx:seqRef" . header source and regular expression
should be separated by inserting ":" .To match HTTP url, use url=/url . Then
target sequence needs to be defined after inserting ";" . Also one can
use"{AND}"as to specify logical AND , "{OR}" as to specify logical OR to match
multiple headers and url in expression)
Thanks,
Malith
> 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
>
> Attachments: EIPLibraryDocumentation.patch,
> EIPSamplesIntegration.patch, EIP_SynapseLib_Initial.zip, EIP_SynapseLib.zip,
> import1.xml, SimpleTestProxy.xml, SYNAPSE-745-eiplibcore.zip,
> SynapseEipLibSamples.patch, SynapseLib_with_classloading.zip
>
>
> 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)
> Goals
> 1. Implement a library of identified set of built-in integration patterns
> using synapse templates and template libraries
> 2. Sample and Test integration into Synapse for eip pattern libararies
> 3. Improve Documentation around the eip pattern libararies
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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]
