Re: [jruby-dev] JRuby under OSGi

2010-12-15 Thread Ketan Padegaonkar
On Wed, Dec 15, 2010 at 7:32 AM, Anthony Juckel wrote: > If you don't change the manifest, I assume you're requiring the builtin > folder (and other ruby/jruby libs) to be installed on the local machine in > order for require 'java' to work.  If I'm wrong in that, and you have a way > to load the

Re: [jruby-dev] JRuby under OSGi

2010-12-15 Thread Anthony Juckel
On Dec 15, 2010 8:41 AM, "Ketan Padegaonkar" wrote: > Hi, > > Here's what I've done. You may checkout http://swtbot.org/tools/ for > the final look and feel of the console. > > * Use jruby's manifest AS-IS > * Create another bundle(https://gist.github.com/742000) that: > * can manage creating and

Re: [jruby-dev] JRuby under OSGi

2010-12-15 Thread Ketan Padegaonkar
Hi, Here's what I've done. You may checkout http://swtbot.org/tools/ for the final look and feel of the console. * Use jruby's manifest AS-IS * Create another bundle(https://gist.github.com/742000) that: * can manage creating and disposing of jruby runtimes * Does a "DynamicImport-Package: *"

Re: [jruby-dev] JRuby under OSGi

2010-12-11 Thread Anthony Juckel
I've spent some time trying to update JRuby so that I could leave JRuby's bundle classloader as the default classloader (so I don't have to export builtin/* from that bundle), but still allow JRuby to load classes from other classloaders. I have something that's working for my simple test case, bu

Re: [jruby-dev] JRuby under OSGi

2010-11-30 Thread Rob Heittman
Yes, we're injecting instances of the scriptable objects as globals, and relying on a combination of OSGi, Java, and OS level security mechanisms to keep folks inside the intended sandbox. On Tue, Nov 30, 2010 at 3:23 PM, Anthony Juckel wrote: > I'm new to embedding JRuby, so I'm curious what you

Re: [jruby-dev] JRuby under OSGi

2010-11-30 Thread Anthony Juckel
On Mon, Nov 29, 2010 at 8:20 PM, Rob Heittman wrote: > I use JRuby under OSGi several places. I also have to do step #1. > > In my user story, the non-workingness of step #2 is a good thing; the OSGi > paradigm is helping restrict my REPL to see only what I mean it to -- users > can't accidentall

Re: [jruby-dev] JRuby under OSGi

2010-11-29 Thread Rob Heittman
I use JRuby under OSGi several places. I also have to do step #1. In my user story, the non-workingness of step #2 is a good thing; the OSGi paradigm is helping restrict my REPL to see only what I mean it to -- users can't accidentally/on-purpose go in and randomly exercise Java classes at will,