To explain more about what I need to do:
I need to take some data out of my message and construct a URL (to a cgi-like interface) to make a call over http.
ie,
inbound message contains: "myparameter" in the payload
I need to then call:
http://somehost:someport/mycgi?dothis=myparameterIn mule 1.4.x we wrote a component that makes the http call. I found this architecture confusing. You have this inbound message that gets fed to a component, and then disappears. It is like it fell through a trap door while you weren't looking.
I'd rather use an actual outbound router to deliver the message.
I was hoping the template-endpoint-router could do this trick.
--
service:
<inbound>
<inbound-endpoint xxx />
</inbound>
<component>
extract myparameter somehow
</component>
<outbound>
<template-endpoint-router theparameter="myparameter">
<template outbound endpoint>
</template-endpoint-router>
</outbound>
--
1) Once I've found "myparameter" with the component, how do I feed it into the template-endpoint-router? Do I replace the payload with it? Put it on the message headers somehow?
2) How do I configure the http endpoint to accept "myparameter" at the proper place in the url?
... Maybe this isn't possible, and the only way to get out of Mule 2.0.2 with the URL I need, will have to be through the component.
rotten wrote:
The current documentation is missing an example for the "template-endpoint-router".
Can someone point me to how it actually should be used?
