[
https://issues.apache.org/jira/browse/WICKET-6334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897156#comment-15897156
]
Martin Grigorov commented on WICKET-6334:
-----------------------------------------
For components/detachables we detach a clone of the original.
We create a clone to keep the original still attached.
And we detach the clone to calculate its "shrink" size, i.e. the size it will
take in the disk when being stored with the page.
This will not solve the issue discussed at
http://markmail.org/message/mq5zs2veaj4q4psg though. Because we use the
serialize/deserialize logic to create the clone. So any application that uses
org.apache.wicket.core.util.objects.checker.NotDetachedModelChecker and/or
org.apache.wicket.core.util.objects.checker.SessionChecker will log an error
when creating the clone.
The only good solution that I see is to use the IObjectCheckers only when
serializing Pages.
I.e. if a Session object is serialized alone then do not use the checkers.
I'm not sure whether this is possible. I will have to dig in the serialization
related logic.
> WicketObjects#sizeof() should detach Sessions
> ---------------------------------------------
>
> Key: WICKET-6334
> URL: https://issues.apache.org/jira/browse/WICKET-6334
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 7.6.0
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Priority: Minor
>
> Report at users@ : http://markmail.org/message/mq5zs2veaj4q4psg
> Wicket should detach the Session before calculating its size as it does for
> Component and IDetachable.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
