On Tue, Dec 11, 2012 at 11:02 AM, hefiso
<henrik.filtenborg.soren...@gmail.com> wrote:
> Hi Preben
>
> Thanks for the workaround! Indeed, using
>
> <setProperty
> propertyName="CHARSET_NAME"><constant>iso-8859-1</constant></setProperty>
>
> makes the FTP-producer respect the requested charset.
>
> However, I think the best solution is to make the FTP-component behave just
> like File2 so it is possible to specify an encoding directly on the
> endpoint ("?charset=iso-8859-1").
>
Yeah its best if ftp/file works the same.
Feel free to log a JIRA.
And as always we love contributions
http://camel.apache.org/contributing.html
> Best Regards
> Henrik
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Problem-w-FTP-producer-and-charset-tp5723604p5723897.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
