Hi Gabriel
I have a similar setup using a JDBC realm as well as multiple
applications running on the domain so the best solution for me was to
look for the authorization header in the browser and use this info to
authenticate
Chris posted a great wiki article on how to implement a Dispatcher
Peter Stavrinides a écrit :
Hi all
My question is more of a best practice related question, I want to use
a filter to extract my authentication code from the rest of the
application logic, [...]
Thanks in advance,
Peter
Hi,
First, I'm a real Tapestry newbie, and I believe that Tapestry has
From
http://tapestry.apache.org/tapestry5/tapestry-core/guide/lifecycle.html:
"This is how Tapestry keeps you from worrying about multi-threading
issues ... the objects involved in any request are reserved to just that
request (and just that thread)."
So I think you are right. Let me amend
Hi Chris,
You wrote:
manager to retrieve page members marked as state objects with the
@ApplicationState annotation. Why? Because an instance of a page class
may be accessed simultaneously by many different requests at the same
time. In reality the annotation is just an indicator that a page
will do!
Peter
Chris Lewis wrote:
Actually by indirection it is also my problem ;-), and I'd like to
know if you find this not to be true. I have done some digging and
chatting (on this list) about this topic, and for all I've found this
appears to be how it is designed. As such I shape my id
Actually by indirection it is also my problem ;-), and I'd like to know
if you find this not to be true. I have done some digging and chatting
(on this list) about this topic, and for all I've found this appears to
be how it is designed. As such I shape my ideas and plans around this
understand
Hi Chris,
Thanks for the clarification, this is what I had initially thought...
however some quick and dirty tests made me doubt this, I am not sure why
it didn't turn up for me that way, I will have to check my code again
... not your problem anyway.
Thanks again,
Peter
Chris Lewis wrote:
Hi Peter,
I'll ask Howard to verify what I say here as its a pretty important
issue. Short answer: Yes, you will get the same instance using the state
manager as you would from injection via @ApplicationState... for
simultaneous requests made by the same user (and therefore the same
request/s
Hi Chris,
Thanks for the great wiki article, I have managed to implement what I
needed using 'Tapestry5HowToCreateADispatcher2'. My implementation is
very similar to the example... it seems to work great!
One question though regarding my ASO (which is similar to your
permissions ASO), you me
Hi Chris
Yes, this is kind of what I am looking for, I will give it a go...
Thanks
Peter
Chris Lewis wrote:
Hello Peter,
It sounds like by 'filter' you mean a servlet filter and not a
Tapestry filter. Your requirements sound a tad exotic to me, but these
wikis should get you on the right tr
Hello Peter,
It sounds like by 'filter' you mean a servlet filter and not a Tapestry
filter. Your requirements sound a tad exotic to me, but these wikis
should get you on the right track:
http://wiki.apache.org/tapestry/Tapestry5HowToCreateADispatcher
http://wiki.apache.org/tapestry/Tapestry5
11 matches
Mail list logo
