[kepler-dev] [Bug 4988] Instantiating a wf as a composite that has a tag doesn't work as expected

bugzilla-daemon at ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Fri Jan 14 14:47:44 PST 2011


http://bugzilla.ecoinformatics.org/show_bug.cgi?id=4988

Sean Riddle <swriddle at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #2 from Sean Riddle <swriddle at gmail.com> 2011-01-14 14:47:44 PST ---
(In reply to comment #0)
> However if I tag a workflow, Save Archive it into my local repo workflows
> folder, then find and expand this KAR in the component library gui and drag the
> workflow out to canvas, the parent does not get the tag. If I open the
> composite, it's not in there either.

This is expected behavior. The tag bar displays all tags on the top-level
workflow. The tag is displayed in the original workflow, when it is on the
top-level. When that workflow is instantiated into another as a composite, the
tag is now on the composite, not on the top-level workflow, so it is not
displayed in the tag bar. The tag's presence on the composite can be confirmed
by selecting the Semantic Annotation Pane from the context menu of the
composite.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the Kepler-dev mailing list