Navigation Menu

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

Merge of util:map does not work [SPR-4760] #9437

Closed
spring-projects-issues opened this issue Apr 28, 2008 · 3 comments
Closed

Merge of util:map does not work [SPR-4760] #9437

spring-projects-issues opened this issue Apr 28, 2008 · 3 comments
Assignees
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: bug A general bug
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented Apr 28, 2008

Nate Stoddard opened SPR-4760 and commented

Merging of child util:map (when using the schema configuration) does not seem to work. This issue was first posted in the support forums at http://forum.springframework.org/showthread.php?t=53358.


Affects: 2.5.3

Issue Links:

@spring-projects-issues
Copy link
Collaborator Author

Kevin Calcagno commented

I don't think this bug is valid. Your example appears to misuse util:map. The util:map tag is intended for creating a named bean that is a Map (it's a shortcut for MapFactoryBean). If you want to create a map as a property value of some other bean, just use <map> instead.

(also posted this on the thread in the support forum)

@spring-projects-issues
Copy link
Collaborator Author

Juergen Hoeller commented

We do have an issue there after all, since util:map and co expose a "merge" attribute - which is simply ignored at this point. That's certainly not acceptable. I'll see what I can do about it in the short term.

Juergen

@spring-projects-issues
Copy link
Collaborator Author

Juergen Hoeller commented

Merging through util:map and co is not really in line with the semantics of those tags, since they are designed to define standalone collections with own id etc. As a consequence, I've revised our 2.5 XSDs to not expose the "merge" attribute for util:map and co, whereas it still remains available for plain <map> and co.

Juergen

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: bug A general bug
Projects
None yet
Development

No branches or pull requests

2 participants