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

Allow PropertyResolver implementations to ignore unresolvable ${placeholders} [SPR-9569] #14203

spring-projects-issues opened this issue Jul 6, 2012 · 1 comment


Copy link

@spring-projects-issues spring-projects-issues commented Jul 6, 2012

Chris Beams opened SPR-9569 and commented

Affects: 3.1 GA

Issue Links:

  • #14108 Resolve nested ${..} placeholders via PropertyResolver/Environment ("depends on")
  • #15180 Spring3.2 bug context:property-placeholder nested search property appear java.lang.StackOverflowError
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Oct 26, 2012

Chris Beams commented

commit 06e34f05a65f93a4bc235ea67ebb9535edc1ee1c
Author: Chris Beams <>
Commit: Chris Beams <>

    Allow PropertyResolvers to ignore unresolvable ${placeholders}
    Prior to this commit, the PropertyResolver API (and therefore the
    Environment API) allowed callers a choice between
     #resolvePlaceholders and #resolveRequiredPlaceholders for low-level
    ${placeholder} resolution. However, when calling the higher level
     #getProperty variants, users had no control over whether property
    values returned with unresolvable ${placeholders} would result in an
    exception or simply be passed through.
    This commit introduces a #setIgnoreUnresolvableNestedPlaceholders
    property via ConfigurablePropertyResolver, defaulting to false, the
    value of which is respected by AbstractPropertyResolver#getProperty
    method implementations. See the new test in
    PropertySourcesPropertyResolverTests for usage examples.
    Issue: SPR-9569, SPR-9473


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant