Craig McClanahan wrote: > The simplest next step might be a resource-serving servlet that > behaves the way that the default resource-serving servlet does in a > Java webapp, but starts at the "public" directory instead. Every > appserver and servlet container has such a thing; unfortunately they > are not standardized so we either need to make our own (and include it > in the WAR), or create server-specific configurations for each > deployment scenario.
Well at the moment there is a file-serving servlet included as part of rails-integration, and it appears to be doing its job right. I've managed now to get both the admin pages and the main front-page of Mephisto working almost perfectly...but not at the same time. For the main page, Mephisto serves files via some dynamic routing I don't understand, in order to support its theming mechanism (i.e. provide a theme with appropriate image/css/js names under a certain dir, and Mephisto will make the site serve those versions instead). This means that for all static content served on the main page, Mephisto wants to route through Rails to decide where the content's coming from. For the admin page, Mephisto serves from a number of static paths, generally of the format (hard-coded in CSS) "/images/mephisto/something.gif". So for these files, it expects to have default static file behavior. I can configure the file servlet in Rails-integration to serve the static content for the admin pages or disable it entirely to serve the dynamically-routed static content for the main pages, but I do not know how to do both at the same time. It could be there's some magic happening in Mephisto that I don't understand...I'm certainly no Rails expert. But should this scenario be possible with the current Rails-integration code? - Charlie _______________________________________________ Jruby-extras-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/jruby-extras-devel
