Re: [jaxrs-dev] [External] : Re: Jakarta REST 3.1.0

[Jim Krueger <jckofbyron@xxxxxxxxx>]

Yes, given Argan's response, I agree with you Markus. I retrack my earlier statement.  Jakarta Rest will work just fine and there is no point in pursuing this further.

On Sat, May 7, 2022, 4:12 AM Markus Karg <markus@xxxxxxxxxxxxxxx> wrote:

I actually would not love to open this can of worms again.

Jakarta REST seems fine for most, and nobody ever complained that using JAX-RS alternatively did actively bother or confuse him.

-Markus

 

 

Von: jaxrs-dev [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] Im Auftrag von arjan tijms
Gesendet: Dienstag, 3. Mai 2022 21:51
An: jaxrs developer discussions
Betreff: Re: [jaxrs-dev] [External] : Re: Jakarta REST 3.1.0

 

Hi,

 

On Tue, May 3, 2022 at 5:41 PM Jim Krueger <jckofbyron@xxxxxxxxx> wrote:

But I think a short name (like JAX-RS was) needs to flow easily in speech and be at least relatively ubiquitous).  I don’t know if "Jakarta REST" meets this criteria

 

One of the key arguments was to use preferably a single word, so abbreviations and the duplication from short names are avoided.

 

E.g.

 

Jakarta Concurrency

Jakarta Transactions

Jakarta Messaging

Jakarta Security

 

Etc.

 

That way nobody will feel the need to refer to Concurrency as C, or to Transactions as T. As mentioned earlier, the pervasive use of abbreviations is what made Java EE so hard to get into for people.

 

With the current naming for most of the specs we're almost there. Bean Validation should probably become just Validation (so people won't feel the need to write "bv"). And Jakarta REST is still on the TODO list, but we can rename everything to Jakarta REST as long as it doesn't require a PR.

 

Kind regards,

Arjan Tijms

 

 

 

 

_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jaxrs-dev