Details
-
New Feature
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
The groovy remote project - http://groovy.codehaus.org/modules/remote/ - works by sending the bytes of a closure class (and all nested closures) over to the server to be used to define the class(es) there so the closure instance can be unserialised and executed.
This currently works by searching the classpath for the closure .class files. This doesn't work when the closures weren't compiled beforehand, such as when using groovy from the command line or the groovy console.
It would be great to have a foolproof way of getting the bytes that define a closure class and all the closure's it uses in a way that was agnostic to how the closure was defined/compiled to use here.