传统Java EE服务器内的OSGI运行时 [英] OSGI runtime inside traditional Java EE server

问题描述

我理解它应该是其他方式（OSGI运行时托管Java EE服务器），因为它是显然已经可以使用glassfish。

然而，我们的客户在管理传统的Java EE服务器和大量投资（许可证，培训等）方面拥有丰富的经验，
我们的架构将受益于OSGI模块化架构，但是我不能要求我们的客户端从Java EE服务器切换到OSGI运行时。

有没有办法即使不使用容器管理的资源（例如线程或连接池）以及其他Java EE功能（如JNDI，EJB等），OSGI运行时也将作为战争或耳机安装在传统的Java EE服务器内。

我们的应用程序使用Hibernate，Spring等技术。

解决方案

你可能想看看< a href =http：//www.e来自Equinox的clipse.org/equinox/server/http_in_container.phprel =nofollow noreferrer> bridge servlet 解决方案。
他们有一个特殊的servlet（桥Servlet），它产生一个OSGi运行时，添加一个OSGi HTTP服务，并代理HTTP服务的流量（最终到你注册自己的HTTP服务的servlet）。 >

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-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).

这篇关于传统Java EE服务器内的OSGI运行时的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！