力小程序同一JVM实例加载？ [英] Force applets to load in same JVM instance?

问题描述

我接手维护旧的Web应用程序，它使用嵌入在同一网页的多个小程序。这用来做工精细，但由于下一代的Java插件介绍（〜1.6.0_10）个人小程序不能保证在同一个JVM实例加载。如果它们在不同的JVM加载，它们不能通过AppletContext.getApplets（），或者通过静态变量通信

I've taken over maintenance of an old web application, which uses multiple applets embedded in the same web page. This used to work fine, but since the Next Generation Java plugin was introduced (~1.6.0_10) the individual applets are not guaranteed to load in the same JVM instance. If they load in different JVMs, they cannot communicate through AppletContext.getApplets() or through static variables.

有没有什么办法，我们可以强制小程序在同一个JVM实例加载？只见提到的地方指定相同的java_arguments'参数可能鼓励了Java插件运行在同一个JVM实例applet的解决办法，但是这并不能为我们的应用程序中工作（且在任何情况下，不正式Oracle支持，因此可能会消失的在任何情况下的时间）。

Is there any way we can force the applets to load in the same JVM instance? I saw a workaround mentioned where specifying identical 'java_arguments' parameter may encourage the Java plugin to run applets in the same JVM instance, but this does not work for our application (and in any case is not officially supported by Oracle and hence may disappear any time in any case).

我们也试过用间接的applet到JavaScript到applet的通信直接替换小程序对小程序的通信，但是由于我们的客户使用旧的Web浏览器版本其中prevent我们不能使用这种方法这从工作。我会极力避免通过非本地服务器路由所有本地小程序到applet的通信，如果在所有可能的。

We've also tried replacing direct applet-to-applet communication with indirect applet-to-JavaScript-to-applet communication, but we can't use this approach as our clients use old web browser versions which prevent this from working. I'd be keen to avoid routing all local applet-to-applet communication through a non-local server if at all possible.

推荐答案

我们也有类似的问题，并通过禁用Java的控制面板上的下一代的Java插件，它周围的工作。

We had a similar problem and worked around it by disabling the "next-generation" Java plugin in Java control panel.

这篇关于力小程序同一JVM实例加载？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！