Pojo-based development mode (day03)

The last article discussed spring's design goal: Making Jee development easier.

Okay, as a Java developer, we should all know the Struts framework, and do not know the differences between struts1 and struts2.

First, the two are almost completely different frameworks, and struts2 is more like an upgraded version of another framework webwork. Of course, what we want to discuss here is not struts2, but the advantages of struts2:

The development mode based on action pojo is still understood by code:

Struts2

Public class commonaction {}

Or SSH

@ Controllerpublic class commonaction {}

As an action class at the control layer, in struts2 or SSH framework applications, you no longer need to inherit classes or implement interfaces, which largely releases coupling, from my understanding, this is the pojo-oriented development mode, which is also the advantage of beanfactory implemented by the Spring IoC design mode. dependencies are managed by spring containers.

Pojo-based development mode (day03)