How to fix/workaround java.lang.reflect.InvocationTargetException
Solution 1
InvocationTargetException
1 is thrown because the HTML is calling (trying to load) something that is not an applet. Change it to:
<p><applet code="MainApplet" width="800" width="600">
</applet></p>
Also, as mentioned in the answer of Stephen C. Move the stuff from the constructor into the init()
method.
InvocationTargetException
is a checked exception that wraps an exception thrown by an invoked method or constructor.
Ensure the Java Console is configured to show for applets & JWS apps. If there is no output at the default level, raise it and try again.
While I'm here: Why code an applet? If it is due to spec. by teacher, please refer them to Why CS teachers should stop teaching Java applets.
Solution 2
I suggest that you read the Oracle Applet Development Tutorial. I'm not an expert on applets (understatement!) but you seem to be doing a lot of things differently to how the Tutorial says to do them. For instance, you don't use a main
method to launch an applet, and you should be doing the setup in the init
method not the constructor (see here).
user2403876
Updated on July 09, 2022Comments
-
user2403876 almost 2 years
I've got a question about a particularly annoying error that I haven't been able to figure out, much less overcome. Any time I try to run a Java applet (Applet or JApplet) on my website, I get this error as a pop-up:
java.lang.reflect.InvocationTargetException
No stack trace, no line number, just the error message. So I've Googled around looking for anyone else's workarounds (or ideally actual fixes) but haven't been able to find much. I've tried several variations of my code (sometimes with a JAR file, sometimes not, sometimes a single class, sometimes not, sometimes in a package using a matching directory structure, sometimes no package, etc.) but can't seem to get past this nasty little son-of-a-bug. :)
For a specific example, here's my most recent attempt; first the Java code:
package cmtoolbox; public class CMToolbox { public static void main(String[] args) { MainApplet a = new MainApplet(); } }
The class it sets up:
package cmtoolbox; import javax.swing.JApplet; import javax.swing.JButton; public class MainApplet extends JApplet { public MainApplet() { JApplet main = new JApplet(); main.setSize(800,600); JButton test1 = new JButton(); test1.setText("Test"); main.add(test1); } }
My HTML code:
<html> <head> <title> Experimenting with Java applets </title> </head> <body> <p><applet code="CMToolbox.class" width="800" width="600"> I wish. :) </applet></p> </body> </html>
I suppose that maybe because the web itself can have so many variables (operating systems, browser types, etc.) there is something internal/system-level causing this... but I do have the JRE and JDK installed on my computer so I don't really get why... Anyway, I'm sure I'm not the first guy to hit this roadblock, but it's got me stumped so I'd appreciate any info that may be available on the subject. Also if you know of any good Java web tutorials for absolute noobs that would be great as well. :)
-
Stephen C almost 11 years@AndrewThompson - The documentation I linked to seems to say that
init
is preferable because the environment may not be ready when the constructor is invoked. -
Stephen C almost 11 years+2 For mentioning that you shouldn't be using applets anyway.
-
user2403876 almost 11 yearsOkay, I see your point - I have often thought applets were borderline obsolete anyway (lol). But what would be the alternative, then? Most of the Java web tutorials and resources I've seen deal with applets; so if coding applets is such a dumb idea (and again I get you on that), what else is there? Thanks. :)
-
user2403876 almost 11 yearsWell the project I have in mind was going to be web-based because it would use a shared database among users (users would log in, add info etc). But that's not the only project I have in mind; I was also thinking a game or two, etc. Either way the idea was to get into putting my Java programs on the web.
-
Andrew Thompson almost 11 years"shared database among users (users would log in, add info etc)." A desktop app. can easily connect to a web-app. based front-end to a DB. If you want to 'launch it from a link' you could look to Java Web Start. 'Phoning home' to the same server (for the DB front-end) could be sand-boxed.
-
Andrew Thompson almost 11 years"also thinking a game or two, etc." Again better as a free floating app. on the desktop, launched using JWS.
-
user2403876 almost 11 yearsThanks for the info. I hadn't realized Java programs can connect to the internet without actually being "embedded" in a website. It does make more sense the way you describe tho. Thanks! :)