JBoss has submitted JSR-298, Web Beans API for Java ME to the Java Community Process (JCP). According to the JSR, "The goal of this work is to enable EJB 3.0 components to be used as JSF managed beans, unifying the two component models and enabling a considerable simplification to the programming model for web-based applications in Java." It continues:
Aspects that should be considered in this work include, but are not limited to, the following:
- Definition of additional capabilities to be used with the EJB component model, allowing EJB beans to act as JSF managed beans in a JavaServer Faces application. This is in principle possible without requiring any changes to the EJB or JSF specifications. However, where appropriate, new features could be incorporated into the EJB specification or JSF specification at the discretion of the respective expert groups.
- Definition of a unified annotation-based facility for manipulating contextual variables in a stateful, contextual, component-base architecture. * Definition of an enhanced context model including conversational and business process contexts.
- Definition of an extension point allowing integration of business process management engines with the contextual component model.
- Integration of Java Persistence API extended persistence contexts with the enhanced context model.
- Collaboration with the JSF and Common Annotations for the Java Platform expert groups on the definition of Java annotation based metadata for JSF.
- Ensure that components written to conform to this specification may be executed in the context of a Web Services invocation.
- Ensure that the component model can be used with JSR-227 databinding.
The goal of the Expert Group will be to investigate these issues and identify and pursue other directions that allow a simplification of the overall programming model, while leaving issues relevant only to the EJB specification or only to the JSF specification to the respective Expert Groups.
Comments are due by June 5.
SK Telecom Co., Ltd. has submitted JSR-298, Telematics API for Java ME to the Java Community Process (JCP). According to the JSR,
This JSR is designed to provide a standard API set to control the car devices and diagnose status of the car on the current and the next generation of embedded devices. The API set, for car device control and diagnosis, aims for collecting information of car status and controlling the car devices to support telematics services.
One of the core functionalities to enable telematics service is to control and monitor the car devices through the communication protocol provided by the internal car network such as TCP/IP, CAN, MOST, GPIO, and DIO. Based on this control/monitor functionality, operators and manufacturers can provide various services to car owners or drivers equipped with embedded devices such as handsets or built-in telematics terminals. So the goal of this JSR is to provide a standard API set to control and diagnose car devices with close streamline with J2ME technology.
The proposed JSR API will support:
- Car device control: doors, mirrors, seats, engine, audio, lights, and etc.
- Car status monitor: airbag, engine, car diagnostic module
- Car network protocol manipulation: CAN, MOST, GPIO, DIO, and etc.
The target devices will be J2ME-enabled embedded devices, with connection to the car control network through wire or wireless radio such as Bluetooth or RFID. So, the devices with this JSR can be viewed as a service interface between service provider and the car.
This JSR may have optional API sets dedicated for before-market telematics devices in order to provide more detailed control over car devices including AV unit and proprietary car diagnostics modules. Based on the proposed JSR, the various actors of Telematics including service operators, embedded device vendors, automotive manufacturers, and application/solution developers can find a stable and standard way to build the Telematics services modules.
Comments are due by June 5.