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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Kito D. Mann - Author, JavaServer Faces in Action http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info * Sign up for the JSF Central newsletter! http://oi.vresp.com/?fid=ac048d0e17 * > -----Original Message----- > From: Brad Smith [mailto:[EMAIL PROTECTED] > Sent: Saturday, March 24, 2007 10:36 AM > To: [email protected] > Subject: URLs and backing beans > > I have an application which needs to handle urls that have > the following > patterns: > > http://localhost:8080/myapp/projects/office1 > > http://localhost:8080/myapp/projects/office2 > > http://localhost:8080/myapp/projects/office2/subofficeA > > Conceptually I would like the request to be routed to a > single backing bean called Projects that would use the URL > content after ../projects/.. > to determine what the response should be. > > Are there features in Shale which would make this possible? > Is this where the Application Manager would come into play? > > > > Thank you, > > Brad >
