You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2014/08/07 11:32:12 UTC
[jira] [Created] (WICKET-5667) Preserve the
NotSerializableException if an error occur while using the IObjectCheckers
Martin Grigorov created WICKET-5667:
---------------------------------------
Summary: Preserve the NotSerializableException if an error occur while using the IObjectCheckers
Key: WICKET-5667
URL: https://issues.apache.org/jira/browse/WICKET-5667
Project: Wicket
Issue Type: Improvement
Components: wicket
Affects Versions: 6.16.0
Reporter: Martin Grigorov
Assignee: Martin Grigorov
Priority: Minor
>From the mailing list (http://markmail.org/message/eqrtl73zf2buh76u):
I have a not serializable object X stored in a page. It leads to an
NotSerializableException during page storing. The problem is that this
page contains also a DetachableArrayList (from WicketStuff minis)
which raises an exception when is stored as attached.
1. JavaSerializer tries to serialize page and calls:
SerializationCheckerObjectOutputStream.writeObjectOverride(...)
2. NotSerializableException is catched for object X and
SerializableChecker is called:
new SerializableChecker(outputStream, nsx).writeObject(obj);
3. During that call exception is raised from
AbstractDetachableCollection.writeObject and this new exception is
logged.
The original NotSerializableException from step 2 is lost and we don't
know what really causes problem.
--
This message was sent by Atlassian JIRA
(v6.2#6252)