browser plugin for firefox on windows

[Jiri Vanek]

On 12/29/2016 12:30 PM, Mattias Eliasson wrote:
> Hi,
>
> I know that there are a lot of use cases where Java Plugins are still used. For development Vaadin
> is pretty much the only alternative but I wouldn't say that I'm satisfied with that replacement. It
> uses a lot of resources both on the client and the server and it doesn't have a fraction of the
> features of Swing on a full Java VM. Even if Swing is very outdated as a UI framework there are
> nothing as good as it that runs in a browser. Another option is Flash but you will not have anything
> close to Swing or even AWT in Flash.
>
> But this use case is about running an existing applet and I would say that if it doesn't requires
> graphics, then visualization is probably the best way to go. Pick a Linux distribution that ships
> with decent icedtea-web packages and install that in a virtual machine. Then use that to run the
> applet. It's a long way to go for running an applet but it usually works.
>

Unluckily this is probably the most solid solution - having   vm, with frozen ITW and browser.:(

> Another way is to use the Applet Viewer or perhaps even fork it into an application that bundles
> your applet. It lacks the sandboxing that you would want when running an applet from the web but in
> your use case that may not be a problem.

ITW have "javaws -html" switch which is much improved appletviwer with sandbox(if we still dare to 
say  java's sandbox as bulletproof) . It is working fine (except javascript deployment (and browser 
interaction))


>
...
>> Well, we are dealing with a government entitiy here, so you can count on that applet to probably
>> outlive us all ;-)
>>

Once browsers cut of NPAPI, which is already happening, this will become very security-risky. It is 
not hard to change applet to javaws application. And it gives more freeodm to the developers and 
users. I belive even governments can do that:)  (proof: since origin, ITW had many goverment-based 
reproducers - applications which were "must work on every release" - and in last 5 years, they 
(nearly) all moved to javaws, html5 or anything even more scary)

 From what was said:
  - vendor changes applet to javaws - best for all
  - using javaws -html - good, but have corner cases, and if the applet needs browser interaction it 
is doomed
  - VM ith frozen itw and browser - most solid, but actually opening security hole to yours.. 
system(s) or whatever it is.

J.