OSGi : RouteRegistryInitializer which is responsible for servlet initialization logic is not invoked in OSGi

This issue is specific for Jetty in Felix OSGi container (both org.apache.felix.http.jetty and jetty osgi boot). May be this is a question of the web server bundle in OSGi and there is nothing to do on our side.

I register the servlet manually via the bundle activator (using HttpServiceTracker and manual servlet instance creation). And the application doesn’t have any routes available even though I have class with @Route annotation. It seems that RouteRegistryInitializer doesn’t do its job.

See #4367 for the servlet registration source code.

[pleku]

We should first test the approach recommended here https://github.com/vaadin/flow/issues/4376#issuecomment-405214203 (thanks @Sandared !) for the routes, and if that works, then use it for every other servlet context initializer we have. That can be left for future issues.

[denis-anisimov]

There is no anything specifically done for our code base. So nothing to change generically.

But our current tests uses jetty-osgi-boot which has an ability to run ServletContainerInitializer. But to enable this the appropriate classes are registered: https://github.com/vaadin/flow/blob/master/flow-tests/test-root-context/src/main/resources/META-INF/services/javax.servlet.ServletContainerInitializer

So either this file needs to be removed completely or all Flow initializers should be removed. This will disable automatic types discovering.