How to dynamically update yml files in SpringBoot
Project dependencies
The project is based on version 2.0.0.RELEASE, so snakeyaml needs to be introduced separately, and higher versions are included
<dependency> <groupId>org.yaml</groupId> <artifactId>snakeyaml</artifactId> <version>1.23</version> </dependency>
Most methods on the Internet are to introduce spring-cloud The -context configuration component calls the refresh method of ContextRefresher to achieve the same effect. Consider the following two points that are not used.
The development framework uses logback logs. The introduction of spring-cloud-context will cause log configuration reading Get the error
Introducing spring-cloud-context will also introduce the spring-boot-starter-actuator component, which will open some health check routes and ports, requiring additional control over framework security
YML file content acquisition
Reading files under the resource file requires using ClassPathResource to obtain the InputStream
public String getTotalYamlFileContent() throws Exception { String fileName = "application.yml"; return getYamlFileContent(fileName); } public String getYamlFileContent(String fileName) throws Exception { ClassPathResource classPathResource = new ClassPathResource(fileName); return onvertStreamToString(classPathResource.getInputStream()); } public static String convertStreamToString(InputStream inputStream) throws Exception{ return IOUtils.toString(inputStream, "utf-8"); }
YML file content update
After we obtain the content of the yml file, we visually display it to the front desk for display modification, convert the modified content into a Map structure through the yaml.load method, and then use yaml.dumpAsMap to convert it into a stream and write it to the file
public void updateTotalYamlFileContent(String content) throws Exception { String fileName = "application.yml"; updateYamlFileContent(fileName, content); } public void updateYamlFileContent(String fileName, String content) throws Exception { Yaml template = new Yaml(); Map<String, Object> yamlMap = template.load(content); ClassPathResource classPathResource = new ClassPathResource(fileName); Yaml yaml = new Yaml(); //字符输出 FileWriter fileWriter = new FileWriter(classPathResource.getFile()); //用yaml方法把map结构格式化为yaml文件结构 fileWriter.write(yaml.dumpAsMap(yamlMap)); //刷新 fileWriter.flush(); //关闭流 fileWriter.close(); }
YML Property refresh
There are generally three ways to read and use yml properties in the program
Use Value annotation
@Value("${system.systemName}") private String systemName;
Read through environment injection
@Autowired private Environment environment; environment.getProperty("system.systemName")
Use ConfigurationProperties annotation Read
@Component @ConfigurationProperties(prefix = "system") public class SystemConfig { private String systemName; }
Property refresh
The configuration collection we read through the environment.getProperty method is actually stored in PropertySources. We only need to take out all the key-value pairs and store them in the propertyMap. Convert the content of the updated yml file into a ymlMap of the same format, merge the two Maps, and call the replace method of PropertySources for overall replacement.
But both the ymlMap after yaml.load and the propertyMap taken out by PropertySources Data deconstruction is different and requires manual conversion
The propertyMap collection is a simple key and value pair, and the key is a name in the form of properties, such as system.systemName=>xxxxx Group Management System
ymlMap collection is the key, the nested hierarchical structure of LinkedHashMap, for example system=>(systemName=>xxxxx Group Management System)
The conversion method is as follows
public HashMap<String, Object> convertYmlMapToPropertyMap(Map<String, Object> yamlMap) { HashMap<String, Object> propertyMap = new HashMap<String, Object>(); for (String key : yamlMap.keySet()) { String keyName = key; Object value = yamlMap.get(key); if (value != null && value.getClass() == LinkedHashMap.class) { convertYmlMapToPropertyMapSub(keyName, ((LinkedHashMap<String, Object>) value), propertyMap); } else { propertyMap.put(keyName, value); } } return propertyMap; } private void convertYmlMapToPropertyMapSub(String keyName, LinkedHashMap<String, Object> submMap, Map<String, Object> propertyMap) { for (String key : submMap.keySet()) { String newKey = keyName + "." + key; Object value = submMap.get(key); if (value != null && value.getClass() == LinkedHashMap.class) { convertYmlMapToPropertyMapSub(newKey, ((LinkedHashMap<String, Object>) value), propertyMap); } else { propertyMap.put(newKey, value); } } }
The refresh method is as follows
String name = "applicationConfig: [classpath:/" + fileName + "]"; MapPropertySource propertySource = (MapPropertySource) environment.getPropertySources().get(name); Map<String, Object> source = propertySource.getSource(); Map<String, Object> map = new HashMap<>(source.size()); map.putAll(source); Map<String, Object> propertyMap = convertYmlMapToPropertyMap(yamlMap); for (String key : propertyMap.keySet()) { Object value = propertyMap.get(key); map.put(key, value); } environment.getPropertySources().replace(name, new MapPropertySource(name, map));
Annotation Refresh
Whether it is the Value annotation or the ConfigurationProperties annotation, it is actually used by injecting the property method of the Bean object. We first customize the annotation RefreshValue to modify the class of the Bean where the property is located
By implementing the InstantiationAwareBeanPostProcessorAdapter interface, the corresponding beans are filtered and stored when the system starts. When updating the yml file, the properties of the corresponding
bean can be updated through spring's event notification.
Register events Use the EventListener annotation
@EventListener public void updateConfig(ConfigUpdateEvent configUpdateEvent) { if(mapper.containsKey(configUpdateEvent.key)){ List<FieldPair> fieldPairList = mapper.get(configUpdateEvent.key); if(fieldPairList.size()>0){ for (FieldPair fieldPair:fieldPairList) { fieldPair.updateValue(environment); } } } }
Notify the trigger event and use the publishEvent method of ApplicationContext
@Autowired private ApplicationContext applicationContext; for (String key : propertyMap.keySet()) { applicationContext.publishEvent(new YamlConfigRefreshPostProcessor.ConfigUpdateEvent(this, key)); }
The complete code of YamlConfigRefreshPostProcessor is as follows
@Component public class YamlConfigRefreshPostProcessor extends InstantiationAwareBeanPostProcessorAdapter implements EnvironmentAware { private Map> mapper = new HashMap<>(); private Environment environment; @Override public boolean postProcessAfterInstantiation(Object bean, String beanName) throws BeansException { processMetaValue(bean); return super.postProcessAfterInstantiation(bean, beanName); } @Override public void setEnvironment(Environment environment) { this.environment = environment; } private void processMetaValue(Object bean) { Class clz = bean.getClass(); if (!clz.isAnnotationPresent(RefreshValue.class)) { return; } if (clz.isAnnotationPresent(ConfigurationProperties.class)) { //@ConfigurationProperties注解 ConfigurationProperties config = (ConfigurationProperties) clz.getAnnotation(ConfigurationProperties.class); for (Field field : clz.getDeclaredFields()) { String key = config.prefix() + "." + field.getName(); if(mapper.containsKey(key)){ mapper.get(key).add(new FieldPair(bean, field, key)); }else{ List fieldPairList = new ArrayList<>(); fieldPairList.add(new FieldPair(bean, field, key)); mapper.put(key, fieldPairList); } } } else { //@Valuez注解 try { for (Field field : clz.getDeclaredFields()) { if (field.isAnnotationPresent(Value.class)) { Value val = field.getAnnotation(Value.class); String key = val.value().replace("${", "").replace("}", ""); if(mapper.containsKey(key)){ mapper.get(key).add(new FieldPair(bean, field, key)); }else{ List fieldPairList = new ArrayList<>(); fieldPairList.add(new FieldPair(bean, field, key)); mapper.put(key, fieldPairList); } } } } catch (Exception e) { e.printStackTrace(); System.exit(-1); } } } public static class FieldPair { private static PropertyPlaceholderHelper propertyPlaceholderHelper = new PropertyPlaceholderHelper("${", "}", ":", true); private Object bean; private Field field; private String value; public FieldPair(Object bean, Field field, String value) { this.bean = bean; this.field = field; this.value = value; } public void updateValue(Environment environment) { boolean access = field.isAccessible(); if (!access) { field.setAccessible(true); } try { if (field.getType() == String.class) { String updateVal = environment.getProperty(value); field.set(bean, updateVal); } else if (field.getType() == Integer.class) { Integer updateVal = environment.getProperty(value,Integer.class); field.set(bean, updateVal); } else if (field.getType() == int.class) { int updateVal = environment.getProperty(value,int.class); field.set(bean, updateVal); } else if (field.getType() == Boolean.class) { Boolean updateVal = environment.getProperty(value,Boolean.class); field.set(bean, updateVal); } else if (field.getType() == boolean.class) { boolean updateVal = environment.getProperty(value,boolean.class); field.set(bean, updateVal); } else { String updateVal = environment.getProperty(value); field.set(bean, JSONObject.parseObject(updateVal, field.getType())); } } catch (IllegalAccessException e) { e.printStackTrace(); } field.setAccessible(access); } public Object getBean() { return bean; } public void setBean(Object bean) { this.bean = bean; } public Field getField() { return field; } public void setField(Field field) { this.field = field; } public String getValue() { return value; } public void setValue(String value) { this.value = value; } } public static class ConfigUpdateEvent extends ApplicationEvent { String key; public ConfigUpdateEvent(Object source, String key) { super(source); this.key = key; } } @EventListener public void updateConfig(ConfigUpdateEvent configUpdateEvent) { if(mapper.containsKey(configUpdateEvent.key)){ List<FieldPair> fieldPairList = mapper.get(configUpdateEvent.key); if(fieldPairList.size()>0){ for (FieldPair fieldPair:fieldPairList) { fieldPair.updateValue(environment); } } } } }
The above is the detailed content of How to dynamically update yml files in SpringBoot. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Introduction to Jasypt Jasypt is a java library that allows a developer to add basic encryption functionality to his/her project with minimal effort and does not require a deep understanding of how encryption works. High security for one-way and two-way encryption. , standards-based encryption technology. Encrypt passwords, text, numbers, binaries... Suitable for integration into Spring-based applications, open API, for use with any JCE provider... Add the following dependency: com.github.ulisesbocchiojasypt-spring-boot-starter2. 1.1Jasypt benefits protect our system security. Even if the code is leaked, the data source can be guaranteed.

Usage scenario 1. The order was placed successfully but the payment was not made within 30 minutes. The payment timed out and the order was automatically canceled. 2. The order was signed and no evaluation was conducted for 7 days after signing. If the order times out and is not evaluated, the system defaults to a positive rating. 3. The order is placed successfully. If the merchant does not receive the order for 5 minutes, the order is cancelled. 4. The delivery times out, and push SMS reminder... For scenarios with long delays and low real-time performance, we can Use task scheduling to perform regular polling processing. For example: xxl-job Today we will pick

1. Redis implements distributed lock principle and why distributed locks are needed. Before talking about distributed locks, it is necessary to explain why distributed locks are needed. The opposite of distributed locks is stand-alone locks. When we write multi-threaded programs, we avoid data problems caused by operating a shared variable at the same time. We usually use a lock to mutually exclude the shared variables to ensure the correctness of the shared variables. Its scope of use is in the same process. If there are multiple processes that need to operate a shared resource at the same time, how can they be mutually exclusive? Today's business applications are usually microservice architecture, which also means that one application will deploy multiple processes. If multiple processes need to modify the same row of records in MySQL, in order to avoid dirty data caused by out-of-order operations, distribution needs to be introduced at this time. The style is locked. Want to achieve points

Springboot reads the file, but cannot access the latest development after packaging it into a jar package. There is a situation where springboot cannot read the file after packaging it into a jar package. The reason is that after packaging, the virtual path of the file is invalid and can only be accessed through the stream. Read. The file is under resources publicvoidtest(){Listnames=newArrayList();InputStreamReaderread=null;try{ClassPathResourceresource=newClassPathResource("name.txt");Input

When Springboot+Mybatis-plus does not use SQL statements to perform multi-table adding operations, the problems I encountered are decomposed by simulating thinking in the test environment: Create a BrandDTO object with parameters to simulate passing parameters to the background. We all know that it is extremely difficult to perform multi-table operations in Mybatis-plus. If you do not use tools such as Mybatis-plus-join, you can only configure the corresponding Mapper.xml file and configure The smelly and long ResultMap, and then write the corresponding sql statement. Although this method seems cumbersome, it is highly flexible and allows us to

SpringBoot and SpringMVC are both commonly used frameworks in Java development, but there are some obvious differences between them. This article will explore the features and uses of these two frameworks and compare their differences. First, let's learn about SpringBoot. SpringBoot was developed by the Pivotal team to simplify the creation and deployment of applications based on the Spring framework. It provides a fast, lightweight way to build stand-alone, executable

1. Customize RedisTemplate1.1, RedisAPI default serialization mechanism. The API-based Redis cache implementation uses the RedisTemplate template for data caching operations. Here, open the RedisTemplate class and view the source code information of the class. publicclassRedisTemplateextendsRedisAccessorimplementsRedisOperations, BeanClassLoaderAware{//Declare key, Various serialization methods of value, the initial value is empty @NullableprivateRedisSe

This article will write a detailed example to talk about the actual development of dubbo+nacos+Spring Boot. This article will not cover too much theoretical knowledge, but will write the simplest example to illustrate how dubbo can be integrated with nacos to quickly build a development environment.
