We have just upgraded from wicket 1.5.4 to 1.5.10 and we are getting a NullPointerException in the constructor of all the pages. It is happening because our AuthorizationStrategy.isActionAuthorized calls a method on the on our BasePage class. A NullPointerException occurrs in that method because the constructor of our BasePage has not completed.
This did not occur in 1.5.4 so something must have changed between 1.5.4 and 1.5.10 to cause the AuthorizationStrategy.isActionAuthorized method to be called in the constructor of Component. I'm guessing this may be related to a security fix? My question is this. What is the best way to handle this? I tried moving the code in the constructor of our BasePage to the onInitialize method of our BasePage but that does not fix the issue. Any suggestions? Thanks, Josh -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/NullPointerException-in-Page-constructor-tp4657502.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
