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 2013/04/26 15:14:22 UTC
[jira] [Resolved] (WICKET-5150) Log additional info when
FormComponent fails in updateCollectionModel
[ https://issues.apache.org/jira/browse/WICKET-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-5150.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.5.11
6.8.0
Assignee: Martin Grigorov
Improved.
Thanks for the quickstart!
> Log additional info when FormComponent fails in updateCollectionModel
> ---------------------------------------------------------------------
>
> Key: WICKET-5150
> URL: https://issues.apache.org/jira/browse/WICKET-5150
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 6.7.0
> Environment: Any
> Reporter: Steve Akers
> Assignee: Martin Grigorov
> Priority: Trivial
> Fix For: 6.8.0, 1.5.11
>
> Attachments: jira1.zip
>
>
> When a form component using Collections (e.g. CheckGroup) fails to set the collection in the Model's contained object due to an exception, it produces some log output that looks thus:
> INFO - FormComponent - no setter for the property attached to [CheckGroup [Component id = group]]
> This may be misleading, as any exception will produce this output, including for example a NullPointerException that occurs inside the setter itself. In other words, setter for the property may well exist but an exception sometime during the setter invocation still results in the "no setter" log feedback.
> Suggested improvement is to include some details about the caught exception in this log message that may more directly point to the cause of the failure.
--
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