[kepler-dev] [Bug 4290] - Separate the GUI from the execution engine.

[bugzilla-daemon at ecoinformatics.org]

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


berkley at nceas.ucsb.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED




------- Comment #1 from berkley at nceas.ucsb.edu  2009-08-12 14:44 -------
I've gotten off to a good start isolating the execution engine itself.  I've
added a target to the build called 'build-ptolemy-execution-engine'.  It will
build two jar files.  One with just the ptolemy moml parsing and workflow
execution facilities.  The other with just the classes for the base ptolemy
actors and directors.  More classes may need to be added in the future, but
right now these two jars represent the minimum of what kepler needs to use the
ptolemy execution engine.  It should be noted that when all of ptolemy is
jarred, it is 143MB.  The execution engine jar file is <1MB and the actor jar
file is <2MB.  

I have also created a basic API for this in kepler.  org.kepler.ExecutionEngine
(currently in loader) allows other classes to submit a workflow for execution
in either the current thread or in a new thread.  It also allows for the
addition of ExecutionListeners and the run methods return the Manager for
controlling runtime execution.  This class will probably need to be extended a
bunch, but the basics are there and it does work.  I added a junit test to test
its functionality.  You can run 'ant test -Dmodule=loader' to see it run.

After running 'ant build-ptolemy-execution-engine', you can run the following
command to see it work:

java -classpath 
   
ptII-exe/target/ptII-exe.jar:ptII-actors/target/ptII-actors.jar:util/target/util.jar:common/lib/jar/sms/commons-logging.jar 
    org.kepler.ExecutionEngine 
    /Users/berkley/project/kepler/loader/resources/test/test-model-1.xml