Yes the BinaryFileMarshaller is assuming that, but also the FileSender (and probably other components using the marshaller) is assuming to deal only with one file (one NM one file).
A first step should be to split messages and save every attachment separately. Problem should arise if the number of attachments is not known; in that case we have to evaluate if the better way is to obtain a complex SA or to patch the code. thanks, nicola. Bruce Snyder wrote: > On 7/13/07, Nicola Buso <[EMAIL PROTECTED]> wrote: >> Hi all, >> >> I'm looking to the BinaryFileMarshaler to manage attachments. I need >> to manage more than >> one attach at a time, is there this possibility? >> >> If not I can help to improve BinaryFileMarshaller to do it! > > Just glancing at the code for the BinaryFileMarshaller, it looks like > it assumes a single attachment. You are certainly welcome to improve > it and contribute a patch as noted here: > > http://incubator.apache.org/servicemix/contributing.html > > It's also very advisable to contribute JUnit tests as part of the > patch. This makes review of the patch much easier. > > Bruce -- Nicola Buso Direzione Architetture e Consulenza Direzione Centrale Ricerca e Innovazione Engineering S.p.A. Padova, Italy Cso Stati Uniti, 23/I Tel. ++39 0498692513 e-mail: [EMAIL PROTECTED]
