Closed hdahl closed 9 years ago
Comment #1 originally posted by soi-toolkit on 2013-05-06T13:34:37.000Z:
Initial tests show that there are some backwards-compatibility issues we need to deal with:
Failed tests: testSftpToFtp_ok(org.soitoolkit.tool.generator.onewaysamule340.sftptoftp.SftpToFtpIntegrationTest) testJdbcToSftp_ok(org.soitoolkit.tool.generator.onewaysamule340.jdbctosftp.JdbcToSftpIntegrationTest) testSftpToJms_ok(org.soitoolkit.tool.generator.onewaysamule340.sftptojms.SftpToJmsIntegrationTest) testFtpToFile_ok(org.soitoolkit.tool.generator.onewaysamule340.ftptofile.FtpToFileIntegrationTest) testSftpToFile_ok(org.soitoolkit.tool.generator.onewaysamule340.sftptofile.SftpToFileIntegrationTest) testSftpToJdbc_ok(org.soitoolkit.tool.generator.onewaysamule340.sftptojdbc.SftpToJdbcIntegrationTest) testSftpToVm_ok(org.soitoolkit.tool.generator.onewaysamule340.sftptovm.SftpToVmIntegrationTest) testJmsToSftp_ok(org.soitoolkit.tool.generator.onewaysamule340.jmstosftp.JmsToSftpIntegrationTest) testFtpToFtp_ok(org.soitoolkit.tool.generator.onewaysamule340.ftptoftp.FtpToFtpIntegrationTest) testHttpToSftp_ok(org.soitoolkit.tool.generator.onewaysamule340.httptosftp.HttpToSftpIntegrationTest) testSftpToSftp_ok(org.soitoolkit.tool.generator.onewaysamule340.sftptosftp.SftpToSftpIntegrationTest) testFileToSftp_ok(org.soitoolkit.tool.generator.onewaysamule340.filetosftp.FileToSftpIntegrationTest) testVmToSftp_ok(org.soitoolkit.tool.generator.onewaysamule340.vmtosftp.VmToSftpIntegrationTest) testFtpToSftp_ok(org.soitoolkit.tool.generator.onewaysamule340.ftptosftp.FtpToSftpIntegrationTest)
Comment #2 originally posted by soi-toolkit on 2013-05-06T13:36:34.000Z:
For testSftpToFtp_ok the integration test fails to write the input-testfile to the SFTP-inbound endpoint due to changes in SftpClient for overwrite-handling: http://www.mulesoft.org/jira/browse/MULE-6197 Temporarily changing inbound path to an absolute path (instead of using ~ for the home dir) overcomes the problem, needs further investigation.
Next the test fails with: Stacktrace=org.mule.api.routing.filter.FilterUnacceptedException: Message has been rejected by filter. Message payload is of type: SftpFileArchiveInputStream at org.mule.routing.MessageFilter.filterUnacceptedException(MessageFilter.java:100) at org.mule.processor.AbstractFilteringMessageProcessor.handleUnaccepted(AbstractFilteringMessageProcessor.java:62)
Comment #3 originally posted by soi-toolkit on 2013-06-10T09:03:00.000Z:
For testSftpToFtp_ok: removing the inbound filename filter:
together with using absolute path for inbound-dir makes it work.
Comment #4 originally posted by soi-toolkit on 2013-06-13T10:22:12.000Z:
This issue was updated by revision r2054.
Adding pom-dependencies for Mule 3.4
Comment #5 originally posted by soi-toolkit on 2013-11-04T22:23:04.000Z:
<empty>
Comment #6 originally posted by soi-toolkit on 2014-02-23T15:32:35.000Z:
<empty>
Comment #7 originally posted by soi-toolkit on 2014-02-23T15:42:03.000Z:
SFTP problems relates to these changes in Mule:
Comment #8 originally posted by soi-toolkit on 2014-02-24T09:44:02.000Z:
For File and FTP, the originalFilename-property has changed scope from outbound to inbound, se:
Comment #9 originally posted by soi-toolkit on 2014-02-24T12:51:31.000Z:
This issue was updated by revision r2126.
RequestResponse-generator tests failing for 3.4.0 due to errors like: java.lang.NoClassDefFoundError: org/apache/xml/serializer/ExtendedContentHandler
Fixed by adding dependency to xalan:serializer in 3.4.0-dependencies pom.
Comment #10 originally posted by soi-toolkit on 2014-02-24T15:58:35.000Z:
This issue was updated by revision r2127.
Fixed config for failing tests: testFtpToFile_ok testFtpToFtp_ok
Migration task for: FTP-File, FTP-FTP when upgrading from Mule 3.3 to Mule 3.4: in outbound endpoint, change from: outputPattern="#[header:originalFilename]" to: outputPattern="#[header:INBOUND:originalFilename]"
Original issue 339 created by soi-toolkit on 2013-05-06T13:16:14.000Z:
We probably need to make a release branch for soi-tk 0.6.x before upgrading trunk to version 0.7.0-SNAPSHOT for Mule 3.4.
First step for 3.4 is to add a 3.4-dependencies-pom file and run through the integration testsuite to see if there are backwards-compatibility issues.