• JSRs by Platform
• JSRs by Technology
• JSRs by Stage
• JSRs by Committee
• List of All JSRs



Register for Site

Use of JCP site is subject to the JCP Terms of Use and the Oracle Privacy Policy


• About JCP
  • Program Overview
  • JCP Process Document
  • Calendar
  • JCP Members
  • Executive Committee
  • Elections
• Get Involved
  • Overview
  • Becoming a JCP Member
  • Java in Education
• Community Resources
  • Overview
  • Tutorials
  • JCP Podcasts
  • Spec Lead Guide
  • TCK Tool & Info
  • License Reference
• Community News
  • News
  • Programs & Awards
  • Press Releases
  • Success Stories
• FAQ
• Contact Us

Specification Leads
	Lance Andersen	Oracle
Expert Group
	BEA Systems	DataDirect Technologies	IBM
	Murphy, David	New Atlanta Communications, LLC	Novell, Inc.
	Oracle	PointBase, Inc.

NOTICE: Please be aware the CDC 1.0 specification initially related to this JSR has been replace (superseded) with the newer CDC 1.1 specification. CDC 1.0 will no longer be supported after 18-Aug-2009. This JSR and other optional technologies based on the CDC 1.0 standards are fully compatible with the CDC 1.1 standards. All development and certification efforts should be updated to use the current, supported technology.

Updates to the Original JSR

The following information has been updated from the original proposal on the following dates:

2008.04.17:

Maintenance Lead: Lance Andersen

E-Mail Address: lance.andersen@sun.com

Telephone Number: +1 781 442 2037

Fax Number: +1 781 442 1610

2006.07.19

Specification Lead: Jon Courtney

E-Mail Address: jonathan.courtney@sun.com

Telephone Number: -

Fax Number: +1 972 235 5727

Identification | Request | Contributions | Additional Information

Section 1. Identification

Submitting Member: Sun Microsystems, Inc.

Name of Contact Person: Jon Ellis

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

Telephone Number: +81 3 5717 4517

Fax Number: +81 3 5717 7274

Specification Lead: Jon Ellis

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

Telephone Number: +81 3 5717 4517

Fax Number: +81 3 5717 7274

Initial Expert Group Membership:

IBM
Oracle
Pointbase

Supporting this JSR: IBM
Data-Direct Technologies
Pointbase
Snap

IBM
Oracle
Pointbase

Section 2: Request

2.1 Please describe the proposed Specification:

The proposed specification will define a JDBC Optional Package for Java 2 Micro Edition (J2ME), Connected Device Configuration (CDC) Foundation Profile. This optional package will contain equivalent functionality to the java.sql package provided in Java 2 Standard Edition (J2SE). The functionality required should be adjusted to take into account the limitations of CDC in terms of size, functionality and removal of deprecated APIs. The JDBC Optional Package for CDC would provide a strict subset of the functionality available in J2SE.

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

Java 2 Micro Edition Connected Device Configuration and Foundation Profile.

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

The proposed specification will provide the Java community with a standard database access API for developing applications for devices running CDC. The current lack of a standard API limits the portability of applications that require database access.

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

The CDC Foundation Profile does not contain support for the JDBC API.

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

The JDBC API is a data access api targeted at relational database systems. It maps a traditional call level interface into a set of classes that an be used to access database resource in a natural way from the Java programming language.

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

java.sql

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.

The working model will be mostly email and tele conf. if necessary.

2.12 Please describe the anticipated working model for the Expert Group working on developing this specification.

The Final Approval is anticipated for November 2002

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.

The JDBC 3.0 API Specification - http://java.sun.com/products/jdbc

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

The JDBC 3.0 API Specification defines the JDBC API as it is included in J2SE, the proposed specification will define a subset of this API that is suitable for CDC.

Section 4: Additional Information (Optional)

4.1 This section contains any additional information that the submitting Member wishes to include in the JSR.

N/A