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
I took a cursory glance over your code and saw
item.add(new Link("update", new Model(auftrag))
this way the "auftrag" gets into your session, you should say
item.getModel() there instead of new Model(auftrag)
check your code if there is similar stuff in it - spotting those things
might be quit
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
the objects shouldn't be serialized into the session if you're using
loadabledetachable models, please show us some code
regards,
Michael
Jürgen Lind-2 wrote:
>
> Hi,
>
> I have a question on how the DataView component is supposed to work. In my
> application, I have to show quite large list
