[
https://issues.apache.org/jira/browse/WICKET-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Pieber updated WICKET-4744:
-----------------------------------
Comment: was deleted
(was: tbh I don't like that "osgi-specific" code there at all. For "regular"
wicket application IMHO (at least I don't see any reason) the specific
classresolver shouldn't be required and for "real" osgi apps the current
implementation wouldn't be fully sufficient anyhow since it's not handling OSGi
core classes like BundleContext, Bundle, ... which are very likely to exist in
the components but are not serializable at all. I think the
Application.get()...getSerializer() should be used and someone has use for
something osgi ready might want to use the pax-serializer anyhow instead.
Maybe I miss some detail, but just my 0.02€)
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
