Find JSRs
Submit this Search


Ad Banner
 
 
 
 

Summary  |  Proposal  |  Detail (Summary & Proposal)
JSRs: Java Specification Requests
JSR 145: JAINTM SPA Common API

Stage Access Start Finish
Withdrawn   14 Feb, 2003  
Community Draft Ballot View results 08 Oct, 2002 14 Oct, 2002
Community Review Login page 13 Sep, 2002 14 Oct, 2002
Expert Group Formation   28 Aug, 2001 15 Aug, 2002
JSR Review Ballot View results 14 Aug, 2001 27 Aug, 2001
Status: Withdrawn
Reason: Read the Spec Lead's explanation of the withdrawal.
JCP version in use: 2.1
Java Specification Participation Agreement version in use: 1.0


Description:
This JSR will specify the set of APIs common across the JAIN SPA JSRs. This will provide consistency by reducing duplication of common interfaces and classes among these JSRs.

Please direct comments on this JSR to the Spec Lead(s)
Team

Specification Leads
  Gary Bruce Sun Microsystems, Inc.
Expert Group
  AePONA Fujitsu Limited Incomit AB
  Net4Call A.S. Open Cloud Limited Sun Microsystems, Inc.
  Telcordia Technologies, Inc. Teltier Technologies
Contributors
       

This JSR has been Withdrawn
Reason: Read the Spec Lead's explanation of the withdrawal.

Original Java Specification Request (JSR)

Identification | Request | Contributions | Additional Information

Section 1. Identification

Submitting Member: Sun Microsystems, Inc

Name of Contact Person: Phelim O'Doherty

E-Mail Address: phelim.odoherty@sun.com

Telephone Number: +44 28 9085 1199

Fax Number:


Specification Lead: Phelim O'Doherty

E-Mail Address: phelim.odoherty@sun.com

Telephone Number: +44 28 9085 1199

Fax Number:


Initial Expert Group Membership:

Sun Microsystems, Inc



Section 2: Request

2.1 Please describe the proposed Specification:

The JAIN initiative brings service portability, convergence, and secure network access to telephony and data networks. The JAIN APIs are targeted at appliation developers within network equipment vendors, independent software vendors (ISVs), system integrators, and service providers.

There are currently twenty one different JAIN JSRs which are in the Java Community Process. As a result of tight collaboration among the members of the JAIN initiative, these JSRs have a consistent architecture and they share common design patterns. As a result, they have common base interfaces and classes, such as data types and exception definitions.

This specification will document and specify these common base interfaces and classes to avoid duplication of these interfaces and classes in each of the above JAIN JSRs and to maintain consistency of these interfaces and classes across these JSRs.

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

The target platform for this JSR (and the JAIN JSRs) is Java 2 Platform, Enterprise Edition and the Java 2 Standard Edition.

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

This specification will address the need to provide standardization conventions allowing interoperability of JAIN components and reducing the cost of their integration in an end-to-end JAIN solution.

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

Currently, no existing J2EE or J2SE specification provides a standard Common JAIN API. Existing JAIN APIs need a common JSR to capture these common interfaces and classes to avoid duplication of classes and code in each JAIN API and maintain consistency across the JAIN APIs.

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

The JAIN APIs, including the JAIN Common APIs will be based on standard J2EE and J2SE services, including the JavaBean event model.

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

The API will have one or several packages and the prefix for all packages will be "javax.jain".

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

The specification has no dependency on operating systems, CPUs, or I/O devices.

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

None

2.9 Are there any internationalization or localization issues?

None

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

Once this JSR reaches final release, the JAIN Final release related APIs will be updated to reference the common JAIN JSR. Newer JAIN JSRs will depend on this JSR for common base interfaces and classes.

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

Expected submission date: 08/07
Community draft submitted by 09/28
Community review closed 10/26
Public draft submitted by 11/02
Public review closed 12/02
Proposed Final draft submitted 12/07
Final release 01/11.

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

The anticipated working model is via email and conference calls, with readouts and discussions occuring and the necessary JAIN Community meetings.





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.

JAIN TCAP 1.0 JSR #011
JAIN ISUP JSR #017
JAIN OAM 1.0 JSR #018
JAIN JCC JSR #021
JAIN SLEE JSR #022
JAIN MGCP JSR #023
JAIN SPA JSR #024
JAIN MAP JSR #029
JAIN SIP JSR #032
JAIN INAP JSR #035
JAIN MEGACO JSR #079
JAIN H.323 JSR #081
JAIN SPA Mobility JSR #098
JAIN SCE JSR #100
JAIN SPA GUI JSR #103
JAIN SPA IM JSR #119
JAIN JCAT JSR #122
JAIN SPA PAM JSR #123
JAIN SIPLite JSR #125
JAIN OAM 2.0 JSR #132
JAIN 3G MAP JSR #137

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

This specification will start with the results of the above mentioned JAIN JSR specifications.



Section 4: Additional Information (Optional)

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

None