Changes in OSGI-support

Hi

We’re using Vaadin 8.8.6 and want to upgrade to Vaadin 8.12.0. We run our app successfully in OSGI (Karaf 4.1.5, 4.2.9) with 8.8.6 but plain upgrade to 8.12.0 fails.
With 8.8.6, the http-endpoint listing is like

144 │ ResourceServlet │ gz │ Deployed │ /vaadin-8.8.6/VAADIN/vaadinBootstrap.js.gz │ [/vaadin-8.8.6/VAADIN/vaadinBootstrap.js.gz/*]

and the bootstrap.js is loaded from <script type="text/javascript" src="/vaadin-8.8.6/VAADIN/vaadinBootstrap.js?v=8.8.6"></script>

With 8.12.0 the same entry looks like
149 │ ResourceServlet │ gz │ Deployed │ /VAADIN/vaadinBootstrap.js.gz │ [/VAADIN/vaadinBootstrap.js.gz/*]
and the bootstrap.js is loaded from <script type="text/javascript" src="/vaadin-8.12.0/VAADIN/vaadinBootstrap.js?v=8.12.0"></script>

Version 8.9.0 also results to the same as 8.12.0.
With 8.12.0 we get 404 for the bootstrap, since the URL doesn’t match anymore.
Now I’m assuming commit https://github.com/vaadin/framework/commit/583920f327c338a020d4e09e420548f44127cb7f is the reason behind this change but I fail to see how.

Should I post this also on SO?

For me it looks like that there something wrong with context path configuration, but it is difficult to say anything more specific at the moment.

The context path config hasn’t changed, the only change between those is the Vaadin version.
We have our Servlet registered as VaadinServlet with it’s own ServletContextHelper (not using the one from vaadin-shared).
Apparently this is not a common issue so I’ll need to dig deeper.