Zipped Image not working on MS Windows XP

Question

Hi all,
I have a GUI zipped as a JAR file, which has an internal image which should be shown when starting the application in a directory that does not contain any image files (I use JAI for image manipulation). On Linux, the internal image is correctly unzipped from the JAR; on M$ XP it fails with just any image I tried (JPEG, GIF, PNG, even M$ Bitmap).
Does anybody have a tip for me?
Thanks,
Andreas
<code>
// read internal image
try
debug(Thread.currentThread( ).getStackTrace( )[2].getMethodName( )+" Reading internal image."+ls);
byte[] puffer;
synchronized( o )
InputStream is = (InputStream) getClass ().getResourceAsStream ("/images/"+PREVIEW);
int len = (int) is.available ();
puffer = new byte[len];
is.read (puffer);
is.close ();
System.out.print (ls+"Reading internal image.");
o.notify ();
synchronized( o )
// Use the ImageCodec APIs
ByteArraySeekableStream stream = new ByteArraySeekableStream(puffer);
System.out.println ("Resource size: "+stream.available ()+" bytes.");
String[] names = ImageCodec.getDecoderNames(stream);
for (int i=0; i<names.length; i++)
System.out.println ("Type="+names);
ImageDecoder dec = ImageCodec.createImageDecoder(names[0], stream, null);
RenderedImage im = dec.decodeAsRenderedImage();
IMG = (PlanarImage) PlanarImage.wrapRenderedImage(im);
o.notify ();
catch(Exception mf)
System.out.println ("Could not load internal resource.");
</code>
The M$ error message:
Z:\home\Konverter\dist>java -jar Konverter.jar
Reading settings...
Starting graphics...
Project: Konverter Build #: 1567 Builddate: Tue Feb 21 14:29:27 CET 2006 URL: www.zero29.de
Running in DEBUG mode.
Laying out GUI components...
Reading internal image.Resource size: 18238 bytes.
Type=jpeg
Corrupt JPEG data: premature end of data segment
Could not load internal resource.
done.

Answer 1

Sure, thanks for responding:
<mx:WindowedApplication windowComplete="init()" .........removed excess here
     <mx:Script>
          <![CDATA[
               import mx.core.Window;
               protected var theWIndow:Window;
               protected function init():void{
                    theWindow = new Window();
                    theWindow.open();
          ]]>
     </mx:Script>
</mx:WindowedApplication>
In my actual code I have a mxm component that extends Window, so the Window type would be that instead, but since it directly extends it there is no difference. I am actually using the fb.FBConnect code from the facebook-actionscript-api and its open() call also fails on the pc...that is unless I start the process from a flex Button click, then it all works.