Thanks Kito. I was also considering a servlet filter approach but am leaning towards a custom Processor implementation based on Shale's remoting as you and Rahul recommend.
My only lingering concern is the need to have the url end in the same extension that the JSF servlet is expecting (html in this case). I suppose I could append an "index.html" on every URL but that has a slight code "smell". :) That is Remoting (and JSF) will require http://localhost:8080/myapp/projects/office2/index.html instead of http://localhost:8080/myapp/projects/office2 in order to properly process the request. Brad On Sat, 2007-03-24 at 17:24 -0400, Kito D. Mann wrote: > Brad, > > I often use a Servlet filter for this type of stuff, but a cleaner approach > might be to use Shale Remoting (http://shale.apache.org/remoting). The > process() method in your MethodBindingProcessor > (http://shale.apache.org/1.0.4/shale-remoting/apidocs/org/apache/shale/remot > ing/impl/MethodBindingProcessor) implementation could load the projects, set > the veiw id, and jump to the render response phase.
