java - 最有前途的新 JSR？

Question

最近我选择了一个非常有用的网络服务框架，Jersey (JAX-RS 又名 jsr-311；及其摇滚启动实现)，以及一个漂亮的验证库 Hibernate Validator (“Bean 验证 API”，jsr-303)。

这两个 jsr 都是相对较新的人，这让我想知道我可能还遗漏了什么 -- 鉴于有数百个 JSR，具有不同程度的进展、 Activity 和潜力，跟踪它们并不容易全部。

那么除了我提到的 2 个之外，还有哪些其他人认为有前途且值得关注的？

Answer 1

JSR-291 : Java™ SE 的动态组件支持

---

基于 OSGi 模型，将其集成到 Java 中会非常有趣。

但是JSR-277最终被选中(Java 模块依赖项)... before being dropped来自当前的 JDK7 实现。

与此同时，有plenty of OSGi frameworks out there to play with ;)

---

如“模块依赖关系的表示”一文中所述:

One of the key differences between JSR 291 and JSR 277 is the way in which module dependencies are represented, satisfied, and managed.

[...] a more important difference relates to the need to be able predict the behaviour of a collection of modules. This is crucial when managing the dependencies of modules.

• With JSR 291, an external management system is able to read the dependency declarations in each module and apply the rules in the specification to determine how these modules will be wired up, whether there are any missing dependencies, and, if there are, how such dependencies could be satisfied.

• With JSR 277 the position is quite different when import policies are used. The only way to determine the behavior of an import policy is to execute it. But even then, there is no guarantee that the import policy will give the same result each time it runs. Also, if there are missing dependencies, it is not feasible to examine the import policy to determine how the missing dependencies could be satisfied