Hi, We use something similar for showing dialog/flyout. The component is always in the page, but it renders itself only when it has contents. You can put your component anywhere in the page hierarchy and use Wicket events to update it.
On Fri, Jul 5, 2013 at 12:15 PM, Patrick Davids <[email protected]>wrote: > Hi all, > does anyone have a best practice putting a component on a page (as > singleton) independendly how many other components on that page "needs" it? > > e.g. a global dialog, which can be used from different components. > Not to have 20 invisible dialogs aleady rendered and opened on request. > > In out special to achieve this we do not want use page inheritence. > This component shouldn't be on page, if no other component needs it. > > thanx for help... > kind regards > Patrick > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
