Manage Jetty startup modules

[emilevauge]

I haven't found any solution to manage Jetty startup modules with Gretty http://www.eclipse.org/jetty/documentation/current/startup-modules.html. Is-it possible? Thank you for your work btw :)

[akhikhl]

Hi Emile :) No, Jetty startup modules are not (yet) supported. Can you describe a use-case when you need this feature?

[emilevauge]

I work on a project that uses websockets and that relies on jetty annotation scanning to instanciate endpoints. I cannot get it work using Gretty because some modules are disabled I think. No problem found using a standalone Jetty distribution.

[iNikem]

One more use case in addition to web sockets: We configure a jndi DataSource in jetty and it's jars by adding one more module to the jetty.

[kfowlks]

Another use case is using Keycloak and starting the jetty adapter module.

[provstevi]

Another use case is the Weld module for using CDI.

[jetztgradnet]

We use the official Jetty Docker container which contains the Jetty distribution. Individual modules can be loaded and activated and some settings specified via provided properties. This allows e.g. to load additional connectors, handlers (gzip), logging, ..., all without having to create a single monolithic jetty.xml file. Basically, instead of loading just a single config file, it would be great if serverConfigFile could also be an array of files which are applied in the provided order. Having an additional way to pass some config properties (e.g. http.port, ...) would make this feature complete.