miaoyachun

/**
 * 重載合并屬性實(shí)現(xiàn)
 * 先加載file properties， 然后并入ZK配置中心讀取的properties
 *
 * @return 合并后的屬性集合
 * @throws IOException 異常
 */
@Override
protected Properties mergeProperties() throws IOException {
    Properties result = new Properties();
    // 加載父類的配置
    Properties mergeProperties = super.mergeProperties();
    result.putAll(mergeProperties);
    // 加載從zk中讀取到的配置
    Map<String, String> configs = loadZkConfigs();
    result.putAll(configs);
    return result;
}

/**
 * 重載處理屬性實(shí)現(xiàn)
 * 根據(jù)選項(xiàng), 決定是否將合并后的props寫入系統(tǒng)屬性, Spring boot需要
 *
 * @param beanFactoryToProcess
 * @param props                合并后的屬性
 * @throws BeansException
 */
@Override
protected void processProperties(ConfigurableListableBeanFactory beanFactoryToProcess, Properties props) throws BeansException {
    // 原有邏輯
     super.processProperties(beanFactoryToProcess, props);
    // 寫入到系統(tǒng)屬性
    if (writePropsToSystem) {
       // write all properties to system for spring boot
        Enumeration<?> propertyNames = props.propertyNames();
        while (propertyNames.hasMoreElements()) {
             String propertyName = (String) propertyNames.nextElement();
             String propertyValue = props.getProperty(propertyName);
             System.setProperty(propertyName, propertyValue);
        }
    }
}

@Override
public Object postProcessBeforeInitialization(Object bean, String beanName)
      throws BeansException {
   ConfigurationProperties annotation = AnnotationUtils
         .findAnnotation(bean.getClass(), ConfigurationProperties.class);
   if (annotation != null) {
      postProcessBeforeInitialization(bean, beanName, annotation);
 }
   annotation = this.beans.findFactoryAnnotation(beanName,
 ConfigurationProperties.class);
   if (annotation != null) {
      postProcessBeforeInitialization(bean, beanName, annotation);
 }
   return bean;
}

解決思路有兩個(gè):

• 思路1: 想辦法對(duì)靜態(tài)變量注入, 也就是繞過Spring只能運(yùn)行非靜態(tài)變量才能注入依賴的壁壘
• 思路2: 想辦法@AfterClass改造為非靜態(tài)

  • 實(shí)現(xiàn)Junit RunListener, 覆蓋testRunFinished方法, 這里去實(shí)現(xiàn)類似@AfterClass的功能, 這個(gè)方法是非靜態(tài)的
  • 不要用Junit, 改用TestNG, TestNG里的AfterClass是非靜態(tài)的
  • 用Spring的TestExecutionListeners, 實(shí)現(xiàn)個(gè)Listener, 里面也有個(gè)類似非靜態(tài)的AfterClass的實(shí)現(xiàn), 覆蓋實(shí)現(xiàn)就行

思路2的幾個(gè)方法都可以實(shí)現(xiàn), 但是單元測(cè)試Runner需要用

@RunWith(Theories.class)

而且改用TestNG工程浩大, 只能放棄掉這個(gè)思路

繼續(xù)走思路1, 只能去繞過Spring的依賴注入的static壁壘了, 具體代碼如下:

 @Autowired
 private Destination dfsOperationQueue;
 private static Destination dfsOperationQueueStatic; // static version
 @Autowired
 private MessageQueueAPI messageQueueAPI;
 private static MessageQueueAPI messageQueueAPIStatic; // static version


 @PostConstruct
 public void init() {
        dfsOperationQueueStatic = this.dfsOperationQueue;
        messageQueueAPIStatic = this.messageQueueAPI;
 }

 @AfterClass
 public static void afterClass() {
        MessageVO messageVO = messageQueueAPIStatic.removeDestination(dfsOperationQueueStatic);
        System.out.println(messageVO);
 }

其實(shí)就是用了@PostConstruct 來(lái)個(gè)偷梁換柱而已, 多聲明個(gè)靜態(tài)成員指向非靜態(tài)對(duì)象, 兩者其實(shí)是一個(gè)對(duì)象

知道activemq現(xiàn)在已經(jīng)支持了rest api, 但是官方對(duì)這部分的介紹一筆帶過 (http://activemq.apache.org/rest.html),

通過google居然也沒搜到一些有用的, 比如像刪除一個(gè)destination, 都是問的多,然后沒下文. 于是花了一些心思研究了一下:

首先通過rest api獲取當(dāng)前版本所有已支持的協(xié)議

    http://172.30.43.206:8161/api/jolokia/list

然后根據(jù)json輸出關(guān)于removeTopic, removeQueue的mbean實(shí)現(xiàn)通過rest api刪除destination的方法, 注意到用GET請(qǐng)求而不是POST,不然會(huì)報(bào)錯(cuò) (官網(wǎng)的例子里用的wget給的靈感, 開始用了POST老報(bào)錯(cuò))

其他的請(qǐng)求,應(yīng)該都是類似jolokia的exec get request的格式:

<base url>/exec/<mbean name>/<operation name>/<arg1>/<arg2>/.

server.compression.enabled=true 
server.compression.mime-types=application/json,application/xml,text/html,text/xml,text/plain
server.compression.min-response-size=4096

latency = client send request time + network trans time (->)+ server receive request time+ reponse time + server send reponse time+ network trans time (<-)+ client receive reponse time

latency = first byte out, last byte in time