page).
Other than that: using LDM's and DataView/DataProvider instead of
ListView will help considerably.
Martijn
May I ask what LDM is? Is that Lightweight Data Model?
--
View this message in context:
http://www.nabble.com/Wicket-Session-grows-too-big-real-fast-tp20697077p20802687
you reference in your
page).
Other than that: using LDM's and DataView/DataProvider instead of
ListView will help considerably.
Martijn
--
View this message in context:
http://www.nabble.com/Wicket-Session-grows-too-big-real-fast-tp20697077p20702093.html
Sent from the Wicket
With Wicket 1.3 only one page should be stored in session. You should
check if you don't keep references between pages - that would result
in 1+N pages (with N being the number of pages you reference in your
page).
That's optimized though, so shouldn't typically be a problem. See the
custom
/DataProvider instead of
ListView will help considerably.
Martijn
May I ask what LDM is? Is that Lightweight Data Model?
--
View this message in context:
http://www.nabble.com/Wicket-Session-grows-too-big-real-fast-tp20697077p20754276.html
Sent from the Wicket - User mailing list archive
LoadableDetachableModel
Jeremy Thomerson
http://www.wickettraining.com
-- sent from a wireless device
-Original Message-
From: Flavius [EMAIL PROTECTED]
Sent: Saturday, November 29, 2008 9:40 PM
To: users@wicket.apache.org
Subject: Re: Wicket Session grows too big real fast
Martijn
will
be very tedious. Any help to the problem, or more accurate ways to pinpoint
the problem, would be greatly appreceated.
BR,
Jukka
--
View this message in context:
http://www.nabble.com/Wicket-Session-grows-too-big-real-fast-tp20697077p20697077.html
Sent from the Wicket - User mailing list archive
://www.nabble.com/Wicket-Session-grows-too-big-real-fast-tp20697077p20697077.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED
, or more accurate ways to pinpoint
the problem, would be greatly appreceated.
BR,
Jukka
--
View this message in context:
http://www.nabble.com/Wicket-Session-grows-too-big-real-fast-tp20697077p20697077.html
Sent from the Wicket - User mailing list archive at Nabble.com
page).
Other than that: using LDM's and DataView/DataProvider instead of
ListView will help considerably.
Martijn
--
View this message in context:
http://www.nabble.com/Wicket-Session-grows-too-big-real-fast-tp20697077p20697523.html
Sent from the Wicket - User mailing list archive
.
Jukka
Johan Compagner wrote:
if you make this:
final Recommendation recommendation = (Recommendation)
item.getModelObject();
not final does it compile?
If it doesnt then you have a leak
johan
--
View this message in context:
http://www.nabble.com/Wicket-Session-grows-too-big
it entirely.
Jukka
Johan Compagner wrote:
if you make this:
final Recommendation recommendation = (Recommendation)
item.getModelObject();
not final does it compile?
If it doesnt then you have a leak
johan
--
View this message in context:
http://www.nabble.com/Wicket-Session-grows-too
).
Other than that: using LDM's and DataView/DataProvider instead of
ListView will help considerably.
Martijn
--
View this message in context:
http://www.nabble.com/Wicket-Session-grows-too-big-real-fast-tp20697077p20697523.html
Sent from the Wicket - User mailing list archive
- that would result
in 1+N pages (with N being the number of pages you reference in your
page).
Other than that: using LDM's and DataView/DataProvider instead of
ListView will help considerably.
Martijn
--
View this message in context:
http://www.nabble.com/Wicket-Session-grows-too-big
then you have a leak
johan
--
View this message in context:
http://www.nabble.com/Wicket-Session-grows-too-big-real-fast-tp20697077p20697806.html
Sent from the Wicket - User mailing list archive at Nabble.com
/DataProvider instead of
ListView will help considerably.
Martijn
--
View this message in context:
http://www.nabble.com/Wicket-Session-grows-too-big-real-fast-tp20697077p20702093.html
Sent from the Wicket - User mailing list archive at Nabble.com
Agree. I was almost shocked :-) by Martijn's e-mail about keeping references
between pages. I believed it is a standard practice to keep reference to
previous page for the purpose of cancelling, and of course do it all the
time. It seems very natural to me. O-oops.
LT
2008/11/26 Piller Sébastien
Now that is a really good advice. :-)
-Mensagem original-
De: kan [mailto:[EMAIL PROTECTED]
Enviada em: quarta-feira, 26 de novembro de 2008 14:19
Para: users@wicket.apache.org
Assunto: Re: Wicket Session grows too big real fast
I am not sure if it always applicable, but usually I do
: quarta-feira, 26 de novembro de 2008 14:21
Para: users@wicket.apache.org
Assunto: Re: Wicket Session grows too big real fast
Agree. I was almost shocked :-) by Martijn's e-mail about keeping references
between pages. I believed it is a standard practice to keep reference to
previous page
original-
De: kan [mailto:[EMAIL PROTECTED]
Enviada em: quarta-feira, 26 de novembro de 2008 14:19
Para: users@wicket.apache.org
Assunto: Re: Wicket Session grows too big real fast
I am not sure if it always applicable, but usually I do not do
implements Serializable for domain objects
original-
De: Ladislav Thon [mailto:[EMAIL PROTECTED]
Enviada em: quarta-feira, 26 de novembro de 2008 14:21
Para: users@wicket.apache.org
Assunto: Re: Wicket Session grows too big real fast
Agree. I was almost shocked :-) by Martijn's e-mail about keeping references
between pages. I believed
in context:
http://www.nabble.com/Wicket-Session-grows-too-big-real-fast-tp20697077p20697523.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e
21 matches
Mail list logo
