I had a quick look at Jetty-Rails, some heavy situps done there (like extending Jetty's WebAppContext). And since I remember reading something that Jetty-Rails isn't aiming at production deployment I didn't look any closer at it (maybe I misunderstood something?).
All in all my script is just about 15 lines of Ruby code which creates the Jetty objects (server, web app context, rack filter). And I don't want JRuby-Rack to shutdown the VM, that's my script doing. It just needs to be able to detect the error condition and shut down in case (like Mongrel does, too). So my suggested changes shouldn't be critical at all. On Mon, Oct 27, 2008 at 3:41 PM, Nick Sieger <[EMAIL PROTECTED]> wrote: > On Mon, Oct 27, 2008 at 6:18 AM, Christian Seiler <[EMAIL PROTECTED]> > wrote: > > Hi, > > instead of deploying war-files I use a little Ruby script which spawns > the > > Jetty server objects including JRuby-Rack. While this worked without any > > problems with Goldspike there are a few issues with JRuby-Rack: > > > > 1) I didn't manage to point "rails.root" to the right place (gets screwed > up > > by some internal processing of the path). Therefore I patched rails.rb to > > accept a "rails.root_absolute" parameter which is used without any > further > > treatment in case it exists. > > > > 2) I added a few lines of Java code to RackServletContextListener to be > able > > to detect if errors happened during startup. In case of an error I simply > > want to shutdown the whole server/JVM. > > > > 3) I also added a config param to disable using the servlet context's > logger > > and keep the default Rails logger. > > > > > > I've attached the diffs. Should I create a Jira issue or are there any > other > > solutions for my problems? > > Thanks for the patch Christian. Have you looked at how jetty-rails > bootstraps Jetty with JRuby-Rack? > > I'll put the patch in my work queue and see if I can integrate some or > all of your changes. The only one that concerns me is shutting down > the JVM if errors happen at startup. > > Cheers, > /Nick > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
