🚀 go-pugleaf

We are in an intranet envioronment and swing has done wonders for us.  We
haven't had to sign anything, although we have some times, but it has not
been required.  We do however, exclusively use Netscape 3 & 4.  As far as
the swing jar file, we have set up are netscape, which is served off of an
application server with the Java Plugin.  That way, no one has to download
and install the plug-in.  All they have to do is run the Control Panel and
set their plug-in preferences.

James Birchfield
BTG, Inc.

Darryl Pentz > wrote in message <6rv6f2$gk72@gcs.delta-air.com>...
>
>sean.mcdermott@usa.net wrote in message
<6ruu48$iid$1@nnrp1.dejanews.com>...
>>
>>
>>> > In my latest applet, I've been using the Java plugin and that works
>quite
>>> > well in both browsers...
>>> >
>>>
>>> I already know Swing applets will work if they're signed and we use the
>Java
>>> plug-in. The whole point of my posting was that with the release of
>Swing,
>>> JavaSoft has moved us to a new era. Now you have to SIGN ALL APPLETS TO
>MATTER
>>> WHAT. Remember, before, we only had to sign applets if they attempted to
>leave
>>> the sandbox. That's no longer true! Now, anytime you write an applet, if
>you
>>> use Swing to do the interface, you have to sign it - period.
>>
>>I've been using Swing 1.0.2 (JFC 1.1?) with IE4 and haven't need to sign
>>*anything*.  Everything works perfectly!  You do get a couple of stack
>traces
>>on the Java Console as Swing initializes but these can be ignored.  In
>fact,
>>I'm rather impressed with the speed of Swing once it is loaded.  All I do
>is
>>include the swingall.jar file in the archive part of the applet tag.
>>
>>I do believe you're last sentance regarding Swing and signing is utter
>>nonsense.
>
>
>I agree. The last sentence is bunk. You only have to sign applets that
>require trusted access to your local machine.
>
>- Darryl
>
>