OSGI runtime inside traditional Java EE server

I understand it should probably be other way round (OSGI runtime hosting Java EE servers), as it is apparently already possible with glassfish.

However, our clients have extensive experience in administering traditional Java EE servers and significant investment (licenses, training etc.) Our architecture would benefit from OSGI modular architecture, but I can not ask our clients to switch from Java EE servers to OSGI runtimes.

Is there a way to install OSGI runtime as war or ear inside traditional Java EE servers, even if they will use no container开发者_如何学Go-managed resources (for example thread or connection pools) nor other Java EE features like JNDI, EJB etc?

Our applications use technologies like Hibernate, Spring etc.

---

You might want to look at the bridge servlet solution from Equinox. They have a special servlet (bridge servlet) that spawns an OSGi runtime, adds an OSGi HTTP service, and proxies traffic to the HTTP service (and ultimately to your servlets that register themselves to the HTTP service).