Ok I realize this thread has been dormant for a while, but I'm back to
the issue again. First of all I neglected to mention the first time that
I'm using T5. Siddhartha, I dug into MasterDispatcher after finding it
and thinking this was how it could be done, but I haven't figured it out
yet. I've contributed to it, but the problem is that its configuration
is ordered. So what happens is any Dispatcher I contribute doesn't get
called until after all the rest (PageRender, ComponentAction, etc).
UPDATE!!!!
As I'm writing this I looked at TapestryModule again and notice that
there is an argument allowing me to manipulate where my dispatcher gets
inserted! I have to run, but if you could expand on your implementation
(assuming you can't provide code), that would be great!
Either way, thanks!
Siddhartha Argollo wrote:
I think so too.
My solution was to contribute to MasterDispatcher with a
SecurityDispatcher, that is responsible to verify if the user is
authenticated, before he has access to a page.
It is a request filter, but inside the tapestry framework, not a
servlet filter.
Chris Lewis wrote:
I apologize for being vague. I don't mean a servlet filter, I mean a
filter/filtering system with in the tapestry framework. Something
that might allow me to supply access logic before page rendering, so
that I don't have to require pages to know about the access control
system used. I know this can be implemented in pages and simplified
by subclassing, but I'm wondering if there is a cleaner way, a more
'separation of concerns' oriented way (a page is page, not an access
controller).
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
