Thanks for the tip about the binaryFileMarshaler. I didn't realize you could do it that way.
As for the memory usage: I was assuming that at some point the entire file would be read into memory. If this is not the case, it should not be a problem. -- Allan gnodet wrote: > > Currently, the same pattern as for lightweight components can be > used. You can define a BinaryFileMarshaler implementation > on the endpoint: > <ftp:pollingEndpoint ...> > <ftp:marshaler> > <sm:binaryFileMarshaler /> > </ftp:marshaler> > </ftp:pollingEndpoint> > > The DefaultFileMarshaler and BinaryFileMarshaler only send streams > (on top of the file or underlying ftp connection), so there should be > no memory problems. What are you referring to ? > > One enhancement would be to use an asynchronous send instead of > a sendSync to avoid blocking threads, but it's another problem. > > On 10/30/06, abrighton <[EMAIL PROTECTED]> wrote: >> >> What is the best way to deal with files that are not XML in the ftp and >> file >> polling components? >> Send them as attachments? Are you working on anything in that direction? >> I >> suppose it could >> be a property of the endpoint class, configured in xbean.xml: >> wrapFiles="true"... >> >> The other issue is how to deal with large files that you don't want to >> have >> multiple times in memory, >> but that is another issue. Maybe that could be another property setting, >> indicating to use some kind >> of reference to the file instead of the file itself? >> >> -- >> Allan >> >> -- >> View this message in context: >> http://www.nabble.com/servicemix-ftp%3A-FtpPollingEndpoint--tf2540539.html#a7083459 >> Sent from the ServiceMix - Dev mailing list archive at Nabble.com. >> >> > > > -- > Cheers, > Guillaume Nodet > > -- View this message in context: http://www.nabble.com/servicemix-ftp%3A-FtpPollingEndpoint--tf2540539.html#a7084079 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
