EVALUATION

This is due to the current way Mozilla OJI plugin gets designed. The ultimate reason of doing so was to support JavaClass (part of liveconnect design). So plugin library needs to be loaded during browser starts up. That is where OJI plugin is different from other plugins. I don't see any immediate solution for this issue.
###@###.### 10/12/04 21:29 GMT
###@###.### 10/12/04 21:39 GMT

Reassigning to Danielle, Here is email correspondence with her:
>I don't see immediate solution for this problem.In fact, if there's a >solution, the crux of code change will be with the browser codes.
>I can discuss this problem with Browser's team in China while working on >NPAPI+ project and see if there's anyway we can address this issue or not
>as part of NPAPI+ project.
###@###.### 2004-11-11 13:06:46 GMT

We have been working with Mozilla.org so that mozilla.org will keep update their browser's pointer to latest JRE to the correct version.

Also, with introduction of Deploy Toolkit (aka, Deploy Helper), JRE detection/download/installation can be made simpler using JavaScript from within one's html.
###@###.### 2005-07-18 17:21:44 GMT