-
Notifications
You must be signed in to change notification settings - Fork 38.9k
Closed
Closed
Copy link
Labels
in: coreIssues in core modules (aop, beans, core, context, expression)Issues in core modules (aop, beans, core, context, expression)in: webIssues in web modules (web, webmvc, webflux, websocket)Issues in web modules (web, webmvc, webflux, websocket)type: enhancementA general enhancementA general enhancement
Milestone
Description
Chris Beams opened SPR-8545 and commented
Following the changes made in #13136, it now makes sense to enable JndiPropertySource by default when using a StandardServletEnvironment, as the overhead is minimal and exceptions are no longer thrown when a property is not found in JNDI.
Remove the jndiPropertySourceEnabled flag altogether and allow users to manipulate the JndiPropertySource through the usual mechanisms available from MutablePropertySources if desired.
Affects: 3.1 M1, 3.1 M2
Issue Links:
- JndiPropertySource getProperty throws Exception [SPR-8490] #13136 JndiPropertySource getProperty throws Exception
Referenced from: commits 6db594c, f0460ce
1 votes, 1 watchers
Metadata
Metadata
Assignees
Labels
in: coreIssues in core modules (aop, beans, core, context, expression)Issues in core modules (aop, beans, core, context, expression)in: webIssues in web modules (web, webmvc, webflux, websocket)Issues in web modules (web, webmvc, webflux, websocket)type: enhancementA general enhancementA general enhancement