You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Alexander Kellett (JIRA)" <ji...@apache.org> on 2006/11/01 15:28:19 UTC
[jira] Created: (WICKET-26) Internal clone errors, improvement of
error message
Internal clone errors, improvement of error message
---------------------------------------------------
Key: WICKET-26
URL: http://issues.apache.org/jira/browse/WICKET-26
Project: Wicket
Issue Type: Improvement
Reporter: Alexander Kellett
It took me a surprising amount of time to find:
http://www.wicket-wiki.org.uk/wiki/index.php/FAQs#I_get_.27Internal_error_cloning_object.27_errors
Development in the period of time previous to finding this was more painful than it could have been.
Would it not make sense to at least make an indication on the error page itself that this is not an inherent need for using Wicket but instead something required only when clustering?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (WICKET-26) Internal clone errors, improvement of
error message
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/WICKET-26?page=all ]
Igor Vaynberg resolved WICKET-26.
---------------------------------
Resolution: Won't Fix
there are other instances where cloning via serialization must be supported.
if you enable auto-multiwindow support then the page has to be cloned. also for versioning wicket clones model objects by serialization.
some application servers also serialize sessions on a clean shutdown and load them when they startup next.
there are plenty of reasons to have anything put into http session to be serializable, since wicket keeps its object graphs in the http session we recommend everything be serializable.
> Internal clone errors, improvement of error message
> ---------------------------------------------------
>
> Key: WICKET-26
> URL: http://issues.apache.org/jira/browse/WICKET-26
> Project: Wicket
> Issue Type: Improvement
> Reporter: Alexander Kellett
>
> It took me a surprising amount of time to find:
> http://www.wicket-wiki.org.uk/wiki/index.php/FAQs#I_get_.27Internal_error_cloning_object.27_errors
> Development in the period of time previous to finding this was more painful than it could have been.
> Would it not make sense to at least make an indication on the error page itself that this is not an inherent need for using Wicket but instead something required only when clustering?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira