[jira] [Updated] (WICKET-4264) JavaSerializer Does Not Call SerializableChecker

["James Carman (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Carman updated WICKET-4264:
---------------------------------

    Attachment: WICKET-4264.patch

Here is what I propose to be the solution.  Let me know what you think and I'll try to come up with a way to write a unit test for this.
                
> JavaSerializer Does Not Call SerializableChecker
> ------------------------------------------------
>
>                 Key: WICKET-4264
>                 URL: https://issues.apache.org/jira/browse/WICKET-4264
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.5.3
>            Reporter: James Carman
>         Attachments: WICKET-4264.patch
>
>
> In the new JavaSerializer class, it has a CheckerOutputStream which extends ObjectOutputStream.  The intent is to use the ObjectOutputStream.writeObjectOverride() support.  However, the writeObjectOverride() method is never called unless you use the no-arg constructor from the ObjectOutputStream class (which sets the "enableOverride" flag to true).  The CheckerOutputStream uses the ObjectOutputStream(OutputStream) constructor in its constructor.  Worse yet, even if the writeObjectOverride() method were to be  called, it would create a StackOverflowError because it's calling the super.writeObject() method which is what called it in the first place (infinite recursion).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira