Despite frameworks as jsf, wicket manages lightweight components. It would be adding more complexity to something that is pretty simple. Furthermore, I don't think you will performance better. The important fact in any case is that the browser caches it.
On Thu, May 13, 2010 at 12:38 PM, Ayodeji Aladejebi <aladej...@gmail.com>wrote: > Hi, > > 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 > > -- > Aladejebi Ayodeji A., > -- Fernando Wermus. www.linkedin.com/in/fernandowermus
