RE: URLs and backing beans

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/MethodBindi

SV: SV: URLs and backing beans

Hi In which case I guess Rahul's answer was more useful. Hermod -Opprinnelig melding- Fra: Brad Smith [mailto:[EMAIL PROTECTED] Sendt: 24. mars 2007 17:22 Til: user@shale.apache.org Emne: Re: SV: URLs and backing beans Thank you for the reply Hermod. I should have added that in respo

Re: URLs and backing beans

Thank you Rahul. Yes the RESTful-ness is intentional. I will look these references over. Brad On Sat, 2007-03-24 at 12:12 -0400, Rahul Akolkar wrote: > > > > > The RESTful-ness of the URLs (if that was intentional) makes it seem > like Shale Remoting [1] could be helpful here. In which case,

Re: SV: URLs and backing beans

Thank you for the reply Hermod. I should have added that in response to a url such as those in the original post, the application would return a web page with a list of projects that are active at each office. The goal is to have a bookmarkable URL without creating separate view controllers for e

Re: URLs and backing beans

On 3/24/07, Brad Smith <[EMAIL PROTECTED]> wrote: 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

SV: URLs and backing beans

Hi I'm not shure what you are looking for her but his is my understanding of it. Why would you want a backing bean for this? This is more the responsibility of an ApplicationController. What I would do is to subclass the Shale Aplication controller and add the logic you want there. You can use th

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 bac