Example for pluggable FileProcessStrategy

[OrackBahama <jd...@metadok.de>]

Hi,

I have to process files that always come in pairs with the camel file
component:

00001.xml
00001.pdf
00002.xml
00002.pdf

The xml file will be grabbed transformed and jaxb'd - the pdf file only
attached to a message.
This works fine with an aggregator (unfortunately two polling endpoints
required :-() or alternatively, through attachments.

Nevertheless, I need to move (or moveFailed) *both* files (in sync) to a
backup or error directory after completion.
The camel GenericFileExpressionRenamer is under suspect to be the right
class for overwrites/ extension/modification, but I have absolutely no clue
on how and what to inherit/implement/copy to keep absolutely same bahavior -
and only replace the renaming strategy.

Does anybody know of an example (yes, I know there is a parameter ;-)) how
to plug a homemade FileProcessStrategy or Renamer into the file endpoint ?
Would you agree, that this is the right way - or is something easier out
there ?
Thanks in advance ....
  



--
View this message in context: http://camel.465427.n5.nabble.com/Example-for-pluggable-FileProcessStrategy-tp5735177.html
Sent from the Camel - Users mailing list archive at Nabble.com.