Comments on: Wicket Anti-Patterns: Avoiding Session Bloat

By: Victor

Victor — Fri, 17 Feb 2012 13:31:32 +0000

Btw, thanks for the post. Very helpful!

By: Victor

Victor — Fri, 17 Feb 2012 13:30:50 +0000

Wanted also to ask, the line
final User user = getModelObject();
in #1 (the correct way) is redundant/obsolete and should be deleted. Correct?

By: Ruslan Sh.

Ruslan Sh. — Sat, 06 Aug 2011 20:52:44 +0000

Nice post! It looks like that

final User user = getModelObject();

is redundant in the #1, the correct part of it.

By: Juraj Martinka

Juraj Martinka — Sat, 22 Jan 2011 11:34:12 +0000

Very nice post! I know it’s quite a long time ago but it would be great if you share some more experience with Wicket antipatterns.

By: Tweets that mention Wicket Anti-Patterns: Avoiding Session Bloat | Letsgetdugg -- Topsy.com

Tue, 22 Dec 2009 16:05:22 +0000

[...] This post was mentioned on Twitter by やのつとむ, Jean-Louis Rigau. Jean-Louis Rigau said: Pour poursuivre avec #Wicket : Wicket Anti-Patterns: Avoiding Session Bloat | Letsgetdugg http://bit.ly/74GSuj [...]

By: Gael Marziou

Gael Marziou — Wed, 17 Jun 2009 16:30:48 +0000

Nice post, however there is a problem in the layout of the article: the anti pattern #3 appears in the middle of a code box.

By: victori

victori — Wed, 06 May 2009 10:02:23 +0000

@gabriel

User u = FooPanel.this.getModelObject(); is referencing the passed userMdl. You don’t want to use the user object in the inner class directly or it fully gets serialized. This way only the lightweight userMdl gets serialized.

Wicket is full of surprises when it comes to session bloat if your not careful.

By: Gabriel K.

Gabriel K. — Wed, 06 May 2009 09:45:58 +0000

Nice post!

I have a question about #1.
- Do you really need both using LoadableDetachable AND
User u = FooPanel.this.getModelObject();

Why adding this last line if the IModel if Detachable?