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
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
On 10/30/06, abrighton [EMAIL PROTECTED] wrote:
Thanks for the tip about the binaryFileMarshaler. I didn't realize you could
do it that way.
The marshaler is the easiest way to customize the behavior of endpoints.
As for the memory usage: I was assuming that at some point the entire file
[ https://issues.apache.org/activemq/browse/SM-726?page=all ]
Guillaume Nodet resolved SM-726.
Resolution: Fixed
Assignee: Guillaume Nodet
Author: gnodet
Date: Mon Oct 30 14:43:29 2006
New Revision: 469310
URL:
