Yeah, great work on all the improvements to the file component Claus. I
think it will warrant a blog post of its own when Camel 2.0 comes out :)
Not sure about this suggestion though... I kinda like having defaults in
place so you don't always have to provide configuration. Like, having a
default file name generated is great for testing purposes or for new users
just trying Camel out. Also maybe the file component may be used to drop
files off for processing by some other application which may not care about
the filename, just the contents.
Well, I don't have any big reasons to not go forward with this... these are
just my pre-coffee thoughts :)
Also I'm fine with removing ignoreFileNameHeader.
On Fri, Jan 30, 2009 at 3:14 AM, Claus Ibsen <claus.ib...@gmail.com> wrote:
> Hi
>
> As some of you know the file component have had a major refactor ...
> actually you can nearly consider it as a rewrite in Camel 2.0.
>
> This mail is about a few remaining issues I want to give a heads up
> upon and feedback:
>
>
> Force a filename to be provided when wring a file
> ====================================
>
> I want to force file producer always requiring a header value with the
> filename to write.
> What we have in Camel 1.x is that if no filename header is provided it
> will fallback to use the message id as the filename.
>
> For me that has no use, as its kinda like telling a database here is
> some data store it somewhere, without providing, schema, table, column
> names.
>
> So I want it to reject writing a file and report an exception that the
> filename is missing.
>
> The file language supports you if you want to use the message id as
> the filename. Just set the header value as: ${id}
>
> And also remove option: ignoreFileNameHeader
>
>
> Thoughts?
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
>
--
Cheers,
Jon
http://janstey.blogspot.com/
