[
http://issues.ops4j.org/jira/browse/PAXWICKET-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11629#action_11629
]
Edward Yakop commented on PAXWICKET-19:
---------------------------------------
deptstore sample no longers produce a crash. And recently, I added a feature to
detect which class caused deserialization problem.
To enable serialization debug mode. You would need to:
Objects.setObjectStreamFactory( new PaxWicketObjectStreamFactory( true ) );
When deserialization fails, it will print out the class object that fails to
deserialize.
> Problems with classloading and serialization
> --------------------------------------------
>
> Key: PAXWICKET-19
> URL: http://issues.ops4j.org/jira/browse/PAXWICKET-19
> Project: Pax Wicket
> Issue Type: Bug
> Reporter: David Leangen
> Assignee: Niclas Hedhman
> Priority: Critical
>
> This bug is a real bitch to track down.
> Apparently, the problem has not been fixed even with Edward's recent updates.
> For more backgroud info, see post a few weeks ago on this topic:
> http://lists.ops4j.org/pipermail/general/2008q2/007465.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
