[ 
https://issues.apache.org/jira/browse/CAMEL-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13692901#comment-13692901
 ] 

Aki Yoshida commented on CAMEL-6335:
------------------------------------

Bengt,
The assumption is, if your ftp server requires stepwise traversal, you will 
anyway need access right to the segment you traverse.

While going down the path from the starting point using stepwise traversal, you 
can certainly go up stepwise to the starting point because you have accessed 
those segment before. The original stepwise traveral jumped to the root while 
going back and from there going down to the starting point. This can touch the 
segment outside of the previously accessed segment and resulted in the access 
error mentioned. And as I mentioned in my previous comment, this code must be 
skipped if the path is at the root but otherwise, it is needed.

regards, aki

                
> Sftp cannot change to parent directory in a stepwise fashion
> ------------------------------------------------------------
>
>                 Key: CAMEL-6335
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6335
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-ftp
>    Affects Versions: 2.9.4, 2.9.5, 2.9.6, 2.9.7, 2.10.2, 2.10.3, 2.10.4, 
> 2.11.0
>            Reporter: Bengt Rodehav
>         Attachments: SftpOperations.java.patch
>
>
> The problem occurs when using the sftp protocol with the stepwise option 
> enabled and when polling a subdirectory.
> When Camel has finished polling the subdirectory, it attempts to change 
> directory back to the home directory in a stepwise fashion: Doing "cd .." one 
> step at a time. This logic has a bug that causes it to try to change to a 
> non-existing directory.
> This has been discussed on the user mailing list:
> http://mail-archives.apache.org/mod_mbox/camel-users/201305.mbox/%3CCAJ0TPGJ6gdaEuYgjpKG42HR-ozbyC0e5Z=mi2xrdmnonbty...@mail.gmail.com%3E

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to