[
https://issues.apache.org/jira/browse/WICKET-4867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501987#comment-13501987
]
Ernesto Reinaldo Barreiro commented on WICKET-4867:
---------------------------------------------------
Maybe debug bar should be reworked in way that it does't matter where it is
"placed". Something on the lines
1-Via some "listener" call WicketObjects.sizeOf() at the end of the request
cycle.
2-Put resulting size info (some how) on response.
3-Debug bar reads this info from response (on client).
> Detach the object before calculating its size
> ---------------------------------------------
>
> Key: WICKET-4867
> URL: https://issues.apache.org/jira/browse/WICKET-4867
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 6.2.0, 1.5.9
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Priority: Minor
> Fix For: 6.3.0, 1.5.10
>
>
> The debug panel in wicket-devutils uses WicketObjects#sizeOf() to calculate
> the size of the page and the session.
> The "problem" that I see is that it calculates the size of the non-detached
> object. I think what really matters is the size after detaching it, because
> this is what is being saved in the http session and the disk, and I guess
> this is what the developer needs to know actually.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
