wso2에서 호출이 작동하지 않는 이유 esb

Question

wso2 esb에 문제가 있습니다. 프록시를 작성했으며 원래 입력에서 일부 변경을 수행하기 위해 엔드 포인트를 호출합니다. 그러나 호출 전과 호출 후 로그는 동일합니다 (다른 값이어야합니다). 전화가 전혀 작동하지 않는 것 같습니다. 나에게 나가서 나올 때 null입니다. 왜 이런 일이 일어날 수 있을까요?

 <inSequence> 
    <property name="transport.vfs.ReplyFileName" value="GET" scope="transport"/> 
    <property name="OUT_ONLY" value="true" scope="default" type="STRING"/> 
    <smooks config-key="smooks-csv1"> 
     <input type="text"/> 
     <output type="xml"/> 
    </smooks> 
    <iterate continueParent="true" 
       preservePayload="true" 
       attachPath="//csv-set" 
       expression="//csv-set/search" 
       sequential="true"> 
     <target> 
      <sequence> 
       <xslt key="gov:/first.xsl"/> 
       <xslt key="gov:/second.xsl"/> 
       **<log level="full"/> 
       <call blocking="true"> 
       <endpoint> 
        <address uri="MyEndPiont"/> 
       </endpoint> 
       </call> 
       <log level="full"/>** 
      </sequence> 
     </target> 
    </iterate> 
    <respond/> 
    </inSequence> 
    <outSequence> 
    <aggregate> 
     <completeCondition> 
      <messageCount min="0" max="100"/> 
     </completeCondition> 
     <onComplete expression="//Guest"> 
     </onComplete> 
    </aggregate> 
    </outSequence> 

Answer 1

에서 인용. 변경 목록 :

• 제거 된 respond 중재자.
• call을 send으로 바꿉니다.

• send을 out 시퀀스에 추가했습니다.

  <inSequence> 
      <property name="transport.vfs.ReplyFileName" value="GET" scope="transport"/> 
      <property name="OUT_ONLY" value="true" scope="default" type="STRING"/> 
      <smooks config-key="smooks-csv1"> 
       <input type="text"/> 
       <output type="xml"/> 
      </smooks> 
      <iterate continueParent="true" 
         preservePayload="true" 
         attachPath="//csv-set" 
         expression="//csv-set/search" 
         sequential="true"> 
       <target> 
        <sequence> 
         <xslt key="gov:/first.xsl"/> 
         <xslt key="gov:/second.xsl"/> 
         <log level="full"/> 
         <send> 
         <endpoint> 
          <address uri="MyEndPiont"/> 
         </endpoint> 
         </send> 
        </sequence> 
       </target> 
      </iterate> 
      </inSequence> 
      <outSequence> 
      <aggregate> 
       <completeCondition> 
        <messageCount min="0" max="100"/> 
       </completeCondition> 
       <onComplete expression="//Guest"> 
       </onComplete> 
      </aggregate> 
      <send /> 
      </outSequence> 
  

Answer 2

blocking="false"을 시도해보십시오 (나는 soupUI 내 엔드 포인트를 테스트 한)

이 내 프록시입니다. 이 변경을한다고해서 호출 중재자가 asynchonus가되는 것은 아닙니다. 블로킹 여부에 관계없이 동기식입니다. 블로킹은 구현 세부 사항 일뿐입니다. 이 시도

The Call mediator is used to send messages out of the ESB to an endpoint. You can invoke services either in blocking or non-blocking manner.

When you invoke a service in non-blocking mode, the underlying worker thread returns without waiting for the response. In blocking mode, the underlying worker thread gets blocked and waits for the response after sending the request to the endpoint. Call mediator in blocking mode is very much similar to the Callout mediator.

In both blocking and non-blocking modes, Call mediator behaves in a synchronous manner. Hence, mediation pauses after the service invocation and resumes from the next mediator in the sequence when the response is received. Call mediator allows you to create your configuration independent from the underlying architecture.

는 https://docs.wso2.com/display/ESB500/Call+Mediator