Dependency Management in Synapse
--------------------------------
Key: SYNAPSE-532
URL: https://issues.apache.org/jira/browse/SYNAPSE-532
Project: Synapse
Issue Type: New Feature
Components: Core
Reporter: Saliya Ekanayake
At present Synapse may fail due to dangling references. As an example consider
a proxy service which refers to a sequence. If the sequence definition is not
there it will be a dangling reference and Synapse will fail to mediate properly.
The following items are the possible items on which others may depend.
1. sequences
2. endpoints
3. local entries
4. resources in the registry (remote)
A way to overcome the issue is to resolve dependencies at start up. This,
however, has an issue since we cannot distinguish between references for local
entries and for registry. If we force the user to have all the referring items
either in local entries or in registry prior to start Synapse, then we can
clearly identify missing resources. Anyway if the user removes a used resource
from registry then again Synapse will not be able to handle it. Therefore, IMHO
it will be good to omit the dependency management on registry resources and
focus only on whatever the information available in synapse.xml.
--
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-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
