synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thilini Shanika (JIRA)" <>
Subject [jira] [Commented] (SYNAPSE-928) [GSoC] Versioning of Synapse config artifacts
Date Sat, 01 Jun 2013 05:13:20 GMT


Thilini Shanika commented on SYNAPSE-928:

Hi all,
The proposal of 'Versioning of Synapse Configuration Artifacts' (
is been accepted for Google Summer of Code 2013. I'm willing to add further improvements 
to my proposal as mentioned below.
Under the 'Proposed Solution Approach' of the proposal, I missed to include some facts regarding
runtime perspective of versioned artifact. In runtime, dispatching request to a versioning
artifact is going to be handled by following the conversion process of the unique identifier
and mapping the unique identifier with the relavent versioned artifact.
Further in my proposal,as deliverables, I'm willing to provide a complete set of solid test
cases to test new versioning feature, covering all synapse artifact and to integrate those
test cases into test automation framework of Synapse.
> [GSoC] Versioning of Synapse config artifacts
> ---------------------------------------------
>                 Key: SYNAPSE-928
>                 URL:
>             Project: Synapse
>          Issue Type: Improvement
>            Reporter: Kasun Indrasiri
>            Assignee: Udayanga Wickramasinghe
>            Priority: Critical
>              Labels: gsoc2013, mentor
> 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