which isn't good enough. Say, for example, an applet gets an image out
of a Jar and renders it (in reduced form) on the screen. Later, the
applet attempts to print the image. Because of the greater resolution
available, the AWT image code will attempt to re-fetch the image,
but JarImageSource's input stream will be positioned to the end.

Sorry, I don't have a test case to reproduce this -- I just noticed it
while inspecting the source.