[
https://issues.apache.org/jira/browse/SYNAPSE-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912437#action_12912437
]
Hiranya Jayathilaka commented on SYNAPSE-384:
---------------------------------------------
>From the Synapse PoV a registry is simply an interface. The user can implement
>the interface and plug-in any external repository to Synapse. The same model
>can be used to:
1. Support a read-only registry
2. Support an archived registry
3. Support multiple registries
For instance WSO2 ESB which is based on Apache Synapse does something similar.
In WSO2 ESB, Synapse is linked up with WSO2 Governance Registry which in turns
is a combination of three separate registries. Synapse makes use of all three
repositories through the same implementation class. I guess something similar
can be done to the support your requirements as well. But I don't think this
should be part of core Synapse distribution. These are highly advanced and
customized usecases.
> Archived Repository and Read-Only Registry
> ------------------------------------------
>
> Key: SYNAPSE-384
> URL: https://issues.apache.org/jira/browse/SYNAPSE-384
> Project: Synapse
> Issue Type: Improvement
> Environment: Any
> Reporter: Tanmay saha
>
> Synapse should support archived repository ( in jar or zip format ) and
> Read-Only Registry ( meaning config meta-data can only be read from archived
> Repository). This will help operation or support team to deploy in various
> environment easily.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
