Spring Boot 3 - javax.annotation.PostConstruct -> jakarta.annotation.PostConstruct

[cer]

Some Eventuate classes use @PostConstruct, and so cannot support Spring Boot 2 and Spring 3.

Perhaps the solution replace the annotation with old-style InitializingBean

/cc @kwonglau

[kwonglau]

I believe using the @bean(initMethod='', destroyMethod='') will work well and we can completely remove annotation.

[cer]

Good point. I'd forgotten about that feature. 🤣

[cer]

@kwonglau

Hmm... user-written code needs to use @PostConstruct - see eventuate-tram/eventuate-tram-sagas@33974c7

I think the API would be better if user visible @bean classes implemented InitializingBean

This might, however, require AbstractCommandDispatcher + Spring/Micronaut/... specific CommandDispatcher classes

Thoughts?

[kwonglau]

@cer I like the idea that visible @bean class implements the InitializingBean interface so that we can minimize the diff between Spring Boot 2 vs Spring Boot 3 codebase. This will also make migration easier.

[cer]

@cer I like the idea that visible @bean class implements the InitializingBean interface so that we can minimize the diff between Spring Boot 2 vs Spring Boot 3 codebase. This will also make migration easier.

This might be a non-issue. These beans are created by factories, which can call initialize. That's what eventuate-tram/eventuate-tram-sagas@2e8071d should have done