[
https://issues.apache.org/jira/browse/WICKET-6201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15377090#comment-15377090
]
ASF GitHub Bot commented on WICKET-6201:
----------------------------------------
Github user PhantomYdn commented on the issue:
https://github.com/apache/wicket/pull/74
Created: https://issues.apache.org/jira/browse/WICKET-6201
Also - it will be very helfull to make getObjectWithGetAndSet public.
Sometimes it's usefully to introspect object by wicket utilities. We switched
in [Orienteer](http://orienteer.org) from spring bean introspection to wicket
due not accurate working with beans in Spring (for example if there is a class
with methods like: public String getValue(); public void setValue(Object value)
- Spring is failing measurably even if property "value" was not directly
requested).
> PropertyResolver.setValue failing if there is only setter
> ----------------------------------------------------------
>
> Key: WICKET-6201
> URL: https://issues.apache.org/jira/browse/WICKET-6201
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 7.3.0
> Reporter: Ilia Naryzhny
>
> This issue is related to this PR:
> https://github.com/apache/wicket/pull/74#issuecomment-232608673
> Issue:
> If there is a bean like that:
> public class Bean {
> public void setValue(Object value);
> }
> PropertyValue.setValue is failing to set value for "value" expression with
> message that no "get" methods.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
