Michael,
thanks for your help, it significantly reduced the amount of session data.
Still, the session keeps growing... Is there any way to determine which
objects get serialized and where they are dangling? Removing the Serializable
interface helps me to spot my own classes but it does not work
> >> iteratec GmbHFon: +49 (0)89 614551-44
> >> Inselkammerstrasse 4 Fax: +49 (0)89 614551-10
> >> 82008 Unterhaching Web: www.iteratec.de
> >>
> >> Sitz und Registergericht der iteratec GmbH: München HRB 113 519
> >> Geschäftsführer: Klaus Eberhardt, Mark Goerke, Ing
After some twiddling I found that the PagingNavigator seems to be the culprit.
If I leave it out, the session grows only moderately, when I put it in, the
domain objects end up in the session... Anyway here is the code:
public class AuftragUebersicht extends MasterLayout {
@SpringBean
privat
For additional commands, e-mail: users-h...@wicket.apache.org
>
>
>
-----
Michael Sparer
http://talk-on-tech.blogspot.com
--
View this message in context:
http://www.nabble.com/DataView-and-increasing-session-size-tp21723557p21724558.html
Sent from the Wicket - User mailing list archive at Nabb
Hi,
I have a question on how the DataView component is supposed to work. In my
application, I have to show quite large list of entities and so I am using
a DataView together with LoadableDetachableModels to read the data on demand.
However, when looking at the serialized sessions, I can observe t
