DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33383>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33383

           Summary: NPE while loading GIF image
           Product: Fop
           Version: 1.0dev
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: images
        AssignedTo: fop-dev@xml.apache.org
        ReportedBy: [EMAIL PROTECTED]


list.fo seems to process without error now, except for the following NPE
while loading a GIF image.

java.lang.NullPointerException
        at sun.awt.image.URLImageSource.getConnection(URLImageSource.java:97)
        at sun.awt.image.URLImageSource.getDecoder(URLImageSource.java:106)
        at sun.awt.image.InputStreamImageSource.doFetch
(InputStreamImageSource.java:240)
        at sun.awt.image.ImageFetcher.fetchloop(ImageFetcher.java:172)
        at sun.awt.image.ImageFetcher.run(ImageFetcher.java:136)

I've found various posts on the net from people who have the same effect
but not necessarily the same circumstances. In GifImage we load the image from 
an InputStream using a "DummyConnection" which is a URLConnection. However, 
the Sun ContentHandler for GIF images seems to use their own URLImageSource (a 
ImageProducer descendant) which wants the URL in the URLConnection to be non-
null. Sun also has a InputStreamImageSource internally which they should 
probably use in this case.

I tried supplying a dummy URL to see if the code would still use the 
InputStream that was supplied, but the image was loaded from the URL. So it 
actually opens a new connection.

If anyone has an idea for a work-around, that would be cool.

Happens under Sun JDKs 1.4.2_06 and 1.5.0_01.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Reply via email to