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.