cloudtrends / soi-toolkit

Automatically exported from code.google.com/p/soi-toolkit
1 stars 0 forks source link

Add support for Mule ESB 3.5 #378

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
v3.5.0 and v3.5.1 are available in the open source repo:
https://repository-master.mulesoft.org/releases/

Steps:
1. Add dependencies
2. Run generator tests
3. Review details in release notes (should we modify/improve something?)

Original issue reported on code.google.com by hakan.d...@gmail.com on 22 Sep 2014 at 7:04

GoogleCodeExporter commented 9 years ago
Initial tests indicates problem with 13 of the 88 one-way testst when upgrading 
to 3.5.0:

Failed tests: 
  testSftpToJms_ok(org.soitoolkit.tool.generator.onewaysamule350.sftptojms.SftpToJmsIntegrationTest)
  testFileToVm_ok(org.soitoolkit.tool.generator.onewaysamule350.filetovm.FileToVmIntegrationTest)
  testSftpToJdbc_ok(org.soitoolkit.tool.generator.onewaysamule350.sftptojdbc.SftpToJdbcIntegrationTest)
  testFileToSftp_ok(org.soitoolkit.tool.generator.onewaysamule350.filetosftp.FileToSftpIntegrationTest)
  testSftpToFile_ok(org.soitoolkit.tool.generator.onewaysamule350.sftptofile.SftpToFileIntegrationTest)
  testFileToFile_ok(org.soitoolkit.tool.generator.onewaysamule350.filetofile.FileToFileIntegrationTest)
  testFileToFtp_ok(org.soitoolkit.tool.generator.onewaysamule350.filetoftp.FileToFtpIntegrationTest)
  testFtpToSftp_ok(org.soitoolkit.tool.generator.onewaysamule350.ftptosftp.FtpToSftpIntegrationTest)
  testSftpToSftp_ok(org.soitoolkit.tool.generator.onewaysamule350.sftptosftp.SftpToSftpIntegrationTest)
  testSftpToVm_ok(org.soitoolkit.tool.generator.onewaysamule350.sftptovm.SftpToVmIntegrationTest)
  testFileToJms_ok(org.soitoolkit.tool.generator.onewaysamule350.filetojms.FileToJmsIntegrationTest)
  testSftpToFtp_ok(org.soitoolkit.tool.generator.onewaysamule350.sftptoftp.SftpToFtpIntegrationTest)
  testFileToJdbc_ok(org.soitoolkit.tool.generator.onewaysamule350.filetojdbc.FileToJdbcIntegrationTest)

Tests run: 88, Failures: 13, Errors: 0, Skipped: 0

Original comment by magnus.l...@gmail.com on 24 Sep 2014 at 3:02

GoogleCodeExporter commented 9 years ago
Tests for oneway-robust and request-resposne seems to passed without any issues 
on 3.5.0

Original comment by magnus.l...@gmail.com on 24 Sep 2014 at 3:35

GoogleCodeExporter commented 9 years ago
File inbound-endpoint seems to miss INBOUND scope in the following line:
  moveToPattern="#[header:originalFilename]"

Removes 5 of the 13 errors, 8 sftp related failures to go...

Original comment by magnus.l...@callistaenterprise.se on 10 Oct 2014 at 9:53

GoogleCodeExporter commented 9 years ago
Sftp-output endpoints seems to miss the original-filename when the processing 
pass the vm-endpoint, e.g. the original filename is not passed along 
automatically over the vm - protocol (since when, did this work in 3.4/3.3???)

Adding the following <set-property> before the <vm:outbound-endpoint> to 
explicitly moving the property to the outbound seems to fix the problem:

       <set-property propertyName="originalFilename"
          value="#[header:INBOUND:originalFilename]"
          doc:name="Propagate originalFilename to outbound" />
       <vm:outbound-endpoint connector-ref="soitoolkit-vm-connector" path="sftpToSftp-service" />

Original comment by magnus.l...@callistaenterprise.se on 11 Oct 2014 at 6:33

GoogleCodeExporter commented 9 years ago
Running tests on the sftp-inbound endpoints under Mule 3.5.0 seems to confuse 
it for where to look for files in some way...

See the following log for an example:

2014-10-11 09:01:15,949 WARN  [soitoolkit-sftp-connector.dispatcher.01] 
org.mule.transport.sftp.SftpClient - listing files for: 
/~/sftp/sftptofile/inbound/64b903c0-5114-11e4-9864-0a0027000000.dat
2014-10-11 09:01:15,951 ERROR [soitoolkit-sftp-connector.dispatcher.01] 
org.mule.transport.sftp.SftpMessageDispatcher - Unexpected exception attempting 
to write file, message was: /sftp/sftptofile/inbound
java.io.IOException: /sftp/sftptofile/inbound

It is configured to look for files in the home-folder but looks in the 
root-folder and naturally then fails on permission problems.

SFTPTOFILE_INBOUND_SFTP_FOLDER=${SOITOOLKIT_SFTP_USERNAME}@localhost:2222/~/sftp
/sftptofile/inbound

Manually creating the folders /sftp/sftptofile/inbound and assigning proper 
permissions to sftp-user resolves the problem but that is of course an 
unacceptable workaround...

Needs to look into this...

Original comment by magnus.l...@gmail.com on 11 Oct 2014 at 7:13