A DESCRIPTION OF THE REQUEST :
We rely on the use of multiple applets, but unfortunately, if they do not run in the same JVM, they are unable to communicate with each other as was possible previously. Given the fact that the rules for exactly when a new JVM instance is launched to start a given applet are deliberately left unspecified, as per your documentation, it is impossible for us to guarantee that the applets start in the same JVM.
We need one of the following:
1. The ability to specify not to use separate_jvm by setting it to false. This does not work currently.
2. The ability to specify the current JVM to start the applet in or by naming JVMs and specifying which one to use, explicitly.
3. The ability for getAppletContext to work across JVM Boundaries.
We also requests that the specifications be clarified and that it not be left ot this statement alone. ( " The rules for exactly when a new JVM instance is launched to start a given applet are deliberately left unspecified " ).
I understand that we can modify our architecture to use live connect or possibly turn off the plug, but neither of these options is feasible in our current environment.
As a point of reference Microsoft in an IE8 update launched each applet in a separate JVM and on a subsequent update reversed that decision because of the number of complaints that it broke many applications. Now the same thing is happening for JAVA and an acceptable solution needs to be provided.
EXPECTED VERSUS ACTUAL BEHAVIOR :
Utimately, I expect to be able to perform Applet to Applet Communication without a redesign of our architecture. We need one of the following three options mentioned above to be made available.
Multiple JVMs start preventing existing Applet to Applet Communications.
---------- BEGIN SOURCE ----------
Not Available at this time.
---------- END SOURCE ----------