Re: T5.3 Grid, inPlace Update and expired Sessions

2011-09-12 Thread Lenny Primak
I implemented this in my code and it works wonders. I had to override the Tynamo security login page, which isn't that easy in a good extensible manner, but this now works. I still have to monitor the session for expiration though, because if the session is gone but Shiro's 'remember me' is activa

Re: T5.3 Grid, inPlace Update and expired Sessions

2011-09-11 Thread Lenny Primak
Thanks Joost. This should work too. I will post this solution in the wiki along with mine. I didn't write the custom login page that plugs into tapestry security yet but this should work On Sep 11, 2011, at 1:06 PM, "Joost Schouten (mailing lists)" wrote: > I am not quite sure if this work

Re: T5.3 Grid, inPlace Update and expired Sessions

2011-09-11 Thread Joost Schouten (mailing lists)
I am not quite sure if this works for you as we have build our own security package that protects page and event access and redirects to the loginpage when required. On a loginpage forward we store the requested page to be redirected to after login. The trick with the AJAX call login forward we sol

Re: T5.3 Grid, inPlace Update and expired Sessions

2011-09-10 Thread Lenny Primak
I solved this problem finally by making a component somewhat derivative of tapestry-conversations moderator component. Wasn't easy in the last bit. I will post the code to wiki shortly. What it does is just redirect to the same page if sessions expires, allowing the user to relogin, or if the 'r

Re: T5.3 Grid, inPlace Update and expired Sessions

2011-09-10 Thread Lenny Primak
That would be great, but I personally would be very happy with just a redirect to the current page, which would just get me a login prompt once again, but I suppose there are deeper tapestry-related javascript issues going on here, otherwise this problem would have been licked already. On Sep 10,

Re: T5.3 Grid, inPlace Update and expired Sessions

2011-09-10 Thread Fernando Padilla
Hm.. Did someone already propose to have Tapestry-Security support a popup-login flow? So when tapestry-security hijacks a ajax request, it would return a multizoneupdate that would generate a popup-zone (tapestry doesn't have native support for those yet, but really should!); and would hand

Re: T5.3 Grid, inPlace Update and expired Sessions

2011-09-10 Thread Lenny Primak
Did anybody test tapestry-conversation under Tap 5.3 (beta 5?) I am getting ReferenceError: Can't find variable: ConversationModerator The ConversationModerator.js doesn't seem to get included into the Tapestry page, but the component is there. On Sep 10, 2011, at 12:29 PM, Lenny Primak wrote: >

Re: T5.3 Grid, inPlace Update and expired Sessions

2011-09-10 Thread Lenny Primak
Thanks, Kalle, I think this will work. I would love, if its possible, for tap-security, perhaps? to be able to redirect AJAX requests correctly to the current page or login page in case the session expired. That way, it would all work automatically, instead of showing ugly exception on the scree

Re: T5.3 Grid, inPlace Update and expired Sessions

2011-09-10 Thread Kalle Korhonen
On Sat, Sep 10, 2011 at 2:39 AM, Lenny Primak wrote: > Digging through this a bit deeper, there is an interaction going on here with > tapestry-security. > When the session expires, the user is no longer logged in, and thus > ajax call is being redirected to a login screen, thus the exceptions. >

Re: T5.3 Grid, inPlace Update and expired Sessions

2011-09-10 Thread Lenny Primak
Digging through this a bit deeper, there is an interaction going on here with tapestry-security. When the session expires, the user is no longer logged in, and thus ajax call is being redirected to a login screen, thus the exceptions. But the problem still remains the same, there seems to be no g

Re: T5.3 Grid, inPlace Update and expired Sessions

2011-09-10 Thread Lenny Primak
I tried the way Thiago suggested in the mentioned thread, but that does not work for the inPlace grid. I really, REALLY, really do not want to create/compile my own version of patched tapestry and patch tapestry.js isn't that great of an idea. - Error --- SEVERE: Even

Re: T5.3 Grid, inPlace Update and expired Sessions

2011-09-09 Thread Lenny Primak
Thanks Taha. I do think that this case should be handled by tapestry correctly by default with no patches or hacks. It's a very simple case and very common one as well. I will try the onExceotion approach but not sure it will work because the component is actually internal to the grid and not e

Re: T5.3 Grid, inPlace Update and expired Sessions

2011-09-09 Thread Taha Hafeez
Hi Lenny I handle this issue in a more generic way for all ajax calls. http://tapestry.1045711.n5.nabble.com/Tapestry-Zone-and-Expired-Session-td4634714.html#a4634757 On Sat, Sep 10, 2011 at 10:23 AM, Lenny Primak wrote: > I cannot believe that no one has run into that issue. > Seems like any

Re: T5.3 Grid, inPlace Update and expired Sessions

2011-09-09 Thread Lenny Primak
I cannot believe that no one has run into that issue. Seems like anyone that's using the AJAX Grid would face it. Please vote for https://issues.apache.org/jira/browse/TAP5-1634 if you care, or if anyone has a workaround, please suggest one. Thanks On Sep 2, 2011, at 5:24 PM, Lenny Primak wrot

Re: T5.3 Grid, inPlace Update and expired Sessions

2011-09-02 Thread Lenny Primak
Seems to me that this would be a common thing with any of the AJAX components. Should I open up a JIRA issue? On Fri, 02 Sep 2011 18:14:28 -0300, Lenny Primak wrote: > I figured that was a simple one. Should not have thought so. > all my questions are complicated, otherwise I would have not ask

T5.3 Grid, inPlace Update and expired Sessions

2011-09-02 Thread Lenny Primak
Hi, I've looked all over the Internet for this, but nothing works. I have a basic Grid pulling data from an Entity bean. Obviously, when session expires, I get the "there is no data to display" message. What I really want to do is to redirect to the current page, so the user gets to relogin and