What's New

24/03/25 New Mule Connector 2.2.0

As part of the connector update for Java 17, we have introduced real data streaming capabilities. This enhancement allows for the transmission of unlimited data without encountering out-of-memory exceptions. For instance, it is now possible to download a 10GB file and send it back to AFT seamlessly. This streaming mode can be activated in the connection configuration, where you can also set the buffer size for data transfer.

We have implemented several changes that will affect existing workflows, driven by the Mule guidelines for connectors and the modifications mentioned above.

1. The pickup source operation has been renamed to <code>mft:file-pickup-listener</code>. This change means that when customers upgrade to the new version, they will need to update their pickup operation within their workflow. They can achieve this by editing the XML file to replace the <code>mft:file-pickup-source</code> element with <code>mft:file-pickup-listener</code>.

2. The dropoff operation now returns file details as a payload. Previously, we provided a data stream as the payload and included dropoff file details as attributes. However, this approach caused issues when using streaming and did not conform to our coding guidelines. We believe this change will not adversely affect any workflows.

   In cases where it is necessary to retain the payload after the dropoff operation, you can redirect the dropoff payload to a variable. This way, the original payload will remain intact and can be reused. This feature may prove beneficial in scenarios such as:

   <file read> -data stream--> <dropoff> - data stream---> <file write>

   In this example, the dropoff operation will, by default, overwrite the payload with the dropoff file details (including filename, filesize, and filecode). However, by redirecting the dropoff output to a variable, you can ensure that the original payload is still available for use in the file write operation.