 
Use of JCP site is subject to the
JCP Terms of Use and the
Oracle Privacy Policy
 |
|
 JSRs: Java Specification Requests
JSR 136: JavaTM Technology for Service Providers
Reason: Community support was not sufficient to support an Expert Group. JCP version in use: 2.1 Java Specification Participation Agreement version in use: 1.0 Description: This would have correlated JSRs targeted at next-generation service providers, documented how these JSRs fit together within end-to-end service provider networks, and introduced developers to emerging service provider network-targeted APIs. Please direct comments on this JSR to the Spec Lead(s) Team
This JSR has been Withdrawn Section 1. Identification Submitting Member: Sun Microsystems Name of Contact Person: Swee Lim E-Mail Address: swee.lim@sun.com Telephone Number: (650) 786-6819 Fax Number: (650) 786-8611 Specification Lead: Swee Lim E-Mail Address: swee.lim@sun.com Telephone Number: (650) 786-6819 Fax Number: (650) 786-8611 List of other Participants who endorse this JSR:
Projected expert group will include experts from:
Section 2: Request 2.1 Please describe the proposed Specification:BackgroundThe service provider community has been actively driving Java into the service provider industry. This community has submitted over 20 JSRs (see Section 3). Most of these JSRs are hosted under two distinct and independent initiatives; JAINTM and OSS through JavaTM. These JSRs define Java APIs that enable rapid development and deployment of innovative and revenue enhancing applications and services for next generation integrated networks and wireless networks.
Scope of this JSR The primary output of this JSR is a set of documents. This JSR and the resulting specification will:
This JSR will correlate and reference the above JSRs in the Java Technology for Service Providers specification. This specification will include a broad overview of the components in current and emerging service provider network architectures, such as PSTN, 2G/3G Wireless, and/or next generation converged networks. It will show which JSRs and APIs are applicable to an individual component and how Java APIs are used to interface related components.
This introduction will be provided in the form of a developers guide describing the use and application of the above APIs. This guide may contain code examples illustrating the concurrent use of multiple APIs, common design and interaction patterns, distribution techniques, pitfalls, and recommended coding practices. The JAIN and OSS/J initiatives will continue to provide detailed design and architectural guidelines for JSRs within their respective areas of interest. This JSR recognizes and respects the independence and autonomy of these initiatives from each other and from this JSR. Each initiative's intense focus on their respective areas of interest have been instrumental and very successful at motivating in-progress JSRs and initiating new JSRs within their respective communities. This JSR will continue to depend on these independent initiatives, their respective communities, and their JSRs to define APIs, including future directions and roadmaps. This JSR will embrace the JSR specifications defined under these initiatives, incorporate them by reference into this JSR, and show how the JSRs initiated by these initiatives fit within the above end-to-end service provider network architectures. This JSR should exploit synergy's and avoid duplicating work done by these initiatives. However, the administration of this JSR will be autonomous and independent of the above initiatives.. While working on this JSR, this JSR may receive suggestions and/or become aware of a need to revise APIs being defined by a pre-existing JSR. This JSR will pass on these suggestions and findings to the appropriate JSR's expert group for their consideration and evaluation. Revisions and changes to these APIs will remain the charter of the appropriate JSR's expert group.
2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)This specification targets both the J2SE platform and the J2EE platform. The target platform will be determined by the individual JSRs referenced by this specification.2.3 What need of the Java community will be addressed by the proposed specification?Currently, there are over 20 JSRs targeted at the service provider industry and its Java developers. There is a need in the service provider industry and Java community to understand how these JSRs (and APIs) fit together, and how to build an end-to-end Java technology based solution. This JSR will address this need by defining an overall Java Technology for Service Provider architecture which will provide guidance to developers on the use and application of these APIs within the end-to-end service provider network. It will stimulate and facilitate adoption of Java technology in the service provider network. It will also open new market opportunities for vendors in the Java community.2.4 Why isn't this need met by existing specifications?The current service provider JSRs target and focus on specific application areas or components within the service provider network. For example, a JAIN protocol JSR focuses on a specific SS7 or IP protocol, while an OSS/J JSR focuses a specific OSS application, such as service activation. There is no existing JSR that attempts to provide a comprehensive overview of how many of the existing JSRs are related and how they fit within the end-to-end service provider network.This JSR complements the existing service provider JSRs. It presents a macro overview that embraces all the above JSRs, while the existing individual JSRs present detailed views into specific components and their APIs within the Java Technology for Service Provider architecture. 2.5 Please give a short description of the underlying technology or technologies:This is covered in Section 2.1.2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)Not applicable. This JSR will not define APIs.2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?No2.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 expected schedule for this specification is about 1 year. The target milestones for this JSR are listed below: Community Draft:
Jan 2002
This schedule is subject to change. The actual schedule will be determined by the expert group. 2.12 Please describe the anticipated working model for the Expert Group working on developing this specification.Primary form of collaboration will be via email and augmented by regularly scheduled conference calls when necessary.Since it is expected that the expert group will consult with the JAIN and OSS/J experts, face-to-face meetings will be coordinated with regularly scheduled meetings of these communities to facilitate fluid exchange of information and encourage participation by the experts of these initiatives. The administration of this JSR will be autonomous and independent of the JAIN and OSS/J initiatives. 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.For the following JSR contributions, see http://java.sun.com/aboutJava/communityprocess/search.htmlJAIN JSRs
3.2 Explanation of how these items might be used as a starting point for the work.This specification will reference the above JSR specifications and show developers how these specifications fit into a Java technology architecture for service providers. |
||||||||||||||||||||||||||||||||||||
