I have been battling this problem for a few days, using other suggestions I've found to no avail. I've tried using #EnableAspectJAutoProxy(proxyTargetClass = true) on the SpringApplication entry and the Configuration classes. I have spring.aop.auto.true and spring.aop.proxy-target-class.true in my application yml file and still the same error. I have tried setting it as an interface with no luck as well. I have this as the Component that is being complained about
#Component
#EnableRetry
#Slf4j
public class DocumentProcessorApiService {
private final RestTemplate documentsApiRestTemplate;
private final DocumentsApiProperties documentsApiProperties;
private final MulesoftProperties mulesoftProperties;
private static final String DOCUMENT_SEARCH_PATH = "/documents/_search";
private static final String PROPS_NAME_VALUE_MAP_FIELD = "propsNameValueMap";
private static final String DOCUMENT_TYPE_FIELD = "Document Type";
private static final String UW_ERROR_REPORT_TYPE = "UW ERROR RPT";
#Autowired
public DocumentProcessorApiService(#Qualifier("documentsApiRestTemplate") RestTemplate documentsApiRestTemplate, DocumentsApiProperties documentsApiProperties,
MulesoftProperties mulesoftProperties) {
this.documentsApiRestTemplate = documentsApiRestTemplate;
this.documentsApiProperties = documentsApiProperties;
this.mulesoftProperties = mulesoftProperties;
}
and this is what is using it as Autowired as well
#Service
#Slf4j
public class LifeWorkflowEventListener {
private final EventConverter eventConverter;
private final JmsService jmsService;
private final DocumentProcessorApiService documentProcessorApiService;
private final LifeApplicationService lifeApplicationService;
#Value("${kafka.consumer.workflow-event.action-event-type:}")
String actionEventType;
#Autowired
public LifeWorkflowEventListener(#Qualifier("lifeWorkflow") EventConverter eventConverter,
JmsService jmsService,
DocumentProcessorApiService documentProcessorApiService,
LifeApplicationService lifeApplicationService) {
this.eventConverter = eventConverter;
this.jmsService = jmsService;
log.info("documentProcessorApiService {}", documentProcessorApiService.toString());
this.documentProcessorApiService = documentProcessorApiService;
this.lifeApplicationService = lifeApplicationService;
}
I appreciate any ideas I have not tried yet, or letting me know if I'm doing something else wrong.
Thank you
This happens because Spring thinks that it has to wrap methods in DocumentProcessorApiService, for example, to handle transactions. In order to do that, it creates a proxy. If you have an interface, Spring can make the proxy return true when it's asked "are you assignment compatible with type XYZ".
Steps to fix:
Rename DocumentProcessorApiService to DocumentProcessorApiServiceImpl. Rename the file manually and fix the compile error instead of refactoring; see below.
Create an interface DocumentProcessorApiService
Make DocumentProcessorApiServiceImpl implement that interface
If you used refactoring for the rename, replace DocumentProcessorApiServiceImpl everywhere with DocumentProcessorApiService except for the name of the class itself.
Add an entry in a #Configuration bean to let Spring know how to create DocumentProcessorApiService
This works. If it doesn't, then there must be a mistake elsewhere. In this case, ask a new question with the changed code and the exact error message.
See also: Spring error "Bean named 'x' is expected to be of type 'y', but was actually of type [com.sun.proxy.$Proxy]"
I'm trying to use application.properties file values in controller. Using following code.
#Value("${app.baseURL}")
private final String BaseUrl;
I found another way to do this.
#Controller
public class userController {
String BaseUrl;
public userController(#Value("app.baseURL")String BaseUrl) {
this.BaseUrl= BaseUrl;
}
}
What is the efficient way ?
What is the efficient way ?
No one of them is more efficient.
The first one uses the field injection and the second one the constructor injection.
I see rather a real difference in terms of design.
The first one set BaseUrl as an internal dependency that clients of the class cannot set. Only Spring can.
In most of cases, it is a bad idea as it buries class dependencies.
A common issue with this kind of design is unit testing.
As you write an unit test you have to have simple and natural ways to set the dependencies of the instance under test.
How to do that with an not accessible field ?
Reflection ? Not fine either.
The constructor injection of your second code is a much better way.
If you have few fields then use #Value at field level not at method level. If there are maximum number of property you have to use then use autowire Environment.
#Value("${app.baseURL}")
private final String BaseUrl;
Autowire Environment
#Autowired
Environment env;
To get the property value by key using Environment
env.getProperty("some-strProp")
if you have a lot of properties belong to each other you also can use a property class
application.yml:
your:
properties:
root:
path: "/root/path/to/resource"
enabled: true
timeout: 10
java class:
#ConfigurationProperties("your.properties.root")
public class MyProperties {
private String path;
private boolean enabled;
private int timeout;
//getter & setter
}
use constructor injection to access the properties:
#Service
public class MyService {
private final MyProperties properties;
#Autowired
public MyService(MyProperties properties) {
this.properties = properties;
}
}
https://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-external-config.html#boot-features-external-config-typesafe-configuration-properties
you also can validate property classes:
#Validated
#ConfigurationProperties("your.properties.root")
public class MyProperties {
#NotEmpty
private String path;
#NotNull
private Boolean enabled;
#Min(1)
private int timeout;
//getter & setter
}
https://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-external-config.html#boot-features-external-config-validation
I want to let Spring assign a property value.
public class Foobar {
#Value("${example.property.foo:bar}")
private String foo;
}
Let's say I want to refer to example.property.foo in several different places, so I'd rather assign the flag as a constant on Foobar:
public class Foobar {
public static final String FOO_PROPERTY_FLAG = "example.property.foo";
}
The setting of example.property.foo=whatever happens elsewhere (as a system property, or in a #TestPropertySource).
How can I refer to FOO_PROPERTY_FLAG in the annotation? This works:
#Value("${" + FOO_PROPERTY_FLAG + ":bar}")
But it's kind of ugly. Can I use the "#{}" expression syntax here somehow?
#Value("${#{FOO_PROPERTY_FLAG}:bar}") // doesn't work; value is never injected
You can do something like:
public static final String KEY = "propertyName";
#Value("#{T(a.b.c.package.MyConstants).KEY}")
The important part is to specify package and class. Otherwise spring will try to lookup constant in BeanExpressionContext which is actually executing your SpEL
private #Value("${propertyName}") String propertyField;
No getters or setters!
With the properties being loaded via the config:
<bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"
p:location="classpath:propertyFile.properties" name="propertiesBean"/>
There's also the totally non-Xml version:
#PropertySource("classpath:propertyFile.properties")
public class AppConfig {
#Bean
public static PropertySourcesPlaceholderConfigurer propertySourcesPlaceholderConfigurer() {
return new PropertySourcesPlaceholderConfigurer();
}
Make sure and add in the namespace URI xmlns:p="springframework.org/schema/p"; to use the p: prefixed attributes
I want to access values provided in application.properties, e.g.:
logging.level.org.springframework.web: DEBUG
logging.level.org.hibernate: ERROR
logging.file=${HOME}/application.log
userBucket.path=${HOME}/bucket
I want to access userBucket.path in my main program in a Spring Boot application.
You can use the #Value annotation and access the property in whichever Spring bean you're using
#Value("${userBucket.path}")
private String userBucketPath;
The Externalized Configuration section of the Spring Boot docs, explains all the details that you might need.
Another way is injecting org.springframework.core.env.Environment to your bean.
#Autowired
private Environment env;
....
public void method() {
.....
String path = env.getProperty("userBucket.path");
.....
}
#ConfigurationProperties can be used to map values from .properties( .yml also supported) to a POJO.
Consider the following Example file.
.properties
cust.data.employee.name=Sachin
cust.data.employee.dept=Cricket
Employee.java
import org.springframework.boot.context.properties.ConfigurationProperties;
import org.springframework.context.annotation.Configuration;
#ConfigurationProperties(prefix = "cust.data.employee")
#Configuration("employeeProperties")
public class Employee {
private String name;
private String dept;
//Getters and Setters go here
}
Now the properties value can be accessed by autowiring employeeProperties as follows.
#Autowired
private Employee employeeProperties;
public void method() {
String employeeName = employeeProperties.getName();
String employeeDept = employeeProperties.getDept();
}
Currently, I know about the following three ways:
1. The #Value annotation
#Value("${<property.name>}")
private static final <datatype> PROPERTY_NAME;
In my experience there are some situations when you are not
able to get the value or it is set to null.
For instance, when you try to set it in a preConstruct() method or an init() method. This happens because the value injection happens after the class is fully constructed. This is why it is better to use the third option.
2. The #PropertySource annotation
#PropertySource("classpath:application.properties")
// 'env' is an Environment variable
env.getProperty(configKey);
PropertySouce sets values from the property source file in an Environment variable (in your class) when the class is loaded.
So you able to fetch easily afterword.
Accessible through System Environment variable.
3. The #ConfigurationProperties annotation.
This is mostly used in Spring projects to load configuration properties.
It initializes an entity based on property data.
#ConfigurationProperties identifies the property file to load.
#Configuration creates a bean based on configuration file variables.
#ConfigurationProperties(prefix = "user")
#Configuration("UserData")
class user {
// Property & their getter / setter
}
#Autowired
private UserData userData;
userData.getPropertyName();
You can do it this way as well....
#Component
#PropertySource("classpath:application.properties")
public class ConfigProperties {
#Autowired
private Environment env;
public String getConfigValue(String configKey){
return env.getProperty(configKey);
}
}
Then wherever you want to read from application.properties, just pass the key to getConfigValue method.
#Autowired
ConfigProperties configProp;
// Read server.port from app.prop
String portNumber = configProp.getConfigValue("server.port");
Follow these steps.
Create your configuration class like below. You can see:
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.beans.factory.annotation.Value;
#Configuration
public class YourConfiguration {
// Passing the key which you set in application.properties
#Value("${userBucket.path}")
private String userBucket;
// Getting the value from that key which
// you set in application.properties
#Bean
public String getUserBucketPath() {
return userBucket;
}
}
When you have a configuration class then inject in the variable from a configuration where you need.
#Component
public class YourService {
#Autowired
private String getUserBucketPath;
// Now you have a value in the getUserBucketPath
// variable automatically.
}
You can use the #Value to load variables from the application.properties if you will use this value in one place, but if you need a more centralized way to load these variables #ConfigurationProperties is a better approach.
Additionally, you can load variables and cast them automatically if you need different data types to perform your validations and business logic.
application.properties
custom-app.enable-mocks = false
#Value("${custom-app.enable-mocks}")
private boolean enableMocks;
You can use #Value("${property-name}") from the
application.properties if your class is annotated with
#Configuration or #Component.
There's one more way I tried out was making a Utility class to read properties in the following way -
protected PropertiesUtility () throws IOException {
properties = new Properties();
InputStream inputStream =
getClass().getClassLoader().getResourceAsStream("application.properties");
properties.load(inputStream);
}
You can make use of static method to get the value of the key passed as the parameter.
You should inject #Autowired private Environment env; from import org.springframework.core.env.Environment;
And then use it this way:
env.getProperty("yourPropertyNameInApplication.properties")
#Value Spring annotation is used for injecting values into fields in Spring-manged beans, and it can be applied to the field or constructor/method parameter level.
Examples
String value from the annotation to the field
#Value("string value identifire in property file")
private String stringValue;
We can also use the #Value annotation to inject a Map property.
First, we'll need to define the property in the {key: ‘value' } form in our properties file:
valuesMap={key1: '1', key2: '2', key3: '3'}
Not that the values in the Map must be in single quotes.
Now inject this value from the property file as a Map:
#Value("#{${valuesMap}}")
private Map<String, Integer> valuesMap;
To get the value of a specific key
#Value("#{${valuesMap}.key1}")
private Integer valuesMapKey1;
We can also use the #Value annotation to inject a List property.
#Value("#{'${listOfValues}'.split(',')}")
private List<String> valuesList;
To pick the values from property file, we can have a Config reader class, something like ApplicationConfigReader.java.
Then define all the variables against properties. Refer to the below example,
application.properties
myapp.nationality: INDIAN
myapp.gender: Male
Below is the corresponding reader class.
#Component
#EnableConfigurationProperties
#ConfigurationProperties(prefix = "myapp")
class AppConfigReader{
private String nationality;
private String gender
// Getter and setter
}
Now we can auto-wire the reader class wherever we want to access property values.
E.g.,
#Service
class ServiceImpl{
#Autowired
private AppConfigReader appConfigReader;
//...
// Fetching values from the configuration reader
String nationality = appConfigReader.getNationality() ;
String gender = appConfigReader.getGender();
}
An application can read three types of values from the application.properties file.
application.properties
my.name = kelly
my.dbConnection = {connection_srting:'http://localhost:...', username:'benz', password:'pwd'}
Class file
#Value("${my.name}")
private String name;
#Value("#{${my.dbConnection}}")
private Map<String,String> dbValues;
If you don't have a property in application.properties then you can use the default value:
#Value("${your_name: default value}")
private String msg;
You can use the #Value annotation for reading values from an application.properties/yml file.
#Value("${application.name}")
private String applicationName;
There are 3 ways to read the application.properties,
using #Value, EnvironmentInterface and #ConfigurationProperties..
#Value(${userBucket.path})
private String value;
2nd way:
#Autowired
private Environment environment;
String s = environment.getProperty("userBucket.path");
3rd way:
#ConfigurationProperties("userbucket")
public class config {
private String path;
//getters setters
}
Can be read with getters and setters..
Reference - here
Injecting a property with the #Value annotation is straightforward:
#Value("${jdbc.url}")
private String jdbcUrl;
We can obtain the value of a property using the Environment API
#Autowired
private Environment env;
...
dataSource.setUrl(env.getProperty("jdbc.url"));
Another way to find a key/value in the configuration.
...
import org.springframework.core.env.ConfigurableEnvironment;
...
#SpringBootApplication
public class MyApplication {
#Autowired
private ConfigurableEnvironment myEnv;
...
#EventListener(ApplicationReadyEvent.class)
public void doSomethingAfterStartup()
throws Exception {
LOG.info("myEnv (userBucket.path): " + myEnv.getProperty("userBucket.path"));
}
}
You can access the application.properties file values by using:
#Value("${key_of_declared_value}")
The best ways to get property values are using:
1. Using Value annotation
#Value("${property.key}")
private String propertyKeyVariable;
2. Using the Environment bean
#Autowired
private Environment env;
public String getValue() {
return env.getProperty("property.key");
}
public void display() {
System.out.println("# Value : " + getValue);
}
Spring Boot allows us several methods to provide externalized configurations. You can try using file application.yml or YAML files instead of the property file and provide different property files setup according to different environments.
We can separate out the properties for each environment into separate YAML files under separate Spring profiles. Then during deployment you can use:
java -jar -Drun.profiles=SpringProfileName
to specify which Spring profile to use. Note that the YAML files should be named like
application-{environmentName}.yml
for them to be automatically taken up by Spring Boot.
Reference: 2. Externalized Configuration
To read from the application.yml or property file:
The easiest way to read a value from the property file or YAML is to use the Spring #value annotation. Spring automatically loads all values from the YAML file to the Spring environment, so we can directly use those values from the environment like:
#Component
public class MySampleBean {
#Value("${name}")
private String sampleName;
// ...
}
Or another method that Spring provides to read strongly-typed beans is as follows:
YML
ymca:
remote-address: 192.168.1.1
security:
username: admin
Corresponding POJO to read the YAML content:
#ConfigurationProperties("ymca")
public class YmcaProperties {
private InetAddress remoteAddress;
private final Security security = new Security();
public boolean isEnabled() { ... }
public void setEnabled(boolean enabled) { ... }
public InetAddress getRemoteAddress() { ... }
public void setRemoteAddress(InetAddress remoteAddress) { ... }
public Security getSecurity() { ... }
public static class Security {
private String username;
private String password;
public String getUsername() { ... }
public void setUsername(String username) { ... }
public String getPassword() { ... }
public void setPassword(String password) { ... }
}
}
The above method works well with YAML files.
Reference: 2. Externalized Configuration
There are two ways to access the value from the application.properties file:
Using the #Value annotation
#Value("${property-name}")
private data_type var_name;
Using an instance of the Environment class
#Autowired
private Environment environment;
// Access this way in the method where it's required
data_type var_name = environment.getProperty("property-name");
You can also inject an instance of the environment using constructor injection or creating a bean yourself.
Try class PropertiesLoaderUtils. This approach doesn’t use any annotation of Spring Boot. It is a traditional class way.
Example:
Resource resource = new ClassPathResource("/application.properties");
Properties props = PropertiesLoaderUtils.loadProperties(resource);
String url_server=props.getProperty("server_url");
Use the getProperty() method to pass the key and access the value in the properties file.
There are actually three ways to read the application.properties file,
Using Environment,
#Autowired
Environment environment
environment.getProperty({propertyName})
Or we can use #Value,
#Value("${property}")
but the problem with #Value is it might throw an exception if the value is not in the properties file.
The suggested way is using #ConfigurationProperties
#ConfigurationProperties("userBucket")
public class test{
private String path;
//getters and setters
}
For a detailed example - Reading application.properties.
The best thing is to use the #Value annotation. It will automatically assign a value to your object private Environment en.
This will reduce your code, and it will be easy to filter your files.
There are two ways,
you can directly use #Value in your class
#Value("#{'${application yml field name}'}")
public String ymlField;
Or
To make it clean you can clean #Configuration class where you can add all your #value
#Configuration
public class AppConfig {
#Value("#{'${application yml field name}'}")
public String ymlField;
}
application.yml or application.properties
config.value1: 10
config.value2: 20
config.str: This is a simle str
MyConfig class
#Configuration
#ConfigurationProperties(prefix = "config")
public class MyConfig {
int value1;
int value2;
String str;
public int getValue1() {
return value1;
}
// Add the rest of getters here...
// Values are already mapped in this class. You can access them via getters.
}
Any class that wants to access config values
#Import(MyConfig.class)
class MyClass {
private MyConfig myConfig;
#Autowired
public MyClass(MyConfig myConfig) {
this.myConfig = myConfig;
System.out.println( myConfig.getValue1() );
}
}
The easiest way would be to use the #Value annotation provided by Spring Boot. You need to define a variable at class level. For example:
#Value("${userBucket.path}")
private String userBucketPath
There is another way you can do this via the Environment Class. For example:
Autowire the environment variable to your class where you need to access this property:
#Autowired
private Environment environment
Use the environment variable to get the property value in the line you need it using:
environment.getProperty("userBucket.path");
Hope this answers your question!
To read application.properties or application.yml attributes follow the following steps:
Add your attributes in application.properties or application.yaml
Create config class and add your attributes
application.jwt.secretKey=value
application.jwt.tokenPrefix=value
application.jwt.tokenExpiresAfterDays=value ## 14
application:
jwt:
secret-key: value
token-prefix: value
token-expires-after-days: value ## 14
#Configuration("jwtProperties") // you can leave it empty
#EnableConfigurationProperties
#ConfigurationProperties(prefix = "application.jwt") // prefix is required
public class JwtConfig {
private String secretKey;
private String tokenPrefix;
private int tokenExpiresAfterDays;
// getters and setters
}
NOTE: in .yaml file you have to use kabab-case
Now to use the config class just instantiate it, you can do this manualy or with dependency injection.
public class Target {
private final JwtConfig jwtConfig;
#Autowired
public Target(JwtConfig jwtConfig) {
this.jwtConfig = jwtConfig;
}
// jwtConfig.getSecretKey()
}
For me, none of the above did directly work for me.
I did the following:
In addition to Rodrigo Villalba Zayas' answer, I added implements InitializingBean to the class and implemented the method
#Override
public void afterPropertiesSet() {
String path = env.getProperty("userBucket.path");
}
So that will look like
import org.springframework.core.env.Environment;
public class xyz implements InitializingBean {
#Autowired
private Environment env;
private String path;
....
#Override
public void afterPropertiesSet() {
path = env.getProperty("userBucket.path");
}
public void method() {
System.out.println("Path: " + path);
}
}
I had this problem too. But there is a very simple solution. Just declare your variable in the constructor.
My example:
application.propperties:
#Session
session.timeout=15
SessionServiceImpl class:
private final int SESSION_TIMEOUT;
private final SessionRepository sessionRepository;
#Autowired
public SessionServiceImpl(#Value("${session.timeout}") int sessionTimeout,
SessionRepository sessionRepository) {
this.SESSION_TIMEOUT = sessionTimeout;
this.sessionRepository = sessionRepository;
}
You can use #ConfigurationProperties. It's simple and easy to access a value defined in application.properties:
# Datasource
app.datasource.first.jdbc-url=jdbc:mysql://x.x.x.x:3306/ovtools?useUnicode=true&useJDBCCompliantTimezoneShift=true&useLegacyDatetimeCode=false&serverTimezone=UTC
app.datasource.first.username=
app.datasource.first.password=
app.datasource.first.driver-class-name=com.mysql.cj.jdbc.Driver
server.port=8686
spring.jpa.hibernate.ddl-auto=update
spring.jpa.generate-ddl=true
spring.jpa.show-sql=true
spring.jpa.database=mysql
#Slf4j
#Configuration
public class DataSourceConfig {
#Bean(name = "tracenvDb")
#Primary
#ConfigurationProperties(prefix = "app.datasource.first")
public DataSource mysqlDataSourceanomalie() {
return DataSourceBuilder.create().build();
}
#Bean(name = "JdbcTemplateenv")
public JdbcTemplate jdbcTemplateanomalie(#Qualifier("tracenvDb") DataSource datasourcetracenv) {
return new JdbcTemplate(datasourcetracenv);
}