Had to un-install JRE, again. "AWT-EventQueue-13" exception.

Question

Hello every body readers,
and a Happy Christmas from me in Sweden.
I installed latest JRE "jre1.5.0_01".
Had to uninstall and use Microsoft java instead, AGAIN.
Those who said to me in past: "Use IE Java. Works better" was probably right.
As now Sun Java only occupies a considerable amont of space in my PC.
You will probably ask me to re-write my HTMLs to fit JRE.
Suppose IExplorer6 wasn't backwards compitable with HTML-pages.
Most .html pages in world would have to be re-written!!!!!!!!!
JRE makes error when trying to update MyClass.class.
"at DJClock.update(E:\Msdev\projects\DJClock\DJClock.java:552)"
A leftover from development stage of this software.
Well!
And this you offer millions of poor users around the world to download?????
Maybe you will not recognize this fault,
and try some political jargong 'we never do anything bad" non-excuse.
I would simple say: "we are very sorry!" to all potential users reading this thread.
We humans are NOT perfect. When try to appear perfect, we deny the truth.
And we would not be credible in fellow men's eyes.
Isn't it pathetic hear someone say:
"I did not have seex with that woman"
when it is obviously a big lie. :D :D
I hope you're human at this developers site.
I have a slight hope some few around here
are not only "living effective programming robot machines".
Regards and thanks for your FREE, although not working software
/halojoy - Sweden 2004-12-29
FACTS follows:
In my htdocs:
APP1-folder
     MyClass.class
     index.html(<applet codebase="." code="MyClass.class"</applet>)
APP2-folder
     MyClass.class
     index.html(<applet codebase="." code="MyClass.class"</applet>)
Uses same class, but I have copy at 2 places.
First applet will run correctly.
Second applet will generate following message:
Exception in thread "AWT-EventQueue-13" java.lang.NullPointerException
     at sun.font.FontDesignMetrics.stringWidth(Unknown Source)
     at DJClock.update(E:\Msdev\projects\DJClock\DJClock.java:552)
     at sun.awt.RepaintArea.updateComponent(Unknown Source)
     at sun.awt.RepaintArea.paint(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.pumpOneEventForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)

Answer 1

Thanks, alvareze.
But I think you haven't read my post correctly.
I think I provided enough information for eanyone to repeat my situation in their own computer.
Anf find out there is a bug.
I wish I was wrong, on behalf of users suffering from this,
but I am sure I am right!
So here is what you do.
1) Take an applet, xxxxxx.class, intended for showing in a html-page.
2) Create 2 folders at your server. Lets call them: APPL1 and APPL2
3) Write 2 different index.html containing applet xxxxxx.class
4) You make a copy of this Class: xxxxxx.class in EACH of two folders APPL1, APPL2
5) Each index.html in separate folders Calls their own copy of xxxxxx.class
in respective folder.
6) The structure you have now is, what I ALREADY told you. (am I talking to children. No!):
In my htdocs:
APP1-folder
     MyClass.class
     index.html(<applet codebase="." code="MyClass.class"</applet>)
APP2-folder
     MyClass.class
     index.html(<applet codebase="." code="MyClass.class"</applet>)
6) Now you can visit your both websites:
- http://root/APPL1/index.html
running applet.
Then visit
- http://root/APPL2/index.html
running same applet.
And I am sure you will end up with same error message.
AWT-EventQueue-13" exception.
(see Above. And below. LISTEN CAREFULLY, I will only say this TWICE):
Uses same class, but I have copy at 2 places.
##) My EXPLANATION:
possibly causing this error, and making JRE useless for me:
When JRE runs into a Class with same name again,
it will update that class in its library.
But when it does it searches, STILL, in the developers Drive E:\
A leftover code, from developing stage.
Instead JRE should look for MyClass.class in drive where,
I put JRE files. In this case Drive C:\
##) In other words:
- at MyClass.update(E:\Msdev\projects\MyClass\MyClass.java:552)
should be, to avoid error
- at MyClass.update(C:\my path to JRE\MyClass\MyClass.java:552)
##) First applet will run correctly.
##)Second applet will generate following message:
Exception in thread "AWT-EventQueue-13" java.lang.NullPointerException
     at sun.font.FontDesignMetrics.stringWidth(Unknown Source)
     at MyClass.update(E:\Msdev\projects\MyClass\MyClass.java:552)
     at sun.awt.RepaintArea.updateComponent(Unknown Source)
     at sun.awt.RepaintArea.paint(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.pumpOneEventForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)
I wont bother with this again,
as I do not like to explain myself over and over
to people that are not REALLY interested in getting my information.
And it will not effect me in any way, as I no longer use this free JRE from great Sun Java Laboratories.
I stick to Microsoft Java, until you find your bugs, yourselves, fixes this software version.
Then you tell me to download it again, please!
Thanks again for you wish to provide us users with a super software.
nothing wrong with your aim or goal, but ...
maybe can strike back, when releasing not properly debugged sotware
to millions and millions of potential users.
Better no reputation, than bad reputation= badwill.
So sometimes better late release than too early.
Have seen this happen with other software version around www.
By the time bugs are corected, customers are happily using another similiar software.
No hard feelings.
Happy Ne Year everybody!
computer and internet freaks, like me
/halojoy - in snowy northern part of Sweden (had a white christmas, as always)
Sorry, will not be here again, talking to deaf? people :)
in same subject
GoodBye