Re: IE & applets
From: Tom (tom.cowdery_at_bigfoot.com)
Date: 03/26/04
- Next message: Richard Chrenko: "Re: java webstart"
- Previous message: Peter Wilford: "Resource access"
- In reply to: Lazy70: "Re: IE & applets"
- Next in thread: Lazy70: "Re: IE & applets"
- Reply: Lazy70: "Re: IE & applets"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 26 Mar 2004 08:00:49 -0800
"Lazy70" <s.pulvirenti@katamail.com> wrote in message news:<c40sjs$2bll5o$1@ID-111830.news.uni-berlin.de>...
> "Tom" <tom.cowdery@bigfoot.com> wrote in message
> news:f00f4c38.0403251350.735f7b9d@posting.google.com...
> >
> > For a newbie, your question is almost expected. You don't mention
> > what class wasn't found, so I may not address your particular problem.
>
> it's not a Sun class, is a third party class
That may be the source of the problem. If you did not write it, you
can't be sure what version of Java was used to create it. It may
using a version that is too new for the browser. IE's version of Java
is over 4 years old!
> > The easy answer is don't use IE. I switched to Mozilla a couple of
> > years back and I have never regretted it. But that is another issue.
>
> Unfortunately my site is publi, so I can be able to know what browser users
> use.
> However my problem is the same in IE and in netscape.
> I have said IE in prevoius post because my suspects about double JVM were
> strong
It wasn't clear from your first post whether you were writing code or
just trying to get your browser to work. Obviously, if you are trying
to create the applet, you cannot control what browser is used.
What version of Netscape are you using? Older versions of Netscape
(4.7 and earlier) will have the same problem as IE. Newer versions of
Netscape usually come with a more modern version of Java.
> > Any browser made by Microsoft has the potential to have problems with
> > applets created in Java. This is due to the fact that IE ships with a
> > VM that is NOT 100% compatible with the Sun standard. In fact, this
> > has been the central issue in multiple lawsuits against MS by Sun.
>
> I'm not agree about this point of view.
You are welcome to disagree, but it is more than just a point of view
- it is a fact - proven in courts of law. IE is the only browser on
the market that ships with a non-standard, 4 year old version of Java
that will not work on any other platform!
> In my (little) experience I have other problems with other browser, other
> SO, etc.
> Sometime is Sun JVM that is not platform - indipendent, even if often all
> works fine.
Obviously, English in not your first language. That is OK. I'm sure
you are doing better in English that I would in your language. I
think I know what you are trying to say, so I'll reply based on that
understanding.
You are probably correct that the Sun JVM isn't perfect. What is?
But Java is Sun's creation. It owns Java and all third-party versions
of Java are required to be compatible with Sun's version. So if you
stick with a Sun-compatible version, whether it is written by Sun,
IBM, Blackdown, Apple, or some other licensee, you can rest assured
that the version that you are using has been tested to be 100%
compatible. The ONLY version out there that failed the test is
Microsofts version. (I'm sure others failed, but they weren't
released until they passed.)
Also, don't forget that some sites were created with Microsofts
version. That can mean that they will ONLY work with the MS version
(depending on what API they used). That is part of the reason that MS
was sued and lost.
And even in tested versions, code written with version 1.4 may not run
on a version 1.3 JVM. At least with Sun, you can always get the newer
version. The MS version will never be updated.
Actually, you can get older versions from Sun as well. One option is
to download version 1.1 from Sun and use it to create your applet. If
your code will compile with version 1.1, it should work on most
browsers - including IE. Just don't be surprised if your third-party
class won't compile with the older version. I suspect that that is
the source of the problem.
A better long-term option is to write the HTML so it forces the
browser to use the plug-in. That lets you write with the latest
version and lets the user see the applet with the latest version. If
someone doesn't have the correct version of the plug-in (or doesn't
have the plug-in at all), the browser will inform them of the
deficiency and let them download it. Basically, it is the same system
used by things like Flash or QuickTime. I believe some of the other
replies have links that explain how to do that so I'll let you refer
to them.
- Next message: Richard Chrenko: "Re: java webstart"
- Previous message: Peter Wilford: "Resource access"
- In reply to: Lazy70: "Re: IE & applets"
- Next in thread: Lazy70: "Re: IE & applets"
- Reply: Lazy70: "Re: IE & applets"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
