Besides what is put in the session, you also have got to take into
account what will be serialized/ copied as a change for back button
support. This is where potential problems with annonymous classes
start, as while you are looking for keeping a rather small change, you
get the whole page with eve
Added to the wiki at http://www.wicket-wiki.org.uk/wiki/index.php/Best_Practices_and_Gotchas#Wicket_Servlet_Mapping
regards
On 12/27/05, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
What you do here is quite harmless... The page is already in the
session (page map and all), so the extra reference t
Sorry.
At http://www.wicket-wiki.org.uk/wiki/index.php?title=Best_Practices_and_Gotchas#Anonymous_Inner_classes
On 12/27/05, Alexandre Bairos <[EMAIL PROTECTED]> wrote:
Added to the wiki at http://www.wicket-wiki.org.uk/wiki/index.php/Best_Practices_and_Gotchas#Wicket_Servlet_Mapping
regards
On
What you do here is quite harmless... The page is already in the
session (page map and all), so the extra reference to it doesn't hurt.
The problem comes when you attach a business object to your page:
/** Dont do this */
class MyPage extends WebPage {
private MyVeryLargeObject subject;
/
