Java platforms

Question

Recently, I came across many different frameworks for creating web applications in Java, such as: Play !, Wicket, Grails, Lift and Tapestry. What is a structure and what are the advantages of using it? In addition, I would like to try one. I want a lightweight and easy-to-use platform that we started working with, since my knowledge in web development is very limited. Which one would you recommend?

I’m also sure that this question has been asked a dozen times, but it’s rather tedious to look for past questions to find the answer you are looking for.

Answer 1

Before attempting to use any infrastructure, you must first understand the basics of Servlets and JSP.

Answer 2

I believe Lift is for Scala.

Tapestry is a universal interface.

Grails is Groovy, Spring, and Hibernate is combined into a Ruby On Rails environment to quickly build CRUD web applications.

Play! and Wicket deserve the nicknames of the frame.

You do not mention Spring; you have to look at it. This is what I would recommend. This is a combination of dependency injection, aspect-oriented programming, and excellent save modules, MVC web and portal, remote transactions, declarative transactions, message POJOs and much more. He has a lot of mind and traction. It was bought by VMWare, so it will work for a while.

You will need more than a web development platform. In all cases, you cannot do web development without HTML, CSS, and JavaScript.

Answer 3

If you are looking for something quick and easy, I think play it! framework suits you. MVC architecture made it look like Ruby on Rails. Unlike the traditional Java structure, it will automatically recompile the Java source code when changes are made, so shorten the software development cycle from coding-> compilation-> testing to coding->.

Answer 4

A structure is something like a toolkit that you can use to build. The benefits of using one include saving time rather than wheel ingenuity and more. This includes frameworks written in other languages.

I assume you are good at Java, then my personal recommendation is to give Play! take a look and spend something on something, something in it before you have to try other heavyweights (if at all).

Answer 5

I will not disagree with someone who says, "Learn the basics of servlets first." As you request recommendations, add PicoContainer to the list.

Pico is similar to Spring in that it does dependency injection and supports test development, but does it in a pure (IMO) more "Java-like" way, preferring constructors and not using funny XML configuration context files such as Spring applications (usually ) (Helps reduce some of the xml errors that caused runtime errors by replacing them with preferred compilation errors for Java code.)

Another nice thing is that it is a tiny little structure that makes big attempts to avoid dozens of addictions and inflate the gang (something Spring has to take care of). The downside (of course, always) is that it is a small community. (Again, all the Spring resources located there on Google are now somewhat contaminated with information about past / different versions of this constantly evolving structure, so it’s not always better anymore.)