EJB 容器的向后兼容性如何？
我继承了一个在 JBoss 2.4.3 上运行的应用程序（我相信它与 EJB 规范 2.0 兼容），并且我遇到了很多问题（例如能够使用现代 log4j“ Logger”api [JBoss 2.4 特定问题促使我升级]）。
我知道我应该能够毫无问题地使用 EJB 2.1 容器 (Jboss 4)，但我是否应该期望能够更进一步？
EJB 的向后兼容性要求是什么？
它们是否意味着通过主要版本向后兼容？
应用程序供应商是否使它们完全向后兼容？
需要进行哪些修改才能使旧应用程序符合要求？ （小还是大？应用程序配置或重新编译？等）
I have inherited an application that is running on JBoss 2.4.3 (which I believe is EJB spec 2.0 compatible), and I'm running into quite a few issues (like being able to use modern log4j "Logger" apis [JBoss 2.4 specific issues pushing me to upgrade]).
I understand that I should be able to use a EJB 2.1 container (Jboss 4) without issue, but should I expect to be able to go further?
What are the backwards compatibility requirements for EJB?
Are they meant to be backwards compatible through major versions?
Do application vendors make them fully backwards compatible?
What modifications are necessary to make an older application conform? (small or large? application configuration or re-compilation? etc)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
log4j 和 EJB 2.0 不相关。如果您遇到 log4j 问题，那么很可能是类路径问题，而不是 EJB 2.0 兼容性问题。您的旧应用程序可能假设 log4j 位于系统类路径上的某个位置。
log4j and EJB 2.0 are not related. If you have problems with log4j, then most likely it is a class path issue and not EJB 2.0 compatbility issue. Probably your old application assumes that log4j is somewhere on system class path.
http://what- when-how.com/enterprise-javabeans-3/backward-compatibility-and-interoperability-with-ejb-2/ 指出
这是一个好兆头。接下来进一步讨论混合 EJB 2 和 3 功能。所以可能会有一些例外，但实际上不应该是几乎不可能的情况。
现实可能有所不同；如果我发现 jboss 升级有问题，我会更新。
http://what-when-how.com/enterprise-javabeans-3/backward-compatibility-and-interoperability-with-ejb-2/ states that
Which is a good sign. It goes on further to talk about mixing EJB 2 and 3 functionality. So there may be some exceptions, but it really shouldn't be any where near impossible.
Reality may be different; I'll update if I find problems with my jboss upgrade.
请参阅 EJB 库的此兼容性报告：
See this compatibility report for the EJB library: