 Introduction:-

Java Platform, Enterprise Edition or Java EE is Oracle's enterprise Java computing platform. 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 and annotations for
configuration. Optionally XML can be used to override annotations or to deviate from the platform defaults.

 General APIs:-

 javax.servlet.*

The servlet specification defines a set of APIs to service mainly HTTP requests. It includes the JavaServer
Pages (JSP) specification.

 javax.websocket.*

The Java API for WebSocket specification defines a set of APIs to service WebSocket connections.

 javax.ejb.*

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.

 javax.validation.*

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.

 javax.transaction.*

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.

 javax.security.auth.message.*

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).

 javax.enterprise.concurrent.*

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.

 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.

 Java editions:-

 Micro Edition (ME)

 Java Specifications:-

1. Web Applications:-

 Servlet
 JavaServer Pages
 Expression Language
 JSTL
 JavaServer Faces
 WebSocket
 JSON Processing

2. Web Services:-

 JAX-RS
 Enterprise Web Services
 JAX-WS
 Web Services Metadata
 Java API for XML Messaging
 JAXR