-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Qute CDI integration - named dependent bean is destroyed before it's actually used #24137
Comments
/cc @manovotn |
We would have to introduce some kind of "expression evaluated callback" in order to implement this correcly. Alternatively, we could bind a |
We couldn't because the lifecycle of a |
- dependent beans are now: 1) shared accross all expressions for a single rendering operation, 2) destroyed correctly after the rendering finished - resolves quarkusio#24137
- dependent beans are now: 1) shared accross all expressions for a single rendering operation, 2) destroyed correctly after the rendering finished - resolves quarkusio#24137
I think that the current behavior makes no sense. However, the CDI rules for EL seem to be quite inefficient. Therefore, in my proposal
|
- dependent beans are now: 1) shared across all expressions for a single rendering operation, 2) destroyed correctly after the rendering finished - resolves quarkusio#24137
- dependent beans are now: 1) shared across all expressions for a single rendering operation, 2) destroyed correctly after the rendering finished - resolves quarkusio#24137
The behavior is not standardized anywhere but it would make sense to follow the CDI rules for EL: https://jakarta.ee/specifications/cdi/2.0/cdi-spec-2.0.html#dependent_context_ee
NOTE: In this context, "destroyed" means that if a
@Dependent
bean has a@PreDestroy
callback associated then this callback is executed before the bean instance is used e.g. to output a value.The text was updated successfully, but these errors were encountered: