[
https://issues.apache.org/jira/browse/WICKET-5252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693816#comment-13693816
]
Daniel Zwicker commented on WICKET-5252:
----------------------------------------
I know that wicket doesn't know how to use my object. But i would expect an
exception in the case that wicket want to set a property and this property is
not accessible. So i get aware of this situation and can think about the
solution. But just accessing this private field should not be the decision of
wicket. As -you are right- can't know how to use my objects.
> PropertyResolver breaks immutable objects by calling setAccessible
> ------------------------------------------------------------------
>
> Key: WICKET-5252
> URL: https://issues.apache.org/jira/browse/WICKET-5252
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 6.8.0
> Reporter: Daniel Zwicker
>
> If a Bean only have private fields and no setter this object is immutable.
> The decision to implement such an object has a bunch of implications. e.g. it
> is thread safe, you can take snapshots of these object to store a version
> history and so on.
> Now your use of reflection breaks this isolation silently. I believe if
> somebody want set the values of the object he should implement a setter or
> provide a public field.
--
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
