Request to Payara Team: please distinguish between EE4J (am implementation projec ) and Jakarta EE or Enterprise Profile (the new specification name)

[Darren Kelly]

To the Payara Team,

You recently circulated an email (by Dominika Tasarz-Sochacka, Head of Marketing & Community Building at Payara), advertising this seminar:

"What's in store for EE4J, MicroProfile & Payara Server" Thursday, March 1, 2018, 4 p.m

(I will sadly probably miss the event because of other commitments.)

In the description of the event it states:

 'EE4J – the migration of Java EE from the JCP to the Eclipse Foundation.'

This is NOT correct, and it is typical of the at-times frustratingly Eclipse-centric eclipse community (with no reflection on the Payara team).

The new SPECIFICATION and TECHNOLOGY name is being decided by a vote open until 23 Feb 2018 (tomorrow), between:

- Jakarta EE (my preference, likely to become known as JEE).

- Enterprise Profile

Conflating EE4J, the Eclipse-specific implementation with the entrerprise-technology specification is not helpful,
and can lead to the misconception that the Eclipse-specific efforts are somehow "standard".

(For what it's worth, I was never in favour of Java EE going to the Eclipse Foundation, I would have far preferred the Apache Foundation.)

Please do (and once the vote is in) take the trouble in your forum postings, newsletters, documentation, and seminars, to distinguish between the Eclipse-specific EE4J implementation aspects and the wider "Enterprise Java" (to be newly named) community effort.

Eclipse does not eclipse everything. I have used the Eclipse IDE, EMF, and other Eclipse technologies a lot professionally. I also use NetBeans IDE and Apache technlogies a lot. When I work with Eclipse I become truly annoyed at how Eclipse-centric their documentation is. I once worked with a colleague who simply could not understand that the Unified Modeling Language (UML) is a technology from the Object Management Group (OMG), he kept confusing it with the UML2 project within the Eclipse Community. Not the fault of Eclipse of course, but not surprising given the Eclipse-centric way their documentation is often written.

Payara is a wonderful technology product, and you have super team; good luck in the new world of Jakarta EE or the Enterprise Profile !

Darren Kelly, Webel IT Australia

PS: You are going to need a new tag: Jakarta EE or Enterprise Profile

[Darren Kelly]

Related links: VOTE NOW !

https://www.infoworld.com/article/3254191/java/vote-now-for-enterprise-javas-new-name.html

https://jaxenter.com/ee-next-brand-name-vote-now-141217.html

[Mike Croft]

Hi Darren,

For the moment, we use EE4J both because we don't have a decision between the new names and also because EE4J is the name of the project within Eclipse, and that is what we will be talking about as well. For example, I would say that one of the things in store for EE4J is the move of Java EE to the Eclipse foundation. There are other things that relate to EE4J that we will probably cover too, like the change in management structure when going from the JCP to Eclipse, how working groups are formed and how the new Java EE will be developed going forward, perhaps with reference to things like MVC 1.0 or JMS 2.1. If we didn't say EE4J, then these two specs would not be included, since they are not Java EE.

As you may already know, Steve is on the PMC for EE4J, so that's where we'll be approaching things from.

I'm like you though - very hopeful for the Jakarta EE name and eager to start using it! I'm sure once the final announcement of the vote results is made, then it will become easier to be clear in communication!

Mike

[Darren Kelly]

@Mike Croft

On Thursday, February 22, 2018 at 9:28:51 PM UTC+11, Mike Croft wrote:

I'm sure once the final announcement of the vote results is made, then it will become easier to be clear in communication!

Thanks for your thoughtful clarifying reply.

Onwards with TAFKAEJ (The Architecture Formerly Known as Enterprise Java)

[Mike Croft]

Thanks Darren. I've updated the tags for this post accordingly ;-)