Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jaxrs-dev] Jersey the only implemention of jax-rs ?
Hi Zahid,

The list of Jakarta EE specifications is available here: https://jakarta.ee/specifications/. As has already been discussed here, there are a number of implementations for most of these - for example Jersey, RESTEasy and CXF all implement JAX-RS, and Hibernate, EclipseLink and OpenJPA implement JPA. I appreciate that potentially gives you a number of different implementations to evaluate across the specifications that you're consuming (not 1800 though - the website you link to is for example data models). If each specification only had one implementation, it could be argued that it isn't really a specification - just a library. There are a number of Jakarta EE compatible servers: https://jakarta.ee/compatibility/, and this is in-part down to the availability of a number of different implementations for the various specifications.

From a developer perspective, you shouldn't need to know the deep details of each implementation - just the specification should be enough. If you're developing to the specification, you should be able to move from one implementation to another without too much difficulty.

Hope that helps.

Jon

On Mon, Nov 1, 2021 at 9:56 AM Zahid Rahman <zahidr1000@xxxxxxxxx> wrote:

On Mon, 1 Nov 2021, 09:04 Markus Karg, <markus@xxxxxxxxxxxxxxx> wrote:
In a free world every vendor is free to produce his own product implementing the same spec, optimized for different kinds of workloads or use cases, so you as a consumer of that products are free to pick that implementation that works best in your particular use case. That is what is achieved. The repository does not hold 1800 specifications for a single real life application, but just a few. Even full Jakarta EE does not include 1800. This number is totally wrong.
-Markus


-----Ursprüngliche Nachricht-----
Von: jaxrs-dev [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] Im Auftrag von Zahid Rahman
Gesendet: Montag, 1. November 2021 04:10
An: jaxrs developer discussions
Betreff: Re: [jaxrs-dev] Jersey the only implemention of jax-rs ?

Thanks Markus.

I can't see what is to be achieved
part from confusing application developers  with so many  API
implementations  from a single  specification

when I have a repository of 1800  specifications  for building real
life applications.   :)


https://www.backbutton.org
¯\_(ツ)_/¯
♡۶♡ ۶♡۶

On Sun, 31 Oct 2021 at 07:55, Markus Karg <markus@xxxxxxxxxxxxxxx> wrote:
>
> Besides Jersey there are several other implementations, CXF and RESTeasy for example.
> -Markus
>
>
> -----Ursprüngliche Nachricht-----
> Von: jaxrs-dev [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] Im Auftrag von Zahid Rahman
> Gesendet: Sonntag, 31. Oktober 2021 07:05
> An: jaxrs developer discussions
> Betreff: [jaxrs-dev] Jersey the only implemention of jax-rs ?
>
> Hi,
>
> Background:
> I learned from this article
> https://www.infoworld.com/article/3373652/java-persistence-with-jpa-and-hibernate-part-1-entities-and-relationships.html
>
> JPA is a specification with at least three different  implementations.
> Hibernate.io, eclipse EclipseLink and apache mybatis are three
> implementations of  JPA. (Maybe more)
>
> I further learned  from this page
> https://blog.payara.fish/whats-payara-server-made-of
> Jersey is an implementation of JAX-RS.
> Payara author also states on the  same page EclipseLink implementation
> of JPA is used by payara.
> Therefore if for example I was interested in using payara then I
> should focus on EclipseLink API syntax.
>
> If I have an interest in the microservices paradigm , more precisely
> Eclipse microprofile.io flavour of microservices paradigm.
> microprofile.io and its vendors using microprofile  mention jax-rs  as
> the base API.
>
> I know that jax-rs is a specification and jersey is its implementation
> , so  I to know if I wish to use jersey, I should  focus
> on these usage product documentation
> https://eclipse-ee4j.github.io/jersey.github.io/documentation/latest3x/index.html.
>
> I am seeking clarity ;
> Is jersey the only implementation of jax-rs therefore  these usage
> https://eclipse-ee4j.github.io/jersey.github.io/documentation/latest3x/index.html
> documentation  will apply to all microprofile application servers  ?
> or
> are there any other implementations apart from jersey of jax-rs based
> microprofile  implementation  of the microservices paradigm ?
>
>
> Regards
>
> Zahid
>
>
>
> https://www.backbutton.org
> ¯\_(ツ)_/¯
> ♡۶♡ ۶♡۶
> _______________________________________________
> jaxrs-dev mailing list
> jaxrs-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jaxrs-dev
>
> _______________________________________________
> jaxrs-dev mailing list
> jaxrs-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jaxrs-dev
_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jaxrs-dev

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


--
Jonathan Gallimore

Back to the top