Since [WELD-1915], Weld SE is always registering a shutdown hook. This is beneficial for the end-user application that doesn't have to care about that concern.
However, for frameworks and libraries that integrate with Weld SE, that leads to conflicting shutdown lifecycle as they may have their own shutdown hook.
For example, that breaks DeltaSpike container control API whose Weld adapter shutdown method becomes useless in the context of a shutdown hook sequence. Incidentally, the Camel CDI component {{ MainSupport }} is broken has Camel has its own shutdown hook and cannot control the Weld container anymore.
An A better approach would be to enable the deactivation of the Weld SE shutdown hook as this is a common practice.
|
