You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by loboEsa <la...@gmail.com> on 2009/10/17 21:27:56 UTC
Pipeline vs Enrichment
What´s the difference between eip:pipeline and eip:enrichment ?
For me, both receive InOnly message then send to InOut service to do
something and the response be sent as InOnly service to continue with the
flow.
Where am I wrong?
--
View this message in context: http://www.nabble.com/Pipeline-vs-Enrichment-tp25941125p25941125.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Pipeline vs Enrichment
Posted by loboEsa <la...@gmail.com>.
Thanks Gert.
Now it's clear to me.
Gert Vanthienen wrote:
>
> L.S.,
>
> The pipeline pattern is just about handling the MEPs, it will not do
> anything else with the message payloads. You can use it to e.g. wire
> a bean that enriches the content, but in that scenario, it's the bean
> that receives the exchange and enriches it and sends back the
> response. However, the pipeline is also a very generic pattern which
> can be used for content enrichment, but also for message
> transformation and other use cases.
>
> The content enricher pattern does handle the payloads itself by
> sending both the InOut request and response along in a new element,
> e.g. if you send <request><hello/></request> with the InOut exchange
> and receive <result><message2/></result> you'll get a final message
> that contains both of these like
> <enricher><request><hello/></request><result><message2/></result></enricher>.
> So the enricher is a very specific pattern, which will merge the
> request and response messages from the InOut exchange into the
> payload.
>
> Does this make the distinction between the two of them a bit more clear?
>
> Regards,
>
> Gert Vanthienen
> ------------------------
> Open Source SOA: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
>
>
>
> 2009/10/18 loboEsa <la...@gmail.com>:
>>
>> Thanks Johan for your answer.
>>
>> But I continue with my question about the difference betwen pipeline and
>> enrichment, because enrichment do the same only that the In-Out MEP be
>> used
>> to add information to the content and pipeline doesn`t have this
>> limitation,
>> but only be a conceptual definition because as component in the In-Out
>> transformer you can do wathewver you want, add, delete, sustitute
>> information.
>>
>> In other words, if you use the same In-Only MEP and the same In-Out MEP
>> as
>> transformation in pipeline or enrichment you must have the same result .
>>
>> Or no?
>>
>>
>>
>>
>> Johan Edstrom-3 wrote:
>>>
>>> The Pipeline component is a bridge between an In-Only (or Robust-In-
>>> Only) MEP and an In-Out MEP. When the Pipeline receives an In-Only
>>> MEP, it will send the input in an In-Out MEP to the tranformer
>>> destination and forward the response in an In-Only MEP to the target
>>> destination.
>>>
>>> On Oct 17, 2009, at 1:27 PM, loboEsa wrote:
>>>
>>>>
>>>> What´s the difference between eip:pipeline and eip:enrichment ?
>>>>
>>>> For me, both receive InOnly message then send to InOut service to do
>>>> something and the response be sent as InOnly service to continue
>>>> with the
>>>> flow.
>>>>
>>>> Where am I wrong?
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://www.nabble.com/Pipeline-vs-Enrichment-tp25941125p25941125.html
>>>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>>>
>>>
>>> Johan Edstrom
>>>
>>> joed@opennms.org
>>>
>>> They that can give up essential liberty to purchase a little temporary
>>> safety, deserve neither liberty nor safety.
>>>
>>> Benjamin Franklin, Historical Review of Pennsylvania, 1759
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Pipeline-vs-Enrichment-tp25941125p25949090.html
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>>
>
>
> -----
> ---
> Gert Vanthienen
> http://gertvanthienen.blogspot.com
>
--
View this message in context: http://www.nabble.com/Pipeline-vs-Enrichment-tp25941125p25960160.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Pipeline vs Enrichment
Posted by Gert Vanthienen <ge...@gmail.com>.
L.S.,
The pipeline pattern is just about handling the MEPs, it will not do
anything else with the message payloads. You can use it to e.g. wire
a bean that enriches the content, but in that scenario, it's the bean
that receives the exchange and enriches it and sends back the
response. However, the pipeline is also a very generic pattern which
can be used for content enrichment, but also for message
transformation and other use cases.
The content enricher pattern does handle the payloads itself by
sending both the InOut request and response along in a new element,
e.g. if you send <request><hello/></request> with the InOut exchange
and receive <result><message2/></result> you'll get a final message
that contains both of these like
<enricher><request><hello/></request><result><message2/></result></enricher>.
So the enricher is a very specific pattern, which will merge the
request and response messages from the InOut exchange into the
payload.
Does this make the distinction between the two of them a bit more clear?
Regards,
Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
2009/10/18 loboEsa <la...@gmail.com>:
>
> Thanks Johan for your answer.
>
> But I continue with my question about the difference betwen pipeline and
> enrichment, because enrichment do the same only that the In-Out MEP be used
> to add information to the content and pipeline doesn`t have this limitation,
> but only be a conceptual definition because as component in the In-Out
> transformer you can do wathewver you want, add, delete, sustitute
> information.
>
> In other words, if you use the same In-Only MEP and the same In-Out MEP as
> transformation in pipeline or enrichment you must have the same result .
>
> Or no?
>
>
>
>
> Johan Edstrom-3 wrote:
>>
>> The Pipeline component is a bridge between an In-Only (or Robust-In-
>> Only) MEP and an In-Out MEP. When the Pipeline receives an In-Only
>> MEP, it will send the input in an In-Out MEP to the tranformer
>> destination and forward the response in an In-Only MEP to the target
>> destination.
>>
>> On Oct 17, 2009, at 1:27 PM, loboEsa wrote:
>>
>>>
>>> What´s the difference between eip:pipeline and eip:enrichment ?
>>>
>>> For me, both receive InOnly message then send to InOut service to do
>>> something and the response be sent as InOnly service to continue
>>> with the
>>> flow.
>>>
>>> Where am I wrong?
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Pipeline-vs-Enrichment-tp25941125p25941125.html
>>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>>
>>
>> Johan Edstrom
>>
>> joed@opennms.org
>>
>> They that can give up essential liberty to purchase a little temporary
>> safety, deserve neither liberty nor safety.
>>
>> Benjamin Franklin, Historical Review of Pennsylvania, 1759
>>
>>
>>
>>
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Pipeline-vs-Enrichment-tp25941125p25949090.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
Re: Pipeline vs Enrichment
Posted by loboEsa <la...@gmail.com>.
Thanks Johan for your answer.
But I continue with my question about the difference betwen pipeline and
enrichment, because enrichment do the same only that the In-Out MEP be used
to add information to the content and pipeline doesn`t have this limitation,
but only be a conceptual definition because as component in the In-Out
transformer you can do wathewver you want, add, delete, sustitute
information.
In other words, if you use the same In-Only MEP and the same In-Out MEP as
transformation in pipeline or enrichment you must have the same result .
Or no?
Johan Edstrom-3 wrote:
>
> The Pipeline component is a bridge between an In-Only (or Robust-In-
> Only) MEP and an In-Out MEP. When the Pipeline receives an In-Only
> MEP, it will send the input in an In-Out MEP to the tranformer
> destination and forward the response in an In-Only MEP to the target
> destination.
>
> On Oct 17, 2009, at 1:27 PM, loboEsa wrote:
>
>>
>> What´s the difference between eip:pipeline and eip:enrichment ?
>>
>> For me, both receive InOnly message then send to InOut service to do
>> something and the response be sent as InOnly service to continue
>> with the
>> flow.
>>
>> Where am I wrong?
>>
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Pipeline-vs-Enrichment-tp25941125p25941125.html
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>
> Johan Edstrom
>
> joed@opennms.org
>
> They that can give up essential liberty to purchase a little temporary
> safety, deserve neither liberty nor safety.
>
> Benjamin Franklin, Historical Review of Pennsylvania, 1759
>
>
>
>
>
>
>
--
View this message in context: http://www.nabble.com/Pipeline-vs-Enrichment-tp25941125p25949090.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Pipeline vs Enrichment
Posted by Johan Edstrom <jo...@opennms.org>.
The Pipeline component is a bridge between an In-Only (or Robust-In-
Only) MEP and an In-Out MEP. When the Pipeline receives an In-Only
MEP, it will send the input in an In-Out MEP to the tranformer
destination and forward the response in an In-Only MEP to the target
destination.
On Oct 17, 2009, at 1:27 PM, loboEsa wrote:
>
> What´s the difference between eip:pipeline and eip:enrichment ?
>
> For me, both receive InOnly message then send to InOut service to do
> something and the response be sent as InOnly service to continue
> with the
> flow.
>
> Where am I wrong?
>
>
>
> --
> View this message in context: http://www.nabble.com/Pipeline-vs-Enrichment-tp25941125p25941125.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
Johan Edstrom
joed@opennms.org
They that can give up essential liberty to purchase a little temporary
safety, deserve neither liberty nor safety.
Benjamin Franklin, Historical Review of Pennsylvania, 1759