Change project name to Jakarta Enterprise Beans about enterprise-beans HOT 5 CLOSED

This time I do agree with @bshannon... :-) EJB is a Registered TM of Oracle and we'll have to stop using it to describe new capabilities after the technology moves to Jakarta. We can still use EJB to refer to the past Java EE EJB technology -- as long as we give it proper attribution.

To be consistent with the rest of the Specification Projects being proposed, I would prefer to go with something Jakarta Enterprise Beans.

from enterprise-beans.

Any objections to Jakarta Enterprise Beans?

from enterprise-beans.

While JEB or Jeb does seem like a nice acronym, that does pose a bit of a problem for the well established EJB acronym.... as well as the fact that the API package is javax.ejb, and many of the interfaces start with EJB, and the annotation is EJB.

However, since every other Jakarta specification will start with Jakarta, would it really be that important to have this one spec not adopt the convention, and go with Enterprise Jakarta Beans?

In the renamed version of the specification, could the introduction just indicate that it covers "enterprise beans" and for compatibility purposes, the API will refer to them as "enterprise (Jakarta) beans"? Or something like that.

from enterprise-beans.

We actually have to stop using the "EJB" acronym, so Jakarta Enterprise Beans is better.

from enterprise-beans.

Jakarta Enterprise Beans it is...

from enterprise-beans.