Help migrate to 4.x in plain OSGi environment

[spacehorst]

Hi all,

can somebody please point me how to migrate from RAP 3.x to 4.x in a plain OSGi environment?

We successfully have been using a bndtools based project setup for RAP 3.x e4 for several years which is as following:
An OSGi framework is launched containing an Apache Felix bundled Jetty 9 as well as Eclipse RAP relevant bundles excluding the RAP bundled Jetty. The RAP application configuration is done via declarative services.

I fail transfering this setup in analogy to RAP 4.3 for unknown reasons.
I managed all the transition from javax.* to jakarta.*, the Apache Felix Jetty is now version 12.
The application bundles are well resolved and the bundles are all in active respective starting state (manual activation of lazy activated bundles works).

Now the #configure-Method of our RAP ApplicationConfiguration component is never called, leading to a 404 in Jetty.
Debugging lead me to the point that org.eclipse.rap.rwt.osgi.internal.ApplicationLauncherImpl#launchWithConfiguration has an empty ServiceConatiner for org.eclipse.rap.service.http.HttpService.
(Switching the Jetty implementation to the RAP-provided one works, despite that org.eclipse.rap.http.jetty-Bundle is lazy and has to be activated manually.)

What is the meaning of org.eclipse.rap.service.http.HttpService and how does it relate to org.osgi.service.http.HttpService which has quite the same signature?
How can we achive a setup with 4.x using an arbitrary osgi.Http*- service implementation ?

Thanks
Sebastian