Component#findParent(SomeClass.class) may be useful -igor
On Sun, Feb 28, 2010 at 1:00 PM, David Chang <[email protected]> wrote: > I have two pages. The first page is extended by the second page. On the > second page, I want to access a component on the first page. One way to do > this is to make the component a member variable of the first page. I feel > this way may have two drawbacks: > > 1. A member variable uses more resources (memory, clustring, etc.) > 2. Not all pages extending the first page may need to access this component, > which make it seem unnecessary for such pages. > > Is there any more elegant way? > > I just started Wicket programming for a personal project. Thanks for any > input! > > Regards, David > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
