[kepler-dev] [Bug 3576] - support for accessing cascading metadata from within CompositeCoactor

bugzilla-daemon at ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Fri Oct 31 16:11:44 PDT 2008


------- Comment #1 from mcphillips at ecoinformatics.org  2008-10-31 16:11 -------
I just committed an alternative version of CompositeCoactor that supports
binding to cascading metadata (or annotations) associated directly or
indirectly with a single data token bound by the same invocation of the
composite.  This appears to work as desired.

Before propagating this change to the original source file I want to (a) verify
that the other functions of the class still work, (b) make the new feature work
for an arbitrary number of bound data tokens, and (c) add support for the '?'
qualifier indicating that the metadata is optional (i.e., that the composite
should fire even if the metadata does not exist).

More information about the Kepler-dev mailing list