Which JSRs Are Included In Java EE 7?
I started to fill out a table of all of the Java Specification Requests that are supposed to go into Java EE 7. Because the platform edition is still being decided, some of the details are rather hard to pin down.
The full EJB Product for Java EE 7 has these following standard components and APIs:-
|
Name |
Version |
Description |
JSR |
Web Profile |
|
Batch Process |
1.0 |
Batch Processing |
352 |
|
|
Bean Validation |
1.1 |
Bean validation framework |
349 |
|
|
Common Annotations |
1.1 |
Common Annotations for the Java EE platform |
250 |
Might be |
|
CDI |
1.1 |
Contexts and Dependency Injection for Java EE |
346 |
Y |
|
Concurrency Utilities |
1.0 |
Concurrency Utilities for the Java EE platform |
236 |
|
|
DI |
1.0 |
Dependency Injection for Java |
330 |
|
|
EL |
3.0 |
Unified Expression Language for configuration of web components and context dependency injection |
341 |
Y |
|
EJB |
3.2 |
Enterprise Java Beans, entity beans and EJB QL |
345 |
Y (Lite) |
|
JAAS |
Java Authentication & Authorization Service |
|||
|
JACC |
1.4 |
Java Authorization Contract for Containers |
115 |
|
|
Java EE Management |
1.1 |
|||
|
JASPIC |
1.1 |
Java Authentication Service Provider Interface for Containers |
196 |
|
|
JavaMail |
1.4 |
Java Mail API |
919 |
Might be |
|
JAXB |
Java API for XML Binding |
|||
|
JAXP |
1.4 |
Java API for XML Parsing |
206 |
|
|
JAX-RS |
2.0 |
Java API for RESTful Services |
339 |
Y |
|
JAX-WS |
1.3 |
Java API for XML –based Web Services including SOAP and WSDL |
224 |
|
|
JCA |
1.7 |
J2EE Connector Architecture |
? |
|
|
JCache |
1.0 |
Temporary Caching API for Java EE |
107 |
Maybe |
|
JMS |
2.0 |
Java Message Service |
343 |
|
|
JPA |
2.1 |
Java Persistence API |
338 |
Y |
|
JSF |
2.2 |
Java Server Faces |
344 |
Y |
|
JSON |
1.0 |
JavaScript Serialization Object Notation Protocol |
353 |
Maybe |
|
JSP |
2.3 |
Java Server Pages |
? |
Y |
|
JSPD |
1.0 |
Java Server Pages Debugging |
? |
Y |
|
JSTL |
1.2 |
Java Standard Template Library |
? |
Y |
|
JTA |
1.2 |
Java Transaction API |
||
|
Managed Beans |
1.0 |
Managed Beans 1.1 |
342? |
Y |
|
Servlet |
3.1 |
Java Servlet |
340 |
Y |
|
Web Services |
1.3 |
224 |
||
|
Web Services Metadata |
2.1 |
Are these the correctly numbered JSRs? Are you involved with the newest of these JSRs? If so can you give a definite answer?
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)
Comments
Reza Rahman replied on Wed, 2012/07/18 - 12:02am
Seb Cha replied on Wed, 2012/07/18 - 5:37am
Jonathan Fisher replied on Wed, 2012/07/18 - 9:42am
Jonathan Fisher replied on Wed, 2012/07/18 - 10:08am
in response to:
Jonathan Fisher
Reza Rahman replied on Wed, 2012/07/18 - 11:38am
in response to:
Jonathan Fisher
Hantsy Bai replied on Thu, 2012/07/19 - 8:08pm
As a developer, I hope JEE7 can remove some duplication and inconsistency among the specs in JEE6. for example:
1. the @Singleton, one from EJB and anther is from JSR330.
2. the Scope, JSR299 and JSR 330 include Sope concept, and I noticed there was a new "state" related specs proposed in JEE7, what is it for? I am very glad in JEE7 the JSF scope will move to CDI.
3. ManagedBean, introduced in JEE6, but all beans in JEE are not refined from this concept, right? what is it ? If we need this concept, I hope all EG of JEE7 could seat together and discuss how to refine the existing beans to ManagedBean, such as general POJO, EJB, WebService, CDI Bean etc.
I'v got much pain in the last two years when I used JSF2 Ajax and CDI Bean together in my project, I hope this can be disappeared.
As a end user of JEE, I would like use JEE smoothly as Spring ecosystem, no conflict, no insistency, no gap between different specs, no war between different EG.
Hantsy
George Jiang replied on Sun, 2012/07/22 - 4:03am
in response to:
Hantsy Bai
I'v got much pain in the last two years when I used JSF2 Ajax and CDI Bean together in my project
What pain is it? Could you please elaborate.