synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Udayanga Wickramasinghe (JIRA)" <>
Subject [jira] [Commented] (SYNAPSE-928) [GSoC] Versioning of Synapse config artifacts
Date Mon, 29 Apr 2013 05:22:16 GMT


Udayanga Wickramasinghe commented on SYNAPSE-928:

This looks good and +1 for Hiranya's ideas...
However having a quick look at your configurations , i think some information in configuration/s
is redundant -->
IMO we dont need both explicit file hierachy and xml hierachy at the same time . Having both
will make it harder to manage the artifacts as well. (ie:- if we have sequence 'foo' ver 1.0
it should be either declared in XML <-sequence key="foo" version=”1.0”/> OR in the
file hierarchy NOT both ) Also which ever type we choose , this versioning strategy needs
to be maintained in Synapse Environment/Configuration (through some form of a table) in a
consistent manner across all artifacts.. 

So i think , for now It would be good to look at how the Different deployers work (ie- sequence
deployer,etc and AbstractSynapseArtifactDeployer Interface/s) in synapse and also how the
artifacts are binded to Synapse-configuration at deployment time, and Runtime Dispatchers(ie:-for
Proxy services/Tasks/APIs) . Having an sufficient idea on how they work would be useful for
you in implementing a artifact versioning lifecycle as well (we should come up with a state
diagram with lifecycle for a particular versioned artifact in the proposal some time .). 


> [GSoC] Versioning of Synapse config artifacts
> ---------------------------------------------
>                 Key: SYNAPSE-928
>                 URL:
>             Project: Synapse
>          Issue Type: Improvement
>            Reporter: Kasun Indrasiri
>            Priority: Critical
>              Labels: gsoc2013
> Currently non of the synapse artifacts fully support versioning mechanism. This feature
is to support a new versioning strategy for all such artifacts. 
> Sequence, Proxy Service, API, Endpoints 

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:

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

View raw message