Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GA BLOG - Jakarta Enterprise Beans 4.0 (part of Jakarta EE 9.1) #19395

Open
tkburroughs opened this issue Nov 18, 2021 · 0 comments
Open

GA BLOG - Jakarta Enterprise Beans 4.0 (part of Jakarta EE 9.1) #19395

tkburroughs opened this issue Nov 18, 2021 · 0 comments

Comments

@tkburroughs
Copy link
Member

The information you provide here will be included in the Open Liberty GA release blog post (example), which will be published on openliberty.io/blog/, and potentially elsewhere, to promote this newly released feature/function of Open Liberty. For this post to be included in the GA issue please make sure that this is completed by the end of Friday following the GM (Wednesday).

Please provide the following information the week before the GA date (to allow for review and publishing):

  1. Which Liberty feature(s) does your update relate to?

This Open Liberty GA introduces the following Jakarta EE 9 features which now possess their all-new Jakarta EE 9 package names:

  • Jakarta Enterprise Beans 4.0 (enterpriseBeans-4.0)
  • Jakarta Enterprise Beans 4.0 Home (enterpriseBeansHome-4.0)
  • Jakarta Enterprise Beans 4.0 Lite (enterpriseBeansLite-4.0)
  • Jakarta Enterprise Beans 4.0 Persistent Timer (enterpriseBeansPersistentTimer-4.0)
  • Jakarta Enterprise Beans 4.0 Remote (enterpriseBeansRemote-4.0)
  • Jakarta Enterprise Beans 4.0 Message-Driven Beans (mdb-4.0)
  1. Who is the target persona? Who do you expect to use the update? eg application developer, operations.

application developer

  1. Write a paragraph to summarize the update, including the following points:

    This is for feature : JakartaEE 9: Jakarta Enterprise Beans 4.0 Support #11450
    And is a sub-feature of : JakartaEE: Deliver Jakarta EE 9 #9876

    Note: This is a sub-feature of the overall Jakarta EE 9.1 feature, and everything about the overall Jakarta EE 9.1 feature rollout is applicable to Jakarta Enterprise Beans 4.0 as well. So, please include this information with all other Jakarta EE 9.1 features with the following information being unique to Jakarta Enterprise Beans:

With the introduction of Jakarta EE 9.1, the Jakarta Enterprise Beans 4.0 specification includes a few minor changes over the prior version of the specification, Enterprise JavaBeans (EJB) 3.2, as follows.

  • Note the new names of the features; all of the same features exist, but the feature name prefix has changed from "ejb" to "enterpriseBeans". For example, enterpriseBeansLite-4.0 is the new version of ejbLite-3.2.

  • The API package has changed from "javax.ejb" to "jakarta.ejb"

  • The @Schedule annotation is now repeatable

  • The following API methods have been removed:

    • javax.ejb.EJBContext.getCallerIdentity() -> use getCallerPrincipal()
    • javax.ejb.EJBContext.getEnvironment() -> use JNDI lookup in java:comp/env
    • javax.ejb.EJBContext.isCallerInRole(java.security.Identity) -> use isCallerInRole(String)
    • javax.ejb.SessionContext.getMessageContext() (removed with JAX-RPC)

    All other capabilities of Enterprise Beans remain the same as the prior specification version (3.2).

What happens next?

  • Add the label for the beta you're targeting: target:YY00X-beta.
  • Make sure this blog post is linked back to the Epic for this feature/function.
  • Your paragraph will be included in the GA release blog post. It might be edited for style and consistency.
  • You will be asked to review a draft before publication.
  • If you would also like to write a standalone blog post about your update (highly recommended), raise an issue on the Open Liberty blogs repo. State in the issue that the blog post relates to a specific release so that we can ensure it is published on an appropriate date (it won't be the same day as the GA blog post).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants