Mailing-List: contact commits-help@wicket.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@wicket.apache.org
Message-ID: <26186685.1199662294388.JavaMail.jira@brutus>
Date: Sun, 6 Jan 2008 15:31:34 -0800 (PST)
From: "Matej Knopp (JIRA)" <jira@apache.org>
To: commits@wicket.apache.org
Subject: [jira] Commented: (WICKET-1262) Page#readResolve is not called
In-Reply-To: <15317665.1199662294158.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/WICKET-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556451#action_12556451 ] 

Matej Knopp commented on WICKET-1262:
-------------------------------------

Changing the access modifier to public seem to selve it. This looks like a bug in ObjectInputStream, because the serialization specificaiton says that there can be any access modifier for readResolve.

> Page#readResolve is not called
> ------------------------------
>
>                 Key: WICKET-1262
>                 URL: https://issues.apache.org/jira/browse/WICKET-1262
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.0-final
>         Environment: JDK6
>            Reporter: Matej Knopp
>            Assignee: Matej Knopp
>            Priority: Critical
>             Fix For: 1.3.1
>
>
> Page#readResolve is not called on page deserialization. This causes significant problems when there are dependencies between pages. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.