You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Tanmay saha (JIRA)" <ji...@apache.org> on 2008/07/01 21:42:45 UTC
[jira] Created: (SYNAPSE-384) Archived Repository and Read-Only
Registry
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Assigned: (SYNAPSE-384) Archived Repository and Read-Only
Registry
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiranya Jayathilaka reassigned SYNAPSE-384:
-------------------------------------------
Assignee: Ruwan Linton
> 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
> Assignee: Ruwan Linton
>
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-384) Archived Repository and Read-Only
Registry
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-384) Archived Repository and Read-Only
Registry
Posted by "Stefan Lecho (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632364#action_12632364 ]
Stefan Lecho commented on SYNAPSE-384:
--------------------------------------
It would be interesting that Synapse supports *multiple* archived repositories. Reasoning a little bit further ... it would be nice if Synapse supported a repository directory that can contain multiple SyanpseARchive (.SAR) files that are included to "build" the complete repository. Each SAR contains a group of related proxies, targets, endpoints, ....
This would even more facilitate the deployment in various environments, because only a specific SAR could be re-deployed without impacting existing services.
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org