This week's book giveaway is in the OCAJP forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide 1Z0-808 and have Jeanne Boyarsky & Scott Selikoff on-line! See this thread for details.
To deploy as an Applet, you would need to do some modification to your code so that it is an Applet, rather then an application. Using JWS, you can basically deploy your application as is.
The main difference is that an applet runs "inside" the web page. Just like all those wonderful advertisements on web pages today that use Flash, the applet appears within the web page. If the user closes the browser, or navigates away from the page, the Applet stops.
Using JWS, the application runs outside the web page (and outside the browser). In other words, it runs as if the user had it installed on their computer. And as mentioned above, if you go the Applet route, your program must extend either Applet or JApplet (which is a subclass of Applet).
The "tricky" part of both of these technologies is that you do not know what (if any) version of the JRE the user has installed on their computer. There are ways to set a minimum requirement in the deployment code. So if your Application needs Java version 1.5 or later, and the user has 1.4.2 installed, an installer is automatically launched to install the 1.5 version (assuming you set up your JWS JNLP page or your Applet's <object> tag correctly).