 
Use of JCP site is subject to the
JCP Terms of Use and the
Oracle Privacy Policy
 |
|
 JSRs: Java Specification Requests
JSR 129: Personal Basis Profile Specification
NOTICE: Please be aware, this JSR has been replaced (superseded) by a newer JSR, (JSR 216). JSR 129 cannot be used/referenced for Java certifications. All development and certification efforts should be updated to use the current, supported technology. NOTE that this JSR was developed under JCP 2.1, but moved to JCP 2.6 in the Maintenance process. Original Java Specification Request (JSR)
Identification |
Request |
Contributions |
Additional Information
Section 1. Identification Submitting Member: Sun Microsystems, Inc. Name of Contact Person: Jonathan Courtney E-Mail Address: jonathan.courtney@sun.com Telephone Number: +1 408 276 7398 Fax Number: +1 408 276 7201 Specification Lead: Jonathan Courtney E-Mail Address: jonathan.courtney@sun.com Telephone Number: +1 408 276 7398 Fax Number: +1 408 276 7201 Initial Expert Group Membership: (Since the work of JSR 062 will depend very heavily on this Profile, we recommend that the initial EG for this JSR be composed of members of JSR 062, and the meetings held concurrently.) Espial
Section 2: Request
2.1 Please describe the proposed Specification:The J2ME Personal Basis Profile provides a J2ME application environment for network-connected devices supporting a basic level of graphical presentation.? This Profile will serve as the basis for the Profile defined by JSR 062, which has the additional requirements of full web fidelity and legacy PersonalJava application support. The J2ME Personal Basis Profile provides a profile of the JavaTM 2 Platform, Micro Edition in devices characterized as follows:
2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)Java 2 Micro Edition, CDC + Foundation Profile 2.3 What need of the Java community will be addressed by the proposed specification?Provide a standard Java 2 Micro Edition profile for devices with relatively limited resources and basic GUI facilities.? Such devices were previously served by the "minimum" PersonalJava Application Environment configuration.? It will also provide a basis on which a Profile specification that supports full PersonalJava facilities may be built. It is anticipated that the proposed Profile will be useful in markets where a basic graphical interface is required, but a full AWT support is inappropriate, e.g. interactive digital television, Java-based automobile services, information kiosks, etc. 2.4 Why isn't this need met by existing specifications?JSR 062 (Personal Profile Specification) is positioned as the migration path from the PersonalJava Application Environment (PJAE).? Therefore, JSR 062 has the explicit requirement of supporting all the features required of legacy PersonalJava applications.? To address the needs of devices that are less capable than those characterized by JSR 062, the proposed Profile will be a subset of JSR 062 appropriate to device platforms as described above. 2.5 Please give a short description of the underlying technology or technologies:See section 2.1 for expected underlying device technologies.? Specifically, the underlying graphics system will only be capable of supporting core java.awt capability, e.g. single Frame support, no direct Window creation, no heavyweight widget support, etc.? Additionally, JDK 1.1 APIs with smaller implementation footprint and core functionality will be favored over JDK 1.3 API support when considering APIs not included in the J2ME Foundation Profile. 2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)N/A 2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?Networking support is required, a hardware user interface capable of supporting basic GUI functionality and input mechanisms is required. 2.8 Are there any security issues that cannot be addressed by the current security model?None yet identified. 2.9 Are there any internationalization or localization issues?Requirements to be researched by the expert group developing this specification. 2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?The specification of JSR 062 will need to reference this Profile as the basis for its ongoing work. 2.11 Please describe the anticipated schedule for the development of this specification.Community review targeted for autumn 2001. 2.12 Please describe the anticipated working model for the Expert Group working on developing this specification.Face-to-face meetings approximately every 2 months, regular email exchange, teleconferences as needed. 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.The J2ME whitepaper provides a framework for defining the goals and scope of the specification.? JSR 062 describes superset functionality that will depend upon the Profile.? The J2ME Foundation Profile defines subset functionality on which the proposed Profile will be based. Section 4: Additional Information (Optional)
4.1 This section contains any additional information that the submitting Member wishes to include in the JSR.None |
