> This might not be Wicket's intended way to use getApplication But is > there a real serious reason to make getApplication final?
It's one of these methods we actually wanted to get rid off in the long term. It would be best to have just one way to get the application: MyApplication.get(). Same goes for session and request cycle. > Which problem so I run into when I use this pattern? Well, not a problem per se, but it's just in general not good to have multiple ways to do the same thing in an API. Eelco
