Java Platform, Enterprise Edition
|This article's lead section may not adequately summarize key points of its contents. (August 2016)|
||This article is written like a manual or guidebook. (June 2016) (Learn how and when to remove this template message)|
The platform provides an API and runtime environment for developing and running enterprise software, including network and web services, and other large-scale, multi-tiered, scalable, reliable, and secure network applications. Java EE extends the Java Platform, Standard Edition (Java SE), providing an API for object-relational mapping, distributed and multi-tier architectures, and web services. The platform incorporates a design based largely on modular components running on an application server. Software for Java EE is primarily developed in the Java programming language. The platform emphasizes convention over configuration[irrelevant citation] and annotations for configuration. Optionally XML can be used to override annotations or to deviate from the platform defaults.
Java EE is developed under the Java Community Process.
The platform was known as Java 2 Platform, Enterprise Edition or J2EE until the name was changed to Java Platform, Enterprise Edition or Java EE in version 5. The current version is called Java EE 7.
- J2EE 1.2 (December 12, 1999)
- J2EE 1.3 (September 24, 2001)
- J2EE 1.4 (November 11, 2003)
- Java EE 5 (May 11, 2006)
- Java EE 6 (December 10, 2009)
- Java EE 7 (May 28, 2013, but April 5, 2013 according to spec document. June 12, 2013 was the planned kickoff date)
- Java EE 8 (expected first half of 2017)
Standards and specifications
Java EE is defined by its specification. As with other Java Community Process specifications, providers must meet certain conformance requirements in order to declare their products as Java EE compliant.
Java EE includes several API specifications, such as RMI, e-mail, JMS, web services, XML, etc., and defines how to coordinate them. Java EE also features some specifications unique to Java EE for components. These include Enterprise JavaBeans, connectors, servlets, JavaServer Pages and several web service technologies. This allows developers to create enterprise applications that are portable and scalable, and that integrate with legacy technologies. A Java EE application server can handle transactions, security, scalability, concurrency and management of the components it is deploying, in order to enable developers to concentrate more on the business logic of the components rather than on infrastructure and integration tasks.
||This section contains embedded lists that may be better presented using prose. (June 2016) (Learn how and when to remove this template message)|
- The servlet specification defines a set of APIs to service mainly HTTP requests. It includes the JavaServer Pages (JSP) specification.
- The Java API for WebSocket specification defines a set of APIs to service WebSocket connections.
- This package defines the root of the JavaServer Faces (JSF) API. JSF is a technology for constructing user interfaces out of components.
- This package defines the component part of the JavaServer Faces API. Since JSF is primarily component oriented, this is one of the core packages. The package overview contains a UML diagram of the component hierarchy.
- This package defines the classes and interfaces for Java EE's Expression Language. The Expression Language (EL) is a simple language originally designed to satisfy the specific needs of web application developers. It is used specifically in JSF to bind components to (backing) beans and in CDI to name beans, but can be used throughout the entire platform.
- These packages define the injection annotations for the Contexts and Dependency Injection (CDI) APIs.
- These packages define the context annotations and interfaces for the Contexts and Dependency Injection (CDI) API.
- The Enterprise JavaBean (EJB) specification defines a set of lightweight APIs that an object container (the EJB container) will support in order to provide transactions (using JTA), remote procedure calls (using RMI or RMI-IIOP), concurrency control, dependency injection and access control for business objects. This package contains the Enterprise JavaBeans classes and interfaces that define the contracts between the enterprise bean and its clients and between the enterprise bean and the ejb container.
- This package contains the annotations and interfaces for the declarative validation support offered by the Bean Validation API. Bean Validation provides a unified way to provide constraints on beans (e.g. JPA model classes) that can be enforced cross-layer. In Java EE, JPA honors bean validation constraints in the persistence layer, while JSF does so in the view layer.
- This package contains the contracts between a persistence provider and the managed classes and the clients of the Java Persistence API (JPA).
- This package provides the Java Transaction API (JTA) that contains the interfaces and annotations to interact with the transaction support offered by Java EE. Even though this API abstracts from the really low-level details, the interfaces are also considered somewhat low-level and the average application developer in Java EE is either assumed to be relying on transparent handling of transactions by the higher level EJB abstractions, or using the annotations provided by this API in combination with CDI managed beans.
- This package provides the core of the Java Authentication SPI (JASPIC) that contains the interfaces and classes to build authentication modules for secure Java EE applications. Authentication modules are responsible for the interaction dialog with a user (e.g. redirecting to a Form or to an OpenID provider), verifying the user's input (e.g. by doing an LDAP lookup, database query or contacting the OpenID provider with a token) and retrieving a set of groups/roles that the authenticated user is in or has (e.g. by again doing an LDAP lookup or database query).
- This package provides the interfaces for interacting directly with Java EE's platform default managed thread pool. A higher-level executor service working on this same thread pool can be used optionally. The same interfaces can be used for user-defined managed thread pools, but this relies on vendor specific configuration and is not covered by the Java EE specification.
- This package defines the Java Message Service (JMS) API. The JMS API provides a common way for Java programs to create, send, receive and read an enterprise messaging system's messages.
- This package defines the entry AP for Java EE Batch Applications. The Batch Applications API provides the means to run long running background tasks that possibly involve a large volume of data and which may need to be periodically executed.
- This package defines the Java EE Connector Architecture (JCA) API. Java EE Connector Architecture (JCA) is a Java-based technology solution for connecting application servers and enterprise information systems (EIS) as part of enterprise application integration (EAI) solutions. This is a low-level API aimed at vendors that the average application developer typically does not come in contact with.
In an attempt to limit the footprint of web containers, both in physical and in conceptual terms, the web profile was created, a subset of the Java EE specifications. The Java EE web profile comprises the following:
|Specification||Java EE 6||Java EE 7|
|JavaServer Pages (JSP)||2.2||2.3|
|Unified Expression Language (EL)||2.2||3.0|
|Debugging Support for Other Languages (JSR-45)||1.0||1.0|
|JavaServer Pages Standard Tag Library (JSTL)||1.2||1.2|
|JavaServer Faces (JSF)||2.0||2.2|
|Java API for RESTful Web Services (JAX-RS)||1.1||2.0|
|Java API for WebSocket (WebSocket)||n/a||1.0|
|Java API for JSON Processing (JSON-P)||n/a||1.0|
|Common Annotations for the Java Platform (JSR-250)||1.1||1.2|
|Enterprise JavaBeans (EJB)||3.1 Lite||3.2 Lite|
|Java Transaction API (JTA)||1.1||1.2|
|Java Persistence API (JPA)||2.0||2.1|
|Contexts and Dependency Injection for the Java EE Platform||1.0||1.1|
|Dependency Injection for Java||1.0||1.0|
Certified application servers
Although by definition all Java EE implementations provide the same base level of technologies (namely, the Java EE spec and the associated APIs), they can differ considerably with respect to extra features (like connectors, clustering, fault tolerance, high availability, security, etc.), installed size, memory footprint, startup time, etc.
- Web container
- Deployment Descriptor
- Java BluePrints
- Sun Java System Portal Server
- Java EE version history
- Sun Community Source License
- Java Research License
- "Differences between Java EE and Java SE - Your First Cup: An Introduction to the Java EE Platform". Docs.oracle.com. 2012-04-01. Retrieved 2012-07-18.
- "Minimal 3-tier Java EE app, without any XML config - J-Development".
- "The Java Community Process(SM) Program - JSRs: Java Specification Requests - detail JSR# 342".
- Wieldt, Tori. "Introducing Java EE 7: June 12 Kickoff".
- "Java EE 8 Roadmap Update (The Aquarium)".
- "The Java Community Process(SM) Program - JSRs: Java Specification Requests - detail JSR# 316".
- "Java EE Compatibility".
- "Comparing GlassFish Open Source Edition versions 2.x and 3.0.x".
- "Java EE Compatibility". Java.sun.com. 2010-09-07. Retrieved 2012-07-18.
- "WebLogic Now Java EE 7 Compatible! (The Aquarium)".
- "Oracle Weblogic Server 12.1.1".
- "[WFLY-469] Parent Issue for Java EE 7 Support - JBoss Issue Tracker".
- "JBoss AS 7.1.0.Final "Thunder" released - Java EE 6 Full Profile certified! | My Wiki | Planet JBoss Community". Planet.jboss.org. 2012-02-17. Retrieved 2012-07-18.
- "JBoss Application Server - JBoss Community".
- "JBoss Application Server - JBoss Community".
- "Java EE Compatibility".
- "JBoss AS is now EE5 certified!". 15 September 2008.
- "JBoss EAP 7.0 Compatility Configuration".
- Business Wire (2012-06-20). "Red Hat Launches JBoss Enterprise Application Platform 6 to Help Enterprises Move Application Development and Deployment to the Cloud". Business Wire. Retrieved 2012-07-18.
- "Websphere AppServer 9 Configuration".
- "What's new in WebSphere Application Server V8". Ibm.com. Retrieved 2012-07-18.
- "Java EE 7 has landed in WAS Liberty - WASdev". 25 June 2015.
- "IBM Java EE 6 Web Profile Tested Configurations".
- "Apache Geronimo fully certified for Java EE 6 - The H Open: News and Features". H-online.com. 2011-11-14. Archived from the original on 20 April 2012. Retrieved 2012-07-18.
- "TMAX JEUS 8 Tested Configuration".
- "TmaxSoft JEUS 8 Now Java EE 7 Compatible! (The Aquarium)".
- "Tested Configurations, Java EE 6 - TMAX JEUS 7". Oracle.com. 2010-09-07. Retrieved 2012-07-18.
- "Java EE6 Web Application Server, WAS Software". Us.tmaxsoft.com. Retrieved 2012-07-18.
- "Cosminexus: Hitachi Application Server".
- "Hitachi Cosminexus Now Java EE 7 Compatible! (The Aquarium)".
- "Java EE 6 - Tested Configurations, Java EE 6 - Hitachi uCosminexus Application Server v9.0". Oracle.com.
- Fujitsu Interstage Application Server powered by Windows Azure
- "Tested Configurations, Java EE6 - Fujitsu Interstage". Oracle.com. 2010-09-07. Retrieved 2012-07-18.
- "Fujitsu Releases Interstage Application Server V10.1". Fujitsu.
- "NEC WebOTX Application Server V9.x Certification".
- "Apache TomEE". Openejb.apache.org. Retrieved 2012-07-18.
- "MarketWatch.com". MarketWatch.com. Retrieved 2012-07-18.
- TomEE, Apache. "Apache TomEE 7.0.1".
- "Please Welcome Siwpas as Java EE Certified Option!". Oracle.com. Retrieved 2015-12-07.
- "SAP NetWeaver Cloud Java EE 6 Web Profile Certified! (The Aquarium)".
- "SAP Software Solutions - Business Applications and Technology".
|Wikimedia Commons has media related to Java EE.|
- Oracle Technology Network's Java EE
- Oracle's Java EE Compatibility page - Certified Java EE Compatible Implementations
- Core J2EE Patterns
- A short tutorial introducing beginning Java EE developers to the Java EE platform
- Cloud Tutorial - Java EE in a Day Java EE Tutorial that embraces the use of a Cloud IDE to let you learn the fundamentals of Java EE in just one day