[
https://issues.apache.org/jira/browse/WICKET-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12987518#action_12987518
]
Hudson commented on WICKET-1802:
--------------------------------
Integrated in Apache Wicket 1.4.x #405 (See
[https://hudson.apache.org/hudson/job/Apache%20Wicket%201.4.x/405/])
merging message improvement on PropertyResolver from trunk
Issue: WICKET-1802
> Propertyresolver could be more informative
> ------------------------------------------
>
> Key: WICKET-1802
> URL: https://issues.apache.org/jira/browse/WICKET-1802
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.4-M3
> Reporter: Martin Makundi
> Assignee: Johan Compagner
> Fix For: 1.4.16, 1.5-RC2
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> WicketMessage: no set method defined for value: true on object: ...
> at
> org.apache.wicket.util.lang.PropertyResolver$MethodGetAndSet.setValue(PropertyResolver.java:1107)
> In case there is a getter method defined, it would significantly help
> debugging to display the get method name in the exception.
> I suggest fixing the problem with:
> - " on object: " + object);
> + " on object: " + object + " while
> respective getMethod being " + getMethod.getName());
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
