[GitHub] [shardingsphere] poo0054 commented on issue #18966: ShardingAlgorithmProvidedBeanRegistry login has failed

[GitBox <gi...@apache.org>]

poo0054 commented on issue #18966:
URL: https://github.com/apache/shardingsphere/issues/18966#issuecomment-1181246588

   Hello, thank you very much for your reply. I think I've found the reason   .I should have introduced sentinel.
   I found the sentinelbeanpostprocessor in sentinel. It is not a postprocessor decorated with static.   So sentinelautoconfiguration will be loaded. When creating sentinelautoconfiguration bean, many processors will be used, including methodvalidationpostprocessor.   And I just customized a bean validator in baseconfiguration, and I injected a testservice in baseconfiguration. I injected data sources into testservice. As a result, the data source is loaded in advance. The whole spring lifecycle sequence is completely destroyed
   
   
   
   The following is my simplified case in gitlab:
   
   > https://gitlab.com/poo0054/test
   
   Thank you very much for your help!


-- 
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: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org