Re: Optional wrapping H1 tag

I'd do it like this: h1 wicket:id=logo-h1 a wicket:id=logo-home.../a /h1 add(new WebMarkupContainer(logo-h1) { void onConfigure() { super.onConfigure(); setRenderBodyOnly(!getPage().getClass().equals(Homepage.class)); } }.add(new Link...)); In other words: only render the H1

Re: Session invalidation and background thread

Hi, I guess it depends on the lifecycle of those threads how I would handle this. Suppose the session is invalidated and destroyed, what should happen to the threads? Do they continue (A) or do they need to stop (B)? A) In this case I would not depend on the session at all, if possible.

Re: Session invalidation and background thread

Bas, Thanks for your answer. I understand what you're saying and you're right. If I were designing the application now I'd do one of your suggestions. But unfortunately we've written most of the code and these threads now depend on spring session beans. Right now B is pretty much the only viable

Re: Optional wrapping H1 tag

Thanks for the answers, everyone! On Sat, Nov 23, 2013 at 5:20 AM, Bas Gooren b...@iswd.nl wrote: I'd do it like this: h1 wicket:id=logo-h1 a wicket:id=logo-home.../a /h1 add(new WebMarkupContainer(logo-h1) { void onConfigure() { super.onConfigure();