Which Java-based MVC framework is most similar to ASP.NET MVC?

Question

I have been studying ASP.NET MVC over the past few months, and I think this is a great improvement over ASP.NET. Personally, it’s very pleasant for me to use (unlike ASP.NET WebForms :)), I began to wonder how the .NET world could live so long without such a structure (at least, not widespread and supported by Microsoft as it may be. NET ports of Java MVC frameworks, e.g. Spring.NET).

I know that people with Java have had such frameworks for a long time, and there are many features of Java MVC.

If a web developer was thinking about switching from Java to .NET, which Java infrastructure is the easiest to switch from, and vice versa, if an ASP.NET MVC developer thinks about expanding his skillset and learning Java MVC (web), which would be the most similar to the ASP.NET MVC architecture - and functionally?

Which Java MVC structure is most similar to ASP.NET MVC?

Answer 1

SpringMVC, VRaptor, Grails (not Java, but somewhat relevant for the Java world)

Answer 2

Play Framework seems to me. It has controllers as classes, actions as methods, a Razor-like mechanism for viewing, binding objects, and almost everything looks the same.

Even routing seems pretty much the same.

Answer 3

Wikipedia has a list of heaps of frameworks:

http://en.wikipedia.org/wiki/Comparison_of_web_application_frameworks

and those based on Java technology, about half of them are component based (which you don't need), and the other half are MVC. If you are interested, you can follow the links to some of them for more information.

In general

• the more mature ones will have more detailed entries - both on Wikipedia and in the wild. There will also be more documentation, sample code, tutorials, ...

• The younger ones can be simpler, more fun, more universal, since they are based on the old ones, eliminate known shortcomings and add new features. For example, JSF and Struts are “big” in the industry, but many developers (I think I know) are considered dated, clumsy, bloated, etc.

You will probably have a problem getting a response from people with enough experience to directly compare products on the .Net and Java side; most developers tend to stay on one side of this fence.

Until I understand the similarities with ASP.Net, I argue that Struts and JSF are Java industry workhorses, and this will be useful for your resume, although or maybe because they are not modern or sexy. Of these two, I think Struts has more MVC.

Answer 4

If I were looking for the simplest framework, I would dive into Struts. Struts 1.0 was written in one day, and is arguably the most valuable hourly watch effort ever made by a programmer.

If I wanted to expand my knowledge and / or skills, I could lean towards Spring MVC. If you need certain functionality for Java web development, other people's chances require it too, and that Spring already has it. (Spring is more than just Spring MVC, you can just use Spring MVC, but it goes well with a lot more if you choose.)

Answer 5

Apache Struts :

Apache Struts is a free, open source environment for building Java web applications.

Web applications differ from regular websites in that web applications can create a dynamic response. Many websites provide only static pages. The web application can interact with databases and business logic mechanisms to customize the response.

JavaServer Pages-based web applications sometimes combine database code, page design code, and control flow code. In practice, we find that if these problems are not separated, larger applications become difficult to maintain.

One way to share problems in a software application is to use the Model-View-Controller (MVC) architecture. A model is a business code or database code, a view is a page design code, and a controller is a navigation code. The Struts framework is designed to help developers create web applications using the MVC architecture.

The structure contains three key components:

• The "request" handler provided by the application developer that maps to the standard URI.
• A response handler that transfers control to another resource that completes the response.
• A tag library that helps developers create interactive application forms with server pages.

The architecture and frame labels match the style requirements. Struts works well with regular REST applications and with innovative technologies such as SOAP and AJAX.