ZipException when trying to run Saxon on UNIX

[Jill Smythe]

Hi,
I am trying to run Saxon7.8 on an XML document (StreamAM.xml) with an XSL
stylesheet (StatusStream.xsl) in the following way:
/opt/java_1.4.1/bin/java -jar
/usr/dev/psoft/ps8common/saxon/saxon7.jar StatusAM.xml StatusStream.xsl
> StatusAM.htm
but keep getting the following ZipException:

>>Exception in thread "main" java.util.zip.ZipException: error in
opening zip file
>>at java.util.zip.ZipFile.open(Native Method)
>> at java.util.zip.ZipFile.<init>(ZipFile.java:112)
>> at java.util.jar.JarFile.<init>(JarFile.java:117)
>>at java.util.jar.JarFile.<init>(JarFile.java:55)

I am working on UNIX with Weblogic6.1 web server and am really not sure why this is occurring -- it works fine when run on Windows...? Does anyone know Saxon or have any suggestions as to why this might be occurring? I'm pulling my hair out.
Thanks in advance,
Jill

[Lasse Koskela]

Try running
/opt/java_1.4.1/bin/jar -tf /usr/dev/psoft/ps8common/saxon/saxon7.jar
If it throws the same exception, the .jar file must be corrupted.

[Jill Smythe]

Hi Lasse,
Thanks for your reply. I tried executing as you suggested and got *slightly* different error:

>>  java.util.zip.ZipException: invalid EXT descriptor signature
>>      at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:355)
>>      at java.util.zip.ZipInputStream.read(ZipInputStream.java:141)
>>      at java.util.zip.ZipInputStream.closeEntry(ZipInputStream.java:91)
>>      at sun.tools.jar.Main.list(Main.java:744)        
>>      at sun.tools.jar.Main.run(Main.java:192)
>>      at sun.tools.jar.Main.main(Main.java:904)

Would you suggest that the jar file is corrupted? What is the -tf option?
Any suggestions will help!
Thanks again,
Jill

[Lasse Koskela]

Yes, the file is corrupted and you need to download it again from somewhere.
The "t" option tells jar to display the contents of a .jar file, and the "f" options tells jar that the following argument is the .jar file itself

[Jill Smythe]

Hi Lasse,
Thanks a lot for your help -- As you suggested, the jar file was corrupted and the problem was fixed by re-intalling it.

Thanks again!
Julie