Eclipse Community platvormi , which replaces Java EE (Java Platform, Enterprise Edition) after the transfer of the specification development processes, TCK and reference implementation to the non-profit organization Eclipse Foundation. Jakarta EE 8 offers the same set of specifications and TCK tests as Java EE 8. The differences are limited to a name change and a shift to new specification development processes. The platform was released under a new name because Oracle only transferred the technologies and project management, but did not transfer the rights to use the Java trademark to the Eclipse community. The overall project for the development of Jakarta EE is called EE4J (Eclipse Enterprise for Java).
The release signals the completion of building the infrastructure and establishing processes for the development of specifications for the server-side Java platform on a neutral ground, independent of specific vendors and allowing for transparent and open decision-making processes, development and certification. Compatibility assessment kits TCK (Technology Compatibility Kits), provided under the Eclipse TCK license, are proposed for the certification of products compatible with Jakarta EE.
Jakarta EE 8 serves as a starting point for creating new specifications, in the preparation of which various vendors will participate. Plans for further specification expansion include the development of business application development tools for cloud computing (). Changes prepared in the course of collaborative work will be proposed for the next release of Jakarta EE 9, with major innovations including the Jakarta NoSQL specification and a change to the namespace.
Jakarta NoSQL will define standard high-level interfaces for interaction between Java applications and NoSQL databases, which is a significant step in preparing the Java platform for using the Cloud Native paradigm. The framework will be used as a reference implementation. The change in the namespace is due to the inability to use the names java and javax in the new functionality of Jakarta EE, hence the transition to the new namespace 'jakarta.*'
As for decision-making, the new process of (JESP), mida Jakarta EE Working Group kasutab Jakarta EE arendamiseks. JESP pÔhineb Eclipse'i kogukonnas aktsepteeritud avatud spetsifikatsioonide ettevalmistamise pÔhimÔtetel EFSP (Eclipse Foundation Specification Process). Jakarta EE spetsifikatsioonides tehtud muudatuste kinnitamiseks vÔi uue versiooni koostamiseks on vajalik kÔikide strateegiliste liikmete absoluutne enamus, lisaks kÔikidele teistele hÀÀletusmÀÀrustele, mis on mÀÀratletud EFSP-s.
Allikas: opennet.ru
