I personally think that we should look at it from the point of view of the API consumer. What would they want to happen in case of an error reading an archive?
IMO an IOException. How we get to that exception on the implementation side is another matter. If we could check all conditions and throw "legitimate" IO exceptions - it would be perfect. Since that's unfortunately not feasible for the time being, wrapping a runtime exceptions sounds like the most pragmatic and future proof approach to me. So I am in favor of 2) cheers, Torsten
