Dependent.class beans lifecycle: Manual destroy required?

[StephenOTT]

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!

[StephenOTT]

@sberyozkin any insight you can provide?

[StephenOTT]

Based on a conversation with @mkouba:

1. If you require the lifecycle events (such as PreDestroy) of the Dependent bean to be run, then you would need to explicitly/manually destroy the bean.
2. If you do not manually destroy the bean, and the bean is detached from other beans, then GC will remove it.