I don't understand the question. I may be viewing the same web page as you, but that doesn't mean we should share the same computer display monitor. If there are two copies of the display (yours and mine), then there should be two copies of the display's components.
What's wrong with just building the model for each user's component around the same application-scoped Java POJO? (Of course, you might have to synchronize concurrent access to it, but that's just standard Java.) On Thu, May 13, 2010 at 12:38 PM, Ayodeji Aladejebi <[email protected]>wrote: > > Please any concept of shared components in Wicket. If I have a component > that the content (model) will always be the same across all sessions and > users, is there a wicket api approach for ensuring we only have one of such > components throughout the application scope --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
