Dependent.class beans lifecycle: Manual destroy required? #41145
Unanswered
StephenOTT
asked this question in
Q&A
Replies: 2 comments
-
@sberyozkin any insight you can provide? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Based on a conversation with @mkouba:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is generally the example mentioned for adding support to quarkus for getElResolver support:
https://github.com/apache/myfaces/blob/main/extensions/quarkus/runtime/src/main/java/org/apache/myfaces/core/extensions/quarkus/runtime/spi/QuarkusCdiELResolver.java
The link above mentions that
Dependent
beans are not supported. But in my use case, i need Dependent support.What i am looking to understand is the implications for generating new instances of the
Dependent
beans and requirements for their destruction.I have been able to generate new instances with a small code modification, but
For a dependent bean, do we need to explicitly destroy it? If yes, is there any infra in place to do this?
Also, if we look at: https://github.com/apache/myfaces/blob/main/extensions/quarkus/runtime/src/main/java/org/apache/myfaces/core/extensions/quarkus/runtime/spi/QuarkusCdiELResolver.java#L86, we see them caching the bean resolution. Is this actually required? / Does it make perf difference? or are they already being cached as part of the bean manager?
thanks!
Beta Was this translation helpful? Give feedback.
All reactions