hello! I’m hitting some weird problem with a custo...

# spring

[Dariusz Kuc]

hello! I’m hitting some weird problem with a custom BeanPostProcessor that my application context fails to load up as it fails to resolve some of the post processor dependencies complaining about unability to parse out SPeL value passed for one its parameters. My understanding is that Spring post processors should be applied at that point as they are PriorityOrdered so they take precedence over the regular ordered beans. Using Spring Boot 2.2.5.RELEASE

It’s a longshot but just wondering if anyone here hit some similar issue.

[Dariusz Kuc]

unfortunately don’t have an option to drop that custom bean processor as other libs depend on it 😞

[Dariusz Kuc]

error i’m hitting

Caused by: java.lang.NumberFormatException: For input string: "${my.property:60}"

since my.property is not specified it should default to 60 but it looks like it tries to parse whole string as an integer

[Dariusz Kuc]

it looks like ConfigurableBeanFactory used to create the dependent beans does not have

boolean hasEmbeddedValueResolver();

[thanksforallthefish]

is it koltin code? in that case, it should be "\${my.property:60}"

[Dariusz Kuc]

its coming from java lib

[Dariusz Kuc]

it looks like it has to do something with the order of loading up the beans