Thanks,Claus.I was able to get rid of this bug by placing the endpoint Uri on
the camel context inside <simple> tags and then get this from the camel
header on the java class.
Eg.
<setHeader
headerName="comsumerUrl"><simple>file:${in.header.clientFileDir}?include=.*_BNYM_.*txt
&amp;move=${properties:data_home}/${file:onlyname.noext}-${date:now:yyyyMMddHHmm}.TXT</simple></setHeader>
 <to uri="bean:locatesConsumer?method=consumeFile" />

and on the locatesConsumer class:
String endPointUri=ex.getIn().getHeader("comsumerUrl", String.class);
        consumer.start();
        String body=consumer.receiveBody(endPointUri, 2000,String.class);
It works fine.
I have seen one minor issue for the move file parameter what I was thinking
that a copy of the camel File will be created with current timestamps inside
the data_home directory but infact a sub-directory is created with the
current timestamps and that contain the file(just been processed).
Claus,can you help regarding this issue.

Regards,
Sanjeev




--
View this message in context: 
http://camel.465427.n5.nabble.com/Unable-to-use-move-movefailed-and-donefilename-with-consumer-template-endpoint-Uri-tp5736913p5737202.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to