Wednesday Sep 10, 2014

Why Another MVC?

In this new article, JavaServer Faces (JSF) spec lead Ed Burns explains two kinds of model view controller (MVC) as part of the JSF framework. The article's goal is to show the continued commitment to JSF evolution and to clarify the complementary usages of these two view technologies.


The two kinds of MVC in question are UI component oriented MVC and action oriented MVC. This article first goes over these two different styles of MVC, then explains the rationale for filing a separate JSR for MVC 1.0 and explains how this new specification will relate to the next version of JSF. 

If you attend JavaOne, you find many JavaOne sessions about JSF


Tuesday Apr 24, 2012

Spring to Java EE Migration – Part 4, the Finale

In a new article, now up on otn/java, titled “Spring to Java EE Migration, Part 4,” David Heffelfinger presents the final part of his series in which he demonstrates the ease of migration from the Spring Framework to Java EE. Here he compares equivalent functionality in Java EE and Spring in areas such as MVC design pattern implementation, data access, transaction management, and dependency injection.

He concludes the series with these remarks:

“In this series of articles, we developed a Java EE version of Spring’s Pet Clinic application. We saw how the advanced tooling provided by NetBeans enables us to quickly develop a Java EE application…. Once we were done building the Java EE version of the application, we compared it with the Spring version, noting that the original version has several dependencies whereas the Java EE version has none, because it takes advantage of all the services provided by the Java EE application server.

Finally, we compared how to implement similar functionality such as MVC and DAO implementation, transaction management, and dependency injection with Spring and Java EE. In every case with Spring, some XML configuration needs to be done besides adding annotations to the code. Java EE relies on convention, and in most cases, no XML configuration is needed in order to implement these services.

Although newer versions of Spring rely a lot less on explicit XML configuration than earlier versions, there are always a few little lines here and there that we need to add to an XML configuration file in order to get most of the Spring annotations to work, violating the DRY (don’t repeat yourself) principle...

Additionally, Spring applications tend to have several dependencies, because they are meant to run in a “lightweight” Servlet container such as Tomcat or Jetty and these containers don’t provide all the required functionality. In contrast, Java EE applications are meant to be deployed in a full-blown Java EE 6 application server such as Oracle GlassFish Server...

For these reasons, I always recommend Java EE over Spring for enterprise application development.”

Have a look at the article here.
About

Insider News from the Java Team at Oracle!

duke
Links


Search

Archives
« May 2015
SunMonTueWedThuFriSat
     
1
2
3
4
9
10
11
15
16
17
21
23
24
25
26
27
28
29
30
31
      
Today