Thanks for your input. This is interesting. Somehow I got confused. Shouldn't this method be natural part of a Component? As you know, each component has child components, which is why a Wicket page has a hiearchy of components.
Let's take MarkcupContainer for the moment. Using this class means I have to add another element in the markup page, which seems complicate thhings a bit and does not seem elegant. Did I miss something? Regards. --- On Sun, 2/28/10, Major Péter <majorpe...@sch.bme.hu> wrote: > From: Major Péter <majorpe...@sch.bme.hu> > Subject: Re: Better way to find a parent compoent in page hiearchy? > To: users@wicket.apache.org > Date: Sunday, February 28, 2010, 4:20 PM > Maybe, this will be good for you: > http://wicketstuff.org/wicket13doc/org/apache/wicket/MarkupContainer.html#get(java.lang.String) > > Regards, > Peter > > 2010-02-28 22:12 keltezéssel, David Chang írta: > > igor, thanks for prompt help! > > > > I can use Component#findParent(SomeClass.class) to > find the first page. How can I further find the component by > this Wicket ID? I need to overwrite its display value. > > > > Thanks again. > > > > --- On Sun, 2/28/10, Igor Vaynberg <igor.vaynb...@gmail.com> > wrote: > > > >> From: Igor Vaynberg <igor.vaynb...@gmail.com> > >> Subject: Re: Better way to find a parent compoent > in page hiearchy? > >> To: users@wicket.apache.org > >> Date: Sunday, February 28, 2010, 4:04 PM > >> Component#findParent(SomeClass.class) > >> may be useful > >> > >> -igor > >> > >> On Sun, Feb 28, 2010 at 1:00 PM, David Chang > <david_q_zh...@yahoo.com> > >> 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: 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 > >> > >> > > > > > > > > > > > --------------------------------------------------------------------- > > 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 > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
