I think we should throw the exception out to let the user know there is something wrong with the Zip file. If the ZipIterator eat up the exception, it could be every hard for the user to find out why the camel route doesn’t work as he expects. I just fill a JIRA[1] to throw the exception out from the ZipIterator.
[1]https://issues.apache.org/jira/browse/CAMEL-7409 -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On May 4, 2014 at 5:37:18 PM, Claus Ibsen (claus.ib...@gmail.com) wrote: > On Sat, May 3, 2014 at 10:08 AM, Serge Shikov wrote: > > Here is part of ZipIterator: > > > > > > > > Note ignored IOException's. I think is should be logged and processed. > > Probably messages should be generated even if we can't unzip some entries. > > > > > > > > -- > > View this message in context: > > http://camel.465427.n5.nabble.com/zip-file-best-practices-tp5713437p5750812.html > > > > Sent from the Camel - Users mailing list archive at Nabble.com. > > Hi > > Yeah sounds like we should detect those io exceptions and propagate > them back so Camel can react. Maybe we can have an option on the zip > iterator to ignore those exceptions so people can partially read > corrupted jars. > > Fell free to log a JIRA ticket > http://camel.apache.org/support > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > Email: cib...@redhat.com > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen > hawtio: http://hawt.io/ > fabric8: http://fabric8.io/ >
