Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jetty 9 Container.start() should wait till all non-webapp handlers are deployed. #13

Open
joakime opened this issue Nov 18, 2013 · 1 comment

Comments

@joakime
Copy link
Contributor

joakime commented Nov 18, 2013

There are various non-webapp, non-servlet, based handlers that can be added to the Jetty server (such as Login / Security / Proxy / FCGI / Rewrite / etc ...)

These need to be deployed, before the webapp archive, and before the server.start() call.

The call in JettyEmbeddedContainer.start() to server.start() should be run after all of these handlers are added.

@joakime
Copy link
Contributor Author

joakime commented Feb 17, 2022

@starksm64 this could be addressed by supporting proper (jetty) module based configuration, like 2 of the other issues hint at (#5 and #9).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant