Berin Loritsch wrote:
Leif Mortenson wrote:Where would these be specified? I am already using this syntax when doing
One way around it is to specify the longer form of ${ROLE}/${type} which for the above could be translated to:
org.leif.mortenson.TJMFDataSourceProvider/capture org.leif.mortenson.TJMFDataSourceProvider/sharpen org.leif.mortenson.TJMFDataSourceProvider/detect-motion org.leif.mortenson.TJMFDataSourceProvider/output
the lookup. But the cyclical dependency is being flagged at container startup.
Are you suggesting configuring these in the @avalon.dependency meta
definitions? If so, that would not really work as the chaining order would be
not be configurable without rebuilding the application.
What about moving the dependency checks to the lookup phase rather than
the container initialization phase. Have not thought it out enough to say whether
or not that is even possible... The dependency tree needs to be worked out to
decide on a startup order, but maybe we should ignore loops at that point and
then let them be detected as components are being initialized on demand.
If the container pushed each component onto a thread local stack as it was
being initialized, it would just be a matter of checking to see whether or not the
component class is already in the stack at the start of initialization. If it is, then
we have a loop.
Cheers, Leif
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
