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

bugzilla-daemon at ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Wed Oct 21 16:15:30 PDT 2009


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

           Summary: Module dependencies in MoML files
           Product: Kepler
           Version: 1.x dev
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: core
        AssignedTo: aschultz at nceas.ucsb.edu
        ReportedBy: aschultz at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org


To reproduce:  
Save a KAR from the WRP suite
change to the kepler suite
on startup you see the error: 
Error encountered in: <property name="TOP Provenance Recorder"
class="org.kepler.provenance.ProvenanceRecorder">
etc....

I used to think this was an issue with the startup building of the library and
that dependencies in the KARs was the problem.  But it turns out to be much
more malicious.  It is actually a dependency from the MoML file itself. 
Because the WRP suite has the Provenance recorder included in the moml, when
the provenance module is not around the error is displayed and the workflow can
not be used.  So this means that any moml file generated by the WRP suite
cannot be run in the Kepler suite.  Unlike in Reporting where the reporting
files are separate from the MoML itself and therefore the MoML can still run in
the Kepler suite.

So the task here is to figure out how to add a dependency on the provenance
module to all the workflows that are created from the WRP suite.  The ability
to do this I think is not built into the KAR design and I'll have to figure out
how to do it.


More information about the Kepler-dev mailing list