RouteDefinition.recipientList(...) post processing callback

[FuzzKat Media <fu...@gmail.com>]

Hi
I have a file route that sends a set of files (unix scripts) to many
servers. This one to many is achieved via the

RouteDefinition.recipientList(property(TO_FILE_COMPONENT_URI))

with the TO_FILE_COMPONENT_URI containing the array of to URIs (each
pointing to the NAS location for the particular server)

All works fine, except I need to be able to do 'post' processing on
the destination files - in this case a chmod 700
/the/path/to/the/destination/script

I can't see a callback inteface on the producer side of the File component.

I could write a Processor to do all the files after they are written
by recipientList(...), but would prefer to just configure via the out
URI query string.

any thoughts, ideas welcome.

thanks in advance
steve

Re: RouteDefinition.recipientList(...) post processing callback

[Claus Ibsen <cl...@gmail.com>]

Hi

You can have 2 recipient lists

The first for the file endpoint
And the 2nd for the custom chmod

But I guess you want one recipient list, and have 2 endpoints grouped.
But this is currently not supported.

On Mon, Apr 29, 2013 at 2:35 PM, FuzzKat Media <fu...@gmail.com> wrote:
> Hi
> I have a file route that sends a set of files (unix scripts) to many
> servers. This one to many is achieved via the
>
> RouteDefinition.recipientList(property(TO_FILE_COMPONENT_URI))
>
> with the TO_FILE_COMPONENT_URI containing the array of to URIs (each
> pointing to the NAS location for the particular server)
>
> All works fine, except I need to be able to do 'post' processing on
> the destination files - in this case a chmod 700
> /the/path/to/the/destination/script
>
> I can't see a callback inteface on the producer side of the File component.
>
> I could write a Processor to do all the files after they are written
> by recipientList(...), but would prefer to just configure via the out
> URI query string.
>
> any thoughts, ideas welcome.
>
> thanks in advance
> steve



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen