Hi,

If you modify the jboss-esb-unfiltered.xml file in the helloworld_ftp_action quickstart to use the following settings:

<?xml version = "1.0" encoding = "UTF-8"?>
<jbossesb xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.0.1.xsd" parameterReloadSecs="5">
 <providers>
 <ftp-provider name="FTPprovider" hostname="@FTP_HOSTNAME@" >
 <ftp-bus busid="helloFTPChannel" >
 <ftp-message-filter
 username="@FTP_USERNAME@"
 password="@FTP_PASSWORD@"
 passive="false"
 directory="@FTP_DIRECTORY@"
 input-suffix=".dat"
 work-suffix=".esbWorking"
 post-delete="false"
 post-suffix=".COMPLETE"
 error-delete="false"
 error-suffix=".HAS_ERROR"
 />
 </ftp-bus>
 </ftp-provider>

 <jms-provider name="JBossMessaging" connection-factory="ConnectionFactory">
 <jms-bus busid="quickstartEsbChannel">
 <jms-message-filter dest-type="QUEUE" dest-name="queue/quickstart_helloworld_ftp_esb"
 selector="source='fromHelloworldFTPAction'"/>
 </jms-bus>
 </jms-provider>

 <schedule-provider name="cronExample">
 <cron-schedule scheduleid="cron-schedule" cronExpression="0/5 * * * * ?"/>
 </schedule-provider>

 </providers>
 <services>
 <service
 category="myCategory"
 name="myFileListener"
 description="Hello World File Action (esb listener)" >
 <listeners>
 <ftp-listener name="FtpGateway"
 busidref="helloFTPChannel"
 is-gateway="true"
 scheduleidref="cron-schedule">
 <property name="composer-class" value="org.jboss.soa.esb.listeners.gateway.RemoteFileNameMessageComposer"/>
 </ftp-listener>
 <jms-listener name="helloWorldFileAction" busidref="quickstartEsbChannel" />
 </listeners>
 <actions mep="OneWay">
 <action name="action2" class="org.jboss.soa.esb.actions.SystemPrintln">
 <property name="printfull" value="true"/>
 </action>
 </actions>
 </service>
 </services>
</jbossesb>

Sorry my bad here. ..

The fs listener specifies the attribute 'post-rename' to stop the ESB from renaming it after it has processed the file. Processed in most cases consist of extracting the contents of the file, and packaging it into an ESB Message object.
But I just tried this and noticed that the 'post-rename' attribute is not available for the ftp-message-filter.
I'll create a JIRA for this. Sorry for misleading you

Regards,

/Daniel

The remote code is a specialisation of the local filesystem code so you may still be able to do this through properties.

I haven't tried this, so take it with as much salt as you wish, but try creating a property named 'postRename' and see if it is picked up.

The way I got around this (since our implementation will pull large files) is to create an FtpLocalFileNameMessageComposer and inject it into the ftp-listener config. RemoteFileNameMessageComposer is mostly worthless because it just gives you the path of the remote file and leaves it up to the action processing pipeline to do the downloading.

If you look at the default MessageComposer (RemoteFileMessageCompser), it does all of the downloading in the compose() method. Just make your own composer to download the file to a local directory and then return only the location of the local file. Of course, then you must do your own file management on the local side (delete after processed, etc), but it avoids huge memory consumption.

I'd give you the code, but it's not mine to give away and I actually like my job, so I'm hesitant to jeopardize. It shouldn't be difficult to modify the existing composer to do your bidding.