Bob Scheifler wrote:
First can somebody shed me light how a typical jar: handler can mask the
distinction between definite lack of existence and less definite errors.
Peter may need to correct me, but I believe the problem is that you
can't rely on being able to use the IOException thrown to determine
the category (vs getPreferredConnection using the actual HTTP
response code to make the category distinction).
I'd guess that there is no distinction in what FileNotFoundException means. It
might mean that the Jar is not there, but can also mean that a resource in the
jar is not there.
Is that what you are referring to Bob?
Gregg Wonderly
