Internet Explorer, Applets and multiple JVM versions

Thread view:

JavaEnquirer - 24 May 2005 15:11 GMT

I'm using IE 6 and was wondering how you can force different applets to
use different JVM version plugins.

We have a situation whereby users need to use a 3rd party applet using
Java 1.3 (Jinitiator) and need to use an in-house applet using Java
1.5. Users will use both applets simultaneously. What can we do to
ensure that each browser session uses its own specific JVM without
polluting the other browser sessions?

Many thanks in advance.

Reply to this Message

Andrew Thompson - 24 May 2005 15:28 GMT

> I'm using IE 6 and was wondering how you can force different applets to
> use different JVM version plugins.

Is 'IE 6' a specific and non-negotiable requirement?

The reason I ask is that it might be easier to achieve
what you want by launching two separate browsers, as in..
(1 x IE 6) + (1 x FireFox)

What are the exact requirements that lead to wanting the
applets open _simultaneously_. And perhaps most importantly,
why can your web-app not be run within a single page as a
'linear' application?

Signature

Andrew Thompson
http://www.PhySci.org/codes/ Web & IT Help
http://www.PhySci.org/ Open-source software suite
http://www.1point1C.org/ Science & Technology
http://www.LensEscapes.com/ Images that escape the mundane

Reply to this Message

JavaEnquirer - 24 May 2005 16:01 GMT

Having both applets open simulataneously is non-negotiable. The users
work in a contact centre and require both applets to deal with requests
from members of the public. Applet1 is a 3rd party contact centre
product which can be configured to launch parameterised URLs.

We use Applet1 to log calls from the public. A service area is then
selected and a parameterized URL is invoked launching applet2 which
deals with the specific details of the request. When the request is
dealt with, applet2 is closed and the user continues with applet1. A
new call is taken, the details are logged in applet1, which then
invokes applet2 ad infinitum.

In an ideal world we would ditch applet1. However, we cannot as it has
been paid for and it is too political to ditch it.

On the subject of launching two separate browsers, that is a goer if
and only if applet1 running in IE can invoke a URL which causes say
Firefox to open with the applet2.

Reply to this Message

Andrew Thompson - 25 May 2005 06:33 GMT

> Having both applets open simulataneously is non-negotiable. The users
> work in a contact centre and require both applets to deal with requests
[quoted text clipped - 14 lines]
> and only if applet1 running in IE can invoke a URL which causes say
> Firefox to open with the applet2.

Uggh. This conversation is already hurting my head.

So, to sum up.

The 3rd Party (politics/non-negotiable) applet is Oracle's
JInitiator that requires Java 1.3 _specifically_. Not '1.3+',
but a specific version of 1.3?

That applet sends information via URL [ as in showDocument(URL, target)? ]
to the in-house applet that continues the processing. The in-house
applet uses Java 1.5 features.

Is that right so far?

Pete suggested one of the few possible solutions I can think of to
this mess. Though I usually recommend people steer clear of the horrid
nested <object><embed> structure, the use of IE would mean you could simply
use the <object> element and be done with it.

Other possible approaches might be
- to have your URL's pointing to a servlet,
- calling applet 2 using webstart, giving the URL parameters as part
of the .JNLP file (though I think that would also require some
serverside help).
- Hosting the JInitiator applet within another applet, intercepting
the calls to showDocument, ..and taking some other action more
appropriate/useful than attempting to open a new applet.

Signature

Reply to this Message

JavaEnquirer - 25 May 2005 10:12 GMT

>> Is that right so far?

Spot on.

Thanks for the reply, I'll take a look at the web start option.

Reply to this Message

Pete Barrett - 24 May 2005 19:05 GMT

>I'm using IE 6 and was wondering how you can force different applets to
>use different JVM version plugins.
[quoted text clipped - 6 lines]
>
>Many thanks in advance.

I think there's an attribute or a parameter in the OBJECT tag for
invoking an applet which can specify the JVM version. If there isn't,
have a look at the JSP tag for invoking an applet. (I remember it's
somewhere, but don't have my documents here at the moment - these are
the likely places.)

Of course, it may be no more than a request to use one particular JVM
- I've never had to use it, so don't know how well it works.

Pete Barrett

Reply to this Message

Internet Explorer, Applets and multiple JVM versions

Free Magazines