[kepler-dev] [Bug 3150] - Need to add PTII Python actors back into Kepler

bugzilla-daemon@ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Mon Feb 18 16:26:26 PST 2008


------- Comment #1 from cxh at eecs.berkeley.edu  2008-02-18 16:26 -------
The issue here is that Jython, the Java implementation of Python, writes
a cache file for each jar file in the class path.  This results in the
following problems:

1) Slow start up time, see
This is the reason the Jython actors were pulled.  Part of the problem
is that Kepler was loading all the actors at start up, which was causing
the Jython actor to create a cache file for each jar file in the classpath.
I'm not sure if Kepler is still loading all the actors at startup or not.

2) The caching tends to fail with applets and other security restricted 
situations.  This could prevent Jython actors from working in a distributed
environment.  If Kepler always invokes the Jython caching mechanism on 
startup, then Kepler could fail to start in a sandbox.

The Jython project has show some activity in 2007, perhaps the caching has
changed, though a quick review of the Jython website does not show anything

I just updated $PTII/lib/jython.jar to Jython2.2.1.

More information about the Kepler-dev mailing list