tag:blogger.com,1999:blog-3060516345583304229.post1787118788793911701..comments2023-06-04T06:50:29.767-07:00Comments on Ben Arciszewski Development: GWT Simple Security ConfigurationBen Arciszewskihttp://www.blogger.com/profile/02242641729372468998noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-3060516345583304229.post-20625368630079318522012-01-05T02:53:20.890-08:002012-01-05T02:53:20.890-08:00Thank you to tell us so much useful information. S...Thank you to tell us so much useful information. So nice sharing. I’m glad to read it.Sign Installationhttp://www.valleysigninstallation.comnoreply@blogger.comtag:blogger.com,1999:blog-3060516345583304229.post-40323894459429946302011-02-15T19:47:59.015-08:002011-02-15T19:47:59.015-08:00Xevi,
Thanks for pointing out the flaw in the ori...Xevi,<br /><br />Thanks for pointing out the flaw in the original. I actual made the boolean local to the onAfterRequestDeserialized method. I check and throw an exception if access is denied right there. I updated the code to reflect my changes.<br /><br />B-Ben Arciszewskihttps://www.blogger.com/profile/02242641729372468998noreply@blogger.comtag:blogger.com,1999:blog-3060516345583304229.post-11009616460211460902011-02-14T13:50:58.868-08:002011-02-14T13:50:58.868-08:00I implemented a solution like this usign more code...I implemented a solution like this usign more code.<br /><br />I found the user of onAfterRequestDeserialized very elegant, but this code has a problem. It isn't ThreadSafe because a lot of concurrent connections cat manipulate the boolean attribute.<br /><br />You must use a ThreadLocal to be ThreadSafe and mantain the elegant design. <br /><br />Regads,<br /><br />XeviAnonymousnoreply@blogger.com