apache/shardingsphere

ShardingSphere Bean is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

Lacxner opened this issue · 8 comments

Lacxner commented

Bug Report

For English only, other languages will not accept.

Before report a bug, make sure you have:

Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot reproduce it on current information, we will close it.

Please answer these questions before submitting your issue. Thanks!

Which version of ShardingSphere did you use?

5.0.0Beta

Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?

ShardingSphere-JDBC

Expected behavior

Actual behavior

Reason analyze (If you can)

Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.

Example codes for reproduce this issue (such as a github link).

Console print Bean is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) where application bootstraps.
1628085763(1)
1628085883(1)

linghengqian commented

I will make a try.

linghengqian commented

  • There is a problem, ShardingSphere JDBC SpringBoot Starter is still using spring-context-4.3.25.RELEASE instead of spring-context-5.x, which causes org.springframework.context.annotation.Configuration not to exist proxyBeanMethods properties.

  • Considering issues like #20963 , I think we should drop ShardingSphere JDBC SpringBoot Starter support for SpringBoot OSS 1.X?

  • image

  • image

linghengqian commented

  • I noticed that the git record actually used Spring Framework 5.x for a while, but was reverted. I will be submitting a PR to drop support for Spring Boot OSS 1.X shortly.

  • Considering https://spring.io/projects/spring-framework#support , the scope of the project's springframework.version should start from 5.3.0 to facilitate collaboration.

github-actions commented

Hello , this issue has not received a reply for several days.
This issue is supposed to be closed.

  • ❤️1
linghengqian commented
  • I just can't submit a PR right away due to personal matters.
linghengqian commented
  • Found that I can't fully solve this problem locally, I'm not working on this issue.
linghengqian commented
  • This issue should be marked as resolved and closed due to #22469 .
RaigorJiang commented

Closed for #22469.