The specific application of AOP in spring is best illustrated with examples

Spring has a lot to offer, and I'm going to quickly walk you through the main aspects of each of them.

First, let's be clear about the spring scope. Although Spring covers many aspects, we already have a clear idea of what it should and shouldn't cover.

The main purpose of Spring is to make J2EE easy to use and to promote good programming habits.

Spring doesn't redevelop what already exists. As a result, in Spring you will find packages with no logging, no connection pools, and no distributed transaction scheduling. These are provided by open source projects (e.g. Commons Logging for all log output, or Commons DBCP for data connection pooling) or by your application server.

spring

Spring's goal is to make the technology that already exists easier to use.

For example, although we don't have underlying transaction coordination processing, we provide an abstraction layer that overrides JTA or any other transaction strategy.

Spring doesn't compete directly with other open source projects unless we feel we have something new to offer. For example, like many developers, we were never happy about Struts and felt that there was room for improvement in the MVC Web Framework. Spring has direct competition in some areas, such as lightweight IOC containers and AOP frameworks, but there are no popular solutions in these areas.

Spring is a trailblazer in these areas. ）

Spring also benefits from intrinsic consistency.

All the developers are singing the same hymn, and the underlying idea is still the one that Expert One-On-One J2EE designed and developed.

And we've been able to use some of the main concepts, such as inverted control, to deal with multiple domains.

Spring is portable between application servers.

Of course, portability is always a challenge, but we avoid any specific platform or non-standardization, and support users on WebLogic, Tomcat, Resin, JBoss, WebSphere, and other application servers.

Summary. 1.The coupling between components is reduced, and the decoupling between the various layers of the software is realized2

It is easy to use numerous services such as transaction management, messaging services, etc.3Containers provide singleton mode support 4Containers provide AOP technology, which makes it easy to implement functions such as permission interception, runtime monitoring, etc.5

Containers provide a large number of auxiliary classes to speed up the development of applications, and provide integration support for mainstream application frameworks, such as hibernate, jpa, struts, etc., which are low-intrusive designs with extremely low pollutionThe DI mechanism, which is independent of various application servers, reduces the complexity of business object replacement, and is highly open, and does not force the application to rely entirely on Spring, and developers can freely choose some or all of Spring.

What are the benefits of Spring? The following errors are (a) a AOP will be happy to answer for you. Have a great day. Hello, just an option?

1.The coupling between components is reduced, and the decoupling between the layers of the software is realized2It is easy to use numerous services such as transaction management, messaging services, etc.3

Containers provide singleton mode support 4Containers provide AOP technology, which makes it easy to implement functions such as permission interception, runtime monitoring, etc.5Containers provide a large number of auxiliary classes to speed up the development of applications, and provide integrated support for mainstream application frameworks, such as hibernate, jpa, struts, etc., which are low-intrusive designs, and the fouling of the ** is extremely low8

The DI mechanism, which is independent of various applications, reduces the complexity of business object replacement, and does not force the application to rely entirely on Spring, and developers can freely choose some or all of Spring.

First of all, the landlord needs to understand the concept of "thing handling".

AOP is mainly for thing processing, and it is relative to the previous programming thing processing, without AOP, we have to hardcode the thing processing in the method, with AOP, we only need to configure things in the Spring configuration file, which is called declarative thing processing. In general, the configuration is to configure a method name that matches a certain format, and when this method is run, spring will intercept it and add the transaction processing to it.

In layman's terms, Spring's AOP is quite similar to the role of a motherboard in a computer. Motherboard: It is to connect various components to it and manage it in a unified manner, so as to avoid the confusion of the connection between the components and the device.

I don't know if you understand a little bit about that.

Section-oriented programming, mainly using Spring's ** mechanism for log writing.

AOP needs to understand his principle and then talk about the use. Mainly use transaction control, of course, run logs, permission control, etc.