On Monday 22 May 2006 05:14 pm, Charles O Nutter wrote:
> This comes back again to JRuby's startup being modelled on a
> filesystem-based distribution when we really want to move toward a binary
> jarred up distribution. It's a bit silly to have to set filesystem paths to
> use JRuby, and it would
This comes back again to JRuby's startup being modelled on a filesystem-based distribution when we really want to move toward a binary jarred up distribution. It's a bit silly to have to set filesystem paths to use JRuby, and it would be impossible once we start deploying multiple independent JRuby
On Mon, 22 May 2006, David Corbin defenestrated me:
>
> > Also send any any other thoughts on security/configuration of the runtime.
> > I am going to try and rearrange some stuff to make the BSF/JSR223
> > integration a bit easier on the brain.
>
> I haven't really figured out how it ought to wo
On Monday 22 May 2006 09:41 am, Thomas E Enebo wrote:
> Thanks for the update...David, can you mail me the properties?
"org.apache.bsf.serverLaunch"*
"user.dir"
"user.home"
"java.class.path"*
"jruby.lib"
"jruby.home"
The two marked with a * are in BSF, but the java.class.path could probably be
Thanks for the update...David, can you mail me the properties?
Also send any any other thoughts on security/configuration of the runtime.
I am going to try and rearrange some stuff to make the BSF/JSR223
integration a bit easier on the brain.
-Tom
On Sat, 20 May 2006, David Corbin defenestrate
Well, I've spent a good chunk of the day working with JRuby applets. It is
easy to write an applet, and have it run in the AppletViewer. Running it in
a real browser, however, hits security problems one after another. I had to
add 6 system properties to the java.policy file (4 for JRuby, 2 fo
