A content enricher is a pattern for augmenting a message with missing information. The ServiceMix EIP content enricher is more or less equivalent to a pipeline that adds missing data as the message passes through an enricher target. Consequently, when migrating to FUSE Mediation Router, you can re-implement the ServiceMix content enricher as a FUSE Mediation Router pipeline.
The following example shows how to define a content enricher using the ServiceMix EIP
component. Incoming messages pass through the enricher target,
test:additionalInformationExtracter, which adds some missing data to the
message before the message is sent on to its ultimate destination,
test:myTarget.
<eip:content-enricher service="test:contentEnricher" endpoint="endpoint">
<eip:enricherTarget>
<eip:exchange-target service="test:additionalInformationExtracter" />
</eip:enricherTarget>
<eip:target>
<eip:exchange-target service="test:myTarget" />
</eip:target>
</eip:content-enricher>The following example shows how to define an equivalent route using FUSE Mediation Router XML configuration:
<route> <from uri="jbi:endpoint:http://progress.com/demos/test/contentEnricher/endpoint"/> <to uri="jbi:service:http://progress.com/demos/test/additionalInformationExtracter"/> <to uri="jbi:service:http://progress.com/demos/test/myTarget"/> </route>
The following example shows how to define an equivalent route using the FUSE Mediation Router Java DSL:
from("jbi:endpoint:http://progress.com/demos/test/contentEnricher/endpoint").
to("jbi:service:http://progress.com/demos/test/additionalInformationExtracter").
to("jbi:service:http://progress.com/demos/test/myTarget");