Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-community] Specification acronyms
Christian/all,

I have a little bit of insight from the spec committee and although I just have one Individual voice and vote on behalf of the community, I was also the longest serving Individual both in the Java EE EG (since Java EE 6) and JCP EC, part of its duties are now with the spec committee.

We still see a lot of people asking for "J2EE" experience after all those years, it won't die completely even as we approach 2020.
We should try to use the project and spec names where possible. Some like "Jakarta Messaging" still being nicknamed "JMS" probably won't be a big tragedy because if you abbreviate it, you still end up with "JMS". "Jakarta Persistence" also would not be damaged if some still called the API part "JPA", while especially in this case, the Java package already contains the name.
Others like the current "EJB" might be harder because the proposed name would twist it to "JEB" (not that anybody wants to advertise politicians here?;-) 
Some specs like CDI always had a terribly long name. There was a suggestion to cut it down to "Jakarta Contexts" but not only would abbreviating that make little sense, it would also diminish the value and scope of CDI by dropping the whole "Dependency Injection" part, while  @Inject is what many associate with it although it's only part of another smaller spec embedded underneath.  

JAX-RS was always a wrong and ill-fated acronym, the "X" if any could be related to "javax", in reality it was mostly a quick and dirty transfer of the "JAX-WS" (for XML and SOAP) into RESTful Web Services, therefore IMO here it is a house cleaning and nobody should use JAX-RS any more after the Jakarta EE name changes.

Werner




On Sat, May 25, 2019 at 5:13 PM Christian Kaltepoth <christian@xxxxxxxxxxxx> wrote:
Hi all,

I'm not sure where the best place to ask this question is, so I'm cross posting this to the community, PMC and WG lists.

I would like to kindly ask for some clarification about how to deal with the popular Java EE specification acronyms like JPA, JAX-RS, EJB, etc in the future. A few people mentioned that Jakarta EE must not use these acronyms anymore, but AFAIK there wasn't any official statement about that.
  • Mike mentioned in his blog post that some acronyms like EJB, JPA or JAX-RS need to change
  • Ivar wrote that it would be up to the spec committee to define guidelines or restrictions regarding the use of acronyms.
  • Bill noted that details about this issue are wrapped up in the negotiations between Oracle and the EF
Could anyone please provide some insights? Especially regarding these questions:
  • Can Jakarta EE continue to use the old acronyms like EJB, JAX-RS and so on? If no, which ones are forbidden? I guess the ones containing a "J" which stands for "Java"?
  • If we are not allowed to keep the old acronyms, should each project find a new acronym or should we prevent any kind of acronym like suggested by Ivar? Has there been any discussions about this so far?
Thanks a lot!

Christian


--
Christian Kaltepoth

_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-community

Back to the top