[kepler-dev] [Bug 4132] - Workflow Run Manager - Open in New Window is just opening the workflow, not the ROML or report

bugzilla-daemon at ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Thu Nov 12 17:42:56 PST 2009


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





------- Comment #3 from barseghian at nceas.ucsb.edu  2009-11-12 17:42 -------
I've gotten option 1 to work locally: when opening (a) run(s) from WRM, just
build a temp kar and then open it. This has the benefit of essentially using
the same code as the Open Archive action, so new code won't have to be added if
in the future we add things to KARs. To do this I exported the run(s) to a temp
KAR file. Then you must create a KARFile from this, call
KARFile.cacheKARContents(), and then you may open it. However, I first had to
remove a check in cacheKARContents that requires the KAR first be in the local
repo (I don't want temp files showing up in the local repo). This procedure
seems to work fine, everything opens. I discussed why this requirement is here
with Aaron -- it's here to ensure the local repo is a reflection of what's in
cache. Also, if someone were to open a run via the procedure I just created,
then were to click the Sources=>Build (or Refresh in the tree when this action
is implemented) button which syncs the local repo(s) w/ cache, my items would
be cleared, and any subsequent call to cache looking for them would fail (maybe
changing from the workflow tab to the report designer or report tab causes a
lookup from cache, I'm not sure offhand).

So, we discussed an alternate solution which leaves the design requirement that
allows the local repo(s) and cache stay in sync -- change open to not *require*
things first be in cache. If it's not in cache, just open it. This would fix
the bug where kars cannot be opened from arbitrary locations. This means
refactoring -- any calls in things like karentryhandlers that obtain things out
of cache should also be able to fall back on trying to just open the items out
of the kar.

I'm not clear on how much work this will be, I'm going to start trying to
see...


More information about the Kepler-dev mailing list