 |
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.
|
| |
Order Management API
This API for operational support systems defines an interface to an order-management component, with specific extensions for activation and work-order management use cases.
|
| |
Mobile User Interface Customization API
The Mobile User Interface Customization API provides a way to query and modify the user interface customization properties of a mobile device or platform.
|
| |
OSS Discovery API
An API that allows network discovery applications to be developed and integrated with other OSS/J enabled applications.
|
| |
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.
|
| |
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).
|
| |
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.
|
| |
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.
|
| |
XML API for Java ME
A general purpose XML API for the next generation of mobile devices. It supports SAX 2 event handler-based parsing and efficient DOM-style document processing.
|
| |
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.
|
| |
Javadoc
Javadoc is a tool for generating API documentation in HTML format from doc comments in source code. It can be downloaded only as part of the Java 2 SDK.
|
| |
Workspace Versioning and Configuration Management
Workspace Versioning and Configuration Management provides client support for creating and manipulating sets of version-controlled files and Web resources.
|
| |
XML Digital Signature APIs
A standard set of high-level implementation-independent APIs for XML digital signatures services. The XML Digital Signature specification is defined by the World Wide Web Consortium.
|
| |
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.
|
| |
Scripting for the Java Platform
The specification describes mechanisms allowing scripting-language programs to access information developed in the Java Platform and allowing scripting-language pages to be used in Java server-side applications.
|
| |
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.
|
| |
Mobile Operational Management
Mobile Operational Management creates a predictable management environment for mobile devices capable of installing, executing, profiling, updating, and removing Java and associated native components in the Java ME Connected Device Configuration.
|
| |
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.
|
| |
Mobile Service Architecture
This specification creates a mobile service architecture and platform definition for high-volume wireless handsets. It broadens the architecture defined by the Java Technology for the Wireless Industry specification (JSR 185) to incorporate new technologies for the high-volume mobile 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.
|
| |
Pluggable Annotation Processing API
In order to support annotation processing at build time, this API allows annotation processors to be created. It also allows automation of the discovery of appropriate annotation processors for a given source file.
|
| |
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 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.
|
| |
Mobile Telephony API (MTA)
MTA defines a set of functions for controlling calls and using network services suitable for Java applications written for Java ME devices. The API and its platform definition use common telephony features and are suitable for high-volume devices with limited resources.
|
| |
Presence API
This is a generic and protocol-agnostic API for presence (the notion of an entity being a part of a network). It provides a standard portable and secure interface to control, manage, and manipulate presence information between presence clients and servers.
|
| |
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.
|
| |
Mobile Sensor API
The Mobile Sensor API is a general sensor API that extends the usability and choice of sensors for Java ME applications. It defines generic sensor functionality optimized for resource-constrained devices such as mobile devices. It offers unified way of managing sensors, connected to mobile devices, and easy access to the sensor data.
|
| |
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.
|
| |
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.
|
| |
Standard Extension API for Integrated Development Environments
A standard IDE extension API that lets developers implement integrated development environment (IDE) add-in modules once and have their features run with any IDE supporting the standard specification.
|
| |
Service Component Architecture
In response to requests from customers and Independent Software Vendor (ISV) partners, BEA, Cape Clear, IBM, Interface21, IONA, Oracle, Primeton Technologies, Progress Software, Red Hat., Rogue Wave, SAP, Siemens, Software AG, Sun, Sybase and TIBCO are collaborating on specifications for building systems that use a Service-Oriented Architecture (SOA), which aim to provide developers with simpler and more powerful ways of constructing applications based on SOA. These specifications are published under royalty-free terms.
|
| |
Java Modeling Language (JML)
JML is a behavioral interface specification language that can be used to specify the behavior of Java modules.
|
| |
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.
|
| |
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.
|
| |
Web Services Metadata for the Java Platform
This specification defines an annotated Java syntax for programming Web services. The specification builds on the Java language metadata facility to provide an easy-to-use syntax for describing Web services at the source-code level for the J2EE platform.
|
| |
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.
|
| |
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.
|
| |
Payment API
The payment API enables application developers to initiate mobile payment transactions in J2ME applications. The syntax for the description of the associated provisioning data enables API implementers to support different payment instruments.
|
| |
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.
|
| |
Service Component Architecture
Service Component Architecture (SCA) is a set of specifications that describe a model for building applications and systems using a Service-Oriented Architecture. SCA extends and complements prior approaches to implementing services, and SCA builds on open standards such as Web services. These specifications are published under royalty-free terms.
|
| |
Service Data Objects
Service Data Objects (SDO) is designed to simplify and unify the way in which applications handle data. Using SDO, application programmers can uniformly access and manipulate data from heterogeneous data sources, including relational databases, XML data sources, Web services, and enterprise information systems. The SDO specifications are published under royalty-free terms.
|
| |
Service Component Architecture
In response to requests from customers and Independent Software Vendor (ISV) partners, BEA, IBM, IONA, Oracle, SAP, Siebel Systems, and Sybase are collaborating on specifications for building systems that use a Service-Oriented Architecture (SOA), which aim to provide developers with simpler and more powerful ways of constructing applications based on SOA. These specifications are published under royalty-free terms.
|
| |
Specifications: Service Component Architecture (SCA) and Service Data Objects (SDO)
In response to requests from customers and Independent Software Vendor (ISV) partners, IBM is jointly delivering two specifications for building systems that use a Service-Oriented Architecture (SOA), which aim to provide developers with simpler and more powerful ways of constructing applications based on SOA: Service Component Architecture (SCA) and Service Data Objects (SDO).
|
| |
Monitoring and Management Specification for the Java Virtual Machine
These APIs provide Java applications, system-management tools, and RAS-related tools with the ability to monitor the health of the Java virtual machine as well as manage certain run-time controls.
|
| |
Scalable 2D Vector Graphics API for J2ME
This is a J2ME optional package that enables rendering scalable 2D vector images, including external images in W3C Scalable Vector Graphics (SVG) format. The primary use cases of this API are map visualization, scalable icons, enterprise applications, user interfaces, and other applications that require scalable and rich animated graphics.
|
| |
SWT: The Standard Widget Toolkit
SWT is a widget toolkit for Java designed to provide efficient, portable access to the user-interface facilities of the operating systems on which it is implemented.
|
| |
XML Digital Signature APIs
This specification defines and incorporates a standard set of high-level implementation-independent APIs for XML digital signatures services. The XML Digital Signature specification is defined by the World Wide Web Consortium.
|
| |
OSS Inventory API
The OSS Inventory API defines J2EE-based interfaces between inventory repositories and other operational support system (OSS) components, such as customer relationship management, service and network activation, SLA management, service impact analysis, and service and network planning.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
Mobile Internationalization API
This specification defines an optional J2ME API that enables the internationalization and localization of MIDP applications. The API provides locale-specific formatting of common data items such as times, dates, and currency amounts, and access to application resources that contain UI text strings and other localizable items in a compact file format.
|
| |
Monitoring and Management Specification for the Java Virtual Machine
These APIs provide Java applications, system-management tools, and RAS-related tools with the ability to monitor the health of the Java virtual machine as well as manage certain run-time controls.
|
| |
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.
|
| |
Server API for Mobile Services: Messaging (SAMS: Messaging)
The SAMS: Messaging specification defines a protocol-agnostic messaging API for composing, sending, and receiving short messages and multimedia messages. It provides a client API to Short Message Service (SMS) and Multimedia Messaging Service (MMS) servers.
|
| |
Security and Trust Services API for J2ME
This API provides security services to Java applications running on J2ME-enabled devices and enables new value-added functions to be deployed on these devices. It enables a device to become trusted -- to provide security mechanisms to support a wide variety of application-based services, such as access to corporate network, mobile commerce, and digital rights management.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
Metadata Facility for the Java Programming Language
The metadata facility allows classes, interfaces, fields, and methods to be marked as having particular attributes, enabling them to be processed in special ways by development tools, deployment tools, or run-time libraries.
|
| |
Network Transfer Format for Java Archives
This specification defines a dense download format for Java classfiles to achieve considerable size savings over compressed JAR files.
|
| |
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.
|
| |
Unicode Supplementary Character Support
Unicode Supplementary Character Support provides a mechanism to support Supplementary Characters as defined in the Unicode 3.1 specification. The new APIs are a collection of small extensions to the existing Java class library APIs that seek to preserve and extend the platform's existing character processing model and thus provide compatibility with existing programs.
|
| |
SIP Servlet API
The Session Initiation Protocol (SIP) is used to establish and manage multimedia IP sessions. The SIP Servlet API is a high-level extension API for SIP servers, enabling SIP applications to be deployed and managed based on the servlet model
|
| |
Timer and Work Manager for Application Servers
The Timer for Application Servers specification provides an API for using timers in an application-server supported fashion, enabling J2EE-based applications, including servlets, EJB apps, and JCA Resource Adapters, to schedule future timer notifications and receive timer notifications. The Work Manager for Application Servers specification provides an API for application-server supported concurrent execution of work items, enabling J2EE-based applications, including servlets and EJB apps, to schedule work items for concurrent execution. This will provide greater throughput and better response time.
|
| |
OSS Billing Mediation API
This specification provides an API via the OSS through Java initiative that allows telecom network management applications to be developed and integrated with Java-enabled IP billing systems.
|
| |
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.
|
| |
JavaServer Faces (JSF)
The JavaServer Faces specification defines an architecture and APIs that simplify the creation and maintenance of Java server application GUIs.
|
| |
J2ME Web Services Specification
The J2ME Web Services Specification defines an optional package that provides standard access from J2ME to Web services.
|
| |
Streaming API for XML (StAX)
The Streaming API for XML (StAX) is a Java-based API for pull-parsing XML. The API exposes a simple iterator-based API, which allows the programmer to ask for the next event and allows state to be stored in a procedural fashion.
|
| |
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.
|
| |
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.
|
| |
PDA Optional Packages for the J2ME Platform
These optional packages provide features that are commonly found on PDAs and other mobile devices in the J2ME space: one package for Personal Information Management (PIM) access, and one package for accessing file systems through the Generic Connection Framework (GCF).
|
| |
XML Data Binding Specification
This specification provides a facility for compiling an XML schema into one or more Java classes that can parse, generate, and validate documents that follow the schema.
|
| |
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.
|
| |
SIP API for J2ME
SIP API for J2ME defines a multipurpose Session Initiation Protocol (SIP) API for J2ME clients. It enables SIP applications to be executed in memory-limited terminals, and is especially targeted to mobile phones.
|
| |
Mobile 3D Graphics API for J2ME
This is lightweight, interactive 3D graphics API that sits alongside J2ME and MIDP as an optional package. It's intended for a wide range of applications, including games, animated messages, screen savers, custom user interfaces, product visualization, and so on.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
Portlet Specification
This specification defines a set of APIs for portal computing addressing the areas of aggregation, personalization, presentation, and security.
|
| |
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.
|
| |
SOAP with Attachments API for Java
The SOAP with Attachments API for Java (SAAJ) provides a standard way to send XML documents over the Internet from the Java platform. SAAJ enables developers to produce and consume messages conforming to the SOAP 1.1 specification and SOAP with Attachments note.
|
| |
PDA Optional Packages
The PDA Optional Packages provide a means to access native Personal Information Manager information (PIM) and File Systems in J2ME configurations. Personal Information Managers typically provide Calendaring, Contacts and ToDos.
|
| |
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.
|
| |
Location API for J2ME
This specification enables developers to write mobile location-based applications for resource-limited devices. It provides a compact and generic API that produces information about a device's present physical location to Java applications. The API is designed as an optional package that can be used with many J2ME profiles. The minimum platform assumed is the J2ME Connected, Limited Device Configuration (CLDC).
|
| |
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.
|
| |
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 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.
|
| |
Personal Profile Specification
The J2ME Personal Profile provides the J2ME environment for devices with a need for a high degree of Internet connectivity and Web fidelity.
|
| |
OSS Quality of Service API
This API allows telecom management applications to be developed and integrated with Java-enabled Quality of Service systems.
|
| |
Implementing Enterprise Web Services
This specification defines the programming model and runtime architecture for implementing Web services in the Java language.
|
| |
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.
|
| |
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 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.
|
| |
