Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
Jersey and RESTEasy are popular JAX-RS implementations. There are other Rest Webservice implemenations such as Restlet.
I want to know which one to use when? what is the most used implementation nowadays in web application developments.
I'd go for Spring MVC version of REST, it suppports Dependancy Inversion(DI), Also spring supports many pluggable features like support for freemarker template, jaxb, xmlbeans etc., you will have plenty of options on return data.
Also, i wouldn't disagree on using jersey or resteasy, they are very lightweight compared to spring. If you don't want to use spring, then either one of the above mentioned should work as well, there are no major pros and cons.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 11 months ago.
Improve this question
I need to use Kafka in my spring-boot application and I see spring-boot has its own spring-kafka library. I am new to spring and java and confused if I should be using spring-kafka or any other application's spring-based lib rather than using the core libraries and what are the benefits of either one of them.
Spring boot with Kafka comes with various autoconfiguration out-of-the-box to save you from the trouble of configuring each and everything (though you can definitely override spring-boot opinionated autoconfiguration).
So, if you want a ready-made application to work quickly, you can take the help of spring-boot and its utilities.
If your preference is configuring each and everything to gain fine control, use core libraries.
I'd say it's just a matter of choice or preference.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
We have a pretty large codebase developed on Spring Boot and over the course of time, we have kept adding starters as required. I am going through a bit of housekeeping and have noticed that there are quite a bit of overlap in the dependencies provided by the starters. For eg. for creating a REST API, we started out with the spring-boot-starter-web and later added spring-boot-starter-data-rest. But I just noticed that spring-boot-starter-web is a direct dependency of spring-boot-starter-data-rest.
Now I know that as a best practice, if my code is using a library directly, that library should always be a direct dependency instead of relying on another library depending on it. But Spring Boot starters are just a BOM so I am wondering if there is a better practice here.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I am new bee to spring. I am trying to build an application using JSP and Hibernate with Spring. Is it a good practice to use jsp, servlets and use spring to declare the database connectivity and beans in xml or should i use spring mvc please guide me.
You can use whatever part you need from spring. That is one of the best thing about springframework. If you need to use spring just for data access layer then that is fine use it just for that. If you will use it dependency injection frawework for your project then you can use it that way.
Spring MVC is just a presentation layer part of spring. I have been using springframework for last 12 years and I haven't used SpringMVC until last year. So I recommend you to use what you know best for presentation layer but I also strongly recommend using spring for back-end layer.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
there seems to be many ways to access a REST web service. but different documentation out there states they all have problems and now i am confused what to use.
Here are our options:
HTTPClient - from apache, but deprecated. However Apache does provide some alternative
HttpURLConnection - has bugs in it.
AndroidHttpClient - includes the workaround for a major bug in HttpURLConnection
I really don’t know which one to use from the list above. Is there one which I am missing that I should be using
to access a REST web service ?
Ideally, to access a REST Web service, you use a higher-level library, like Retrofit, that handles more of the work for you.
Otherwise, Google's official recommendation is to use HttpURLConnection.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
( trying rewording as per suggestions )
I would like to know which of the two would be less learning curve for writing RESTful web services? ( for someone who dont know both)
I really don't need web MVC .
I would like easy mapping from URL to java function, JSON/XML output options, avoid malicious input from user, translation support for strings etc and low latency for response with data coming from MySQL.
I am looking for the simplicity too.
Thanks in advance!!
For simplicity, use Java EE 6+. You can start RESTful programming using JAX-RS API (javax.ws.rs) without any need to set up Jersey or Spring.
Jersey:
Pros: Standard API (JAX-RS)
Cons: MVC support is less richer than Spring MVC.
Spring:
Pros: Many features, many documents, active community.
Cons: Many rules to learn.