At this time, I believe we can begin a Public Review in June or July. The EG will continue to meet weekly until the Public Review has begun. We are currently using Zoom for our EG meetings.

Please let the Spec Lead know if you have additional questions.

JSR-302 has taken much more time to produce than expected, but it is now essentially complete. This effort began in mid-2006, so it has taken 14 years of continuous effort. There are many reasons for the delay, but an examination of our history is not the purpose of this document.

However, it is appropriate to consider whether the original goals of this JSR continue to be relevant in 2020 as we prepare to submit our specification for Public Review. The goal of this JSR was stated in its original request:

“The proposed specification will define those capabilities needed to use Java technology to create safety critical applications. This means that the features included will be a minimal set, with such specific characteristics as static resource allocation and usage, minimal temporal conflicts, and without dynamic loading, leading to the ability to validate implementations using a variety of standards, including DO-178B / ED-12B. It is further implied that the features chosen can be validated using formal models, schedulability analysis, and modified condition/decision coverage (MC/DC) analysis.”

“It is strongly intended that this specification will incorporate the existing Java technology paradigm maximally, subject to the need for application validation. For example, it must be possible to create applications with fully predetermined resource allocation as required by most safety critical standards. This implies, for example, that a garbage collector might not be usable under such standards, and that it might be inappropriate for components to be dynamically loaded. Such applications will likely require a transformation from Java bytecodes to target machine representation prior to certification.”