Lifecycle methods not called in test scope for beans extending a class with lifecycle methods

[janfa]

When using a bean factory for the test scope, lifecycle methods are not invoked on beans that inherit from a superclass containing such methods.

In contrast, when running the application with the default scope, the behavior is as expected, and the methods annotated with e.g. @PostConstruct are invoked correctly.
It appears that the generated TestBeanFactory$DI build_-methods are missing the builder.addPostConstruct() statement.

Here's a minimal example project demonstrating this issue: https://git.iem.de/jan/avaje-generator-bug-example
In this project, the main application correctly resolves the greeting message, whereas the unit test fails to do so.
So far, I haven't been able to pinpoint the exact location in the inject-generator that causes this behavior.

One interesting detail I’ve noticed: The issue seems to depend on the naming of the subclass. If the subclass name ends with the name of the superclass, the problem does not occur. You can test this by renaming ServiceCreator to just Service in the provided example.

Thanks for your work on this project!

[SentryMan]

This seems less of a bug and more of a "factory methods don't support postconstruct." automatically

[SentryMan]

You need to do something like

@TestScope
@Factory
public class TestBeanFactory {
  @Bean(initMethod = "setup")
  public GreetingService greetingService() {
    return new GreetingService();
  }
}

[SentryMan]

@janfa is the above solution sufficient for you?

[rbygrave]

Looks like a bug to me. I need to look at it.

…

On Fri, 25 Apr 2025, 4:33 pm Josiah Noel, ***@***.***> wrote: *SentryMan* left a comment (avaje/avaje-inject#809) <#809 (comment)> @janfa <https://github.com/janfa> is the above solution sufficient for you? — Reply to this email directly, view it on GitHub <#809 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABTATNP4MUWTEMS65O4DTL23G3JTAVCNFSM6AAAAAB3Y42TVGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMRZGM2DSMRYG4> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[janfa]

@SentryMan my current workaround is to explicitly annotate the setup method in GreetingService with @PostConstruct. Then, the factory method contains the invocation of addPostConstruct and the test result is as expected.

Given this, the behavior doesn’t seem entirely consistent.
For certain tests, I’d like to provide beans via a factory, even though in the default scope they aren’t provided that way. It wasn’t clear to me that this would affect the lifecycle methods in terms of "factory methods don't support postconstruct automatically".
If that is indeed the intended behavior, I’m absolutely fine with it. Otherwise, I’d be glad to help refine the implementation.

[SentryMan]

Alright then, if it's a bug then I'll fix it

[SentryMan]

It feels like more of an enhancement, since we made no effort to support inherited lifecycle methods in the first place.