hello! what is the preferred way to structure various configuration files, e.g. given some common co...

# spring

[Dariusz Kuc]

hello! what is the preferred way to structure various configuration files, e.g. given some common configuration beans is it better to

@Configuration @Import([A, B])
class TopLevelConfig {
  // uses beans from A/B
  // defines beans used commonly by A and B
}

or

@Configuration
class CommonConfig { // common beans }

@Configuration @Import(CommonConfig)
class A

@Configuration @Import(CommonConfig)
class B

@Configuration @Import([A, B])
class TopLevelConfig { // use beans from A/B }

[Dariusz Kuc]

basically is there any issue with importing same config multiple times

[Minatorak]

what is toplevelConfig do for?

[Dariusz Kuc]

Just organizes the imports and is the entry point for auto config

[Dariusz Kuc]

In 1 it also defines common beans for a/b (extracted to CommonConfig in 2)

[Sourabh Rawat]

Do you even need the imports? wont class A automatically detect CommonConfig, unless you are not using default auto configuration settings?

[Dariusz Kuc]

it is a library so cannot rely on auto config

[Dariusz Kuc]

afaik auto config should be configured only at an app level