K
Knute Johnson
I've got some software running in the wild that uses JApplets. My
client decided to update the Java version from 1.6 something to
1.7.0_21. The applets communicate with the server they come from. This
caused a security exception. I re-compiled and self-signed one of the
applets to see if that would solve the issue but then I got a
ConnectException. I'm not sure why and it could be related to the
Serialzed data being transmitted between the applet and server.
Should self signing the .jar files solve any problems from changing the
Java versions for my applets?
Thanks,
client decided to update the Java version from 1.6 something to
1.7.0_21. The applets communicate with the server they come from. This
caused a security exception. I re-compiled and self-signed one of the
applets to see if that would solve the issue but then I got a
ConnectException. I'm not sure why and it could be related to the
Serialzed data being transmitted between the applet and server.
Should self signing the .jar files solve any problems from changing the
Java versions for my applets?
Thanks,