[kepler-dev] [Bug 5290] originModule not always set

[bugzilla-daemon at ecoinformatics.org]

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

--- Comment #2 from Derik Barseghian <barseghian at nceas.ucsb.edu> 2011-11-10 19:16:11 PST ---
Ok, what's happening is reporting and workflow-run-manager override some
properties in gui and common's configuration. When you override a property it
doesn't get the originModule subproperty. If these configs get written to disk,
and you switch back to e.g. vanilla, you'll get errors on startup. I believe
this is a shortcoming with our current system. I'm not sure the
solution...should overridden properties be written out  along side the
originals with an originModule subproperty, and we change the ConfigManager to
choose the appropriate property based on what modules are active? This doesn't
seems especially appealing or easy.

Most of the properties reporting and wrm override could actually instead be
simply added with addProperty, thus getting originModule subproperties and
avoiding the problem -- but unfortunately we have at least one that I think
needs to be a true override, wrm's <viewPaneTabPanes><viewPane>Workflow.

We could possibly punt by putting the two new workflow-scheduler-gui properties
in workflow-scheduler-gui's configuration (these are the only 2 properties in a
soon to be published module that cause the problem that I know of -- but Dan
may need to chime in wrt fault-tolerance), but I'd have to discuss that with
Jing. We decided where he currently has them seems like the best place.

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