[英]Modernization of the JMS API in Java EE 7
Here is a list of JSRs (Look at JSR 316 ). 这是一个JSR列表(请参阅 JSR 316 )。 When more details become available they will create a JSR for Java EE 7 and until then everything is speculation.
当更多细节可用时,他们将为Java EE 7创建一个JSR,直到那时一切都在猜测。
Reading the article you posted there is a telling quote: 阅读你发布的文章是一个有说服力的引用:
Of course, all it's still early days and a lot can change once the expert groups form and get to work.
当然,所有这些都还处于早期阶段,一旦专家组形成并开始工作,很多事情就会发生变化。
Basically EE 7 is in the very early days and the standardization process hasn't even really started. 基本上EE 7是在很早的时候,标准化过程甚至还没有真正开始。
There were a few words being said about this on Devoxx '10: 在Devoxx '10上有一些关于这个的说法:
JMS is an old specification, which need to evelove for addressing new communication layers:
JMS是一个旧规范,需要开发用于寻址新的通信层:
- resolving specification ambiguities
解决规范含糊不清
- standardized vendor extension
标准化供应商扩展
- integration with other specifications
与其他规格集成
- integration with the web tier
与Web层集成
- (websocket, JSON, NIO2)
(websocket,JSON,NIO2)
It's not much yet, hopefully more will be revealed soon. 它还没有多少,希望很快就能揭晓。 There was btw also a JMS BOF at Devoxx.
顺便说一句,在Devoxx也有一个JMS BOF。 Perhaps someone took notes of that?
也许有人记下了那个?
There is now JSR 343: JavaTM Message Service 2.0 : 现在有JSR 343:JavaTM Message Service 2.0 :
Changes that will be considered by the Expert Group for inclusion in this new revision include, but are not limited to, the following:
专家组将考虑纳入此新版本的变更包括但不限于以下内容:
- Changes to improve ease of development
改变以提高开发的便利性
- Clarification of the relationship between the JMS and other Java EE specifications
澄清JMS与其他Java EE规范之间的关系
- Definition of a new mandatory API to allow any JMS provider to be integrated with any Java EE application server
定义新的强制API,以允许任何JMS提供程序与任何Java EE应用程序服务器集成
- Extensions to support Java EE 7
支持Java EE 7的扩展
- Other enhancements as requested by the community
社区要求的其他增强功能
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.