spring12个xml总结（spring12个xml总结）.docVIP

spring12个xml总结（spring12个xml总结） Spring summarizes twelve best practices configured with XML 1. do not use autowiring Spring can bind its dependency section by class introspection, so that you dont have to specify the properties and constructors of bean. The properties of Bean can be automatically bound by attribute names or type matching. The constructor implements automatic binding by type matching. You can even specify the automatic check auto binding mode, which can boot Spring to select an appropriate running mechanism. Lets look at an example below: Class= com.lizjason.spring.OrderService Autowire= byName / The attribute name of the OrderService class is used in the container to match the bean instance. Automatic binding can potentially save some typing and reduce some confusion. But you shouldnt use it in real-world engineering because it sacrifices the clarity and maintainability of the configuration. Many of the tutorials and the introduction tout the automatic binding as an excellent feature of Spring without mention of the sacrifice of this feature. In my opinion, this is like the object Spring in pooling. Its more like a business feature that takes on more market. It is a good idea for the small size of the XML configuration file, but it actually adds complexity, especially when you run a project with a large class declaration. Although Spring allows you to mix automatic binding and manual binding, this contradiction makes XML configuration more difficult to understand. 2. use popular naming This is also true for Java encoding. Using clear, descriptive, coordinated popular names in engineering is very useful for developers to understand the XML configuration. For example, for beanID, you can name it from the popular Java class name. For example, the beanID of OrderServiceDAO is named orderServiceDAO. For larger projects, you can prefix the beanID with a package name. 3. use simple forms Simple form to avoid lengthy, because it is from the elements in attr