[kepler-dev] [Bug 5175] New: Fix remaining issues with exporting multiple runs into one KAR
bugzilla-daemon at ecoinformatics.org
bugzilla-daemon at ecoinformatics.org
Mon Sep 13 12:14:28 PDT 2010
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5175
Summary: Fix remaining issues with exporting multiple runs into
one KAR
Product: Kepler
Version: 2.0.0
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: workflow run manager
AssignedTo: barseghian at nceas.ucsb.edu
ReportedBy: barseghian at nceas.ucsb.edu
QAContact: kepler-dev at kepler-project.org
Estimated Hours: 0.0
In 2.1, opening a KAR that contains two workflows and report layouts won't
necessarily open the report layouts.
The problem here is that the karEntryHandler open methods don't know what
tableauFrame an item should be associated with when opening it. I thought I had
worked around this in 2.1 by using get/setRankingTableauFrame methods to keep a
reference in the WorkflowManager singleton to the tableauFrame most recently
dealt with, but this doesn't (always?) work because it needs the items opened
in a certain order. When this bug occurs, the workflows are both opened (and
the reportDesignerPanels are associated with their respective tableauFrames),
and then the rest of the entries are dealt with. What I believe the current 2.1
code needs is for one workflow to be opened, and then its items, and then the
next workflow and its items. In detail: ReportLayoutKAREntryHandler.open calls
getRankingTableauFrame(), but what this open method sometimes needs is a
tableauFrame that's been opened prior to the current "ranking" one.
I plan to release the reporting suite with the restriction of only being able
to export 1 run into a KAR, so that 2 different solutions do not need to be
implemented for this problem (since 2.1 and trunk differ), and so that bug this
doesn't hold up the release. We can enable this functionality during the next
releases, which will be cut from trunk.
--
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