camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bengt Rodehav <>
Subject sftp "broken" in Camel 2.5
Date Wed, 03 Nov 2010 08:31:32 GMT
I have been using Camel 2.4 for sftp up until now. For several excellent
reasons I now want to upgrade to Camel 2.5 but it seems that the sftp
support has been "broken" - or at least it has changed from the previous
version. I have seen posts about the sftp changes on this list but I haven't
tested the changes until now (which I of course should have).

I've read the following thread
try to understand what has been done. However, the thread isn't that easy to
follow and I need to know:

1. What was the problem in the first place?
2. What has been changed in Camel 2.5 compared to 2.4?
3. What is not backwards compatible?

My attempt to understand this lead me to the following answers (please
correct me if I'm wrong):

1. Some server(s) do not allow retrieval of files from other directories
than the working directory.

2. Camel now changes directory before retrieving the file and it does so in
a "stepwise" manner.

3. Presently I know that my sftp test against Serv-U (on Windows) doesn't
work. I'll elaborate a little bit about what seem to happen:

First of all, I haven't yet tested to GET files just to PUT them. Regardless
if I'm using a relative path  like


or an absolute path like


I always get

Cannot change directory to: /*

If I change a setting in Serv-U to "lock user in home directory" (which is
not the default), then Serv-U will translate "/" to the home directory and
it will work. However, I need to support situations where "/" is not
automatically translated to the home directory since this is very server
dependent. Currently I can't seem to do that. Without having looked at the
source code yet, it seems like Camel is always changing directory to "/"
before doing anything else. Why is that?

Note that since Serv-U is running on Windows, when not "locking the user to
home directory", the absolute path "/" doesn't even exist. When using
Filezilla (client) to access Serv-U I notice that the syntax it uses for
changing directory (if I ask it to) is:


The topmost directory that can be "changed to" is


Since Camel now seems to always start by changing to "/" it will never
succeed. Don't know if this is specific to Serv-U or of Windows sftp servers
in general.

A couple of comments:

- If some servers need to change the directory before retrieving (or
putting) files, then the behavior must be configurable since there will also
be servers that will not allow you to change the directory in this way. When
choosing between behaviors, go with what is already supported otherwise
existing applications will break. New behavior is best supported by adding
additional configuration options.

- If a change of directory scheme is to be supported, then it must be
configurable whether to change the directory in "one go" or "stepwise"
(first to the top, then to the next level and so on). "The top" isn't always

- I don't see how to use a relative path (which I have been doing before).
Even if I specify a relative path, Camel will try to change the directory to
"/" anyway. This is a backwards incompatible change. Is there a workaround I
can use if I upgrade to Camel 2.5?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message