Signing an applet is not that difficult, I just had to do it last week.
It does take a little while to read the jar-signing tutorial and a
longer while to read (and absorb) the documentation for the keytool
command, but I don't see it as a show-stopper for you.
I used a self-signed certificate, since my application was for internal
company use. Sounds like yours is too, so that's probably the way for
you to go. Unless your college has already paid up for one of the public
[mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham
Sent: July 25, 2008 09:39
To: 'Java Programming on and around the iSeries / AS400'
Subject: RE: using jt400 in a java applet
My vendor is involved but the vendor has no knowledge of the jt400.jar I
am using and so I have been investigating from that angle to try and
prove or disprove something in that class might be the problem. Since my
error is about reflection and it appears that the jt400.jar is using
that the error is coming from the jt400.jar and not the vendors code.
I'm not real thrilled about needing to distribute a policy file to every
PC that needs to use the applet. That would be OK for college owned PCs
as we can push the policy file out but this applet could be used from an
employee on a home system on a vpn connection and I want to try and use
the tool to build applications that could be used by students also and I
will not be trying to have them modify a java policy file to make that
possible. I will go learn about how to sign an applet and see of that is
an option for me.
Thanks for the explination
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.