funky-eyes commented on issue #6223: URL: https://github.com/apache/incubator-seata/issues/6223#issuecomment-1870734603
实际上的根本性问题是seata的配置中心实现不是以一种结合模式，比如seatafile+spring+远程配置中心，而是多选一的形式，导致了使用file的时候强行通过代理来与spring进行结合，而不是在spring下以spring schema扩展，springboot的SpringApplicationRunListener等拿到environment将其作为一个扩展的配置中心视线，以链式注册到某个configuration，按照优先级排序，从哪读取到非空值后则截止。还有你所说的#3991 的问题，springboot+file下并不会起到动态刷新配置的作用，所以就把它关闭了。还有一点就是，所有需要动态的配置都是需要监听的，spring貌似没有提供一个刷新事件的event对外（springcloud是有的） In fact, the fundamental problem is that the configuration center implementation of seata is not in a combination mode, such as seatafile + spring + remote configuration center, but in the form of multiple choices, which leads to the use of file when forcibly combining with spring through a proxy, instead of extending with spring schema under spring, the SpringApplicationRunListener of springboot, etc. get it as an extended configuration center line of sight, register with a configuration in a chain, sort by priority, and cut off after reading the non-null value from where. There is also the problem of #3991 you mentioned, springboot + file does not play a role in dynamically refreshing the configuration, so it is closed. Another point is that all dynamic configurations need to be listened to, and spring does not seem to provide a refresh event external (springcloud has it) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
