ImportHttpServices scans concrete classes implementing @HttpExchange interfaces

spring-web:7.0.8

When currently attempting to adapt and extend based on an httpclient interface, it will inject this class into the httpServiceProxyRegistry-bean. However, in reality, it is a regular class rather than an interface. Can non-interface classes be filtered out during the filtering process.

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'httpServiceProxyRegistry': [com.feeyo.common.client.limitx.ClientLimitxService] is not an interface
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1815)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:603)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:525)
at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:333)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:371)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:331)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:201)
at org.springframework.web.service.registry.AbstractHttpServiceRegistrar.getProxyInstance(AbstractHttpServiceRegistrar.java:204)

Start in AbstractHttpServiceRegistrar.java, especially getProxyInstance, and trace how ImportHttpServices discovers types annotated with @HttpExchange. Reproduce the failure with a concrete class implementing such an interface, then verify that registry creation ignores the concrete class while still handling the interface proxy.