Find JSRs
Submit this Search

Ad Banner

Summary  |  Proposal  |  Detail (Summary & Proposal)
JSRs: Java Specification Requests
JSR 320: Services Framework

Stage Access Start Finish
Expert Group Formation   13 Nov, 2007  
JSR Review Ballot View results 30 Oct, 2007 12 Nov, 2007
Status: Dormant
JCP version in use: 2.6
Java Specification Participation Agreement version in use: 2.0

This specification will define a high level, lightweight services and management framework API's that will provide JME based devices the ability to manage long running applications and services.

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

Specification Leads
  Roger N. Mahler AT&T
Expert Group
  AromaSoft Corporation AT&T Deutsche Telekom AG
  LG Electronics Inc. Samsung Electronics Corporation Sun Microsystems, Inc.

This JSR has been Dormant
Reason: The Executive Committee voted to list this JSR as dormant in May 2012.

Original Java Specification Request (JSR)

Identification | Request | Contributions | Additional Information

Section 1. Identification

Submitting Member: SBC

Name of Contact Person: Roger N. Mahler

E-Mail Address:

Telephone Number: +1 404 236 6920

Fax Number: +1 404 236 5949

Specification Lead: Roger N. Mahler

E-Mail Address:

Telephone Number: +1 404 236 6920

Fax Number: +1 404 236 5949

Initial Expert Group Membership:


Supporting this JSR:


Section 2: Request

2.1 Please describe the proposed Specification:

This specification will define a high level, lightweight services and management framework API's that will provide Java ME (Connected Limited Device Configuration-CLDC and Connected Device Configuration-CDC) based devices the ability to manage long running applications and services. These services can be either elements with no user interfaces (traditional services/enablers) or elements with user interfaces (applications) that need to be managed either locally or remotely. This specification will provide API?s and will leverage and/or extend the existing life cycle management capabilities and programming model provided by the specific profiles and will be independent of specific underlying configurations. This capability will allow middleware providers the ability to manage their platforms as well as services and capabilities that attach or utilize their middleware. This specification will at a minimum provide the capabilities to:

  • Install/Uninstall applications and services
  • Start a Application/Service
  • Stop a Application/Service
  • Discover a Application/Service
  • Monitor a Application/Service
  • Service Application/Alarming

In order to accelerate adoption and time to market this specification will align, and leverage existing specifications both inside the JCP as well as specifications being developed in the industry.

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

The target Java platform is the Java ME. This optional package will run on both configurations CLDC and CDC and corresponding JME profiles:

2.3 The Executive Committees would like to ensure JSR submitters think about how their proposed technology relates to all of the Java platform editions. Please provide details here for which platform editions are being targeted by this JSR, and how this JSR has considered the relationship with the other platform editions.

This API targets JME.

2.4 Should this JSR be voted on by both Executive Committees?


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

Currently Java ME is lacking a Java API that allows a middleware provider the ability to manage the services that require, or are required by the middleware. This will become more critical as MIDP3 introduces the concept of services Liblets and long running services MIDLets. Several specifications are looking at solving parts of the requirements/problems. Where possible, this specification will leverage capabilities developed by other specifications such as, but limited to:

  • JSR-271 - MIDP3
  • JSR-279 - Service Connection API for Java ME
  • OMA Device Management

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

With the impending release of MIDP3 and other previously released multi-threaded configurations/profiles, this specification will provide a light-weight services framework to provide high level services management. There is currently little or no standardized, Lightweight capabilities provided by Java ME that allows for the management of services in a standardized, and predictable manner.

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

Services API's Specifically the services API?s that will allow for the run-time management of applications and services running as part of the container. Please refer to section 2.1 for proposed Services Framework:
The services framework will extend the capabilities of the existing application model allowing for the registration and management of capabilities provided by the services.
This services framework is intended to support other framework and components. Other possible framework binding that would be possible include the Liberty Identity Web Services Framework (IDWSF), Web Services Framework and the Services Connection API for Java ME.
Additionally this specification is intended to use and or leverage the following specifications as it's base:

  • JSR-139 - Connected Limited Device Configuration
  • JSR-218 - Connected Device Configuration
  • JSR-271 - MIDP3
  • JSR-279 - Service Connection API for Java ME
  • OMA Device Management

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


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


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


2.11 Are there any internationalization or localization issues?


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


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

Expert Group Formation: Q4 2007
Early Draft Review: Q2 2008
Public Review: Q3 2008
Proposed Final Draft: Q4 2008
Final Approval Ballot: End-Q4 2008

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

It is anticipated that a combination of email discussion, feedback on regular drafts, conference calls and face-to-face meetings will work well.

2.15 It is important to the success of the community and each JSR that the work of the Expert Group be handled in a manner which provides the community and the public with insight into the work the Expert Group is doing, and the decisions that the Expert Group has made. The Executive Committees would like to ensure Spec Leads understand the value of this transparency and ask that each JSR have an operating plan in place for how their JSR will address the involvement of the community and the public. Please provide your plan here, and refer to the Spec Lead Guide for a more detailed description and a set of example questions you may wish to answer in your plan.

The expert group will remain open for new nominations until Early Draft Review (EDR).
Interim drafts of the specification will be made available on the JSR community page. The schedule will be defined by the expert group.
Additionally the observer alias will be used, to inform interested members of the community about progress and open issues in this JSR.
The users@jsp-spec-public mailing list will be open to the public to discuss issues related to the JSP specification.

2.16 Please describe how the RI and TCK will de delivered, i.e. as part of a profile or platform edition, or stand-alone, or both. Include version information for the profile or platform in your answer.

Due to the optional package character of this request, RI and TCK will be delivered as standalone products.

2.17 Please state the rationale if previous versions are available stand-alone and you are now proposing in 2.13 to only deliver RI and TCK as part of a profile or platform edition (See sections 1.1.5 and 1.1.6 of the JCP 2 document).


2.18 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.

These are initial commercial terms to be used and remain subject to the execution of final legal agreements covering the subject matter hereof.
- The Specification will be made publicly available under two separate, royalty-free and fully paid-up licenses:-
a) A license for the purpose to analyze and use the specification for research, evaluation, and development will be available. No rights to use an implementation of the Specification for internal deployment, the creation and/or distribution of implementations of the Specification for direct or indirect commercial (including strategic) gain or advantage, the modification of the Specification (other than to the extent of the licensee's fair use rights) or the distribution of the Specification to third parties will be granted under that license.
b) A second license will be available granting rights for the creation and/or distribution of commercial implementations of the Specification in accordance with the JSPA.

RI and TCK will be licensed to all interested parties, TCK and RI will be licensed separately. For TCK we plan to introduce a single one time fee of max $50,000 and annual maintenance fee of max $20,000 for a term of three years. TCK will include both binary environment and source code of the test suite.
Maintenance fee covers limited basic support. Major new releases (esp. from new follower JSR) might be subject to additional single one time fee.
For the RI source code we will charge one time access fee, and annual maintenance fee.

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.


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


Section 4: Additional Information (Optional)

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