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/01/16 14:09:24 UTC

[jira] [Commented] (WICKET-4744) Investigate reworking WicketObjects#clone(Object|Model) methods to use ISerializer

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

Martin Grigorov commented on WICKET-4744:
-----------------------------------------

In branch 'sandbox/WICKET-4744-WicketObjects-use-Java-Serialization-APIs' I've improved #cloneObject() to use the configured ISerializer.
#cloneModel() does object replacement with Java Serialization APIs and it is not easy to be reworked.

Additionally improved the API by using type inference for the return types.

Please review.

> Investigate reworking WicketObjects#clone(Object|Model) methods to use ISerializer
> ----------------------------------------------------------------------------------
>
>                 Key: WICKET-4744
>                 URL: https://issues.apache.org/jira/browse/WICKET-4744
>             Project: Wicket
>          Issue Type: Sub-task
>          Components: wicket
>    Affects Versions: 6.0.0
>            Reporter: Martin Grigorov
>
> WicketObject#cloneXYZ() methods use normal Java serialization to clone an object/model.
> This will not work if the application uses a custom ISerializer which doesn't require all objects to be Serializable.
> It is not straight forward to replace this custom code with JavaSerializer because there are overrides for object replacement.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)