probably the code redirects to login page, but the login page is not authorized, so it redirects to login page, but the login page is not authorized.
-igor On Wed, Sep 29, 2010 at 7:08 AM, hemilshah <[email protected]> wrote: > > Hi, > > I have a authorization mechanism in my application. I have a class which > extends Wicket AbstractPageAuthorizationStrategy class. It has a overridden > method isPageAuthorized() as required by Wicket to implement Authorization > logic. > > Now, if this method returns false then the functionality runs in infinite > loop. I am not sure why this is happening. Following is the code snippet - > > protected boolean isPageAuthorized(final Class pageClass){ > > return isAuthorized((PubSession)Session.get(), pageClass); > > } > > public static boolean isAuthorized(PubSession ses, Class pageClass){ > > if (a = b) > return false; // Here it runs in infinite loop > > } > > Please help me to solve this problem. > > Thanks. > Regards, > Hemil > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/isPageAuthorized-method-runs-infinitely-tp2719086p2719086.html > Sent from the Forum for Wicket Core developers mailing list archive at > Nabble.com. >
