麻豆小视频在线观看_中文黄色一级片_久久久成人精品_成片免费观看视频大全_午夜精品久久久久久久99热浪潮_成人一区二区三区四区

首頁 > 編程 > JSP > 正文

Spring Annotaion Support詳細(xì)介紹及簡單實例

2024-09-05 00:22:55
字體:
供稿:網(wǎng)友

     最近正在看spring官網(wǎng),看Spring IOC的時候看Spring容器擴(kuò)展點的時候發(fā)現(xiàn)了BeanPostProcessor 這個接口。下面是官方對它的詳細(xì)描述:

          BeanPostProcessor接口定義了回調(diào)方法,您可以實現(xiàn)提供自己的(或覆蓋容器的默認(rèn))實例化邏輯,依賴性解析邏輯,等等。如果你想實現(xiàn)一些自定義邏輯Spring容器實例化完成后,配置和初始化一個bean,您可以插入一個或多個BeanPostProcessor實現(xiàn)。

          您可以配置多個BeanPostProcessor實例,您可以控制的順序執(zhí)行這些BeanPostProcessors通過設(shè)置屬性。你可以設(shè)置這個屬性只有BeanPostProcessor實現(xiàn)命令接口;如果你寫自己的BeanPostProcessor你也應(yīng)該考慮實現(xiàn)theOrdered接口。詳情,請咨詢BeanPostProcessor的Javadoc和命令接口。

          BeanPostProcessor有兩個方法postProcessBeforeInitialization,postProcessAfterInitialization.如果一個對象實現(xiàn)了這個接口,那么就會在容器初始化init方法之前(就像InitializingBean的afterPropertiesSet()和其它公開的init方法)或在Spring bean初始化之后執(zhí)行回調(diào)。

          實現(xiàn)BeanPostProcessor接口的類由容器是特殊而區(qū)別對待。所有BeanPostProcessors和他們在啟動時直接引用實例化bean,作為特殊的ApplicationContext的啟動階段。接下來,所有BeanPostProcessorsare注冊分類的方式,適用于所有進(jìn)一步bean容器。因為實現(xiàn)AOP auto-proxying aBeanPostProcessor本身,無論是BeanPostProcessors還是beas他們有資格獲得auto-proxying直接引用,因此沒有方面編織進(jìn)去。

          實現(xiàn)BeanPostProcessor接口的類由容器是特殊而區(qū)別對待。所有BeanPostProcessors和他們在啟動時直接引用實例化bean,作為特殊的ApplicationContext的啟動階段。接下來,所有BeanPostProcessorsare注冊分類的方式,適用于所有進(jìn)一步bean容器。因為實現(xiàn)AOP auto-proxying aBeanPostProcessor本身,無論是BeanPostProcessors還是beas他們有資格獲得auto-proxying直接引用,因此沒有方面編織進(jìn)去。

          使用回調(diào)接口或注釋與自定義實現(xiàn)BeanPostProcessor是一種常見的擴(kuò)展SpringIoC容器。RequiredAnnotationBeanPostProcessor是Spring的一個例子 —— 一個實現(xiàn)BeanPostProcessor附帶的Spring分布,確保JavaBean屬性bean上標(biāo)有一個(任意)注釋(配置)會依賴注入值。

你說我一看到上面的AOP這個Spring兩大特性之一我心里面都有一點小激動。后面他再來個Spring的Annotation一般也是用這個接口實現(xiàn)的。這下就忍不住了想去看一看RequiredAnnotationBeanPostProcessor這個類到底干了什么。直接上源碼

Spring Annotation Support  /*  * Copyright 2002-2013 the original author or authors.  *  * Licensed under the Apache License, Version 2.0 (the "License");  * you may not use this file except in compliance with the License.  * You may obtain a copy of the License at  *  *   http://www.apache.org/licenses/LICENSE-2.0  *  * Unless required by applicable law or agreed to in writing, software  * distributed under the License is distributed on an "AS IS" BASIS,  * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  * See the License for the specific language governing permissions and  * limitations under the License.  */  package org.springframework.beans.factory.annotation;  import java.beans.PropertyDescriptor; import java.lang.annotation.Annotation; import java.lang.reflect.Method; import java.util.ArrayList; import java.util.Collections; import java.util.List; import java.util.Set; import java.util.concurrent.ConcurrentHashMap;  import org.springframework.beans.BeansException; import org.springframework.beans.PropertyValues; import org.springframework.beans.factory.BeanFactory; import org.springframework.beans.factory.BeanFactoryAware; import org.springframework.beans.factory.BeanInitializationException; import org.springframework.beans.factory.config.BeanDefinition; import org.springframework.beans.factory.config.ConfigurableListableBeanFactory; import org.springframework.beans.factory.config.InstantiationAwareBeanPostProcessorAdapter; import org.springframework.beans.factory.support.MergedBeanDefinitionPostProcessor; import org.springframework.beans.factory.support.RootBeanDefinition; import org.springframework.core.Conventions; import org.springframework.core.Ordered; import org.springframework.core.PriorityOrdered; import org.springframework.core.annotation.AnnotationUtils; import org.springframework.util.Assert;  /**  * {@link org.springframework.beans.factory.config.BeanPostProcessor} implementation  * that enforces required JavaBean properties to have been configured.  * 強(qiáng)制檢測JavaBean必須的properties是否已經(jīng)被配置  * Required bean properties are detected through a Java 5 annotation:  * 必須的bean屬性通過Java 5中的annotation自動檢測到  * by default, Spring's {@link Required} annotation.  *  * <p>The motivation for the existence of this BeanPostProcessor is to allow  * BeanPostProcessor存在的意義是允許  * developers to annotate the setter properties of their own classes with an  * arbitrary JDK 1.5 annotation to indicate that the container must check  * for the configuration of a dependency injected value. This neatly pushes  * 開發(fā)人員注釋setter屬性與一個他們自己的類任意的JDK 1.5注釋表明容器必須檢查依賴注入的配置值。  * responsibility for such checking onto the container (where it arguably belongs),  * 這樣就巧妙的把check的責(zé)任給了Spring容器(它應(yīng)該就屬于的)  * and obviates the need (<b>in part</b>) for a developer to code a method that  * simply checks that all required properties have actually been set.  * 這樣也就排除了開發(fā)人員需要編寫一個簡單的方法用來檢測那么必須的properties是否已經(jīng)設(shè)置了值  * <p>Please note that an 'init' method may still need to implemented (and may  * still be desirable), because all that this class does is enforce that a  * 請注意初始化方法還是必須要實現(xiàn)的(并且仍然是可取的)  * 'required' property has actually been configured with a value. It does  * 因為所有這個Class強(qiáng)制執(zhí)行的是'required'屬性是否已經(jīng)被配置了值  * <b>not</b> check anything else... In particular, it does not check that a  * 它并不會check其實的事,特別的是,它不會check這個配置的值是不是null值  * configured value is not {@code null}.  *  * <p>Note: A default RequiredAnnotationBeanPostProcessor will be registered  * by the "context:annotation-config" and "context:component-scan" XML tags.  * 當(dāng)你使用了"context:annotation-config"或者"context:component-scan"XML標(biāo)簽就會默認(rèn)注冊RequiredAnnotationBeanPostProcessor  * Remove or turn off the default annotation configuration there if you intend  * to specify a custom RequiredAnnotationBeanPostProcessor bean definition.  * 你如果打算指定一個自定義的RequiredAnnotationBeanPostProcessor的bean實現(xiàn)可以移除或者關(guān)閉默認(rèn)的annotation配置  *  * @author Rob Harrop  * @author Juergen Hoeller  * @since 2.0  * @see #setRequiredAnnotationType  * @see Required  */ public class RequiredAnnotationBeanPostProcessor extends InstantiationAwareBeanPostProcessorAdapter     implements MergedBeanDefinitionPostProcessor, PriorityOrdered, BeanFactoryAware {    /**    * Bean definition attribute that may indicate whether a given bean is supposed    * to be skipped when performing this post-processor's required property check.    * 這個bean定義的屬性表明當(dāng)執(zhí)行post-processor(后處理程序)這個check提供的bean的必須的屬性    * @see #shouldSkip    */   public static final String SKIP_REQUIRED_CHECK_ATTRIBUTE =       Conventions.getQualifiedAttributeName(RequiredAnnotationBeanPostProcessor.class, "skipRequiredCheck");     private Class<? extends Annotation> requiredAnnotationType = Required.class;    private int order = Ordered.LOWEST_PRECEDENCE - 1;    private ConfigurableListableBeanFactory beanFactory;    /**    * Cache for validated bean names, skipping re-validation for the same bean    * 緩存已經(jīng)確認(rèn)過的bean名稱,跳過后續(xù)同樣的bean    */   private final Set<String> validatedBeanNames =       Collections.newSetFromMap(new ConcurrentHashMap<String, Boolean>(64));     /**    * Set the 'required' annotation type, to be used on bean property    * setter methods.    * 設(shè)置所需的注釋類型,使用bean屬性setter方法    * <p>The default required annotation type is the Spring-provided    * {@link Required} annotation.    * 這個默認(rèn)的required annotation類型是Spring提供的annotation    * <p>This setter property exists so that developers can provide their own    * (non-Spring-specific) annotation type to indicate that a property value    * is required.    * 這里設(shè)置這個property是為了開發(fā)者能夠提供自己定義的annotaion類型用來表明這個屬性值是必須的    */   public void setRequiredAnnotationType(Class<? extends Annotation> requiredAnnotationType) {     Assert.notNull(requiredAnnotationType, "'requiredAnnotationType' must not be null");     this.requiredAnnotationType = requiredAnnotationType;   }    /**    * Return the 'required' annotation type.    */   protected Class<? extends Annotation> getRequiredAnnotationType() {     return this.requiredAnnotationType;   }    @Override   public void setBeanFactory(BeanFactory beanFactory) {     if (beanFactory instanceof ConfigurableListableBeanFactory) {       this.beanFactory = (ConfigurableListableBeanFactory) beanFactory;     }   }    public void setOrder(int order) {     this.order = order;   }    @Override   public int getOrder() {     return this.order;   }     @Override   public void postProcessMergedBeanDefinition(RootBeanDefinition beanDefinition, Class<?> beanType, String beanName) {   }    @Override   public PropertyValues postProcessPropertyValues(       PropertyValues pvs, PropertyDescriptor[] pds, Object bean, String beanName)       throws BeansException {     // 利用緩存確定是否這個bean被validated     if (!this.validatedBeanNames.contains(beanName)) {       // 不跳過       if (!shouldSkip(this.beanFactory, beanName)) {         List<String> invalidProperties = new ArrayList<String>();         for (PropertyDescriptor pd : pds) {           // 如果被標(biāo)記為了required 且 這個屬性沒有屬性值(或其他處理條目)           if (isRequiredProperty(pd) && !pvs.contains(pd.getName())) {             // 增加這個屬性             invalidProperties.add(pd.getName());           }         }         // <span style="color:#ff0000;">如果無效的properties不為空。拋出異常</span>         if (!invalidProperties.isEmpty()) {           throw new BeanInitializationException(buildExceptionMessage(invalidProperties, beanName));         }       }       // 把需要驗證的bean名稱添加進(jìn)去       this.validatedBeanNames.add(beanName);     }     return pvs;   }    /**    * Check whether the given bean definition is not subject to the annotation-based    * required property check as performed by this post-processor.    * 通過post-processor(后處理程序)檢測這個被給予的定義的bean是否受注釋為基礎(chǔ)的check必須的property的管束    * <p>The default implementations check for the presence of the    * {@link #SKIP_REQUIRED_CHECK_ATTRIBUTE} attribute in the bean definition, if any.    * 這個默認(rèn)的實現(xiàn)check存在SKIP_REQUIRED_CHECK_ATTRIBUTE這個屬性的定義的bean    * It also suggests skipping in case of a bean definition with a "factory-bean"    * reference set, assuming that instance-based factories pre-populate the bean.    * 它同樣也建議跳過如果這個bean定義了"factory-bean"引用,假設(shè)那個基于實例的factories預(yù)先配置了bean    * @param beanFactory the BeanFactory to check against    * @param beanName the name of the bean to check against    * @return {@code true} to skip the bean; {@code false} to process it    * 如果返回 true跳過這個bean,返回false就處理它    */   protected boolean shouldSkip(ConfigurableListableBeanFactory beanFactory, String beanName) {     // 如果這個beanFacotry為空或者這個bean工廠不包含一個給定名稱的bean定義。返回false     if (beanFactory == null || !beanFactory.containsBeanDefinition(beanName)) {       return false;     }     BeanDefinition beanDefinition = beanFactory.getBeanDefinition(beanName);     // 判斷這個bean的工廠beanName,如果不為null,返回true     if (beanDefinition.getFactoryBeanName() != null) {       return true;     }     Object value = beanDefinition.getAttribute(SKIP_REQUIRED_CHECK_ATTRIBUTE);     return (value != null && (Boolean.TRUE.equals(value) || Boolean.valueOf(value.toString())));   }    /**    * Is the supplied property required to have a value (that is, to be dependency-injected)?    * 是否這個提供的必須的propery是否有一個值(這個是被依賴注入)?    * <p>This implementation looks for the existence of a    * {@link #setRequiredAnnotationType "required" annotation}    * on the supplied {@link PropertyDescriptor property}.    * 這個實現(xiàn)是為了找到提供的ProertyDescriptor是提供了"required"注解    * @param propertyDescriptor the target PropertyDescriptor (never {@code null})    * @return {@code true} if the supplied property has been marked as being required;    * 返回true,如果提供的property已經(jīng)被標(biāo)記為必須的</span>    * {@code false} if not, or if the supplied property does not have a setter method    * 返回false,如果沒有標(biāo)記為必須的或者提供的property沒有一個setter方法    */   protected boolean isRequiredProperty(PropertyDescriptor propertyDescriptor) {     Method setter = propertyDescriptor.getWriteMethod();     return (setter != null && AnnotationUtils.getAnnotation(setter, getRequiredAnnotationType()) != null);   }    /**    * Build an exception message for the given list of invalid properties.    * 使用所給的異常properties來構(gòu)建異常信息    * @param invalidProperties the list of names of invalid properties    * @param beanName the name of the bean    * @return the exception message    */   private String buildExceptionMessage(List<String> invalidProperties, String beanName) {     int size = invalidProperties.size();     StringBuilder sb = new StringBuilder();     sb.append(size == 1 ? "Property" : "Properties");     for (int i = 0; i < size; i++) {       String propertyName = invalidProperties.get(i);       if (i > 0) {         if (i == (size - 1)) {           sb.append(" and");         }         else {           sb.append(",");         }       }       sb.append(" '").append(propertyName).append("'");     }     sb.append(size == 1 ? " is" : " are");     sb.append(" required for bean '").append(beanName).append("'");     return sb.toString();   }  } 

在上面的代碼中所示。我們可以得出以下結(jié)論:

Spring,Annotaion,Support,Support詳解

上面已經(jīng)把Spring對于 org.springframework.beans.factory.annotation.Required 這個標(biāo)簽的實現(xiàn)出來了。雖然只是一個小例子。但是我們可以根據(jù)Spring以下的的包結(jié)構(gòu)看到這是Spring對于它自身Annotation的很common的實現(xiàn):

Spring,Annotaion,Support,Support詳解

從上面的例子中我可以看出Spring對它本身的Annotaion的一種實現(xiàn)。當(dāng)前文中并沒有講述Exception Message是通過怎么傳遞的。但是這并不是本文討論的范疇,有興趣的朋友可以自己去看看。

感謝閱讀,希望能幫助到大家,謝謝大家對本站的支持!

 

注:相關(guān)教程知識閱讀請移步到JSP教程頻道。
發(fā)表評論 共有條評論
用戶名: 密碼:
驗證碼: 匿名發(fā)表
主站蜘蛛池模板: 成人444kkkk在线观看 | 99在线免费观看视频 | 99精品视频在线免费观看 | 牛牛热这里只有精品 | 欧美精品一区二区三区久久久 | 2021国产精品 | 99热草 | 国产免费久久久久 | h视频在线播放 | 中文字幕在线观看视频一区 | 999精品国产 | 精品国产一区二区三区四区在线 | 国产精品一区在线看 | 亚洲 综合 欧美 动漫 丝袜图 | 国产一级毛片av | japanese massage tube | aa国产视频一区二区 | 国产亚洲精品久久久久婷婷瑜伽 | 国产精品成人亚洲一区二区 | 亚洲天堂成人在线观看 | 99热1| 久久久国产一级片 | 亚洲xxx视频 | 在线看免电影网站 | 亚洲精品永久视频 | av不卡毛片 | 4p一女两男做爰在线观看 | 欧美日韩观看 | 国产精品久久久久久久久粉嫩 | 国产亚洲精品久久久久婷婷瑜伽 | 国产一国产一级毛片视频 | 欧美精品99 | 亚洲3p激情在线观看 | 毛片小网站 | 国产午夜精品一区二区三区不卡 | 国产精品成人av片免费看最爱 | 精品国产一区二区三区四区阿崩 | 一起草av在线 | 精品一区二区三区四区在线 | 51色视频| 亚洲一区在线免费视频 |