[
https://issues.apache.org/jira/browse/SANDBOX-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13944414#comment-13944414
]
Andre Diermann commented on SANDBOX-464:
----------------------------------------
Hello Benedikt,
I see you agree that there should be two distinct methods for the two purposes.
:-) On the other hand I understand your concern and like your idea to find
another name for the method that interprets property expressions. Therefore I
extended the API with a method called getExpressed() (in regards to
getIndexed() and getMapped()). The default get() method remained untouched.
Due to the current abilities of the PropertyInterpreter I makes no sense to
scale the patch by following the above's subtask structure. Hence I rather
split the work in two parts, part 1 contains all the getter stuff, while part 2
will contain everything related to setting properties using expressions.
Please find part 1 in attached patch file "Commons-Sandbox-464-Get.patch".
What do you think?
Regards,
André
> Add support for interpreting property expressions
> -------------------------------------------------
>
> Key: SANDBOX-464
> URL: https://issues.apache.org/jira/browse/SANDBOX-464
> Project: Commons Sandbox
> Issue Type: Task
> Components: BeanUtils2
> Affects Versions: Nightly Builds
> Reporter: Benedikt Ritter
>
> BeanUtils 1 has the functionality to interpret property paths. For example
> the call:
> {code:java}
> BeanUtils.getProperty("adress.street", person);
> {code}
> would first get the address of the given person and then get the street from
> the address and return it. The same is possible for list and mapped
> properties.
> In order to be supplement for BeanUtils1, we need to implement this in
> BeanUtils2.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
