Now that you’ve learned how to create JAR files, how do you actually run the code that you’ve packaged? Consider these three scenarios:
\n
\n- Your JAR file contains an applet that is to be run inside a browser. <\/LI>
\n- Your JAR file contains an application that is to be invoked from the command line. <\/LI>
\n- Your JAR file contains code that you want to use as an extension. <\/LI><\/UL>
\nThis section will cover the first two situations. A separate trail in the tutorial on the extension mechanism<\/A> covers the use of JAR files as extensions. <\/P><\/BLOCKQUOTE>
\nApplets Packaged in JAR Files<\/H3>
\nTo invoke any applet from an HTML file for running inside a browser, you need to use the APPLET tag. For more information, see the Applets<\/A> lesson. If the applet is bundled as a JAR file, the only thing you need to do differently is to use the ARCHIVE<\/EM> parameter to specify the relative path to the JAR file.
\nAs an example, let’s use (again!) the TicTacToe demo applet that ships with the JavaTM<\/SUP><\/FONT> Development Kit. The APPLET tag in the HTML file that calls the demo looks like this: <\/P>
\n<applet code=TicTacToe.class
\n width=120 height=120>
\n<\/applet>
\n<\/PRE><\/BLOCKQUOTE>If the TicTacToe demo were packaged in a JAR file named TicTacToe.jar<\/TT>, you could modify the APPLET tag with the simple addition of an ARCHIVE parameter:
\n<applet code=TicTacToe.class
\n archive=”TicTacToe.jar”
\n width=120 height=120>
\n<\/applet>
\n<\/PRE><\/BLOCKQUOTE>The ARCHIVE parameter specifies the relative path to the JAR file that contains TicTacToe.class<\/TT>. This example assumes that the JAR file and the HTML file are in the same directory. If they’re not, you would need to include the JAR file’s relative path in the ARCHIVE parameter’s value. For example, if the JAR file was one directory below the HTML file in a directory called applets<\/TT>, the APPLET tag would look like this:
\n<applet code=TicTacToe.class
\n archive=”applets\/TicTacToe.jar”
\n width=120 height=120>
\n<\/applet>
\n<\/PRE><\/BLOCKQUOTE><\/BLOCKQUOTE><\/A>
\nJAR Files as Applications<\/H3>
\nYou can run JAR-packaged applications with the Java interpreter. The basic command is:
\njava -jar jar-file<\/I>
\n<\/PRE><\/BLOCKQUOTE>The -jar<\/TT> flag tells the interpreter that the application is packaged in the JAR file format. You can only specify one JAR file, which must contain all the application-specific code.
\nBefore you execute this command make sure the runtime environment has an information of which class within the JAR file is the application’s entry point. <\/P>
\nTo indicate which class is the application’s entry point, you must add a Main-Class<\/TT> header to the JAR file’s manifest. The header takes the form: <\/P>
\nMain-Class: classname<\/I>
\n<\/PRE><\/BLOCKQUOTE>The header’s value, classname<\/TT>, is the name of the class that’s the application’s entry point.
\nFor more information, see the Setting an Application’s Entry Point<\/A> section. <\/P>
\nWhen the Main-Class<\/TT> is set in the manifest file, you can run the application from the command line: <\/P>
\njava -jar app.jar
\n<\/PRE><\/BLOCKQUOTE><\/BLOCKQUOTE>
\n<\/DIV><\/p>\n","protected":false},"excerpt":{"rendered":"Running JAR-Packaged Software Now that you’ve learned how to create JAR files, how do you actually run the code that you’ve packaged? Consider these three scenarios: Your JAR file contains an applet that is to be run inside a browser. Your JAR file contains an application that is to be invoked from the command line. … Continue reading Running JAR-Packaged Software<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-369","post","type-post","status-publish","format-standard","hentry"],"_links":{"self":[{"href":"https:\/\/www.strongd.net\/index.php?rest_route=\/wp\/v2\/posts\/369","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.strongd.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.strongd.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.strongd.net\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.strongd.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=369"}],"version-history":[{"count":0,"href":"https:\/\/www.strongd.net\/index.php?rest_route=\/wp\/v2\/posts\/369\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.strongd.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=369"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.strongd.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=369"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.strongd.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=369"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}