Jory_Thompson wrote:
..
Caused by: java.lang.SecurityException: class "com.thompco.persys.dataLib.entity
.Alarm$$EnhancerByCGLIB$$96089901"'s signer information does not match signer in formation of other classes in the same package
...
This last bit sounds like I am using a different jar signer for each jar?
Sounds like. All the Jar files in any one JNLP must be signed by the same cert., if you want to deploy other Jars that are already signed, it is common practice to put those Jars in their own extension JNLP.
I also want to make sure I am setting up my jnlp file(s) correctly.
No, there is at least one point where that file is invalid, and GIGO! Try checking the main JNLP using
JaNeLA *(<- link).* JaNeLA will load the referenced component-desc/installer-desc JNLPs and check the validity of the files as well as the availability of resources.
..I assume I need to get it working as a stand-alone jar before I install it on my web server?
A local server is sometimes handy for checking aspects of JWS launches. But at the moment I will go directly from testing on the command line, to a server upload.