WSO2 ESB Conditional Router路由限制咨询：能否基于Payload提取的studentno配置条件路由？

First, to answer your core question clearly: Yes, the WSO2 ESB Conditional Router mediator does have a built-in limitation—it’s designed to only evaluate conditions against HTTP headers, query parameters, and transport properties by default. It can’t directly reference variables extracted from the payload or message context properties unless you explicitly make those values accessible to it.

If you want to stick with Conditional Router for your studentno-based routing #

You’ll need to first pull the studentno value from the payload and store it in a message context property (or HTTP header) that the Conditional Router can access. Here’s how to do it step-by-step:

1. Extract the payload value to a context property
   Use the Property mediator to grab the studentno value from your payload and save it to the default message scope. Adjust the expression to match your payload format:

   <!-- For XML payloads -->
   <property 
       expression="//studentno/text()" 
       name="studentNo" 
       scope="default" 
       type="STRING"/>
   
   <!-- For JSON payloads -->
   <property 
       expression="json-eval($.studentno)" 
       name="studentNo" 
       scope="default" 
       type="STRING"/>
   

2. Reference the property in Conditional Router
   Now you can use the $ctx: prefix to access the stored property in your Conditional Router conditions:

   <conditionalRouter>
       <condition>$ctx:studentNo == '12345'</condition>
       <target sequence="Student12345Sequence"/>
       
       <condition>$ctx:studentNo == '67890'</condition>
       <target sequence="Student67890Sequence"/>
       
       <defaultTarget sequence="DefaultStudentSequence"/>
   </conditionalRouter>
   

Alternative: Use Switch Mediator (more straightforward for payload-based routing) #

As you’ve already heard, the Switch mediator is a better fit for this use case because it can directly reference payload values without extra steps. Here’s a quick example:

<!-- For XML payloads -->
<switch source="//studentno/text()">
    <case regex="12345">
        <sequence key="Student12345Sequence"/>
    </case>
    <case regex="67890">
        <sequence key="Student67890Sequence"/>
    </case>
    <default>
        <sequence key="DefaultStudentSequence"/>
    </default>
</switch>

<!-- For JSON payloads -->
<switch source="json-eval($.studentno)">
    <!-- Same case/default logic as above -->
</switch>

Why does Conditional Router have this limitation? #

The Conditional Router is optimized for fast, transport-layer routing decisions (like routing based on request headers or query params) rather than deep message content inspection. It doesn’t parse the message payload by default, hence the need to move payload data to accessible properties first.

内容的提问来源于stack exchange，提问作者ktraos