Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

util:property-path like functionality for the p-namespace [SPR-3360] #8044

Closed
spring-projects-issues opened this issue Apr 11, 2007 · 2 comments
Assignees
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

Paul Austin opened SPR-3360 and commented

Would it be possible to extend the p namespace to allow for functionality similar to the util:property-path element so that you can specify property values using a path reference to other beans.

before

<bean ...>
<property name="foo">
<util:property-path path="bar.beer" />
</property>
</bean>

after

<bean ...
p:foo-path="bar.beer"
/>


Affects: 2.0.4

Referenced from: commits becea61

1 votes, 0 watchers

@spring-projects-issues
Copy link
Collaborator Author

Arjen Poutsma commented

This seems to be resolved via the expression language introduced in 3.0 M1. I will write a test to verify wether it works in the p namespace, though.

@spring-projects-issues
Copy link
Collaborator Author

Arjen Poutsma commented

SimplePropertyNamespaceHandlerWithExpressionLanguageTests is there, and works.

@spring-projects-issues spring-projects-issues added type: enhancement A general enhancement in: core Issues in core modules (aop, beans, core, context, expression) labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 3.0 M2 milestone Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants