Closed sabbyanandan closed 5 years ago
I just had to take a look at it while working on another problem and it appears that ServerController
bean declared in SchemaServerConfiguration
is completely redundant as it doesn't override anything nor it provides any extra features/functionality. So simply removing it from SchemaServerConfiguration
is all that is needed IMO.
It appears the sample breaks when we remove the bean definition. Let's retest and verify.
Since there is no EnableAutoConfiguration
on ServerController
, I believe it is required to redefine the controller bean in ScheamaServerConfiguation
. cc/ @olegz
Since it is working the way it is defined right now, I am closing this issue.
Actually the problem is that at the moment one can no longer start SchemaRegistryServerApplication
as it fails with override warning. I think the real issue is that ServerController
is a @Component
already, so bootstrapping it as a bean is meaningless and instead we should simply include it as @Import
Relates to AvroSchemaRegistry support.