Add support for Mule 3.4

[GoogleCodeExporter]

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.

Original issue reported on code.google.com by hakan.d...@gmail.com on 6 May 2013 at 1:16

• Blocked on: #357

[GoogleCodeExporter]

Initial tests show that there are some backwards-compatibility issues we need 
to deal with:

The integration tests are failing (in the generated onewaySA-mule340 
integration-component) for:
-----
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)

Tests run: 88, Failures: 14, Errors: 0, Skipped: 0
-----

Original comment by hakan.d...@gmail.com on 6 May 2013 at 1:34

[GoogleCodeExporter]

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)

Original comment by hakan.d...@gmail.com on 6 May 2013 at 1:36

[GoogleCodeExporter]

For testSftpToFtp_ok: removing the inbound filename filter:
  <file:filename-wildcard-filter pattern="*.*"/>
together with using absolute path for inbound-dir makes it work.

Original comment by hakan.d...@gmail.com on 10 Jun 2013 at 9:03

[GoogleCodeExporter]

This issue was updated by revision r2054.

Adding pom-dependencies for Mule 3.4

Original comment by hakan.d...@gmail.com on 13 Jun 2013 at 10:22

[GoogleCodeExporter]

Original comment by hakan.d...@gmail.com on 4 Nov 2013 at 10:23

• Now blocked on: #357

[GoogleCodeExporter]

Original comment by hakan.d...@gmail.com on 23 Feb 2014 at 3:32

• Added labels: Milestone-Release0.6.1
• Removed labels: Milestone-Release0.7.0

[GoogleCodeExporter]

SFTP problems relates to these changes in Mule:
 * http://www.mulesoft.org/jira/browse/MULE-6197
 * https://www.mulesoft.org/jira/browse/MULE-6858
 * https://www.mulesoft.org/jira/browse/MULE-6863

Original comment by hakan.d...@gmail.com on 23 Feb 2014 at 3:42

[GoogleCodeExporter]

For File and FTP, the originalFilename-property has changed scope from outbound 
to inbound, se:
 * http://www.mulesoft.org/documentation/display/current/Mule+ESB+3.4.0+Release+Notes#MuleESB3.4.0ReleaseNotes-File,FTP,andSMTPOutboundProperties
 * https://www.mulesoft.org/jira/browse/MULE-6743
 * https://www.mulesoft.org/jira/browse/MULE-6858

Original comment by hakan.d...@gmail.com on 24 Feb 2014 at 9:44

[GoogleCodeExporter]

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.

Original comment by hakan.d...@gmail.com on 24 Feb 2014 at 12:51

[GoogleCodeExporter]

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 comment by hakan.d...@gmail.com on 24 Feb 2014 at 3:58

[GoogleCodeExporter]

Remaining SFTP-problems moved to separate issue 367.
We need to figure out how to handle the incompability introduced with Mule 
3.4.0.

Original comment by hakan.d...@gmail.com on 24 Feb 2014 at 4:20

[GoogleCodeExporter]

Original comment by hakan.d...@gmail.com on 24 Feb 2014 at 4:30

• Changed state: Fixed
• Added labels: BackwardCompatibility-MinorChange, Type-Enhancement
• Removed labels: BackwardCompatibility, Type-Review