Nico Strecker

Also in need

Thx @dosubot very clever answer but what i wanted to propose is that the parameterNameDiscoverer gets an Qualifier and the spelresolver takes that one with the qualifier this is a...

I currently ask the spring team if it could be a spring boot 3.5.0 issue. https://github.com/spring-projects/spring-boot/issues/45938 It seems like the ConditionalOnMissingBean was working in 3.4.6 but is now not working...

I will check that tomorrow and inform you and i try to set up a similar example but it just happens sometimes i dont know the exact reason either

So some info about the classes: # Resilience4j `SpelResolverConfigurationOnMissingBean` is part of the resilience4j `BulkheadAutoConfiguration` autoconfiguration (It imports `BulkheadConfigurationOnMissingBean.class` which extends `AbstractBulheadConfigurationOnMissingBean` which imports `SpelResolverConfigurationOnMissingBean`) so if i understand correctly...

I logged the following in my application locally: ```logs [Bean Init 149] Bean 'parameterNameDiscoverer' of type org.springframework.core.StandardReflectionParameterNameDiscoverer is initializing [Bean Init 150] Bean 'spelResolver' of type io.github.resilience4j.spring6.spelresolver.DefaultSpelResolver is initializing ......

@wilkinsona i did not manage to create a mvp at the moment Could this be interesting because just starting the app 5000 times with res4j and springdoc enabled and implemented...

Hey i know you want a MVP but i cant get one working even when starting the app with the java agents locally with same configs. But i am now...

Short update we had a "longer weekend" in germany. I will now check the getInPriorityOrder (y)

# AlphabeticallyOrdered So when alphabetically ordered the order in the list is: 5 - 18 = `io.github.resilience4j...` Where the `BulkheadAutoConfiguration` is on position 5 in the list (the BulkheadAutoCofig was...