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

Spring doesn't parse jndi variables default values to match the expected-type [SPR-11039] #15667

Closed
spring-issuemaster opened this issue Oct 28, 2013 · 1 comment
Assignees
Milestone

Comments

@spring-issuemaster
Copy link
Collaborator

@spring-issuemaster spring-issuemaster commented Oct 28, 2013

Raman H opened SPR-11039 and commented

Please see forum post for description.
I assume it is a Spring bug as no response there.


Affects: 3.2.2

Reference URL: http://forum.spring.io/forum/spring-projects/container/724764-default-object-false-of-type-string-is-not-of-expected-type-boolean

Referenced from: commits fe46a01, 0aedd81

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

@spring-issuemaster spring-issuemaster commented Nov 5, 2013

Juergen Hoeller commented

This was indeed a limitation that I've fixed for 4.0 RC2 and 3.2.5, explicitly converting a given default value to the desired target type if it isn't assignable right away.

Note that this was primarily a problem with the String-based XML namespace. With a raw JndiObjectFactoryBean, you could pass a specifically typed object into the "defaultObject" property.

Juergen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.