Programming
As we all know, spring is a proponent of interfacing programming. But there are some service categories, such as Saleordermanager and Saleordermanagerimpl, with only 5% chance of another IMPL implementation. 95% time the two brothers stand together, just like C + +. H and. cpp, increased maintenance of the cumbersome, so just start with spring when you want to remove it, today accidentally in Group chat dynamic agent, is to understand the truth, thank sparkle:) IOC is not enforcing interfaces, it is these service classes that typically use spring's declarative transaction mechanism, and declarative transaction mechanisms are implemented using spring AOP. Then look at spring AOP, mixed with Java dynamic proxies and CGLIB2, because Java dynamic proxies are ideal for AOP, but only for interfaces. If you are based on class, Spring AOP uses Cglib to generate the subclass of the target class to implement AOP, quite realistically. So, as long as we specify that AOP can be implemented using CGLIB with declarative transaction beans, it is not programming on an interface. The specified method is to set Proxytargetclass to true. eg.
<bean id= "Baseservice" class= "Org.springframework.transaction.interceptor.TransactionProxyFactoryBean" Abstract= "true" > <property name= "TransactionManager" > <ref bean= "TransactionManager"/> </property> <property name= "Proxytargetclass" > <value>true</value> </property> .... </bean>
This efficiency issue has also been discussed, because these service beans are single cases and the efficiency should not be affected.
Related articles: 1. Simplify spring--configuration file 2. Simplify the Spring--view Layer 3. Simplify the Spring--model layer 4. Simplifying Spring Controller to the simplest of all MVC schemes 5. Simplifying spring--reducing unnecessary interface programming
