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.

Sign up for GitHub

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

Jump to bottom

xml value-type hard to determine for list/set or maps from the metadata [SPR-5556] #10227

Closed
spring-projects-issues opened this issue Mar 9, 2009 · 0 comments
Closed

xml value-type hard to determine for list/set or maps from the metadata [SPR-5556] #10227

spring-projects-issues opened this issue Mar 9, 2009 · 0 comments
Assignees
@jhoeller
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement
Milestone
3.0 M3

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented Mar 9, 2009 •
edited
Loading

Costin Leau opened SPR-5556 and commented

Through XML it is possible to specify a default value type for list, sets and for a map keys and values. However, the parser doesn't store this information in the metadata and just uses it internally. The only workaround for the moment, is for clients to reparse the XML nodes, providing they have access to them.
A quick solution would be to add another field to ManagedLists/Sets/Maps to store this information (i.e. defaultTypeClassName). This can be done in BeanDefinitionDelegate class, in methods parseList/Set/MapElement

Affects: 2.5.6

Issue Links:

Referenced from: commits 1b5812d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jhoeller jhoeller

Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement
Projects
None yet
Milestone
3.0 M3
Development

No branches or pull requests
2 participants
@jhoeller @spring-projects-issues