JRE 1.5.0_13 problem with Modal Window

Question

We have stand alone browser based application built on HTML, Javascript, and Java (non-GUI applet). We were running the Sun JRE 1.4.2_06, but have recently upgarded to 1.5.0_13. As soon as we upgraded to 1.5, started experiencing the below problem -
The HTML screen displays a modal windows which makes a Java call to the MQClient software through Applet (via OBJECT Tag) to communicate with mainframe. The MQClient Java code seems to be blocked until the user clicks on any other area of the screen to shift the focus from our modal dialog to any other window (either clicking on the task bar, clicking on another window in the background, or hitting Alt/F10 key).
The same code runs fine with JRE 1.4.2_06.
Based on a further analysis+ it seems like there is an issue, when a modal html window makes a java call for creating a socket connection (other then localhost). In this scenario, socket is never created unless you drag a modal window or move a focus away from a modal window.
Above problem seems to be resolved with JRE 1.6.0_10.
Edited by: Ashwani_Saxena123 on Oct 31, 2008 5:42 AM

Answer 1

Ashwani_Saxena123 wrote:
Ours is a stand-alone browser based (IE 6.0) application, which communicates between JavaScript to Java using Applet (with Object Id tag).Why? What for?
.. All the Java class files are bundled in a zip file under different packages and Zip file path is provided at run time when Application starts. It is safest to distribute classes and application resources as Jar files. One reason is that Sun decided to not bother even checking Zips for digital signatures, so no trusted app. can afford to try loading Zip files.
..The path of Zip file is at C:\EALife\Program ...Whoa up a second there!
If this applet is only ever being loaded on the same machine as the codebase, why is it an applet at all? It would make more sense to distribute/install an application.
If this applet is being loaded by PCs at remote locations, then the will probably not have a C:\EALife\Program path at all (especially is they use Ubuntu, like here).
..and home directory path is C:\EAFramework\Program\Screens. We are putting all paths in a single variable (APP_CLASS_PATH) and using that variable as a parameter value in Object Id tag for creating an Applet. Below is the code snnipet for Object Id tag -Sun has championed a script to use for applet versioning and writing the applet element. I suggest you use it instead, it is known as 'deployJava.js' - see top hit at Google for details.