[
https://issues.apache.org/jira/browse/WICKET-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880112#action_12880112
]
Joseph Pachod commented on WICKET-2919:
---------------------------------------
from a ML discussion:
http://apache-wicket.1842946.n4.nabble.com/inconsistency-in-property-expression-when-using-for-self-reference-td2259495.html#a2259495
> inconsistency in property expression when using . for self reference
> --------------------------------------------------------------------
>
> Key: WICKET-2919
> URL: https://issues.apache.org/jira/browse/WICKET-2919
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.9
> Reporter: Joseph Pachod
> Priority: Minor
> Attachments: PropertyModelTest.java
>
>
> Let's consider this class :
> class Container {
> String string = "foo";
> List<String> strings = Arrays.asList(new String[]{"test"});
> }
> This would work:
> new PropertyModel<String>(container, ".string").getObject()
> => returns "foo"
> but this doesn't:
> new PropertyModel<String>(container, ".strings[0]").getObject()
> it fails with
> org.apache.wicket.WicketRuntimeException: no get method defined for class:
> class org.demo.PropertyModelTest$Container expression: strings
> Similarly, this doesn't work:
> new PropertyModel<Container>(container, ".").getObject()
> exception is :java.lang.StringIndexOutOfBoundsException: String index out of
> range: 0
> In the end, should the dot being allowed for self reference ? It's already
> used as the property separator, so it would be quite misleading.
> I've attached some proper junit test for these points.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
