Jacob Kessler wrote:
I'm a bit fuzzy on gem vs. stand-alone startup, but I don't think that
that is relevant here (since I see the same behavior in stand-alone.
In Stand-alone, we create a new runtime (using JavaEmbedUtils.initialize
after setting some very basic parameters), use loadservice.require to
bring in config/environment.rb, and our rack handler, then call
call(env) on whatever rails hands to our rack handler. We tried to stay
as hands-off with the Ruby codes as possible, to try to avoid weird
things like this.
Hmm, I noticed that script/server actually requires boot.rb, not
environment.rb. Is it possible that the gem is loading the wrong thing
at startup?
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
