Effective October 27, 2012, online and email support for FuseSource products will move to Red Hat support channels. For more information, please see the JIRA Migration to Red Hat FAQ.
As of October 27th, please open all new issues in the Red Hat Customer Portal .
Issue Details (XML | Word | Printable)

Key: ESB-1630
Type: Documentation Documentation
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: Fintan Bolton
Reporter: Claus Ibsen
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
FUSE ESB

Mistake in Camel Content Enricher Example in the ESB docs

Created: 07/Feb/12 01:35 PM   Updated: 07/Feb/12 02:57 PM
Component/s: Documentation
Affects Version/s: 4.4.1-fuse-01-20
Fix Version/s: None


 Description  « Hide
See this page
http://fusesource.com/docs/esb/4.2/eip/MsgTran-Enricher.html

Which is also presented in the latest
http://fusesource.com/docs/esb/4.4.1/camel_eip/MsgTran-Enricher.html

The example which sets a header before calling contentEnrich is wrong, eg
from("activemq:queue:order")
.setHeader(Exchange.FILE_NAME, header("orderId"))
.pollEnrich("file://order/data/additional")
.to("bean:processOrder");

This is not currently support in Camel. The ASF camel docs has this warning

Data from current Exchange not used
pollEnrich does not access any data from the current Exchange which means when polling it cannot use any of the existing headers you may have set on the Exchange. For example you cannot set a filename in the Exchange.FILE_NAME header and use pollEnrich to consume only that file. For that you must set the filename in the endpoint URI.

There is a JIRA ticket to improve this in the future
https://issues.apache.org/jira/browse/CAMEL-4163



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Fintan Bolton added a comment - 07/Feb/12 02:57 PM
FIxed the doc source for the Camel EIP guide. This fix will go out in the next release.