[kepler-dev] [Bug 4483] - Module dependencies in MoML files

[bugzilla-daemon at ecoinformatics.org]

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





------- Comment #12 from welker4kepler at gmail.com  2009-10-22 15:27 -------
If you are going to implement a temporary solution, I think you should instead
just save the current active configuration in the kar file. That is much
simpler for developers and will always work.

Also, I have been thinking about this, and I think part of the problem is
basically Kepler restart. My concern with a module specifying incorrect
dependencies is if those incorrect dependencies lead to an unnecessary restart
of Kepler. You could imagine a situation where two workflows are in fact
compatible, but when you load one or another you find that you need to restart.

I think you should hold off on the idea of having a String transport mechanism
because then we have to think about how we are going to specify dependencies
and I don't think we should be specifying them at such a low level without
thinking about the implications. Saving the active configuration to the kar, by
contrast, is both very simple to implement, requires not extra work for
developers, and is very simple to back out of if and when we come up with a
better solution.