You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Cedric Gatay (JIRA)" <ji...@apache.org> on 2013/06/29 19:21:20 UTC
[jira] [Commented] (WICKET-5254) Create a possibility to disable
increasing of getter/setter, field visibility in PropertyResolver
[ https://issues.apache.org/jira/browse/WICKET-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696159#comment-13696159 ]
Cedric Gatay commented on WICKET-5254:
--------------------------------------
I'm taking this one, trying something (will need review mainly for performance concerns)
> Create a possibility to disable increasing of getter/setter, field visibility in PropertyResolver
> --------------------------------------------------------------------------------------------------
>
> Key: WICKET-5254
> URL: https://issues.apache.org/jira/browse/WICKET-5254
> Project: Wicket
> Issue Type: New Feature
> Reporter: Daniel Zwicker
> Priority: Minor
>
> PropertyResolver make it possible to access private fields and setter. This can break the contract of the beans . I know this is documented. But especially in larger teams not every body knows why a bean is immutable or don't think about it even if they know.
> It would be nice if there is a possibility to enable some kind of exception if the visibility of a property was increased.
> Additional i think a good idea would be to log some warnings in debug mode in these situations.
--
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