[
https://issues.apache.org/jira/browse/WICKET-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046006#comment-13046006
]
Igor Vaynberg commented on WICKET-3778:
---------------------------------------
is there a reason why this is limited to pages? can we not have something more
generic that can be used in case someone somewhere needs to serialize something
else?
also Pedro is right. any patch that implemetns this needs to also remove
IObjectStreamFactory and friends from the picture.
> 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
