Hi Henryk, I'm sorry I just checked the code Zip data format before I applied patch. I cannot agree with you more after checking the code of ZipFile DataFormat. Current ZipFile DataFormat doesn't support to unmarshal the Zip file which has more than one entry. So it make sense to create the Iterator of ZipEntry inside the ZipFile DataFormat.
I will revisit the patch again and move the code to camel-zipfile module. -- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Saturday, March 16, 2013 at 4:27 AM, Henryk Konsek wrote: > > Otherwise its hard for our end users > > to know such functionality exists. > > > > Is there any particular reason to provide separated splitter in > camel-core instead of enhancing existing ZipFile Data Format? Am I > missing something? :) The following snippet would look just perfect > for me... > > from(...).unmarshal().zipFile().split(body(Iterable.class)).to(...) > > In my humble opinion ZipFile data format is responsible for handle > ZipEntry streams, so we shouldn't create ZipSplitter in camel-core but > rather improve existing ZipFile code. > > Best regards. > > -- > Henryk Konsek > http://henryk-konsek.blogspot.com
