Fausto Lelli wrote: > Hi, > FileServlet approach was discussed too in the earlier stages of the plugin. > > Another approach would be remove FileServlet at all, move all static content > to the root of the web app and modify rails rounting accordingly. Thus the > servlet container would try to load the file, and fail over to rails > if it doesn't. > > Obviously this would require to change rails application directory scheme, > which is why this option was rejected.
Yeah, as a Java developers I like this, and as a Rails developer I'd absolutely hate it...so it's a tough call. I guess this is a case where I really prefer Rails way of having static content in a subdir of the app, rather than configuration as a subdir of the static content location. It's always seemed a little backward to me to have WEB-INF under the location I put all my static pages, and indeed a little wierd to mix both static pages and HTML pages in the same location, but hey, lesson learned. Why can't the RailsServlet also perform FileServlet duties, dispatching to Rails only when it can't route to a static file? - Charlie _______________________________________________ Jruby-extras-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/jruby-extras-devel
