Skip to main content
  • Log in
  • Manage Cookies
Eclipse Foundation
Download
  • Projects
  • Working Groups
  • Members
  • Community
    • Marketplace
    • Events
    • Planet Eclipse
    • Newsletter
    • Videos
    • Blogs
  • Participate
    • Report a Bug
    • Forums
    • Mailing Lists
    • Wiki
    • IRC
    • Research
  • Eclipse IDE
    • Download
    • Learn More
    • Documentation
    • Getting Started / Support
    • How to Contribute
    • IDE and Tools
    • Newcomer Forum
  • More
      • Community

      • Marketplace
      • Events
      • Planet Eclipse
      • Newsletter
      • Videos
      • Blogs
      • Participate

      • Report a Bug
      • Forums
      • Mailing Lists
      • Wiki
      • IRC
      • Research
      • Eclipse IDE

      • Download
      • Learn More
      • Documentation
      • Getting Started / Support
      • How to Contribute
      • IDE and Tools
      • Newcomer Forum
    • Search

  1. Home
  2. Blogs
  3. Ivar Grimstad's blog
  4. Jakarta EE Compatible Explained

Jakarta EE Compatible Explained

Thursday, February 16, 2023 - 16:58 by Ivar Grimstad

You have probably heard the term Compatible being used in the context of Jakarta EE What does it actually mean? And what is the difference between a Jakarta EE Compatible Product and a Jakarta EE Compatible Implementation? Before we dive into explaining those terms, let’s first look at the parts a specification is made up of.

The Specification Document describes the specification in textual form. Some specifications may not have a physical document but have everything described in the JavaDoc of the API component.

The API, or Application Programming Interface, is not considered a normative artifact. That means that an implementation can reproduce the API as long as the signature of the API is identical

The Technology Compatibility Kit (TCK) defines how to test that an implementation fulfills all the requirements in order to implement the specification.

At least one Open Source(*) implementation that passes the TCK is required in order for a specification to be made final.

(*) The approved Open Source licenses for ratifying compatible implementations are EPL-2.0, BSD-3-Clause, and Apache-2.0

Compatible Implementation

An implementation of a Jakarta specification is considered to be a Compatible Implementation when it can demonstrate that it fulfills all the requirements of the Technology Compatibility Kit (TCK) for that particular specification. For example, Hibernate Validator 7.0 and Hibernate Validator 8.0 are both compatible implementations of Jakarta Bean Validation 3.0. Hibernate Validator 7.0 were used as ratifying compatible implementation when Jakarta Bean Validation 3.0 was released and is therefore listed on the Jakarta Bean Validation 3.0 specification page.

Compatible Product

A Compatible Product is a Compatible Implementation of the Jakarta EE Platform, Jakarta EE Web Profile, or Jakarta EE Core Profile. In addition to fulfilling the requirements of the Jakarta EE Platform, Jakarta EE Web Profile, or Jakarta EE Core Profile TCKs, the implementor must participate in the Jakarta EE Compatibility Program to be listed on the Jakarta EE Compatible Products page.

The Jakarta EE compatible logo can only be used by those that have implemented a Jakarta EE Compatible Product as well as fulfill the requirements of the Jakarta EE Compatibility Program.

Tags: 
EclipseFoundation
Jakarta EE
Eclipse Foundation
Source: 
https://www.agilejava.eu/2023/02/16/jakarta-ee-compatible-explained/
  • Ivar Grimstad's blog

Eclipse Foundation Blogs

  • Wayne Beaton (821 posts)
  • Mike Milinkovich (322 posts)
  • Ivar Grimstad (254 posts)
  • Benjamin Cabé (131 posts)
  • Tanja Obradovic (60 posts)
  • Thabang Mashologu (37 posts)
  • John Kellerman (31 posts)
  • Paul Buck (22 posts)
  • Brian King (19 posts)
  • Frédéric Desbiens (19 posts)
  • Mikaël Barbero (17 posts)
  • Christopher Guindon (16 posts)
  • Gael Blondelle (14 posts)
  • Hailley Seed (10 posts)
  • Denis Roy (9 posts)
  • Hudson Kelly (8 posts)
  • Michael Plagge (4 posts)
  • Serina El Salibi (3 posts)
  • Shabnam Mayel (3 posts)
  • Shanda Giacomoni (3 posts)
  • Jacob Harris (2 posts)
  • Clark Roundy (2 posts)
  • Karla Ferrer (2 posts)
  • Paul White (1 posts)
  • Stephanie Swart (1 posts)
  • Sharon Corbett (1 posts)

Recent blog posts

  • Organising Your Eclipse Open Source Project Team
  • Hashtag Jakarta EE #168
  • New SLSA++ Survey Reveals Real-World Developer Approaches to Software Supply Chain Security
  • Take the 2023 Jakarta EE Developer Survey
  • Hashtag Jakarta EE #167
  • Product Liability Directive: More Bad News for Open Source
  • Rodrigo Pinto: Eclipse Cloud DevTools Contributor of the Month!
  • Hashtag Jakarta EE #166
  • March 2023 Update on Security improvements at the Eclipse Foundation
  • Eclipse Cloud DevTools Digest - January and February, 2023
More

Eclipse Foundation

  • About Us
  • Contact Us
  • Sponsor
  • Members
  • Governance
  • Code of Conduct
  • Logo and Artwork
  • Board of Directors
  • Careers

Legal

  • Privacy Policy
  • Terms of Use
  • Copyright Agent
  • Eclipse Public License
  • Legal Resources

Useful Links

  • Report a Bug
  • Documentation
  • How to Contribute
  • Mailing Lists
  • Forums
  • Marketplace

Other

  • IDE and Tools
  • Projects
  • Working Groups
  • Research@Eclipse
  • Report a Vulnerability
  • Service Status

Copyright © Eclipse Foundation. All Rights Reserved.

Back to the top