Perhaps during development mode there should be a warning message if Wicket sees any fields on any components that are of type Page (or a subclass thereof)? Or, even if the actual object is a page (the variable type could be some interface), it should spit out a warning telling you to use PageReference instead?
On Tue, May 18, 2010 at 8:37 AM, Wilhelmsen Tor Iver <toriv...@arrive.no> wrote: >> Well, I think that's quite obvious when you consider that each page is >> the "root" of a "tree" (not directed, acyclic graph) of components. >> Each component can have at most one parent. > > But you can pass a component to a different page/component without adding it; > like in the example of having a "back link" which wants a page to navigate > back to. If you keep that Page in an instance variable in the "back-from" > Page you will needlessly serialize that, too, unless you use a PageReference. > > - Tor Iver > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
