You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the container.close() is called, we may get an exception from HelidonContainerImpl that Container not running.
This is because we set the "not running" before finalizing the container work. One of the things it does is that it triggers events (such as Application scoped before destroyed event) that may in turn instantiate beans. If such a bean uses CDI.current(), it breaks.
To reproduce:
create a bean that is not used by the application at all
The "stop" part should throw an exception as described above.
Correct behavior:
The CDI.current() should work (maybe we could issue a single warning with stacktrace, such as "container is shutting down, yet CDI was requested)
The text was updated successfully, but these errors were encountered:
When the
container.close()
is called, we may get an exception fromHelidonContainerImpl
thatContainer not running
.This is because we set the "not running" before finalizing the container work. One of the things it does is that it triggers events (such as Application scoped before destroyed event) that may in turn instantiate beans. If such a bean uses
CDI.current()
, it breaks.To reproduce:
The "stop" part should throw an exception as described above.
Correct behavior:
The
CDI.current()
should work (maybe we could issue a single warning with stacktrace, such as "container is shutting down, yet CDI was requested)The text was updated successfully, but these errors were encountered: