 |
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.
|
| |
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).
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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 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 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 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 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 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 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 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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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 Discovery API
An API that allows network discovery applications to be developed and integrated with other OSS/J enabled applications.
|
| |
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 Quality of Service API
This API allows telecom management applications to be developed and integrated with Java-enabled Quality of Service systems.
|
| |
OSS Service Activation API
This API allows telecom management applications to be developed and integrated with Java-enabled Service Activation systems.
|
| |
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).
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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).
|
| |
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.
|
| |
Personal Basis Profile
The J2ME Personal Basis Profile provides a J2ME application environment for network-connected devices supporting a basic level of graphical presentation.
|
| |
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.
|
| |
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.
|
| |
Portlet Specification
This specification defines a set of APIs for portal computing addressing the areas of aggregation, personalization, presentation, and security.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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).
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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 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.
|
| |
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 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.
|
| |
