JSR 114: JDBC Rowset Implementations

Updates to the Original Java Specification Request (JSR)

The following updates have been made to the original JSR.

2.18 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.

Specification license
RI license
TCK license

The JSR was completed under JCP version 2.1, covered by JSPA 1. Maintenance work is being conducted under JCP 2.9.

The Maintenance Lead of JSR 114 was changed from Amit Handa to Lance Andersen (lance.andersen@oracle.com).

2.11 Please describe the anticipated schedule for the development of this specification.

It is intended that this JSR will be delivered as part of the J2SE^TM "Tiger" release.

2013.10.16:
This JSR was moved to JCP 2.9.

2.19 Please describe the communications channel you have established for the public to observe Expert Group deliberations, provide feedback, and view archives of all Expert Group communications.

Please use jdbc-spec-discuss@openjdk.java.net

2.20 What is the URL of the Issue Tracker that the public can read, and how does the public log issues in the Issue Tracker?

Currently we are using http://bugs.openjdk.java.net.

2.21 Please provide the location of the publicly accessible document archive you have created for the Expert Group.

Files are archived in the "Community Files" under the "Community" tab on this page.

---

Original Java Specification Request (JSR)

Identification | Request | Contributions

Section 1. Identification

Submitting Member: Sun Microsystems, Inc.

Name of Contact Person: Jon Ellis

E-Mail Address: jon.ellis@eng.sun.com

Telephone Number: +1 408 517 6918

Fax Number: +1 408 863 3195

Specification Lead: Jon Ellis

E-Mail Address: jon.ellis@eng.sun.com

Telephone Number: +1 408 517 6918

Fax Number: +1 408 863 3195

NOTE that this information has been updated from this original JSR.

Initial Expert Group Membership:

Macromedia
Borland
Compaq
HP/Bluestone
IBM
Informix
Merant
Oracle
SilverStream

Section 2: Request

2.1 Please describe the proposed Specification:

The proposed specification will define the API's for implementations of the Rowset interface. These implementations will be focused on providing the facilities needed by developers wanting to pass tabular data between distributed tiers and components. The specification will define the XML document format that will be used to represent the Rowset objects that are passed between components.

It is expected that the resulting specification and implementation will be integrated with JavaServer Pages tag libraries providing web developers with a richer environment for manipulating tabular data.

2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)

Java^TM 2 Platform, Standard Edition
Java^TM 2 Platform, Enterprise Edition

2.3 What need of the Java community will be addressed by the proposed specification?

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 scalabilty of applications and the flexibility of the programming model.

2.4 Why isn't this need met by existing specifications?

The JDBC 2.1 specification defined the javax.sql.Rowset interface and proposed several implementations. These proposed implementations are only outlined in the JDBC specification; this specification will specify these implementations more completely.

2.5 Please give a short description of the underlying technology or technologies:

See the Rowset chapter in the JDBC 2.1 specification for an overview of the Rowset interface.

2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)

Not yet determined.

2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?

No

2.8 Are there any security issues that cannot be addressed by the current security model?

No

2.9 Are there any internationalization or localization issues?

No

2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?

No

2.11 Please describe the anticipated schedule for the development of this specification.

It is anticipated that the development of the specification should be completed in 6 to 9 months.

Note that this section has been updated since the original JSR.

Section 3: Contributions

3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.

JDBC 2.1 API Specification (http://java.sun.com/jdbc/download.html)

Rowset Tutorial (http://developer.java.sun.com/developer/Books/JDBCTutorial/chapter5.html) from JDBC API Tutorial and Reference, Second Edition, White et al.

Rowset implementations available on Java Developer Connection

3.2 Explanation of how these items might be used as a starting point for the work.

The JDBC 2.1 API Specification describes the Rowset interface. The Rowset Tutorial proposes several implementations, which are available in binary form via the Java Developer Connection.