Jetty 12 : Handler.Collection does not propagate Server to handlers in expected way

[joakime]

Jetty version(s)
Jetty 12

Description

In Jetty 12, if you use the jetty-core org.eclipse.jetty.server.Handler$Collection the .setHandlers(List) does not propagate the Server correctly.

Example code.

WebAppContext context = new WebAppContext();
context.setContextPath("/");
context.setBaseResource(context.getResourceFactory().newResource(staticBase));
server.setHandler(new Handler.Collection(context, new DefaultHandler()));
server.start();

The DefaultHandler.setServer(Server) never gets called with a valid Server instance.

This is because the internal Handler.Collection processing does it's handler.setServer(server) far too early.
AFAICT, this seems to be the only Handler implementation with this bug.

[gregw]

fixed by a0d6f42

[lorban]

@gregw sorry, I've had to revert these changes in #8452 because they broke the build.

[gregw]

@lorban no probs.... any hint to how the build was broken?

[github-actions]

This issue has been automatically marked as stale because it has been a
full year without activity. It will be closed if no further activity occurs.
Thank you for your contributions.

[gregw]

This was fixed during Handler restructure in 12.