Skip to content

Commit 57a5cbb

Browse files
committed
no message
1 parent db2791b commit 57a5cbb

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

Diff for: README.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -138,10 +138,10 @@ To install and test, assuming that you have previously run the "Camel Route with
138138

139139
4. Copy the following files and notice the new behaviours in the second and third cases, in terms of the registerCall queue and the REPORT.T_INCIDENT table:
140140

141-
- camel-persistence-part2/data/csv-one-record-allok.txt to $SERVICEMIX_HOME/datainsert --> record written in table, new message on registerCall queue
142-
- camel-persistence-part2/data/csv-one-record-failjms-dbok.txt to $SERVICEMIX_HOME/datainsert --> NO record written in table, NO new message on registerCall queue
143-
- camel-persistence-part2/data/csv-one-record-jmsok-faildb.txt to $SERVICEMIX_HOME/datainsert --> NO record written in table, NO new message on registerCall queue
144-
- camel-persistence-part2/data/csv-one-record-failjms-faildb.txt to $SERVICEMIX_HOME/datainsert --> NO record written in table, NO new message on registerCall queue
141+
- camel-persistence-part2/data/csv-one-record-allok.txt to $SERVICEMIX_HOME/datainsert --> record written in table, new message on registerCall queue
142+
- camel-persistence-part2/data/csv-one-record-failjms-dbok.txt to $SERVICEMIX_HOME/datainsert --> NO record written in table, NO new message on registerCall queue
143+
- camel-persistence-part2/data/csv-one-record-jmsok-faildb.txt to $SERVICEMIX_HOME/datainsert --> NO record written in table, NO new message on registerCall queue
144+
- camel-persistence-part2/data/csv-one-record-failjms-faildb.txt to $SERVICEMIX_HOME/datainsert --> NO record written in table, NO new message on registerCall queue
145145

146146
# Idempotent example
147147

@@ -179,9 +179,9 @@ To install and test, assuming that you have previously run the "Camel Route with
179179
>>> (file-to-queue) from(timer://demo?period=2000&repeatCount=15) --> ref:users method: getUser <<< Pattern:InOnly, Headers:{breadcrumbId=ID-biker-chm-local-53796-1322044729997-0-5, firedTime=Wed Nov 23 11:38:53 CET 2011}, BodyType:null, Body:[Body is null]
180180
>>> (file-to-queue) ref:users method: getUser --> aggregate <<< Pattern:InOnly, Headers:{firedTime=Wed Nov 23 11:38:53 CET 2011, id=FUSE, breadcrumbId=ID-biker-chm-local-53796-1322044729997-0-5}, BodyType:String, Body:Raul,
181181

182-
6) Verify that a blob object exist in the DB
182+
6. Verify that a blob object exist in the DB
183183
SELECT * FROM AGGREGATIONREPO1
184-
7) Restart camel route and verify that aggregation process continues
184+
7. Restart camel route and verify that aggregation process continues
185185

186186

187187

0 commit comments

Comments
 (0)