 |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
Wireless Messaging API (WMA)
This set of optional APIs provides standard access to wireless communication resources to allow third-party developers to build intelligent connected Java applications.
|
| |
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.
|
| |
Unified Printing API (Java Print Service API)
This unified Java Print API will be based on a print model that meets the requirements of the current Java 2 Print API, Jini Printing, and the proposed Java Network Printing API.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
Standard Tag Library for JavaServer Pages (JSTL)
JSP tag libraries define declarative, modular functionality that can be reused by any JSP page. JSTL encapsulates, as simple tags, core functionality common to many JSP applications. This standardization lets you learn a single tag and use it on multiple JSP containers. Also, when tags are standard, containers can recognize them and optimize their implementations.
|
| |
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.
|
| |
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).
|
| |
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
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 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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
SQLJ
SQLJ is a three-part ANSI/ISO/NIST standard for using embedded SQL statements in Java programs, using Java to write persistent stored modules, and defining and maintaining nonrelational data types inside an object/relational database.
|
| |
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.
|
| |
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
|
| |
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.
|
| |
Real-time Specification for Java
The Real-time Specification for Java extends the Java platform to support both current practice and advanced real-time systems application programming.
|
| |
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.
|
| |
Preferences API
The Preferences API allows programs to manipulate user preference data and configuration data on all Java platforms. Applications require preference and configuration data to adapt to different users, environments, and needs. This API provides a way to store, retrieve, and modify this data.
|
| |
Portlet Specification
This specification defines a set of APIs for portal computing addressing the areas of aggregation, personalization, presentation, and security.
|
| |
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.
|
| |
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.
|
| |
Personal Basis Profile
The J2ME Personal Basis Profile provides a J2ME application environment for network-connected devices supporting a basic level of graphical presentation.
|
| |
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.
|
| |
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).
|
| |
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.
|
| |
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.
|
| |
Open Services Gateway Initiative (OSGi)
OSGi technology is universal middleware that provides a service-oriented, component-based environment for developers and offers standardized ways to manage the software life cycle. The OSGi specifications define an in-VM service oriented architecture (SOA) for networked systems. This architecture significantly reduces the overall complexity of building, maintaining and deploying applications.
|
| |
OSS Trouble Ticket API
The OSS Trouble Ticket API addresses a growing trend within telecommunications industry toward the use of J2EE for development of various aspects of Operations Support Systems (OSSs). IT provides interfaces for creating, querying, updating, and deleting trouble tickets (trouble reports).
|
| |
OSS Service Activation API
This API allows telecom management applications to be developed and integrated with Java-enabled Service Activation systems.
|
| |
OSS Quality of Service API
This API allows telecom management applications to be developed and integrated with Java-enabled Quality of Service systems.
|
| |
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.
|
| |
OSS Discovery API
An API that allows network discovery applications to be developed and integrated with other OSS/J enabled applications.
|
| |
OSS Common API
The OSS Common API is the set of APIs common across the OSS through Java specifications, meant to reduce duplication of common interfaces and classes among these specifications.
|
| |
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.
|
| |
New I/O APIs for the Java Platform
These are J2SE APIs for scalable I/O, fast buffered binary and character I/O, regular expressions, charset conversion, and an improved filesystem interface.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
Mobile Media API (MMAPI)
The Mobile Media API provides a high-level interface to sound and multimedia capabilities of a device running J2ME in order to enable versatile multimedia functionality in J2ME applications.
|
| |
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.
|
| |
Mobile Information Device Profile (MIDP)
MIDP is a set of Java APIs that, together with the Connected Limited Device Configuration (CLDC), provides a complete J2ME application runtime environment targeted at mobile information devices, such as mobile phones and entry-level PDAs.
|
| |
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.
|
| |
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.
|
| |
Long-Term Persistence for JavaBeans Specification
The specification provides streams to convert graphs of JavaBeans architecture to and from version-resilient file formats (typically XML documents). This specification is intended to create a standard for designs that is portable between IDEs.
|
| |
Logging API Specification
This specification defines standard logging APIs for error and trace logging, suitable for logging events from within the J2SE platform and from within Java applications. It is intended to allow field service engineers to obtain information to help diagnose application problems in the field.
|
| |
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).
|
| |
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.
|
| |
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.
|
| |
JavaServer Faces (JSF)
The JavaServer Faces specification defines an architecture and APIs that simplify the creation and maintenance of Java server application GUIs.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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 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 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 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 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 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 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 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 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 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 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 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 Modeling Language (JML)
JML is a behavioral interface specification language that can be used to specify the behavior of Java modules.
|
| |
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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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.
|
| |
