Jax Rs Puns

Is JAX RS still used? SHOULD I LEARN THIS or go for Spring??

I'm considering trying quarkus out in the near future. I've mainly been a spring guy but I've built rest applications with jersey.

I'm wondering if quarkus supports jersey, or if it has a different JAX-RS implementation? If there's a different implementation, I'm wondering about the availability of HK2 dependency injection for non-jersey implementations. That's because I have some re usable libraries from the aforementioned jersey work that leverage HK2 and it would be nice for them all to work seamlessly.

Thanks.

According to this:

PUT creates a new resource.
POST updates a resources’s state.

Shouldn't they have the other's significance?

Is there a mistake in this documentation, or am I missing something?

Any server that scale to the level Spring WebFlux using imperative style.

I have not been doing java backend in the last 7 years or so.

I do not want to go to graph-ql.

Also: is swagger still the shit for documenting the API?

So I was checking out this Quarkus guide and saw that they are using the Repository directly in their Resource/Controller class. They are missing the service class between the controller and the repository as is common with the Controller/Service/Repository pattern. Is it a convention to not have a service class when creating JAX-RS resources?

Hi, I am building a jax-rs rest api and I found mysql writing the same code in most of my resource classes. I have getAll(), store(), find() and destroy() methods and they all do the same thing, the only thing that changes is the model I am creating/retrieving/saving. So I was wondering how I could improve my resource classes. Shall I make an abstract class using generics and write all the logic in that class and then extend that abstract class for my other resources and put the Path annotation on? Any suggestion is appreciated.

While looking what is the difference between creating a REST Api using Jersey vs Spring Rest in Spring MVC .

I found that Jersey is an implementation of JAX-RS specification , while Spring Mvc is an alternative way of creating REST API and which is not following any specification

I wonder what would be the benefits of using one over another ? and in which situation would be suitable to use the former and not the later ?

Hi.

I'm a website developer who is using Java as back-end for my dynamic website. I've known that servlets and scriptlets (in .jsp file) existed, and I was able to reason that those are the ways to work back-end on a website w/ java.

But recently, I have learned about JAX-RS (Java API for RESTful Web Services), and with how I understand it works, I am now wondering: "What is the need for servlets when you can use JAX-RS?" Or: "What is the need for JAX-RS when you can use servlets?" So far i've only seen that they are certain scenarios where one is better than the other, but that doesn't really tell when I should be using one or the other, instead, it is just mentioning that one is used in certain cases.

So, my question is: "What is the difference between JAX-RS and servlets, and if there are any, when should I use one or the other?"

Hello, I'm very new to JAX-RS and Java as well, I'm trying to make a simple JAX-RS RESTful application.

I can see in tutorials, that the Jersey implementation is used very often.

Is is industry standard to use Jersey, or why do all tutorials make use of Jersey? Does it make sense/is it even possible to make a RESTful application without using Jersey or any other frameworks?

Also, I see in some places mentioned that you need a server for testing JAX-RS applications? How do I go about that?

I'm coding in IntelliJ IDEA EE btw

Hi All,

I am looking to integrate my Spring Boot based JAX-RS application with Swagger-UI. Any leads?

Thanks!

I am trying to add JAX-RS to my maven project that already has JPA functionalities in order to respond to database requests from the browser.

How can I add JAX-RS to the already existing project in eclipse ?

What's the difference between JAX-RS vs Java MVC vs Spring MVC (and other things under Spring)?

Learning which one will allow me to most efficiently learn how to build a data streaming dashboard?

Thank you!

Well, I have an Hibernate + Jersey stack for my first time ever using these and I'm stuck.

I use Hibernate to create tables from Entities.

I'm supposed to have an Entity on the server for data transport (DTO) and an actual object on the client side. The entity has several sub-entities. That's 2 versions of the same data and these classes need to exist in the client as well for Jersey to understand what it is, that's a total of 4 class file for the same data... It feels wrong. So how does one have the object definition in only one spot and have it's hibernate tables and dtos updated automatically ? I'm not against having DTOs and 'logic' objects separated but I don't want to duplicate these over the two projects (server & client). I tried to share the classes in Eclipse but whatever I do, either Hibernate or Jersey complains...

Want To Buy Dependency: a JAX-RS 2.1 implementation.

Seriously now, I haven't found any reasonable implementation that I can use. Currently I'm on Wildfly 10.1 and there are 0 relevant results for "Wildfly Java ee 8", "Wildfly JAX-RS 2.1", "RESTEasy JAX-RS 2.1", "RESTEasy SSE" etc.

I like new toys and I want to try out SSEs in a near-production environment. I think Glassfish 5 was released with it so can I use a Jersey dependency? Maybe some Payara alpha? Heck, even Oracle didn't update the Java EE AS page for 8.

JAX-RS first-timer here, example should be fairly simple. The getcourse should return a CourseDTO as a JSON document. Error message included. https://ideone.com/ruK4ti

Hi reddit! I made a very helpful and time-saving maven plugin that works between JAX-RS and Angular projects. Generates an Angular Module with model interfaces and rest services calls. Pleased to share. Link: https://github.com/NahuelOlgiati/jaxrs-angular-maven-plugin

JavaOne 2016

This session provides 50 best practices for Java EE 7, with examples. The best practices covered focus primarily on JPA, CDI, JAX-WS, and JAX-RS. In addition, topics involving testing and deployment are covered. This presentation points out where best practices have changed, common misconceptions, and antipatterns that should be avoided. This is a fast-paced presentation with many code samples.

See Top 50 Java EE 7 best practices

Hi, I am building a jax-rs rest api and I found mysql writing the same code in most of my resource classes. I have getAll(), store(), find() and destroy() methods and they all do the same thing, the only thing that changes is the model I am creating/retrieving/saving. So I was wondering how I could improve my resource classes. Shall I make an abstract class using generics and write all the logic in that class and then extend that abstract class for my other resources and put the Path annotation on? Any suggestion is appreciated.

Hi.

I'm a website developer who is using Java as back-end for my dynamic website. I've known that servlets and scriptlets (in .jsp file) existed, and I was able to reason that those are the ways to work back-end on a website w/ java.

But recently, I have learned about JAX-RS (Java API for RESTful Web Services), and with how I understand it works, I am now wondering: "What is the need for servlets when you can use JAX-RS?" Or: "What is the need for JAX-RS when you can use servlets?" So far i've only seen that they are certain scenarios where one is better than the other, but that doesn't really tell when I should be using one or the other, instead, it is just mentioning that one is used in certain cases.

So, my question is: "What is the difference between JAX-RS and servlets, and if there are any, when should I use one or the other?"