Spring is an Application Framework that serves all levels: provides the BEAN configuration foundation, AOP support, JDBC's extraction framework, abstract transaction support, and so on. It has a very significant feature: at a level if you don't need Spring support, you can use the string Class, only the features of some part of it. From its design concept, you can see String Help you implement the true logical layer and the WEB layer separation. For EJB, Spring is a lightweight J2EE application development framework. The lightweight referred to here is the Spring framework itself, not that Spring can only apply to lightweight application development. Spring's lightweight is reflected in its frame itself, and the support and assembly capabilities of other application tools, Spring makes us reduce the risk between the technical levels compared to EJB's homonomer. EJB has strong cohesiveness, such as data persistence layer management, transaction management, and lifecycle management are all handed over to the management of the EJB container. The white box characteristics of the cohesiveness allows us to give up a part of the controllability to trust the container capacity. . Spring is considering how "not built wheels", how to better assemble these wheels, let them turn better. For example, data persistence layer management can use Hibernate, log management can use JakartacomMonLogging. A more appropriate metaphor is "We have to get a few nails. In order to accomplish this, the hammer producer produces a large and small series of hammers, each with a complex method of use, used to nail a special Nail, the result makes us headache. Solve the problem of excessive hammer, through Spring, we can use several hammers, but it is like only one hammer. " (Note: This paragraph is visible online. Here is this metaphor. I personally feel very vivid) There are also some simple summary on this framework: "Spring has several major parts: bean ApplicationContext, with a unified , IoC's way, manage, assemble, use the system components, replace all plants; persistence framework; web framework. "J2EE Framework" is the vision of Rodjohnson, he hopes that Spring provides the top to the J2EE lightweight solution Comprehensive infrastructure support. "Well, the above is a brief introduction to a new Framework, is said to be the direction of J2EE development. Previously on the discussion of J2EE's best combination, I heard that this JSTL STRUTS (or webwork) Spring Hibernate is very optimistic (the view is different, just for reference, huh), if you are interested, You can take a look at the Springframework Chinese Forum. The topic of this article is transferred below. Spring tag library introduction and usage: This article will focus on the tag library provided by Spring and its usage: When you use Spring Framework in the project, the performance layer can select the Spring Framework's own tag library. Of course, this is not your only choice. You can choose other tag libraries or template replacement techniques. Spring Framework does not provide a very rich tag library for applications. The marker library provided by Spring Framework is just to use it, it is not unpacking. Oh, this is different from the Struts rich tag library. In fact, this is in line with the starting point of Rodjohnson, which is both "no wheel". Of course, the Spring Framework tag library has its own characteristics, it can be said to be a good supplement. The Spring tag library is classified as follows: 1. Spring: HasbinderRors 2. Spring: BIND 3.
Spring: Transform 4. Spring: Message 5. Spring: HTMLESCAPE 6. Spring: Theme Let's take a specific use: 1. Spring: HasbinderRors corresponds to the org.springframework.web.servlet.tags.binderrorseTag tag library processing class. This tag provides an Errors for binding objects. If this tag is used, the error on this object will be displayed on the page. The prerequisite for using this tag is to use the
