[
https://issues.apache.org/jira/browse/WICKET-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046029#comment-13046029
]
Pedro Santos commented on WICKET-3778:
--------------------------------------
By exposing an API to customize the serialization, we don't need this
complexity in WicketObjects.
User will be able to set the Gae serializer as:
public GaeObjectSerializer implements IPage/ObjectSerializer{ ... }
(...)
storeSettings.setPage/ObjectSerializer(new GaeObjectSerializer());
(...)
and the framework will use it. There is no need for a duplicated API to
customize serialization.
Also the JavaSerializer can be changed to use ObjectIn/OutputStream directly.
As it is now, you don't even know which serialization will be done to name it
as 'Java'.
> Add possibility to register different page serializer
> -----------------------------------------------------
>
> Key: WICKET-3778
> URL: https://issues.apache.org/jira/browse/WICKET-3778
> Project: Wicket
> Issue Type: New Feature
> Components: wicket-core
> Affects Versions: 1.5-RC4
> Reporter: Martin Grigorov
> Attachments: wicket-3778.patch
>
>
> Currently Wicket uses default Java serialization to persist/load the page
> to/from the backing stores.
> There are serialization libraries which claim to be more performant than Java
> serialization.
> With this ticket I want to make Wicket more configurable by introducing
> IPageSerializer interface with Java serialization as default implementation
> (as it works today).
> Additionally I'll add an implementation based on
> http://code.google.com/p/kryo/ in wicketstuff project at Github.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
