DummyConnection triggers an unpleasant memory. Look here:
So, no, unfortunately, no ideas from this time. :-(
On 09.08.2005 17:26:04 Manuel Mall wrote:
> On Tue, 9 Aug 2005 08:15 pm, Jeremias Maerki wrote:
> > On 09.08.2005 13:57:09 Manuel Mall wrote:
> > > On Tue, 9 Aug 2005 06:21 pm, Jeremias Maerki wrote:
> > > > On 09.08.2005 11:55:55 Manuel Mall wrote:
> <snip />
> > >
> > > > > BMP and GIF cause
> > > > > exceptions.
> > > >
> > > > That's not so good.
> > >
> > > I'll investigate this.
> > Thanks again.
> Spent the last couple of hours to get to the bottom of the GIF problem.
> Here is the stackdump:
> Uncaught error fetching image:
> at sun.awt.image.ImageFetcher.fetchloop(ImageFetcher.java:172)
> at sun.awt.image.ImageFetcher.run(ImageFetcher.java:136)
> That's it as it happens in a separate thread. The application then
> appears to hang as the main thread seems to wait for some signal from
> the image loading thread that it has completed. Now all this is JDK
> dependent! Java 1.4 works fine but Java 5.0 => Null Pointer Exception.
> It has to do with the GifImage.DummyConnection class. It pass null as
> the URL argument to its superclass constructor and it is that null URL
> which is causing the NPE. Why doesn't it happen with JDK 1.4? Not sure,
> but URLImageSource.getConnection will return the existing connection
> the first time its called and reestablish the connection the 2nd time
> its called. Under JDK 1.4 its appears to be called only once.
> To fix this I need to give the constructor the proper URL of the image
> but this is not available within the class. I am reluctant to change
> all the interfaces, which would affect all image handlers, to carry the
> URL as well as the InputStream just for this problem which is specific
> to GIF.
> Any one out there with some ideas here?
> <snip />
> > Jeremias Maerki