[
https://issues.apache.org/jira/browse/WICKET-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581830#action_12581830
]
Johan Compagner commented on WICKET-1445:
-----------------------------------------
thats for our SerializableChecker so that people gets a nice result where it
exactly goes wrong
And i guess you mean why make a new ObjectOutputStream and then another one to
do that?
That has to be only a default constructor call sets the enableOverride = true;
to the right value
else you cant have the writeObjectOverride method..
i will fix this by adding 2 more methods, flush and close that will delegate
also..
> StreamCorruptedException/PageStore/Serialization broken because
> ObjectOutputStream was not flushed
> --------------------------------------------------------------------------------------------------
>
> Key: WICKET-1445
> URL: https://issues.apache.org/jira/browse/WICKET-1445
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.1, 1.3.2
> Reporter: Niclas Hedhman
> Assignee: Igor Vaynberg
> Fix For: 1.3.3
>
> Attachments: wicket-close-stream.patch
>
>
> The Objects.objectToByteArray() method incorrectly forgets to flush/close the
> ObjectOutputStream it uses. This can create corrupt object streams.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
