 |
Advanced Multimedia Supplements
An optional package for advanced multimedia functionality that is targeted to run as an supplement in connection with the Mobile Media API in Java ME/CLDC environments.
|
| |
Application Installation API
A set of Java APIs that enable cross-platform installation and de-installation of Java applications as well as platform-specific applications.
|
| |
Application Isolation API
This API provides a uniform mechanism for managing Java application life cycles that are isolated from each other, at least with respect to object reachability, but that can potentially share underlying implementation resources. It provides a means of deploying new Java implementation features that enable and enhance scalability while providing an alternative to ad hoc control schemes.
|
| |
AspectJ
AspectJ is an open source aspect-oriented extension to the Java programming language that can be used to modularize crosscutting concerns such as exception handling, multi-object protocols, synchronization, performance optimizations, and resource sharing. AspectJ supports aspects at compile-time by performing a preprocessing step that results in standard Java code.
|
| |
BPELJ: BPEL for Java technology
BPELJ is a combination of Business Process Execution Language (BPEL) and the Java programming language, allowing the two languages to be used together to build business process applications.
|
| |
CC/PP Processing
This set of APIs is for processing Composite Capability/Preference Profiles (CC/PP) information to enable interoperability between Web servers and access mechanisms, and to facilitate development of device-independent Web applications.
|
| |
Certification Path API
The Certification Path API provides a set of provider-based APIs for creating, building, and verifying certification paths (also known as "certificate chains"). A certification path is an ordered list of certificates. If a certification path meets certain validation rules, it can be used to securely establish the mapping of a public key to a subject.
|
| |
Common Annotations for the Java Platform
This specification develops annotations for common semantic concepts in the Java SE and Java EE platforms that apply across a variety of individual technologies. Its purpose is to avoid unnecessary redundancy between annotations defined in different Java Specification Requests.
|
| |
Concurrency Utilities
A set of medium-level utilities that provide functionality commonly needed in concurrent programs. A standard set of concurrency utilities eases the task of writing a wide variety of multithreaded applications and generally improves the quality of the applications that use them.
|
| |
Connected Device Configuration (CDC)
CDC provides the basis of the J2ME platform for devices that have a sufficient 32-bit microprocessor and ample memory. CDC provides a virtual machine and basic class libraries to support Java language applications on consumer electronic and embedded devices such as smart communicators, pagers, personal digital assistants (PDAs), and interactive, digital television set-top boxes.
|
| |
Connected Limited Device Configuration (CLDC)
CLDC is one of two configurations defined through the Java Community Process to be part of the J2ME platform. Combined with a set of device-specific Java APIs, such as the Mobile Information Device Profile (MIDP), CLDC provides a complete J2ME runtime environment for small resource-constrained devices.
|
| |
Contactless Communication API
This API defines Java ME optional packages for contactless communication: one package for bidirectional communication and the other for accessing read-only information. The API is targeted for resource-constrained devices such as mobile phones and consumer electronic devices.
|
| |
Content Handler API
The Content Handler API enables J2ME applications to handle multimedia and Web content to give developers and users a seamless and integrated user environment on mobile phones and wireless devices. It defines an optional package for an API and associated model permitting the invocation of J2ME applications to handle actions on Uniform Resource Identifiers (URI) based on the MIME-type or scheme.
|
| |
Content Repository for Java technology API
This is a standard API for accessing content repositories in Java 2 independently of implementation. A content repository is a high-level information-management system that is a superset of traditional data repositories.
|
| |
Data Mining API (JDMAPI)
JDMAPI addresses the need for a pure Java API that supports the building of data mining models, the scoring of data using models, as well as the creation, storage, access, and maintenance of data and metadata supporting data mining results, and select data transformations. By using JDMAPI, implementers of data mining applications can expose a single, standard API that will be understood by a wide variety of client applications and components running on the J2EE Platform.
|
| |
Debugging Support for Other Languages
This specification establishes standardized tools for correlating Java virtual machine byte code to the source code of languages other than the Java programming language.
|
| |
Decimal Arithmetic Enhancement
This enhancement primarily adds floating point arithmetic to the BigDecimal class, allowing the use of decimal numbers for general-purpose arithmetic without the problems resulting from conversions to and from another type.
|
| |
Dynamic Component Support for Java SE
A dynamic component framework that enables components to be declared through metadata and be assembled at run time using a class-loader delegation network. It allow components to be dynamically life cycle managed (install, start, stop, update, and uninstall).
|
| |
ECPerf Benchmark Specification
ECperf is an EJB performance workload that is real-world, scalable, and captures the essence of why component models exist.
|
| |
Enterprise JavaBeans (EJB)
Enterprise JavaBeans (EJB) technology is the server-side component architecture for the Java 2 Platform, Enterprise Edition (J2EE) platform. EJB technology enables rapid and simplified development of distributed, transactional, secure, and portable applications based on Java technology.
|
| |
Enterprise Media Beans (EMB)
EMB provides a framework to integrate rich media data such as audio, video, or image into applications based on EJB Entity Beans within the J2EE application development model.
|
| |
Enterprise Metadata
Discovery
A metadata discovery and import model for Java EE resource adapters and
Enterprise Application Integration (EAI) tooling frameworks. It allows
resource adapters to plug into an integration framework easily and
improve the adapters' usability within the framework. Any resource
adapter that complies with the specification can plug into any EAI
tooling framework that supports the specification.
|
| |
Enumerations, Autoboxing, Enhanced for Loops and Static Import
The specification extends the Java programming language in four ways: 1. A syntax for defining enumerated types provides linguistic support for the Typesafe Enumeration pattern. 2. An automatic conversion from primitive types to their corresponding reference type wrappers facilitates the integration of generics into the language and reduces inessential clutter. 3. Enhanced for loops allow convenient iteration over collections, without the need for an explicitly defined iterator. This reduces the need for boilerplate iteration code and the corresponding opportunities for errors. 4. A static import mechanism allows the use of unqualified constants.
|
| |
Event Tracking API for Java ME
An optional code package that standardizes application event tracking on a mobile device and the submission of these event records to an event-tracking server via a standard protocol.
|
| |
Fault Management API
A network-facing API that interfaces element managers, system managers, or subnetwork managers that provide fault information when an undesired event occurs. The API specifies the configuration interface for fault detection, including alarm formatting and reporting to enable discovery, isolation, and correction of problems.
|
| |
Federated Management Architecture
FMA specifies a storage-management platform that allows vendors to construct storage-management applications from standard and custom components. Sun's Jiro technology is the first product implementation of FMA.
|
| |
Generic Connection Framework Optional Package for the J2SE Platform
The Generic Connection Framework (GCF) enables applications written to the javax.microedition.io APIs in any existing J2ME Profile to use these APIs in an identical manner in J2SE when the optional package is present.
|
| |
Generic Types
This specification extends the Java programming language with generic types (also known as parameterized types). Without the ability to specify generic types, programs are unnecessarily hard to read and maintain and are more likely to fail with runtime type errors.
|
| |
IMS Services API
This is a high-level API for accessing IP Multimedia Subsystem (IMS) services. It hides IMS technology details and exposes service-level support to enable easy development of IMS applications.
|
| |
Image I/O Framework
This framework enhances Java Advanced Imaging to support the core Java 2 platform in the manipulation of digital images in a variety of file and compression formats. The framework allows Java 2 developers access to arbitrary sampled image formats, including compressed or otherwise encoded formats.
|
| |
Implementing Enterprise Web Services
This specification defines the programming model and runtime architecture for implementing Web services in the Java language.
|
| |
InfoBus
InfoBus enables dynamic exchange of data between JavaBeans component architecture by defining a small number of interfaces between cooperating Beans and specifying the protocol for use of those interfaces.
|
| |
Information Module Profile
This specification defines a J2ME profile targeting embedded networked devices that wish to support a Java runtime environment, but that do not have graphical display capabilities.
|
| |
Instant Messaging API
This is a protocol-agnostic API for instant messaging that provides a standard portable and secure interface to control, manage, and manipulate instant messages between clients through the use of presence servers.
|
| |
J/eXtensions for Financial Services (J/XFS)
A set of standard Java interfaces developed to support the input and output devices used in the financial industry. The J/XFS Forum, spearheaded by Sun and IBM, includes representatives from DeLaRue, NCR, and Wincor Nixdorf Retail and Banking Systems.
|
| |
J2EE Application Deployment
The J2EE Application deployment specification defines standard APIs that will enable any deployment tool that uses the APIs to deploy any assembled application onto a J2EE-compatible platform.
|
| |
J2EE Client Provisioning
J2EE Client Provisioning partitions server applications that provision client applications in such a way that the details of any one client provisioning model are abstracted and standardized. The purpose of enabling portable J2EE provisioning applications is to allow a high degree of flexibility in integrating one or more provisioning models with enterprise services exposed into the J2EE platform in a particular enterprise setting.
|
| |
J2EE Client Provisioning
J2EE Client Provisioning partitions server applications that provision client applications in such a way that the details of any one client provisioning model are abstracted and standardized. The purpose of enabling portable J2EE provisioning applications is to allow a high degree of flexibility in integrating one or more provisioning models with enterprise services exposed into the J2EE platform in a particular enterprise setting.
|
| |
J2EE Connector Architecture
The J2EE Connector Architecture specifies a standard architecture for integrating Java applications with existing enterprise information systems.
|
| |
J2EE Management
The J2EE Management specification provides server vendors and tool vendors with a standard model for managing the J2EE platform. The specification allows rapid development of management solutions for J2EE, provides integration with existing management systems, enables a single management tool to manage multiple vendor implementations of the platform, and enables a specific implementation of a platform to use any compliant management tool.
|
| |
J2ME Foundation Profile
The J2ME Foundation Profile is a set of APIs meant for applications running on small devices that have some type of network connection.
|
| |
J2ME RMI
The J2ME RMI Profile provides Java-to-Java remote method invocation for Java devices and interoperates with J2SE RMI.
|
| |
J2ME RMI Optional Package (RMI OP)
The J2ME RMI Optional Package (RMI OP) provides a mechanism for publishing distributed application protocols that applications can use to manipulate objects on remote systems. RMI OP is a subset of the J2SE Remote Method Invocation (J2SE RMI) package.
|
| |
J2ME Web Services Specification
The J2ME Web Services Specification defines an optional package that provides standard access from J2ME to Web services.
|
| |
JDBC Optional Package for CDC/Foundation Profile
This optional package for the J2ME Connected Device Configuration (CDC) Foundation Profile contains equivalent functionality to the java.sql package provided in Java 2 Standard Edition, adjusted to take into account the limitations of CDC in terms of size, functionality, and removal of deprecated APIs.
|
| |
JDBC Rowset Implementations
The current JDBC API provides an environment for creating and manipulating tabular data associated with tabular data stores. Implementations of the Rowset interface extend this model to allow tabular data to be passed between tiers and components. This ability to "disconnect" tabular data from its source increases the scalability of applications and the flexibility of the programming model.
|
| |
JEFF File Format
The JEFF standard, developed by the J Consortium and approved by ISO, provides a more compact and efficient representation of Java class files intended for memory-constrained devices such as point-of-sales terminals, cellular phones, and smart cards.
|
| |
JSR-235 Service Data Objects
The Java Specification JSR-235 defines the Service Data Object (SDO 2.1.1) API. This API enables application developers to uniformly access and manipulate data from heterogeneous data sources.
|
| |
Java 2 Platform, Enterprise Edition (J2EE)
J2EE is a set of coordinated specifications and practices that together enable solutions for developing, deploying, and managing multi-tier server-centric applications.
|
| |
Java 2 Platform, Micro Edition (J2ME)
J2ME provides an environment for Java applications running on consumer devices, such as mobile phones, PDAs, TV set-top boxes, and embedded devices. The J2ME architecture comprises a variety of configurations, profiles, and optional packages that implementers and developers can choose from and combine to construct a complete Java runtime environment that closely fits the requirements of a particular range of devices.
|
| |
Java 2 Platform, Standard Edition (J2SE)
J2SE comprises the essential SDK, tools, runtimes, and APIs for developers writing, deploying, and running applets and applications in the Java programming language on desktops and servers.
|
| |
Java 3D
The Java 3D API provides a set of object-oriented interfaces that support a high-level programming model for incorporating high-quality, scalable, platform-independent 3D graphics into Java-based applications and applets.
|
| |
Java API for XML Messaging (JAXM)
JAXM enables applications to send and receive document-oriented XML messages using a pure Java API. JAXM implements SOAP 1.1 with Attachments messaging so that developers can focus on building, sending, receiving, and decomposing messages for their applications instead of programming low-level XML communications routines.
|
| |
Java API for XML Processing (JAXP)
Previously known as the Java API for XML Parsing, JAXP supports processing of XML documents using DOM, SAX, and XSLT. JAXP enables applications to parse and transform XML documents independent of a particular XML processing implementation.
|
| |
Java API for XML Registries (JAXR)
JAXR provides a uniform and standard Java API for accessing different kinds of XML registries. An XML registry is an enabling infrastructure for building, deploying, and discovering Web services.
|
| |
Java API for XML Registries (JAXR)
JAXR provides a uniform and standard Java API for accessing different kinds of XML registries. An XML registry is an enabling infrastructure for building, deploying, and discovering Web services.
|
| |
Java API for XML-Based RPC (JAX-RPC)
JAX-RPC enables building of Web services and Web applications based on the SOAP 1.1 specification, Java SE 1.4 or lower, or when rpc/encoded style must be used. If possible, JAX-WS should be used instead because it is based on the most recent industry standards.
|
| |
Java API for XML-Based Web Services (JAX-WS)
JAX-WS is a fundamental technology for developing SOAP-based and RESTful Java Web services. JAX-WS is designed to take the place of JAX-RPC in Web services and Web applications.
|
| |
Java APIs for Bluetooth
This specification standardizes a set of Java APIs to allow Java-enabled devices to integrate into a Bluetooth environment. Bluetooth is an important emerging standard for wireless integration of small devices.
|
| |
Java APIs for Integrated Networks (JAIN)
The JAIN APIs are a set of Java-based APIs that enable the rapid development of next-generation telecommunications products and services on the Java platform.
|
| |
Java APIs for WSDL
This is a standard set of APIs for representing and manipulating services described by Web Services Description Language (WSDL) documents. These APIs define a way to construct and manipulate models of service descriptions.
|
| |
Java Advanced Imaging API
The Java Advanced Imaging API enables developers to incorporate high-performance, network-enabled, scalable, platform-independent image processing into Java-based applications and applets.
|
| |
Java Architecture for XML Binding (JAXB)
JAXB provides an API and tools that automate the mapping between XML documents and Java objects.
|
| |
Java Authentication Service Provider Interface for Containers
An interface by which authentication modules can be integrated with containers and establish the authentication identities used by containers.
|
| |
Java Authentication and Authorization Service (JAAS)
JAAS is a framework that supplements the Java 2 platform with user-based authentication and access-control capabilities. It includes a Java implementation of the standard Pluggable Authentication Module (PAM) architecture, and provides support for user-based, group-based, or role-based access controls. JAAS has been integrated into J2SE 1.4 and later.
|
| |
Java Authorization Contract for Containers
This specification defines a contract between containers and authorization service providers that will result in the implementation of providers for use by containers. It defines new java.security.Permission classes to satisfy the J2EE role-based, authorization model and defines the binding of container-access decisions to operations on instances of these permission classes.
|
| |
Java Binding for the OpenGL API
This specification describes the Java bindings to the native 3D graphics library, OpenGL -- a platform-independent, low-level 3D API. This includes all core GL calls as well as the GLU library. The specification is device-agnostic to allow for the possibility of subsetting the API for different classes of devices.
|
| |
Java Binding for the OpenGL ES API
This optional package describes the Java bindings to the Embedded Subset of the native 3D graphics library, OpenGL -- a platform-independent, low-level 3D API.
|
| |
Java Business Integration (JBI)
JBI extends J2EE and J2SE with business integration service provider interfaces (SPIs). These SPIs enable the creation of a Java business integration environment for specifications such as WSCI, BPEL4WS, and the W3C Choreography Working Group.
|
| |
Java Communications API
The Java Communications API is a Java extension that facilitates developing platform-independent communications applications for technologies such as smart cards, embedded systems, point-of-sale devices, financial services devices, fax, modems, display terminals, and robotic equipment.
|
| |
Java Compiler API
The Java Compiler API is a service-provider API that allows a Java program to select and invoke a Java Language Compiler programmatically. This API is included in the Java SE 6 platform release.
|
| |
Java Data Objects (JDO)
The JDO specification provides for interface-based definitions of data stores and transactions, and for selection and transformation of persistent storage data into native Java programming language objects.
|
| |
Java Foundation Classes
JFC consists of a comprehensive set of graphical user interface class libraries, including: JFC/Swing components, Pluggable Look and Feel, Accessibility API, Java 2D API (Java 2 only), Drag and Drop (Java 2 only), Abstract Windowing Tookit (AWT), and Internationalization.
|
| |
Java Generic Security Services API (GSS-API)
GSS-API provides a layer of abstraction over security mechanisms that perform authentication, message integrity protection, and message privacy protection.
|
| |
Java Interface Definition Language (Java IDL)
Java IDL adds CORBA capability to the Java platform, enabling distributed Web-enabled Java applications to invoke operations transparently on remote network services using the industry standard OMG IDL (Object Management Group Interface Definition Language) and IIOP (Internet Inter-ORB Protocol) defined by the OMG.
|
| |
Java Management Extensions (JMX formerly JMAPI)
The JMX specification provides a management architecture, APIs, and services for building Web-based, distributed, dynamic, and modular solutions to manage Java-enabled resources.
|
| |
Java Management Extensions (JMX) Remote API
This API extends the Java Management Extensions (JMX) specification by adding client APIs. These APIs provide to any Java Manager discovery and access to JMX Agents abstracting the underlying protocol.
|
| |
Java Media Framework (JMF)
The Java Media Framework API enables audio, video, and other time-based media to be added to Java applications and applets. It can capture, play back, stream, and transcode multiple media formats, extending the multimedia capabilities of the J2SE platform.
|
| |
Java Message Service API (JMS)
The JMS API improves programmer productivity by defining a common set of messaging concepts and programming strategies that will be supported by all JMS technology-compliant messaging systems.
|
| |
Java Metadata Interface (JMI)
The JMI specification enables the implementation of a dynamic, platform-independent infrastructure to manage the creation, storage, access, discovery, and exchange of metadata. JMI is based on the OMG's Meta Object Facility (MOF) specification, an industry-endorsed standard for metadata management.
|
| |
Java Modeling Language (JML)
JML is a behavioral interface specification language that can be used to specify the behavior of Java modules.
|
| |
Java Naming and Directory Interface (JNDI)
JNDI enables Java applications to access different, possibly multiple, naming and directory services using a common API. Different naming and directory service providers can be plugged in seamlessly behind this common API.
|
| |
Java Network Launching Protocol and API
Java Network Launching Protocol and API is a specification of protocols and APIs that enable Java applications to be deployed on the Web. Sun's Java Web Start is the reference implementation of this standard.
|
| |
Java Platform Debugger Architecture (JPDA)
JPDA is a set of APIs that provide the debugging support for the Java 2 Platform. (JPDA is included in the J2SE SDK 1.3 and later on all platforms and SDK 1.2.2 for Linux. The download is only required to add JDI and JDWP to the J2SE SDK 1.2.2 on Solaris and Windows platforms.)
|
| |
Java Platform Profiling Architecture
The Java Platform Profiling Architecture is a mechanism and APIs for extracting time and space profiling information from a running Java virtual machine.
|
| |
Java RMI over IIOP
RMI over IIOP gives you a powerful environment in which to do distributed programming using Java technology. It combines the usability of Java Remote Method Invocation (RMI) with the interoperability of the Internet Inter-ORB Protocol (IIOP).
|
| |
Java Rule Engine API
This API prescribes a set of fundamental rule engine operations based upon the assumption that most clients will need to be able to execute a basic multistep rule engine cycle, which consists of parsing rules, adding objects to an engine, firing rules. and getting resultant objects from the engine. The set of operations also supports variations of the basic cycle, particularly variations that would occur in J2EE server deployments.
|
| |
Java SASL Specification
This specification defines a Simple Authentication and Security Layer client and server API in the Java programming language. The API allows developers to write client and server applications or protocol libraries that can authenticate using different SASL mechanisms, and to write mechanism implementations that can be used by such SASL-enabled applications and libraries.
|
| |
Java Servlets
Java Servlet technology provides Web developers with a simple, consistent mechanism for extending the functionality of a Web server and for accessing existing business systems. A servlet is an applet-like program that runs on the server side, without a GUI.
|
| |
Java Smart Card I/O API
Smart Cards, also called integrated circuit cards, are small computing devices that usually come in a credit card sized form factor. Server and PC applications interact with Smart Cards by exchanging APDUs (Application Protocol Data Units) with them. This is a Java API for APDU-based communication.
|
| |
Java Technology for the Wireless Industry
This specification provides an overall architectural description of a wireless client software stack. It includes an integrated reference implementation and technology compatibility kit bundle for the described technologies.
|
| |
Java Telephony API (JTAPI)
JTAPI is the set of classes, interfaces, and principles of operation that constitute a Java extension package in the javax.* name space. JTAPI implementations are the interface between Java computer-telephony applications and telephony services, whether those services are implemented as software or hardware.
|
| |
Java Transaction API (JTA)
JTA specifies standard Java interfaces between a transaction manager and the parties involved in a distributed transaction system: the resource manager, the application server, and the transactional applications.
|
| |
Java USB API
This specification provides an API for communicating with devices attached via the Universal Serial Bus (USB). It allows Java applications to discover, read, write, and manage USB devices.
|
| |
JavaBeans
JavaBeans are reusable Java-based components. Java developers can take advantage of component software development technology while still benefiting from Java's promise of hardware independence.
|
| |
JavaBeans Activation Frameworks (JAF)
JavaBeans Activation Framework is a standard extension to JavaBeans that allows one to determine the type of an arbitrary piece of data, encapsulate access to it, discover the operations available on it, and to instantiate the appropriate JavaBeans component.
|
| |
JavaHelp
JavaHelp software is a platform-independent, extensible help system that enables developers and authors to incorporate online help in applets, components, applications, operating systems, and devices, and to deliver Web-based online documentation.
|
| |
JavaMail
The JavaMail API provides a set of abstract classes that model a mail system. The API provides a platform-independent and protocol-independent framework to build Java-based mail and messaging applications.
|
| |
JavaServer Faces (JSF)
The JavaServer Faces specification defines an architecture and APIs that simplify the creation and maintenance of Java server application GUIs.
|
| |
JavaServer Pages (JSP)
JSP technology is an extension of Java Servlet technology and a key component of the J2EE platform. JSP technology enables rapid development of platform-independent Web-based applications. It separates the user interface from content generation, enabling designers to change the overall page layout without altering the underlying dynamic content.
|
| |
