[
https://issues.apache.org/jira/browse/SYNAPSE-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647832#comment-13647832
]
Hiranya Jayathilaka commented on SYNAPSE-928:
---------------------------------------------
To answer your previous question, the artifact file names are actually not
important in Synapse. Synapse doesn't infer any information out of artifact
file names. So it's only the artifact XML content that matters. For example if
a sequence definition says:
<sequence name="foo" version="1.0">
...
</sequence>
that explicitly states the version of the sequence is 1.0. The above artifact
could be stored in a file named foo.xml, foo-v1.0.xml or even bar.xml. Synapse
doesn't take the file name into count.
However when internally representing different versions of the same artifact,
you might have to take both artifact name and version and somehow combine them
into a single, unique identifier. This could be as simple as
concat(name,version) or hash(concat(name,version)). I believe there's already a
system in place for APIs to handle this. You should be able to use the same
approach.
> [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
> 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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
