My concern with this is that we are still subject to the behavior of the underlying protocol handler and its implementation details. I'm still trying to drill into the current readBytes error coming from the FileInputStream native method on win32 and not having access to the actual error is tedious. The same type of issue exists for JarFile where a lot of detail is in native methods. The first thing we need is a java.util.jar.JarFile abstraction so we can replace its usage. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990133#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...