 
Use of JCP site is subject to the
JCP Terms of Use and the
Oracle Privacy Policy
 |
|
 JSRs: Java Specification Requests
JSR 213: Micro WSCI Framework for J2ME.
Reason: This JSR was not approved by the ME Executive Committee in the JSR Approval Ballot. JCP version in use: 2.5 Java Specification Participation Agreement version in use: 2.0 Description: Effort to define another layer of the J2ME Web Service stack, implementing the 'observable' behavior of a choreographed Web Service on the Device, relative to the message exchange requiring support. Please direct comments on this JSR to the Spec Lead(s) Team
This JSR has been Rejected
Identification |
Request |
Contributions
Original Summary: To be part of a useful and manageable Web Service collaboration on J2ME Devices, individual operations must be allowed to convey enough information about how they can be used in a given scenario in order to enable them to participate in more complex processes. Micro WSCI achieves this by defining a layer on top of the existing J2ME Web Service stack. This layer implements the required 'observable' behavior of a choreographed Web Service on the J2ME Device, relative to the message exchange it must support. Section 1. Identification Submitting Member: Iopsis Software, Inc. Name of Contact Person: Ash Parikh E-Mail Address: ash@iopsis.com Telephone Number: +1 650 358 2522 Fax Number: +1 650 358 0403 Specification Lead: Ash Parikh E-Mail Address: ash@iopsis.com Telephone Number: +1 650 358 2522 Fax Number: +1 650 358 0403 Initial Expert Group Membership: . Supporting this JSR: Section 2: Request
2.1 Please describe the proposed Specification:Micro WSCI is a framework that will reside on the J2ME Device, and will act as a lightweight co-ordinator for choregraphed Web services. Enabling the J2ME Device client for choreographed Web services will empower true P2P collaborations and interactions for complex processes, initiated by the client.
The key features of the Micro WSCI Framework will be: 2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)THE JSR IS TARGETED TO BOTH CLDC/MID-P AND CDC/PERSONALJAVA STACKS. 2.3 What need of the Java community will be addressed by the proposed specification?There exists a need for enabling J2ME Devices to process true P2P collaborations and choreograph Web services. 2.4 Why isn't this need met by existing specifications?The current WSCI Specification from W3C does not target the lightweight client or J2ME platform. 2.5 Please give a short description of the underlying technology or technologies:See 2.1 2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)To be determined. 2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?No 2.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.HERE IS THE TENTATIVE SCHEDULE (WILL BE FORMALIZED LATER): 2.12 Please describe the anticipated working model for the Expert Group working on developing this specification.The expert group members will determine the nature of the working model. It is anticipated that a mixture of email discussion, feedback on regular drafts and face to face meetings will work well. 2.13 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.It is expected that the specification leader will have responsibilities associated with group leadership, including group communications, decision making, and agreeing to the business terms for the Reference Implementation (RI) and Technical Compatibility Kit (TCK). Exact details will be agreed on early in the life of this specification and communicated to expert group members. The RI and TCK will be managed by Iopsis Software. 2.14 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).Iopsis will deliver a standalone reference implementation (RI) and Technology Compatibility Kit (TCK) for Java Process Definition. 2.15 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.Iopsis will license the specification, RI and TCK to all interested parties on a royalty free basis. 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.Web Service Choreography Interface (WSCI) 1.0( http://www.w3.org/TR/wsci/#TOC1.3) 3.2 Explanation of how these items might be used as a starting point for the work.N/A |
|||||||||||||||||||||||||||||||||||||
