Hi,
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 startup. 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.
Resolving the remaining dependencies can be achieved by having a list of
dependents in each of the 1 - 3 elements. This list can be populated at
start time, of course an additional step is necessary to do this.
So I would like to know what you folks think about this approach.
Thanks,
Saliya
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
