commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "mohan pindyala (Commented) (JIRA)" <>
Subject [jira] [Commented] (VFS-182) Usage of FTP with heterogene FTP server (possibility of using Ascii file type)
Date Tue, 22 Nov 2011 21:58:40 GMT


mohan pindyala commented on VFS-182:

Hi Magnus,
    we are trying to use common-vfs for doing sftp tasks.

Our  sftp server is windows based.
Client is a java module which will grab text files from  linux server and using sftp we want
to transfer these text files to windows ftp.

All we need is when we transfer end of line(EOL) character should be take care.  UNIX LR character
should be converted to CRLF for windows.

We searched all over but there was no concrete answer on how to set in common-vfs so that
it takes care of these characters.

Can you point me to the right locations or source code sample which does this?

> Usage of FTP with heterogene FTP server (possibility of using Ascii file type)
> ------------------------------------------------------------------------------
>                 Key: VFS-182
>                 URL:
>             Project: Commons VFS
>          Issue Type: Improvement
>         Environment: Mainframe BULL GCOS8
>            Reporter: Christian Bastin
>         Attachments: vfs-182_allow_ascii_file_type.diff
> Using VFS with ftpServer on Mainframe Bull.  I need the posibility to set the file type
to Ascii.   The navigation in the directory and the filesystem work properly but the accessing
of a data file is not possible.  
> I saw that the FtpClienFactory allways set the file type to binary, is it possible to
give an external parameter, ..
> FtpClienFactory :
> ....
>          // Set binary mode
>                 if (!client.setFileType(FTP.BINARY_FILE_TYPE))
>                 {
>                     throw new FileSystemException("vfs.provider.ftp/set-binary.error",
>                 }
> ...
> Christian Bastin.

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