ASCII mode does not work for SFTP endpoint in Camel

Solution Verified - Updated -


Endpoint is defined with binary=false option, sample:

<to uri="sftp://<hostname>/OUT?username=username&password=xxx&fileName=file.txt&autoCreate=true&binary=false"/>

The result file still contains the same line ending symbols (CRLF for Windows or CR for Unix based systems) as in the source file, i.e. it was not replaced by platform specific line ending symbols for the destination.


JBoss Fuse 6.3.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In