[
https://issues.apache.org/jira/browse/WICKET-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eelco Hillenius reopened WICKET-265:
------------------------------------
Ok, that didn't actually work at all. Turned out to be a pretty naive approach.
We have to rewrite it to make it resemble actual serialization more closely.
> Improve diagnostics on serialization exceptions
> -----------------------------------------------
>
> Key: WICKET-265
> URL: https://issues.apache.org/jira/browse/WICKET-265
> Project: Wicket
> Issue Type: Improvement
> Affects Versions: 1.3, 2.0
> Reporter: Eelco Hillenius
> Assigned To: Eelco Hillenius
> Fix For: 1.3, 2.0
>
> Attachments: DebuggingObjectOutputStream.java,
> DebuggingObjectOutputStream.java, DebuggingObjectOutputStream.java
>
>
> The JDK's default serialization exception doesn't give a whole lot of
> information other than the object that didn't implement serializable. We can
> try to improve on this by giving more info of the object tree that was being
> serialized
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
