M. Shafie,

Just for the record (for those of your clients who could encounter the same issue on Linux...).

By default on most Linux systems, the GUN GCJ Java is installed, not the Oracle one (not OpenSource); as a consequence, *keytool* points to this alternative JDK:

/usr/bin/keytool -> /etc/alternatives/keytool

This caused the problem with jarsigner when deploying XXE with JWS..
When *keytool* symbolic link is pointing to the Oracle JDK keytool:

/usr/bin/keytool -> /usr/java/latest/bin/keytool

Everything is working as expected.
Thanks for your help.
Best regards.
Philippe.



On 07/11/2011 03:55 PM, Hussein Shafie wrote:
On 07/11/2011 02:30 PM, Philippe Nobili wrote:
We deploy our customized XXE using Java Web Start for our Windows users.

Since XXE 4.9.0, the deployment procedure fails right away (we mainly
call the deploywebstart script and then a couple of sed/awk commands to
process the JNLP&   HTML files).

Below an excerpt of  the error message (Java 1.5)

Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad
version number in .class file
           at java.lang.ClassLoader.defineClass1(Native Method)
           at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
           at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
           at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
           at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
           at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
           at java.security.AccessController.doPrivileged(Native Method)
           at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
           at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
           at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
           at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
           at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)


It worked fine with XXE 4.8.0 and prior (using Java 1.5).
Did we miss something ? (we searched the release notes, but certainly
missed the point...)

Excerpts from http://impala.localdomain/xmleditor/changes.html#v4.9.0:
---
Incompatibilities:

      * XMLmind XML Editor now requires Java 1.6 in order to run.

---




PS: Still no way to deploy using Java 1.6, but we guess there is nothing
you can do about it ? Below the error messages:

jarsigner error: java.lang.RuntimeException: keystore load: Invalid
keystore format
deploywebstart: ***ERROR***: command "jarsigner -keystore
"/scr/softs/xxe-pro-4_9_1/webstart/testkeystore" -storepass
"teststorepass" -keypass "testkeypass"
"/scr/softs/xxe-pro-4_9_1/webstart/xxe.jar" "nobili"" exited abnormally
(status = 1)
According to the error message, this other problem is probably not
related to the above one.

I cannot reproduce it. I mean, using latest Java 1.6 on my Linux box:

---
$ deploywebstart -index
---

and (this time, using an actual code signing certificate purchased from
GoDaddy):

---
$ deploywebstart -index -storetype pkcs12 -keystore pixware_cert.pfx \
      -storepass xxx -keypass xxx -alias pixware
---

both work fine for me.




 
--
XMLmind XML Editor Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xmleditor-support

Reply via email to