You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by ale <al...@italtbs.com> on 2007/06/12 17:21:04 UTC
in-out to in-only adapting - solution
i finally managed to find a solution to the synchronizing issue i requested
help for 1 days ago.
I built a component implementing a pattern which could be thought as the
opposite of a pipeline.
It accepts an in-out mep and holds it associated to a correlation key and
then sends the in message
asynchronously to a target service.
When an in-only mep comes in it tries to correlate the message with one of
the stored exchanges and
eventually answers back with the corresponding in-out mep.
That's what it does :
/ ----->IN-ONLY
/
<-- IN-OUT -->
\
\<------IN-ONLY
Its ina very early version but if anybody finds it interesting i could
provide the full sources on
this forum or as a jira issue.
Let me know, bye.
--
View this message in context: http://www.nabble.com/in-out-to-in-only-adapting---solution-tf3908193s12049.html#a11080874
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Re: in-out to in-only adapting - solution
Posted by Gert Vanthienen <ge...@skynet.be>.
L.S.,
Seems like a good addition for servicemix-eip at first glance. If you
want to contribute it to ServiceMix, the easiest way to ensure follow-up
on this would be by raising a JIRA issue.
Thank you,
Gert
ale wrote:
> i finally managed to find a solution to the synchronizing issue i requested
> help for 1 days ago.
> I built a component implementing a pattern which could be thought as the
> opposite of a pipeline.
> It accepts an in-out mep and holds it associated to a correlation key and
> then sends the in message
> asynchronously to a target service.
> When an in-only mep comes in it tries to correlate the message with one of
> the stored exchanges and
> eventually answers back with the corresponding in-out mep.
>
> That's what it does :
>
>
> / ----->IN-ONLY
> /
> <-- IN-OUT -->
> \
> \<------IN-ONLY
>
>
> Its ina very early version but if anybody finds it interesting i could
> provide the full sources on
> this forum or as a jira issue.
>
> Let me know, bye.