Java EE version history

Development/JSP & Servlet 2012. 11. 26. 06:38


he Java Platform, Enterprise Edition or Java EE (formerly known as Java 2 Platform, Enterprise Edition or J2EE) has undergone several changes since 1.0 as well as numerous additions of new specifications.

Contents

  [hide] 

[edit]JPE (May 1998)

Announcement of the JPE (Java Professional Edition) project at Sun.

[edit]J2EE 1.2 (December 12, 1999)

List of J2EE 1.2 specifications Developer's Guide.
TechnologyVersion
JDBC Standard Extension API2.0
Java Naming and Directory Interface Specification (JNDI)1.2
RMI-IIOP1.0
Java Servlet2.2
JavaServer Pages (JSP)1.1
Enterprise JavaBeans (EJB)1.1
Java Message Service API (JMS)1.0
Java Transaction API (JTA)1.0
JavaMail API1.1
JavaBeans Activation Framework (JAF)1.0

[edit]J2EE 1.3 (September 24, 2001)

List of J2EE 1.3 specifications developed under JSR 58 Tutorial
TechnologyVersion
JDBC Extension2.0
Java API for XML Processing (JAXP)1.1
Java Servlet2.3
JavaServer Pages (JSP)1.2
JavaServer Pages Standard Tag Library (JSTL)1.0
Enterprise JavaBeans (EJB)2.0
J2EE Connector Architecture1.0
Java Message Service API (JMS)1.0
Java Transaction API (JTA)1.0
JavaMail API1.2
JavaBeans Activation Framework (JAF)1.0
Java Authentication and Authorization Service (JAAS)1.0

[edit]J2EE 1.4 (November 11, 2003)

List of J2EE 1.4 specifications developed under JSR 151 Tutorial
TechnologyVersionJSR
Web Services Technologies:
Web Services for J2EE 1.11.0
Java API for XML Processing (JAXP)1.2
Java API for XML-based RPC (JAX-RPC)1.1
Java API for XML Registries (JAXR)1.0
Web Application Technologies:
Java Servlet2.4JSR154
JavaServer Pages (JSP)2.0JSR152
JavaServer Pages Standard Tag Library (JSTL)1.1JSR52
JavaServer Faces (JSF)1.1JSR127
Enterprise Application Technologies:
Enterprise JavaBeans (EJB)2.1
J2EE Connector Architecture1.5
Java Message Service API (JMS)1.1
Java Transaction API (JTA)1.0
JavaMail API1.3
JavaBeans Activation Framework (JAF)1.0
Management and Security Technologies:
Java Authorization Service Provider Contract for Containers (JACC)1.0
Java Management Extensions (JMX)1.2
Enterprise Edition Management API1.0
Enterprise Edition Deployment API1.1

[edit]Java EE 5 (May 11, 2006)

List of JEE 5 specifications developed under JSR244 Tutorial
TechnologyVersionJSR
Web Services Technologies:
Web Services1.2JSR109
Java API for XML-Based Web Services (JAX-WS)2.0JSR224
Java Architecture for XML Binding (JAXB)2.0JSR222
Web Service Metadata for the Java Platform2.0JSR181
Java API for XML-Based RPC (JAX-RPC)1.1JSR101
Java API for XML Registries (JAXR)1.0JSR93
SOAP with Attachments API for Java (SAAJ)1.3JSR67
Streaming API for XML (StAX)1.0JSR173
Web Application Technologies:
Java Servlet2.5JSR154
JavaServer Faces (JSF)1.2JSR252
JavaServer Pages (JSP)2.1JSR245
JavaServer Pages Standard Tag Library (JSTL)1.2JSR52
Debugging Support for Other Languages1.0JSR45
Enterprise Application Technologies:
Enterprise JavaBeans (EJB)3.0JSR220
Java Persistence API (JPA)1.0JSR220
Jave EE Connector Architecture1.5JSR112
Common Annotations for the Java Platform1.0JSR250
Java Message Service API (JMS)1.1JSR914
Java Transaction API (JTA)1.1JSR907
JavaMail API1.4JSR919
JavaBeans Activation Framework (JAF)1.1JSR925
Management and Security Technologies:
Java Authorization Service Provider Contract for Containers (JACC)1.1JSR115
J2EE Application Deployment1.2JSR88
J2EE Management1.1JSR77

[edit]Java EE 6 (Dec 10, 2009)

Java EE 6 introduced the concept of profile, which represents a configuration of the platform suited to a particular class of applications. The Web Profile offers a complete stack, with technologies addressing presentation and state management (JavaServer Faces, JavaServer Pages), core web container functionality (Servlet), business logic (Enterprise JavaBeans Lite), transactions (Java Transaction API), persistence (Java Persistence API) and more.

List of JEE 6 specifications developed under JSR 316 Tutorial
TechnologyVersionJSRIncluded in Web Profile
Web Services Technologies:
Java API for RESTful Web Services (JAX-RS)1.1JSR311
Web Services1.3JSR109
Java API for XML-Based Web Services (JAX-WS)2.2JSR224
Java Architecture for XML Binding (JAXB)2.2JSR222
Web Services Metadata for the Java Platform2.1JSR181
Java API for XML-based RPC (JAX-RPC)1.1JSR101
Java APIs for XML Messaging (JAXM)1.3JSR67
Java API for XML Registries (JAXR)1.0JSR93
Web Application Technologies:
Java Servlet3.0JSR315Green tick
JavaServer Faces (JSF)2.0JSR314Green tick
JavaServer Pages (JSP)2.2JSR245Green tick
Expression Language (EL)2.2JSR245Green tick
JavaServer Pages Standard Tag Library (JSTL)1.2JSR52Green tick
Debugging Support for Other Languages1.0JSR45Green tick
Enterprise Application Technologies:
Enterprise JavaBeans (EJB)3.1JSR318Green tick Lite
Java Persistence API (JPA)2.0JSR317Green tick
Contexts and Dependency Injection for Java1.0JSR299Green tick
Dependency Injection for Java1.0JSR330Green tick
Bean Validation1.0JSR303Green tick
Managed Beans1.0JSR316Green tick
Interceptors1.1JSR318Green tick
Java EE Connector Architecture1.6JSR322
Common Annotations for the Java Platform1.1JSR250Green tick
Java Message Service API (JMS)1.1JSR914
Java Transaction API (JTA)1.1JSR907Green tick
JavaMail API1.4JSR919
Management and Security Technologies:
Java Authentication Service Provider Interface for Containers (JASPIC)1.0JSR196
Java Authorization Service Provider Contract for Containers (JACC)1.4JSR115
Java EE Application Deployment1.2JSR88
J2EE Management1.1JSR77

Java EE 6 was first going to be developed under JSR 313 but was canceled. Java EE 6 was developed under JSR 316 and released on December 10, 2009.

The development was plagued with controversy, although passed by 14 yes votes, 1 no vote (Apache), and 1 abstention (Borland), members aired concerns relating to the licensing terms applied by Sun Microsystems.[1]

IBM's "yes" vote was caveated with:

IBM’s vote is based on the technical merits of this JSR and is not a vote on the licensing terms. IBM supports licensing models that create an open and level playing field by allowing third parties to create independent implementations of Java Specifications and that do not allow individuals or companies to exercise unnecessary control for proprietary advantage. We support open source as a licensing model for contributions in the JCP, and would hope others will support this direction. This comment is not necessarily directed at the current business or license terms for this JSR, however, it is a statement of IBM’s preferred licensing model.

Intel's was caveated with:

The Spec Lead has told us there are no “field of use restrictions” on implementations for this particular JSR. The Apache open letter about Java SE [2] claimed that a confidential license for a required JCP test suite restricts how Independent Implementations of that JCP spec can be used. Licenses to test for JCP compatibility must not be used to limit or restrict competing, compatible implementations; licenses containing such limitations do not meet the requirements of the JSPA, the agreement under which the JCP operates. For every JCP ballot, we will ask the Spec Lead whether such restrictions exist in their license.

Red Hat commented

The spec lead of the EE6 specification has confirmed that the EE6 TCK would contain no “field of use restrictions”, as originally raised by Apache with regard to another JSR (i.e. the SE TCK licensing). That is a good thing.
However, in the absence of an explicit JSPA rule that would forbid such field-of-use restrictions, we will remain worried that a similar issue might resurface anytime, for any JSR.
Consequently, in the future, for any submitted JSR (by SUNW or not), we will specifically expect the spec lead to provide clear information on that aspect and take the answer in account when casting our vote.

Apache voted NO with the following comment:

The Apache Software Foundation’s vote is based on the point of view that this spec lead - Sun - is in violation of the JSPA[2]
and therefore shouldn’t be allowed to start another JSR until the above matter is resolved.
This vote is not a comment on the technical merits of the JSR. If not for the issue of the spec lead, the ASF would have otherwise voted “yes”.

[edit]References

  1. ^ See http://www.oreillynet.com/onjava/blog/2007/07/jsr_316_java_ee_6_spec_approve_1.html
  2. ^ a b http://www.apache.org/jcp/sunopenletter.html

[edit]External links




자바 플랫폼, 엔터프라이즈 에디션 또는 Java EE (이전에는 J2EE라 불리었음) 는 버전 1.0 부터 수많은 새로운 사양의 추가로 인해 여러 번의 개정이 있었다.

목차

  [숨기기] 

[편집]JPE (1998년 5월)

JPE 프로젝트 선언

[편집]J2EE 1.2 (1999년 10월 12일)

사양 다운로드

사양 리스트 :

[편집]J2EE 1.3 (2001년 9월 24일)

JSR 58 기준으로 개발

사양 리스트 :

[편집]J2EE 1.4 (2003년 11월 11일)

JSR 151 기준으로 개발

사양 리스트:

[편집]Java EE 5 (2006년 5월 11일)

JSR 244 기준으로 개발

사양 리스트 :

  • JDBC (Java DataBase Connectivity, JDBC) , 버전 3.0
  • JNDI (Java Naming and Directory Interface, JNDI), 버전 1.2
  • 자바 메시지 서비스 (Java Message Service, JMS), 버전 1.1
  • 자바 트랜잭션 API (Java Transaction API, JTA), 버전 1.1
  • 자바 트랜잭션 서비스 (Java Transaction Service, JTS), 버전 1.0
  • 자바 메일 (JavaMail) , 버전 1.4
  • JAF (JavaBeans Activation Framework), 버전 1.1
  • JCA (J2EE Connector Architecture, JCA), 버전 1.5
  • JAXP (Java API for XML Processing, JAXP), 버전 1.3
  • JAAS (Java Authentication and Authorization Service, JAAS), 버전 1.0
  • JACC (Java Authorization Service Provider Contract for Containers, JACC), 버전 1.1
  • Java EE용 웹서비스, 버전 1.2
  • JAX-RPC (Java API for XML-based RPC, JAX-RPC), 버전 1.1
  • JAXR (Java API for XML Registries, JAXR), 버전 1.0
  • JMX (Java Management eXtensions, JMX), 버전 1.2
  • Java Platform, Enterprise Edition Management Specification, 버전 1.1
  • Java Platform, Enterprise Edition Deployment Specification, 버전 1.1
  • JAX-WS (Java API for XML-based Web Services, JAX-WS), 버전 2.0
  • JAXB (Java Architecture for XML Binding, JAXB), 버전 2.0
  • SAAJ (SOAP with Attachments API for Java, SAAJ), 버전 1.3
  • Web Services Metadata for the Java Platform, 버전 2.0
  • StAX (Streaming API for XML, StAX), 버전 1.0

[편집]Java EE 6 (2008년)

JSR 313 기준으로 개발중이었으나 취소되었다. 현재 JSR 316 기반하에 2008년 발표를 목표로 개발중이다.

새로이 추가되는 사양

  • JSR-196 Java Authentication SPI for Containers
  • JSR-236 Timer for Application Servers
  • JSR-237 Work Manager for Application Servers
  • JSR-299 Web Beans
  • JSR-311 JAX-RS: Java API for RESTful Web Services

사양 업그레이드 예정

[편집]같이 보기




저작자표시

'Development > JSP & Servlet' 카테고리의 다른 글

jsp - response.sendRedirect와 request.getRequestDispatcher  (0) 2012.12.24
jsp - 접속 URL 출력  (0) 2012.12.06
jsp - The function size must be used with a prefix when a default namespace is not specified  (0) 2012.11.25
jsp - The absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved  (0) 2012.11.24
자바 EE(Java Platform, Enterprise Edition; Java EE)  (0) 2012.11.09
Posted by linuxism
,

티스토리툴바