Oh, sorry. Rubyconf is over, I have not looked at the date of the
first message, shame on me :)
However I still will be grateful for the useful resources on this
topic. And looking forward for the presentation to be published
somewhere.

On Nov 19, 2:31 ¨Βν¬ Ναλσιν ΑξαξκεΌναλσιν®αξαξ®®®ΐηναιμ®γονΎ χςοτεΊ
> I would greatly appreciate some general overview of the internals. Are
> ruby files compiled into bytecode and then executed or java is invoked
> to execute code line by line. If the first option is possible how do
> you handle dynamic typing issues. Are any code optimizations applied
> to ruby code?
>
> Thanks
>
> On Nov 19, 10:58 ¨Βν¬ ΓθαςμεΟμιφες Ξυττες Όγθαςμεσ®ξυτ®®®ΐσυξ®γονΎ
> wrote:
>
> > Chris Andrews wrote:
> > > That sounds rather cool - do you have any pointers to more information?
>
> > > I've actually chosen to get into J2EE for a new project based on the
> > > ability to deploy both a Rails app and a JRuby MDB using the same app
> > > together in Glassfish, and while it wasn't that difficult (even for
> > > this EE newb), it's far from just writing some Ruby. If there was
> > > something like the equivalent of Warbler for beans, that would be
> > > ideal.
>
> > Ahh, yeah, a "Beaner" or something to package up Ruby + JRuby for EE
> > stuff. That's a good idea.
>
> > I don't have a link to it, since it's more internal discussion at this
> > point. Asking on JRuby mailing list would probably produce some
> > discussion. I believe the idea is that you would just be able to
> > configure a Ruby script or class as the MDB, for example, and GF would
> > know how to spin up JRuby and get at it. Sorta like how Spring can wire
> > in Ruby components (though Spring still ships JRuby 1.0ish, now
> > basically EOLed).
>
> > - Charlie
>
>