API Packages Included in Java EE SDK


What API packages are included in Java EE SDK?

✍: FYIcenter


Java EE SDK includes the follwoing API packages as extensions to Java SE JDK API packages:

  • 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. See FAQ for WebSocket API.
  • javax.faces.* - This package defines the root of the JavaServer Faces (JSF) API. JSF is a technology for constructing user interfaces out of components.
  • javax.faces.component.* - 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.
  • javax.el.* - 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.
  • javax.enterprise,inject.* - These packages define the injection annotations for the Contexts and Dependency Injection (CDI) APIs.
  • javax.enterprise.context.* - These packages define the context annotations and interfaces for the Contexts and Dependency Injection (CDI) API.
  • 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.persistence.* - This package contains the contracts between a persistence provider and the managed classes and the clients of the Java Persistence API (JPA).
  • 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.
  • javax.jms.* - 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.
  • javax.batch.api.* - 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.
  • javax.resource.* - 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.


Download and Install Java EE 8 SDK

What Is Java EE SDK (Software Development Kit)

Download and Review Java EE SDK

⇑⇑ FAQ for Java EE (Enterprise Edition)

2023-02-28, 376🔥, 0💬