synapse-dev mailing list archives

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


Hiranya Jayathilaka commented on SYNAPSE-928:

I agree. We don't need the file hierarchy. The reason Axis2 has this file hierarchy concept
is because it has to deal with binary artifacts. But Synapse artifacts are text (XML) based.
So we can easily encode the versioning information in the artifact itself. No separate file
hierarchy is required. However it would be useful to look at the exact semantics supported
by Axis2 with regard to this (e.g. how the request dispatching works for different versions
of the same service). I think it makes sense to support the same semantics in Synapse. Again,
file hierarchy is just an Axis2 specific implementation detail, and we don't need that.

Another related issue that popped into my mind is how we are going to support versioning for
Synapse library artifacts. Now these are binary artifacts (Udayanga, please correct me if
I'm wrong). So first of all we need to determine whether we are going to support that - does
it make sense? If so how?
> [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