You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Ryan Crumley (JIRA)" <ji...@apache.org> on 2007/06/13 17:20:26 UTC
[jira] Created: (WICKET-643) Create a session debug tool that will
print the object graph that is put into session
Create a session debug tool that will print the object graph that is put into session
-------------------------------------------------------------------------------------
Key: WICKET-643
URL: https://issues.apache.org/jira/browse/WICKET-643
Project: Wicket
Issue Type: New Feature
Components: wicket
Reporter: Ryan Crumley
Priority: Minor
It would be great to have a tool that would help with debuging session related issues that would allow the programmer to view the object graph associated with a users session. This graph would allow the programmer to see what is being stored in session and how it got there. Added bonus for providing an estimated size for each node of the graph.
An implementation may choose to start with org.apache.wicket.util.io.SerializableChecker to create the graph.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-643) Create a session debug tool that
will print the object graph that is put into session
Posted by "Eelco Hillenius (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504304 ]
Eelco Hillenius commented on WICKET-643:
----------------------------------------
SerializableChecker is focussed on finding the first path to a non-serializable object and return that path. It forgets the rest. So the ideas in it can be reused, but not the class itself I'm afraid.
> Create a session debug tool that will print the object graph that is put into session
> -------------------------------------------------------------------------------------
>
> Key: WICKET-643
> URL: https://issues.apache.org/jira/browse/WICKET-643
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Reporter: Ryan Crumley
> Priority: Minor
>
> It would be great to have a tool that would help with debuging session related issues that would allow the programmer to view the object graph associated with a users session. This graph would allow the programmer to see what is being stored in session and how it got there. Added bonus for providing an estimated size for each node of the graph.
> An implementation may choose to start with org.apache.wicket.util.io.SerializableChecker to create the graph.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-643) Create a session debug tool that will
print the object graph that is put into session
Posted by "Andrew Klochkov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Klochkov updated WICKET-643:
-----------------------------------
Attachment: WicketObjectTreePrinter.java
Attached WicketObjectTreePrinter class which can dump http session contents into a file in the form of object tree. In fact it's slightly modified version of org.apache.wicket.util.io.SerializableChecker. I think these 2 classes should be inherited from a common parent class to avoid code duplication.
> Create a session debug tool that will print the object graph that is put into session
> -------------------------------------------------------------------------------------
>
> Key: WICKET-643
> URL: https://issues.apache.org/jira/browse/WICKET-643
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Reporter: Ryan Crumley
> Priority: Minor
> Attachments: WicketObjectTreePrinter.java
>
>
> It would be great to have a tool that would help with debuging session related issues that would allow the programmer to view the object graph associated with a users session. This graph would allow the programmer to see what is being stored in session and how it got there. Added bonus for providing an estimated size for each node of the graph.
> An implementation may choose to start with org.apache.wicket.util.io.SerializableChecker to create the graph.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.