Details
-
Task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
None
-
Not defined
Description
In the past, we have tended towards using PostConstruct for initialisation of classes. However, at times it might be more appropriate to use the ApplicationReadyEvent instead. We should consider our current usage and update to the EventListener instead where appropriate. Things to consider:
- PostConstruct failing will prevent application startup. Sometimes this is the desired behaviour
- ApplicationReady will execute after Optimize is running, so failure will not prevent startup. This might lead to unexpected or undesirable consequences in terms of the state of the application
