Mailing-List: contact dev-help@synapse.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@synapse.apache.org
Date: Mon, 29 Apr 2013 05:22:16 +0000 (UTC)
From: "Udayanga Wickramasinghe (JIRA)" <jira@apache.org>
To: dev@synapse.apache.org
Message-ID: <JIRA.12643160.1366275472207.240612.1367212936421@arcas>
In-Reply-To: <JIRA.12643160.1366275472207@arcas>
References: <JIRA.12643160.1366275472207@arcas>
Subject: [jira] [Commented] (SYNAPSE-928) [GSoC] Versioning of Synapse
 config artifacts
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/SYNAPSE-928?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D136=
44276#comment-13644276 ]=20

Udayanga Wickramasinghe commented on SYNAPSE-928:
-------------------------------------------------

Hi,
This looks good and +1 for Hiranya's ideas...
However having a quick look at your configurations , i think some informati=
on in configuration/s is redundant -->
IMO we dont need both explicit file hierachy and xml hierachy at the same t=
ime . 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 <-s=
equence key=3D"foo" version=3D=E2=80=9D1.0=E2=80=9D/> OR in the file hierar=
chy NOT both ) Also which ever type we choose , this versioning strategy ne=
eds to be maintained in Synapse Environment/Configuration (through some for=
m of a table) in a consistent manner across all artifacts..=20

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

Regards,
Udayanga


               =20
> [GSoC] Versioning of Synapse config artifacts
> ---------------------------------------------
>
>                 Key: SYNAPSE-928
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-928
>             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 artifac=
ts.=20
> Sequence, Proxy Service, API, Endpoints=20

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org