FISH-12192 bugfix: initialize WebContainer before HK2 class scanning so Rest APIs…

[lprimak]

… get loaded properly

fixes #7655

Description

This is a bugfix.

This PR forces loading of WebContainer (if exists) prior to HK2 class scanning.
If this is not done, classes such as @RegisterRestClient that are not directly CDI beans (but are @stereotypes) will not correctly register as valid CDI beans, and deployments will fail in postboot or when starting the server with applications already deployed.

[Pandrex247]

FYI: Conflicts

[lprimak]

Conflicts resolved, thanks!

[lprimak]

@Pandrex247 Any updates on this? It's the "next on the priority list" of my PRs.

Thank you :)

[lprimak]

@Pandrex247 @stian-sigvartsen
This one is up next :) It's been out for a while and works very well :)

[lprimak]

ping...thank you!

[lprimak]

@Pandrex247 @stian-sigvartsen Please bump... thank you

[Pandrex247]

Need to sit down with this and a debugger (and run through the reproducer).
From a quick eyeballing: won't this cause the web container to start for everything including things which didn't cause it to before e.g. EJB JARs?

[lprimak]

No. This just loads bundle. This doesn't start anything.

[Pandrex247]

This doesn't start anything.

Surely it does? Getting the service will call its post construct, which will create and start a web container

[lprimak]

I believe that in this code path, the startup level is below the one that triggers post-construct callbacks.

But in any case, this should not introduce any additional issues, as web containers "starts" in similar sequence even without the "triggering" getService() call - i.e. no bad sideffects,
but again, the more testing the better :)