Could not resolve placeholder 'spring.security.mapping.directory' in string value "${spring.security

最新推荐文章于 2024-09-20 19:01:02 发布
最新推荐文章于 2024-09-20 19:01:02 发布 · 127 阅读 · 0
文章标签：

#java #开发工具

本文探讨了一个在Spring框架中遇到的错误，即在应用上下文中无法解析属性值，导致bean定义无效的问题。详细分析了错误的原因，即在未使用相关组件的情况下配置了错误的属性值。提供了具体的解决方法，包括从applicationContext.xml文件中移除引起问题的属性配置。

1、错误描述

2015-09-20 22:30:25 [main] WARN  org.springframework.context.support.GenericApplicationContext - Exception encountered during context initialization - cancelling refresh attempt
org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean definition with name 'sessionFactory' defined in class path resource [applicationContext.xml]: Could not resolve placeholder 'spring.security.mapping.directory' in string value "${spring.security.mapping.directory}"; nested exception is java.lang.IllegalArgumentException: Could not resolve placeholder 'spring.security.mapping.directory' in string value "${spring.security.mapping.directory}"
	at org.springframework.beans.factory.config.PlaceholderConfigurerSupport.doProcessProperties(PlaceholderConfigurerSupport.java:211)
	at org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.processProperties(PropertyPlaceholderConfigurer.java:223)
	at org.springframework.beans.factory.config.PropertyResourceConfigurer.postProcessBeanFactory(PropertyResourceConfigurer.java:86)
	at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:265)
	at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:162)
	at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:606)
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:462)
	at org.springframework.test.context.support.AbstractGenericContextLoader.loadContext(AbstractGenericContextLoader.java:125)
	at org.springframework.test.context.support.AbstractGenericContextLoader.loadContext(AbstractGenericContextLoader.java:60)
	at org.springframework.test.context.support.AbstractDelegatingSmartContextLoader.delegateLoading(AbstractDelegatingSmartContextLoader.java:108)
	at org.springframework.test.context.support.AbstractDelegatingSmartContextLoader.loadContext(AbstractDelegatingSmartContextLoader.java:260)
	at org.springframework.test.context.DefaultCacheAwareContextLoaderDelegate.loadContextInternal(DefaultCacheAwareContextLoaderDelegate.java:63)
	at org.springframework.test.context.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:83)
	at org.springframework.test.context.DefaultTestContext.getApplicationContext(DefaultTestContext.java:74)
	at org.springframework.test.context.support.DependencyInjectionTestExecutionListener.injectDependencies(DependencyInjectionTestExecutionListener.java:116)
	at org.springframework.test.context.support.DependencyInjectionTestExecutionListener.prepareTestInstance(DependencyInjectionTestExecutionListener.java:82)
	at org.springframework.test.context.TestContextManager.prepareTestInstance(TestContextManager.java:212)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.createTest(SpringJUnit4ClassRunner.java:199)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner$1.runReflectiveCall(SpringJUnit4ClassRunner.java:251)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.methodBlock(SpringJUnit4ClassRunner.java:253)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:216)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:82)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:60)
	at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:67)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:162)
	at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: java.lang.IllegalArgumentException: Could not resolve placeholder 'spring.security.mapping.directory' in string value "${spring.security.mapping.directory}"
	at org.springframework.util.PropertyPlaceholderHelper.parseStringValue(PropertyPlaceholderHelper.java:174)
	at org.springframework.util.PropertyPlaceholderHelper.replacePlaceholders(PropertyPlaceholderHelper.java:126)
	at org.springframework.beans.factory.config.PropertyPlaceholderConfigurer$PlaceholderResolvingStringValueResolver.resolveStringValue(PropertyPlaceholderConfigurer.java:259)
	at org.springframework.beans.factory.config.BeanDefinitionVisitor.resolveStringValue(BeanDefinitionVisitor.java:282)
	at org.springframework.beans.factory.config.BeanDefinitionVisitor.resolveValue(BeanDefinitionVisitor.java:204)
	at org.springframework.beans.factory.config.BeanDefinitionVisitor.visitList(BeanDefinitionVisitor.java:228)
	at org.springframework.beans.factory.config.BeanDefinitionVisitor.resolveValue(BeanDefinitionVisitor.java:192)
	at org.springframework.beans.factory.config.BeanDefinitionVisitor.visitPropertyValues(BeanDefinitionVisitor.java:141)
	at org.springframework.beans.factory.config.BeanDefinitionVisitor.visitBeanDefinition(BeanDefinitionVisitor.java:82)
	at org.springframework.beans.factory.config.PlaceholderConfigurerSupport.doProcessProperties(PlaceholderConfigurerSupport.java:208)
	... 37 more
2015-09-20 22:30:25 [main] ERROR org.springframework.test.context.TestContextManager - Caught exception while allowing TestExecutionListener [org.springframework.test.context.support.DependencyInjectionTestExecutionListener@6c9f45f4] to prepare test instance [com.you.flex.test.dao.StudentDaoTest@50d6bdbe]
java.lang.IllegalStateException: Failed to load ApplicationContext
	at org.springframework.test.context.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:91)
	at org.springframework.test.context.DefaultTestContext.getApplicationContext(DefaultTestContext.java:74)
	at org.springframework.test.context.support.DependencyInjectionTestExecutionListener.injectDependencies(DependencyInjectionTestExecutionListener.java:116)
	at org.springframework.test.context.support.DependencyInjectionTestExecutionListener.prepareTestInstance(DependencyInjectionTestExecutionListener.java:82)
	at org.springframework.test.context.TestContextManager.prepareTestInstance(TestContextManager.java:212)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.createTest(SpringJUnit4ClassRunner.java:199)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner$1.runReflectiveCall(SpringJUnit4ClassRunner.java:251)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.methodBlock(SpringJUnit4ClassRunner.java:253)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:216)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:82)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:60)
	at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:67)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:162)
	at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean definition with name 'sessionFactory' defined in class path resource [applicationContext.xml]: Could not resolve placeholder 'spring.security.mapping.directory' in string value "${spring.security.mapping.directory}"; nested exception is java.lang.IllegalArgumentException: Could not resolve placeholder 'spring.security.mapping.directory' in string value "${spring.security.mapping.directory}"
	at org.springframework.beans.factory.config.PlaceholderConfigurerSupport.doProcessProperties(PlaceholderConfigurerSupport.java:211)
	at org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.processProperties(PropertyPlaceholderConfigurer.java:223)
	at org.springframework.beans.factory.config.PropertyResourceConfigurer.postProcessBeanFactory(PropertyResourceConfigurer.java:86)
	at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:265)
	at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:162)
	at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:606)
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:462)
	at org.springframework.test.context.support.AbstractGenericContextLoader.loadContext(AbstractGenericContextLoader.java:125)
	at org.springframework.test.context.support.AbstractGenericContextLoader.loadContext(AbstractGenericContextLoader.java:60)
	at org.springframework.test.context.support.AbstractDelegatingSmartContextLoader.delegateLoading(AbstractDelegatingSmartContextLoader.java:108)
	at org.springframework.test.context.support.AbstractDelegatingSmartContextLoader.loadContext(AbstractDelegatingSmartContextLoader.java:260)
	at org.springframework.test.context.DefaultCacheAwareContextLoaderDelegate.loadContextInternal(DefaultCacheAwareContextLoaderDelegate.java:63)
	at org.springframework.test.context.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:83)
	... 25 more
Caused by: java.lang.IllegalArgumentException: Could not resolve placeholder 'spring.security.mapping.directory' in string value "${spring.security.mapping.directory}"
	at org.springframework.util.PropertyPlaceholderHelper.parseStringValue(PropertyPlaceholderHelper.java:174)
	at org.springframework.util.PropertyPlaceholderHelper.replacePlaceholders(PropertyPlaceholderHelper.java:126)
	at org.springframework.beans.factory.config.PropertyPlaceholderConfigurer$PlaceholderResolvingStringValueResolver.resolveStringValue(PropertyPlaceholderConfigurer.java:259)
	at org.springframework.beans.factory.config.BeanDefinitionVisitor.resolveStringValue(BeanDefinitionVisitor.java:282)
	at org.springframework.beans.factory.config.BeanDefinitionVisitor.resolveValue(BeanDefinitionVisitor.java:204)
	at org.springframework.beans.factory.config.BeanDefinitionVisitor.visitList(BeanDefinitionVisitor.java:228)
	at org.springframework.beans.factory.config.BeanDefinitionVisitor.resolveValue(BeanDefinitionVisitor.java:192)
	at org.springframework.beans.factory.config.BeanDefinitionVisitor.visitPropertyValues(BeanDefinitionVisitor.java:141)
	at org.springframework.beans.factory.config.BeanDefinitionVisitor.visitBeanDefinition(BeanDefinitionVisitor.java:82)
	at org.springframework.beans.factory.config.PlaceholderConfigurerSupport.doProcessProperties(PlaceholderConfigurerSupport.java:208)
	... 37 more

2、错误原因

由于项目中没有用到spring.security，并且没有导入有关的jar，但是配置了这个，导致报错


3、解决办法

applicationContext.xml去掉：

<value>${spring.security.mapping.directory}</value>


iteye_8264
关注
SpringBoot踩坑日记--Could not resolve placeholder ”spring.data.mongodb.database“ in value
Rsun2018的博客
05-11 1891
在pom中添加以下依赖： <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-configuration-processor</artifactId> <optional>true</optional> </dependen
如何解决 Could not resolve placeholder ‘user.userName‘ in value “${user.userName}“... 问题 | 亲测有效
**My Coding Family**
05-28 8751
解决Could not resolve placeholder 'user.userName' in value "${user.userName}"...【亲测有效】
Could not resolve placeholder ‘xxx‘ in value “${xxx}“
pangdongh的博客
04-03 11万+
文章目录问题解决过程/思路（不想看思路的直接跳解决方案）解决方案结语 问题 今天用idea启动springboot的时候发现某个配置没找到 报错： Injection of autowired dependencies failed; nested exception is java.lang.IllegalArgumentException: Could not resolve placeho...
nacos管理springboot配置时，发生的Could not resolve placeholder两种原因
Brave_heart4pzj的博客
11-11 5294
springboot
Could not resolve placeholder 解决方案
u012039409的博客
08-11 4万+
用spring 配置加载properties文件的时候，报 Could not resolve placeholder 错误。 经过仔细查找，排除文件路径，文件类容错误的原因，经过查找相关资料，出现"Could not resolve placeholder"很有可能是使用了多个PropertyPlaceholderConfigurer或者多个的原因或者是多个PropertyPlace
Spring中报"Could not resolve placeholder"的解决方案
热门推荐
linwei_1029的专栏
10-14 11万+
除去properites文件路径错误、拼写错误外，出现"Could not resolve placeholder"很有可能是使用了多个PropertyPlaceholderConfigurer或者多个的原因。   　　比如我有一个dao.xml读取dbConnect
【解决方法汇总】SpringBoot项目报错 Could not resolve placeholder ‘‘ in value “${}“
yu1812531的博客
03-19 8万+
maven项目启动报错 [restartedMain] o.s.boot.SpringApplication : Application run failed 如图 Error starting ApplicationContext. To display the conditions report re-run your application with ‘debug’ enabled. 2022-03-13 20:58:12.515 ERROR 11480 — [ restartedMain] o.
SpringCloud config 错误 springcloud config Could not resolve placeholder ‘config.info‘ in value “${...
qq_24428851的博客
09-20 726
我的原因是仓库yml文件格式不正确，所以不推荐直接远程仓库文件中编辑。著作权归作者所有,转载或内容合作请联系作者。yml格式错误.png。
启动报错 Could not resolve placeholder ‘gate.ignore.startWith‘ in value “${gate.ignore.startWith}“
journey_c111的博客
08-14 717
配置文件里忘记选环境了。
Could not resolve placeholder ‘XXX‘ in value _${XXX}
x_ai_bian_cheng的博客
06-20 9915
Could not resolve placeholder 'XXX' in value _${XXX}
Could not resolve placeholder 'spring.datasource.url' in value "${spring.datasource.url}"
xcl119xcl的专栏
05-07 8494
参考：http://120.203.18.89:6969/41/could-not-resolve-placeholder-spring-datasource-url-in-value-spring-datasource-url/ 今天在测试环境运行Maven工程时，出现莫名其妙的无法初始化mybatis错误，主要是读取不到配置文件里面，关于数据库的配置。 工程有多个profile，在Idea...
报错解决：Could not resolve placeholder ‘spring.datasource.url‘ in value “${spring.datasource.url}“
邵奈一的博客
11-16 1万+
原因 由于 Git 的分支切换问题，导致需要重新导入 JDK ，而且， IDEA 没有自动识别当前项目为 Maven 管理的项目，所以需要重新导入一下。 解决办法 看一下自己是不是 Maven 项目，点击 IDEA 下图中的1，然后看一下3有没有，如果没有，可以分别点一下2的两个按钮，看有了没有： 如果没有的话，你可以去 pom.xml 文件里，右击，看能够重新引入依赖，如果没有相应的按钮，你会看到提示添加此项目为Maven项目的按钮，点击就可以了。 当然，如果你还不是这种情况的话，你可以尝试一下： cl
spring boot could not resolve placeholder in string value 问题解决方法
hannover100的专栏
09-28 4万+
Caused by: java.lang.IllegalArgumentException: Could not resolve placeholder 'hosts' in string value "${db.hosts}" 问题的产生是由于有多个properties文件造成的，如果再第一个properties文件中没有找，就不认为没有了，不继续找下一个properties文
项目启动报错：Could not resolve placeholder 'spring.datasource.url' in value "${spring.datasource.url}"
有才而性缓，定属大才。有智而气和，斯为大智。
03-26 6395
1.要确保你的配置的文件字符格式无误，确保文件存在 2.项目在配置更改后要对maven进行clean，install的操作，清除以重新编译项目 选择项目 Run As
spring boot 启动错误：Could not resolve placeholder
阿城的博客
08-02 10万+
在启动整个spring boot项目时，出现错误： Could not resolve placeholder原因：没有指定好配置文件，因为src/main/resources下有多个配置文件，例如application-dev.properties, boss.properties等。解决办法： 法1： 在application.properties中加入 spring.profiles
彻底解决Could not resolve placeholder --release
Jiang_WenFeng的博客
03-27 1万+
1.产生的原因，只看文字也能看懂，可以跳过代码部分 if (propVal != null) { propVal = this.parseStringValue(propVal, placeholderResolver, (Set)visitedPlaceholders); result.replace(startIndex, endIndex + this.placeholderSuffix.length.
springboot 读取配置文件注入值失败
w309827333的博客
01-11 1926
异常描述 Caused by: java.lang.IllegalArgumentException: Could not resolve placeholder 'fastdfs.tracker_servers' in value "${fastdfs.tracker_servers}" at org.springframework.util.PropertyPlaceholderHelper...
could not resolve placeholder spring.application
最新发布
01-07
### 解析 Spring Boot 应用中占位符解析失败的问题 当遇到 `Could not resolve placeholder` 错误时，通常意味着应用程序无法找到所需的配置属性。这可能是由于以下几个原因造成的： #### 配置文件未正确指定 如果项目中有多个环境特定的配置文件（如 `application-dev.properties`, `boss.properties`），则需要明确指出哪个配置文件应该被激活。可以在 `application.properties` 中通过设置 `spring.profiles.active` 来实现这一点[^1]。 ```properties # application.properties spring.profiles.active=dev ``` 这样可以确保在开发环境中使用名为 `-dev` 的配置集。 #### Maven 或 Gradle 构建工具配置不当 对于某些依赖管理工具来说，可能是因为构建过程中未能正确处理资源路径或过滤器选项而导致配置缺失。特别是像 Dubbo 这样的分布式服务框架，在其初始化阶段会尝试读取特定名称下的配置项（比如 dubbo.application.name）。因此应当核查 IDE 和构建脚本中的相关设定是否已开启必要的插件支持以及正确的 profile 激活状态[^3]。 #### 开发环境集成问题 有时即使本地机器上有合适的配置存在，IDE 可能仍然不会将其视为有效的资源目录从而忽略掉这些重要的配置数据。针对这种情况，建议检查并调整 IDEA 设置以确保 resources 文件夹已被标记为 Resources Root 并且能够自动识别内部包含的应用程序属性文件[^4]。 综上所述，为了有效解决此类错误消息带来的困扰，可以从以上几个方面入手排查具体成因，并采取相应的措施加以修正。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值