Find JSRs
Submit this Search

Ad Banner

Summary  |  Proposal  |  Detail (Summary & Proposal)
JSRs: Java Specification Requests
JSR 144: OSS Common API

Stage Access Start Finish
Maintenance Release 5 Download page 24 Jul, 2007  
Maintenance Draft Review 6 Download page 06 Jun, 2007 09 Jul, 2007
Maintenance Draft Review 5 Download page 20 Dec, 2006 22 Jan, 2007
Maintenance Release 4 Download page 29 Nov, 2006  
Maintenance Draft Review 4 Download page 09 Jun, 2006 17 Jul, 2006
Maintenance Release 3 Download page 21 Feb, 2006  
Maintenance Draft Review 3 Download page 22 Dec, 2005 23 Jan, 2006
Maintenance Release 2 Download page 22 Nov, 2005  
Maintenance Draft Review 2 Download page 27 Sep, 2005 31 Oct, 2005
Maintenance Release Download page 20 Apr, 2005  
Maintenance Draft Review Download page 29 Oct, 2004 06 Dec, 2004
Final Release Download page 02 Apr, 2002  
Final Approval Ballot View results 19 Mar, 2002 01 Apr, 2002
Proposed Final Draft Download page 14 Feb, 2002  
Public Review Download page 21 Nov, 2001 21 Dec, 2001
Community Draft Ballot View results 02 Oct, 2001 08 Oct, 2001
Community Review Login page 05 Sep, 2001 08 Oct, 2001
Expert Group Formation   21 Aug, 2001 22 Aug, 2001
JSR Review Ballot View results 07 Aug, 2001 20 Aug, 2001
Status: Maintenance
JCP version in use: 2.6
Java Specification Participation Agreement version in use: 2.0

This JSR specifies the set of APIs which are common across the OSS through Java JSRs. This provides consistency by reducing duplication of common interfaces and classes among these JSRs.

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

Specification Leads
Star Spec Lead Vincent Perrot Sun Microsystems, Inc.
Expert Group
  BEA Systems Ericsson Inc. Goswami, Subrata
  Motorola NEC Corporation Nokia Corporation
  Oracle Sun Microsystems, Inc. Telcordia Technologies, Inc.

This JSR was completed under JCP 2.1/JSPA 1.

Original Java Specification Request (JSR)

Identification | Request | Contributions | Additional Information

Original Summary: This JSR will specify the set of APIs, which are common across the OSS through Java JSRs. This will provide consistency by reducing duplication of common interfaces and classes among these JSRs.

Section 1. Identification

Submitting Member: Sun Microsystems, Inc

Name of Contact Person: Daniel Lutoff

E-Mail Address:

Telephone Number: +33 4 76 18 82 50

Fax Number: +33 4 76 18 83 50

Specification Lead: Daniel Lutoff

E-Mail Address:

Telephone Number: +33 4 76 18 82 50

Fax Number: +33 4 76 18 83 50

Initial Expert Group Membership:

  • Co-Submitting Member: BEA
    Name of Contact Person: saify Lanewala
  • Co-Submitting Member: Ericsson
    Name of Contact Person: Stefan Aberg
    Telephone Number: +46 31 747 1997
    Fax Number: +46 31 747 2942
  • Co-Submitting Member: Motorola
    Name of Contact Person: David Raymer
  • Co-Submitting Member: Nokia
    Name of Contact Person: Stefan Vaillant
    Telephone Number: +49 211 9412
    Fax Number: +49 211 9412 3988
  • Co-Submitting Member: Nortel Networks
    Name of Contact Person: Pierre Gauthier
    Telephone Number: +1 613 763 2281
    Fax Number: +1 613 765 7387
  • Co-Submitting Member: NEC
    Name of Contact Person: Shingo Fukui
    E-Mail Address:
  • Co-Submitting Member: Telcordia Technologies
    Name of Contact Person: Rick Porter
    Telephone Number: +1 973 829 4490
    Fax Number: +1 973 829 5981

  • Section 2: Request

    2.1 Please describe the proposed Specification:

    The OSS through Java initiative (OSS/J) is focused on the operations and business support systems ("back office systems") of service providers. The OSS/J APIs are targeted at OSS developers within network equipment vendors, independent software vendors (ISVs), system integrators, and service providers.

    There are currently three different OSS/J JSRs which are in, or completing, public review (OSS Service Activation API -JSR 89-, OSS Quality of Service API -JSR 90- and OSS Trouble Ticket API -JSR 91-). In addition, two new OSS/J JSRs (OSS IP Billing API -JSR 130- and OSS Inventory API -JSR 142) have been initiated and the initiative expects more OSS/J JSRs to initiate in the near future.

    As a result of tight collaboration among the members of the OSS/J 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 OSS/J 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 abovementioned OSS/J JSRs) is Java 2 Platform, Enterprise 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 OSS components and reducing the cost of their integration in an end-to-end OSS solution.

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

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

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

    The OSS/J APIs, including the OSS Common APIs will be based on standard J2EE services. The most important J2EE APIs for this JSR will be the following:

    EJB (Enterprise JavaBeans). To facilitate the integration of OSS components, the OSS/J APIs will define standard EJB interfaces.

    JMS (Java Message Service) Besides the ability to execute synchronous (EJB) methods calls, there is also a need to send asynchronous messages. For this, JMS is being considered to be most viable.

    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.oss".

    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 anticipated.

    2.9 Are there any internationalization or localization issues?

    None anticipated.

    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 three more mature OSS related APIs (JSR 89, JSR 90 and JSR 91) will be updated to reference the common OSS JSR. Newer OSS JSRs (JSR 130 and JSR 142) will depend on this JSR for common base interfaces and classes.

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

    Community Review September 2001
    Public Review Closed 19 December 2001
    Proposed Final Draft 28 January 2002
    Final Approval Ballot 11 February 2002
    Final Release 25 February 2002

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

    We believe this aggressive schedule can be achieved because this JSR's expert group will draw from the experts of the abovementioned OSS/J JSRs. These experts have already worked collaboratively to agree on a common architecture and base infrastructure for JSR 89, JSR 90 and JSR 91. Many of the common interfaces and classes that will be included in this JSR have already been specified and reviewed via JSR 89, JSR 90, and JSR 91.

    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.

    OSS Service Activation (JSR 89)
    OSS Quality of Service (JSR 90)
    OSS Trouble Ticket (JSR 91)
    OSS IP Billing (JSR 130)
    OSS Inventory API (JSR 142)

    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 JSR specifications.