Thats correct. Wicket does so the access denied page in case of Authorization Exception. But the problem for me is the infinite loop. When i am returning false from the isPageAuthorized method it runs into infinite loop. It seems that in case of false return, Wicket is invoking this method again. If this method returns true, then there is no problem.
I need some clarification in overcoming this infinite loop issue if isPageAuthorized returns false. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/isPageAuthorized-method-runs-infinitely-tp2719086p2720237.html Sent from the Forum for Wicket Core developers mailing list archive at Nabble.com.
