commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary D. Gregory (Resolved) (JIRA)" <>
Subject [jira] [Resolved] (VFS-382) SFTP getChildren() does not fail when called on a file
Date Wed, 09 Nov 2011 23:01:51 GMT


Gary D. Gregory resolved VFS-382.

       Resolution: Fixed
    Fix Version/s: Nightly Builds
         Assignee: Gary D. Gregory

Committed revision 1200015.
> SFTP getChildren() does not fail when called on a file
> ------------------------------------------------------
>                 Key: VFS-382
>                 URL:
>             Project: Commons VFS
>          Issue Type: Bug
>    Affects Versions: Nightly Builds
>         Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500)
> Maven home: C:\Java\apache-maven-3.0.3\bin\..
> Java version: 1.6.0_29, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files\Java\jdk1.6.0_29\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>            Reporter: Gary D. Gregory
>            Assignee: Gary D. Gregory
>             Fix For: Nightly Builds
>         Attachments: vfs-382.diff
> SFTP test testChildren(org.apache.commons.vfs2.test.ContentTests) fails
> I've tried this with *Apache SSHd* and *Bitvise WinSSHD* and I get the same failure.
> The test {{org.apache.commons.vfs2.test.ContentTests}} asks for the children ({{getChildren()}})
of a {{file1.txt}} file (not a folder) and does not fail.
> The test expects the {{getChildren()}} method to throw an exception.
> Instead, it returns one file, file1.txt itself.
> Under the covers, we do a "ls file1.txt", which returns "file1.txt".
> It looks like [VFS-210] was an effort to optimize and reduce roundtrips but it may have
broken this code.
> Thoughts on fixing this?
> In {{org.apache.commons.vfs2.provider.sftp.SftpFileObject.doListChildrenResolved()}}?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message