[ http://jira.jboss.com/jira/browse/JBESB-1525?page=all ] Daniel Bevenius updated JBESB-1525: ----------------------------------- Summary: Create a quickstart that demonstrates handling huge files (via ftp) (was: Create a quickstart that demonstrates handling huge file (via ftp)) Description: This quickstart will configure an FTP provider to pickup a file, have a custom MessageComponer that does not put the content of the file into the ESB Message object, but instead puts the path to the file in the message body or as a message property. The action pipeline will consist of a Smooks transformation with a FileRouter, which will append the output of the transformation to a new file. Once the transformation has been performed an ftp notifier or a file router will be used to send the file to a target destination. This will be possible after the upgrade to Smooks version 1.0 (SAX support and FileRouter) The intent of this quickstart is to demonstrate that the ESB can handle large file without causing memory issues while processing. This might require a minor update to the AbstractFileGateway to ensure that the gateway does not distribute the call to the listener on another node. It must stay on the same node if there is not network file system in place, as the file would not exist on the other node. was: This quickstart will configure an FTP provider to pickup a file, have a custom MessageComponer that does not put the content of the file into the ESB Message object, but instead puts the path to the file in the message body or as a message property. The action pipeline will consist of a Smooks transformation with a FileRouter, which will append the output of the transformation to a new file. Once the transformation has been performed an ftp notifier or a file router will be used to send the file to a target destination. This will be possible after the upgrade to Smooks version 1.0 (SAX support and FileRouter) The intent of this quickstart is to demonstrate that the ESB can handle large file without causing memory issues while processing. This might require a minor update to the AbstractFileGateway to ensure that the gateway does not distribute the call to the listener on another node. It must stay on the same node if there is not network file system in place, as the file would not exist on the other node. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira