GlassFish 不支持在 EAR 之间共享公共类加载器？有解决方法吗？
尝试发现尝试解决与将 JFire ERP（符合 EJB 3.1 兼容）从 Jboss 4 移植到 Glassfish v3 相关的阻塞问题是否可行。
我想在 glassfish v3 而不是 jboss 上部署 JFire ERP，这样我就可以将它与我已经开发的系统集成起来。部署在GF上。 在文档中，他们将这种“共享公共类加载器”描述为阻塞问题。但引用的sun文档已经过时了。
“根据 Sun 文档（Sun GlassFish Communications Server 1.5 开发人员指南），GlassFish 不支持在 EAR 之间共享通用的 ClassLoader。由于 JFire 在服务器端使用 EAR 来组织模块（一个 EAR = 一个模块），因此这是一种阻塞问题。”
我已经对此进行了一些研究，但我并不真正理解这个问题，或者即使它仍然是 gf v3 中的问题。
我真的只是想深入了解这个问题&也许是关于我应该去哪里寻找的提示。任何方向或见解将不胜感激。
Trying to discover if it's feasible to attempt tackling blocking issues associated with porting JFire ERP, (EJB 3.1 compliant) from Jboss 4, to Glassfish v3.
I'd like to deploy JFire ERP on glassfish v3 instead of jboss, so I can integrate it with the systems I've already developed & deployed on gf.
In the documentation they describe this 'sharing a common ClassLoader' as a blocking issue. But the quoted sun document is outdated.
"According to this Sun document (Sun GlassFish Communications Server 1.5 Developer's Guide), GlassFish does not support to share a common ClassLoader among EARs. Since JFire uses EARs on the server side to organize modules (one EAR = one module), this is a blocking issue."
I have done some research into it, but I don’t really understand the problem or even if it still is an issue in gf v3.
I’d really just like some insight into the issue & maybe a tip as to where I should be looking. Any direction or insight would be appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
小细节，但引用的文档不正确。尝试 http://docs.sun.com/app/docs/coll/1343.13 相反（最新的 GlassFish 稳定版本是 3.0.1）。
也不确定 EJB 3.1 兼容是什么意思 - 这是一年前的技术版本，尚未受到 JBoss 支持。如果它确实基于 EJB 3.1，那么 JNDI 部署名称现已标准化，并且 jfire 站点上引用的 GlassFish 问题没有实际意义。
我认为你需要 jfire 人员的一些协作/改变。
Minor detail, but the documentation referenced is not the correct one. Try http://docs.sun.com/app/docs/coll/1343.13 instead (latest GlassFish stable release if 3.0.1).
Also not sure what you mean by EJB 3.1 compliant - this is a technology release a year ago and not yet supported by JBoss. If it is indeed based on EJB 3.1, then JNDI deploy names have now been standardized and the GlassFish issue referenced on the jfire site is moot.
I think you need some collaboration/changes from the jfire folks.