[
https://issues.apache.org/jira/browse/WICKET-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637829#comment-13637829
]
Martin Grigorov commented on WICKET-5150:
-----------------------------------------
Can you provide a quickstart application/test case that reproduces the log
message ?
This will save us some time trying to reproduce it and fix it.
Thanks!
> 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
> Priority: Trivial
>
> 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
