Mule

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0-RC2
• Fix Version/s: 2.0.2
• Component/s: Core: Configuration
• Labels:

  None

Right now there is a "test" transport and test schema as part of the TCK. However, we should use the test namespace to configure elements useful for testing. i.e.

FuctionalTestComponent should be configured using something like:

<test:component throw-exception="true"/>

or

<test:component>
    <test:return-data file="data/whatever.txt"/>
</test:component>

Also, I think we should include an event generator component i.e.

<service>
    <test:event-generator frequency="10" messages="1000">
        <test:event-data file="data/whatever.txt"/>
    </test:component>
    <outbound>
        <outbound-pass-through-router>
            <outbound-endpoint address="vm://whatever"/>
       </outbound>
</service>

The event generator could be wrapped up in the test transport and added just by adding an inbound endpoint i.e.

<service>
    <inbound>
        <test:inbound-endpoint eventData="data/whatever.txt" frequency="10" messages="1000"/>
    <component class="org.foo.MyComponent"/>
    <outbound>
        <outbound-pass-through-router>
            <outbound-endpoint address="vm://whatever"/>
       </outbound>
</service>

Of course you could apply inbound transformers here to randomise the data

• Assignee:

  Ross Mason

  Reporter:

  Ross Mason

• Created:

  17/Mar/08 08:50 AM

  Updated:

  12/Jun/08 04:02 AM

  Resolved:

  12/Jun/08 04:02 AM