将 EAR 模块转为 OSGI 包的正确方法
有必要将 EAR 的一部分(即战争)转变成 OSGI 包并保留其互操作性。 Glassfish 3.0.1 已经有了 osgi-web-container 模块,我成功部署了独立的 OSGI war。
但如果是前企业战争,我觉得有点困难。
- 我该如何处理来自以下位置的 EJB 调用: 未来的OSGI战争?够了吗 用真正的 JNDI 替换
@EJB
注入 查找? - API 和库怎么样 跨 EAR 共享?我可以分开并且 重新排列它们,但我仍然会 至少有一个双方都需要的罐子 EAR 和 OSGI 战争。复制,制作 作为 OSGI 捆绑自身并使其成为 以某种方式可以放在耳朵上,将其放置 GF域的库路径?
- 任何其他想法、建议都可以 让混合动力发挥作用?
There is a necessity to turn part of EAR (namely - war) into OSGI bundle and retain it's interoperability. Glassfish 3.0.1 already has osgi-web-container
module and I succeeded to deploy standalone OSGI war.
But in case of of ex-enterprise war it looks a bit difficult to me.
- What do I do with EJB calls from
inside future OSGI war? Is it enough
to replace@EJB
injections with true JNDI
lookups? - What about APIs and libraries
shared across EAR? I could split and
rearrange them, but still I will
have at least one jar needed by both
EAR and OSGI war. Duplicate, make it
as OSGI-bundle itself and make it
available to ear somehow, place it
GF domain's library path? - Any other ideas, advices which could
make that hybrid working?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
以下是一些可以尝试的事情:
@EJB
。即使在 OSGi War(又名 WAB)中,您的@EJB
也将继续工作。我建议您在 GlassFish 论坛 中跟进。
Here are a few things to try out:
@EJB
by JNDI lookup. Your@EJB
will continue to work even inside your OSGi War (aka WAB).I suggest you follow up in GlassFish forum.