Placeholder in @Where annotation can not be resolved
See original GitHub issueTask List
- Steps to reproduce provided
- Stacktrace (if present) provided
- Example that reproduces the problem uploaded to Github
- Full description of the issue provided (see below)
Steps to Reproduce
- Create an entity and a repository
- Add a method to find all entities and add a
@Where
annotation that uses a method parameter from the repository method signature - Call repository method
Expected Behaviour
Placeholder should be resolved and used in @Where
annotation value
Actual Behaviour
Placeholder can not be resolved.
Environment Information
- Operating System: Mac 10.15.6
- Micronaut Version: 2.0.0
- JDK Version: 11
Example Application
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Could not resolve placeholder in string value - java
Solution: Remove the one from applicationContext.xml as it doesn't add anything it only breaks things. Share.
Read more >java.lang.IllegalArgumentException Could not resolve ...
In this post, we will see how to fix java.lang.IllegalArgumentException Could not resolve placeholder exception in Spring Boot.
Read more >java.lang.IllegalArgumentException: Could not resolve ...
The spring boot application failed at startup with the exception java.lang.IllegalArgumentException: Could not resolve placeholder 'message' ...
Read more >PropertySource (Spring Framework 6.0.3 API)
In order to resolve ${...} placeholders in <bean> definitions or @Value annotations using properties from a PropertySource , you must ensure that an ......
Read more >${... } placeholders support in @Value annotations in Spring
When the property cannot be resolved you will get an exception: java.lang.IllegalArgumentException: Could not resolve placeholder ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
PR #800 submited for this issue. This resolves the issue for both JDBC and Hibernate-JPA
I have just noticed that this does not pass the JDK8 test because of the use of StringBuilder. I am going to change it and post a new PR.