On Sun, 27 Oct 2013 11:44:42 -0200, Lenny Primak <lpri...@hope.nyc.ny.us>
wrote:
I don't think Tapestry-Security works for Ajax requests.
I think it's geared more of blocking access to pages for initial load.
I wouldn't say that before checking the source first.
How can you have AJAX requests for a page that's not authorized?
Also, in Tapestry 5.4, this should be handled properly by way T5.4
handles JavaScript.
I'm not following you.
onActivate isn't getting called because Tapestry-Security / Shiro
intercepts it (and denies it's permission)
before onActivate ever gets called.
The statement above would make me think that Tapestry-Security does work
for AJAX requests too, as onActivate() is invoked for every request for
the page, render or action.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
