I pushed the change by the commit, bc6fb9c. Would you help me to test the change is really working? Custom classloader issue is not easy to break down to a simple test case.
On Tue, Feb 8, 2011 at 3:56 PM, Rob Heittman <rob.heitt...@solertium.com> wrote: > Great! I've been running a modified version of 1.6.0RC1 that supports > the context method. This helps me on a multitenant system where each > tenant has its own JRuby engine, which knows how to load classes from > that tenant's GridFS. Hoping this change made things mush easier. > > I used to have to do this with JRuby-specific code to create a JRuby > runtime directly, but now I can inject the special classloader for > each tenant with JSR223. So the server can lose its hard dependency on > JRuby and let the JRuby OSGi module be loaded dynamically from the > GridFS as well. Which, in turn, means I can push out JRuby maintenance > updates to the cluster with no downtime at all! Long path to get > there, but a really great result. Interesting. Do you have blog post or something? JSR223 users who want to get that work on OSGi will be happy about that. So am I. -Yoko > > On Tue, Feb 8, 2011 at 3:28 PM, Yoko Harada <yoko...@gmail.com> wrote: >> Oh, "container." That makes sense to me. >> I'm going to work on this. Hopefully, this will be in RC2. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
