Hey Thanks a lot. I guess header contributor will be the best choice. Regards, Apple Grew my blog @ http://blog.applegrew.com/
On Fri, Apr 9, 2010 at 11:31 PM, Jeremy Thomerson <jer...@wickettraining.com > wrote: > Inline.... > > On Fri, Apr 9, 2010 at 12:55 PM, Apple Grew <appleg...@gmail.com> wrote: > > > @Jeremy > > > > If generated Htmls are not cached then how does wicket achieve such good > > performance? I guess the markups are loaded in memory and the wicket > > components are filled-in at each request. Is it so? > > > Yes - the markup is parsed and cached. Then for each render, it is > attached > to those components and they render the dynamic portions.... > > > > So, if I have a <link> > > tag that points to a static url which is modified at runtime by > > AutoLinkResolver, will that too be refreshed at every request? > > > > It's been a while since I've used AutoLinkResolver, but this should be the > case. Just test and see. That's the best answer. > > > > > > @Igor > > > > CSS are are provided outside Wicket, i.e. by third party application. > > > > So if we have say 2 CSSes - all.css and base.css and, two themes - > classic > > and jazzy, then they will be available at static urls like, > > /classic-all.css > > /classic-base.css, /jazzy-all.css and /jazzy-base.css. > > > > Now if Htmls will have <link> tag in the <head>. The urls of the <link> > > will > > be modified at runtime. If generated Htmls are cached then on next access > > to > > this page the code to refresh the <link> url can't be refreshed, and it > > will > > continue to point at /classic-all.css instead of /jazzy-all.css. > > > > > But generated HTML is not cached. The best way to accomplish what you're > doing is not to put the CSS reference in the HTML, because then you have no > way to modify it. You should add the CSS reference through a header > contributor in your java code so that it is added on each request with the > right reference to your themed file(s). > > -- > Jeremy Thomerson > http://www.wickettraining.com >
