RemoteFileSystemFactory should also support ConfigTree ------------------------------------------------------ Key: JBESB-3486 URL: https://jira.jboss.org/browse/JBESB-3486 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.9, 4.4 CP4, 4.8, 4.7 CP2, 4.7 CP1, 4.7, 4.6 Reporter: Joakim Sandstroem org.jboss.soa.esb.util.RemoteFileSystemFactory only supports FTPEpr, it should also provide a factory method that takes a ConfigTree - The configuration tree can then contain RemoteFileSystem.PARMS* Provides: 1. cleaner configuration using separate properties 2. support for directories directly under the user home folder (applies to sftp, issue below) Issue: 1. use the original RemoteFileSystemFactory and provide sftp://sftp-user:pwd@sftp.server/test-dir as the ftp epr 2. test-dir resides directly in the sftp-user home directory 3. try to upload a file to this directory -> You get the following exception: Caused by: org.jboss.soa.esb.util.RemoteFileSystemException: 2: No such file at org.jboss.internal.soa.esb.util.SecureFtpImpl.uploadFile(SecureFtpImpl.java:578) at fi.barona.esb.integration.sonet.Sonet.sendFile(Sonet.java:142) ... 14 more Caused by: 2: No such file at com.jcraft.jsch.ChannelSftp.throwStatusError(ChannelSftp.java:2291) at com.jcraft.jsch.ChannelSftp._realpath(ChannelSftp.java:1824) at com.jcraft.jsch.ChannelSftp.cd(ChannelSftp.java:263) at org.jboss.internal.soa.esb.util.SecureFtpImpl.uploadFile(SecureFtpImpl.java:548) ... 15 more The above exception occurs because jsch (sftp) does not recognize that the test-dir resides directly in the user home folder, the path should be test-dir, not /test-dir -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira