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.
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 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 8 years ago.
Improve this question
We are currently developing an enterprise web application (Java backend + HTML/JS frontend). This application shall provide cloud-based data analysis functionality to a variety of users. Now, we have decided to use AngularJS for creating the web-frontend. The communication to the backend is realized with REST webservices (implemented in java using jersey, and jetty as webserver).
Some time ago, I have already developed simple java web apps using apache wicket just for examplary reasons. Since I am new to AngularJS, I am wondering if there is any reason why it could still be necessary for us to use a java web-framework (such as wicket, gwt, etc.) additionally to Angular JS?
The other way around: since we use Angular for developing the web-frontend, we do not need any web-framework on the java side any more, right?
I am quite new to java web applications, so any help would really be appreciated :-)
Regards
AngularJS has the $http service which should be able to handle all your GET/POST requests that you need to make to your Java backend. The docs for it are here:
https://docs.angularjs.org/api/ng/service/$http
As long your return data is properly formatted JSON or whichever format you want, Javascript should read it just fine. AngularJS should be fine for your project.
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.
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
I like the way JAX-RS represent URLs.. and find it very easy to be used.
I am thinking of making the JAX-RS works instead of my Servlets, so I can write some JSPs that interact directly with these RESTful resources ...
What do you think?
It's not a decision about your model programming, is a decision about architecture and requirements of your application.
My first experience with JAX-RS was very positive. I used the framework to provide some server side functionality to a desktop app. But I wouldn't see the value of using REST if you are creating a traditional Web app where each client action results in a new Web page getting loaded by the user's browser. If you are building an AJAX app, then I can see how REST might be cleaner to code than Servlet.
What is the nature of the project?
Actually it doesn't matter servlets or even use PHP/HTML front end as you JAX-RS use HTTP request. I would suggest you to use JAX-RS reference implementation for building RESTful Web services call jersey. It provide more goodies ..
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 know this question is subjective but I would really want to know what are the best j2ee web application auto code generators.
I googled and found out the Appfuse is one of them.
Spring ROO is another but it depends on spring i think.
Are there any other better tools?
Basically lot of time is spent on creating regular CRUD screens with the same mundane things for each screen.
So, I would want to reduce the time spent on such simple CRUD screens so that I can focus more on the core application logic.
We use Telosys (http://www.telosys.org/) to generate repetitive code like CRUD screens.
A set of templates are available for Spring MVC, JPA, AngularJS, etc.
We have customized some of them. It saves of lot of time.
The best solution I have seen so far is Grails. It generates groovy code, not java but you can interface painlessly with any java library/class. The convention over configuration features are amazing and one can put up a functioning web app in minutes. I suggest you see for yourself - just try the grails screencasts. They will get you up to speed in 15 minutes.The technologies used under the hood are best-of-breed : spring, hibernate, lucene, quartz, sitemesh etc.