18567 - Java applets don't work in browser

Status: VERIFIED FIXED

(Core Graveyard :: Java: OJI, defect, P3)

Description

[chriss]

I installed the 1999111014 build (Nov 10) on my Win98 machine and checked off
the java installation checkbox using the custom install option. Java appears to
be installed in the c:/program files/javasoft directory (not the c:/program
files/netscape directory)

When I got to http://java.sun.com/openstudio/index.html the clock applet does
not appear. Note that it does appear on Communicator 4.7.

Not sure if this is an install bug or an OJI bug.

Comment 1

[drapeau]

We believe it's an OJI bug at present; we just heard reports in the last three
days or so that OJI no longer works with current Mozilla builds.  Ed Burns is
investigating this right now.  I'll leave it to him to decide whether to mark
this bug as a duplicate of bug 18248.

Comment 2

[edburns]

I have sent mail to chriss and paw explaining where to get the latest JVM.  I
tested it with this JVM and a build of mozilla from this morning, and all the
applets run correctly.  However, clicking on the rotating pink triangle, sends
the JVM into a loop:

Exception occurred during event dispatching:
java.lang.NullPointerException: component argument pData
        at sun.awt.windows.WGraphics.createFromComponent(Native Method)
        at sun.awt.windows.WGraphics.<init>(Unknown Source)
        at sun.awt.windows.WComponentPeer.getGraphics(Unknown Source)
        at java.awt.Component.getGraphics(Unknown Source)
        at sun.awt.RepaintArea.update(Unknown Source)
        at sun.awt.windows.WComponentPeer.handleEvent(Unknown Source)
        at java.awt.Component.dispatchEventImpl(Unknown Source)
        at java.awt.Container.dispatchEventImpl(Unknown Source)
        at java.awt.Component.dispatchEvent(Unknown Source)
        at java.awt.EventQueue.dispatchEvent(Unknown Source)
        at java.awt.EventDispatchThread.pumpOneEvent(Unknown Source)
        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.run(Unknown Source)

I think this is another bug.

Comment 3

[Paul Wyskoczka]

Looks like the NPJava*.dlls are not being copied to the Seamonkey plugins folder.

Comment 4

[chriss]

In today's Nov 18 build, Java is still not installed properly. So this is now an
installer bug - correct?

Reopening bug; Bug should be assigned to [e-mail]

Comment 5

[Daniel Veditz [:dveditz]]

Don't assign it to me, if you think it's a netscape install problem then
assign it to [e-mail]

Sean, however, is doing what he was told to do to install JRE. If the specs of
what to put where were wrong there's no way *he* is going to magically know
that. So before assigning it to Sean someone on the Java team had better make
sure they know fully what's required to install this beast and make it work.

Comment 6

[chriss]

Ed, can you please work with Sean Su on this so Java installs properly?

Comment 7

[leger]

Clearing WORKSFORME resolution due to reopen.

Comment 8

[chriss]

Adding beta1 to keyword field

Comment 9

[leger]

Putting on the PDT+ radar for beta1.

Comment 10

[leger]

Must fix by 03/03 or will not make the beta1 train.

Comment 11

[edburns]

This is a meta-bug.  Look at the dependencies.

Comment 12

[edburns]

This worked last night with Stanley's 02/24/00 JPI, his extra jaws.jar, and a 
5pm-ish mozilla build from 02/24/00 WITHOUT MOZ_DEBUG set.  When I test it 
today, with the same setup, with a MOZ_DEBUG=1 build of the same mozilla code, 
I get the Assertion failure mentioned in my post to 27486.

Comment 13

[edburns]

*** Bug 24487 has been marked as a duplicate of this bug. ***

Comment 14

[Joseph Elwell]

This bug depends on bug 27763 which depends on bug 21250 which was just recently
changed status from PDT+ to PDT-...

Comment 15

[edburns]

The AWT bug impacts this one.

Comment 16

[edburns]

The AWT bug isn't present in Kestrel RC1.  Changing to FIXED.  To replicate my 
success in viewing the page for which this bug was filed, follow these steps.

02 March 00

Here are the steps I took to enable the viewing of applets in mozilla.

STEP 8 IS THE MOST IMPORTANT, and UNUSUAL step.

1. Check tinderbox to see that it's green for win32 clobber

2. Checkout SeaMonkey at around 11:30am on 02 March 2000

3. Built Mozilla with MOZ_DEBUG=1

4. Used the WINNT Add/Remove programs feature to remove any JRE and JDK
   instance I had installed on my machine.  Then I rebooted.

5. Used a find command to make sure there were no instances of any of
   the following files on my C: drive:

   jpins32.dll
   npjava*.dll
   jpishare.dll
   jaws.jar

   This step is also intended to catch the case where you have Netscape
   Navigator 4.x with the Java plugin installed, which I don't.  If you
   do, you must make sure that you don't have the plugin installed.

6. Downloaded the JRE Release Candidate (RC) 1 release by visiting:

   http://developer.java.sun.com/developer/earlyAccess/j2sdk13/
  
   And choosing the "One large bundle" option under the heading

     Internationalized version of Java 2 Runtime Environment 

7. Ran the installer exe.

8. Unzipped George's zip file on top of the install location, which for
   me was C:\Program Files\JavaSoft\JRE\1.3 .

9. Copied C:\Program Files\JavaSoft\JRE\1.3\bin\npjava*.* to my mozilla
   plugins directory, which is:

   D:\Projects\mozilla\dist\WIN32_D.OBJ\bin\plugins

10. Ran 

   D:\Projects\mozilla\dist\WIN32_D.OBJ\bin\mozilla.exe

After doing the profile manager dance, I was able to view applets
without java-related crashes.

Comment 17

[Paul Wyskoczka]

Verified in the 2000030609 build.

Comment 18

[rogerl (gone)]

*** Bug 30306 has been marked as a duplicate of this bug. ***