JSRs: Java Specification Requests
JSR 119: JAINTM SPA Integrity Management and Event Notification API
This JSR has been Withdrawn
Section 1. Identification
Submitting Member: Ulticom
Name of Contact Person: Stephanie Dithurbide
E-Mail Address: firstname.lastname@example.org
Telephone Number: +1 856 787 2784
Fax Number: + 1 856 866 2033
Specification Lead: Gary Bruce
E-Mail Address: Gary.Bruce@Sun.COM
Telephone Number: +44 122 341 8934
Initial Expert Group Membership:
Section 2: Request
2.1 Please describe the proposed Specification:
The JAINTM SPA IM and EN 1.0 specification will provide Java APIs for use in a Parlay client environment.
These APIs are functionally compatible with the Parlay "Client Application to Framework" IM and EN 3.0 APIs.
State-of-the-art design patterns will be used, hiding some details of the underlying communication model between Parlay client and server.
2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)
The JAINTM SPA IM and EN 1.0 specification is targeted for the Java 2 Platform Standard Edition (J2SE) and Java 2 Enterprise Edition (J2EE) platforms.
2.3 What need of the Java community will be addressed by the proposed specification?
The JAINTM SPA IM and EN 1.0 API will be part of a Java technology instantiation of Parlay, which enables external enterprises to rapidly build and deploy applications that exploit capabilities of the underlying telco's network. By adopting Parlay, the Java community can leverage on the huge investment made by Parlay members into the specification and associated adoption across the IT & telecom industry.
This specification is required to ensure continued standardization across the computing industry with regard to public open APIs.
2.4 Why isn't this need met by existing specifications?
There is no JAINTM (or JavaTM) API to represent a Java specification of the Parlay "Client Application to Framework" IM and EN APIs at present.
2.5 Please give a short description of the underlying technology or technologies:
It is anticipated that the proposed API would be implemented on a Parlay client, using an arbitrary communication protocol to a Parlay server, to access IM and EN services in a controlled and secure telecoms environment.
It is highly desired that the API seamlessly interoperates with other JAINTM APIs including but not limited to:
JAINTM SPA TSM, SD and SAM
2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)
The specification will be provided directly in, and in subpackages of:
It will contribute common classes and interfaces to javax.jain and javax.jain.framework, as defined in the JAINTM Common API.
2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?
2.8 Are there any security issues that cannot be addressed by the current security model?
2.9 Are there any internationalization or localization issues?
2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?
2.11 Please describe the anticipated schedule for the development of this specification.
Expert group creation as soon as the JSR is approved.
2.12 Please describe the anticipated working model for the Expert Group working on developing this specification.
Regular face-to-face sessions during JAIN community meetings and conference calls to solve specific issues when required during the JAIN meeting.
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.
Documents describing JAINTM can be found at:
Documents describing Parlay can be found at:
3.2 Explanation of how these items might be used as a starting point for the work.
The Parlay "Client Application to Framework" IM and EN would form the basis of the JAINTM SPA "Client Application to Framework" IM and EN API.