The joy of deploying Servlets

There are several ways to put data on the screen:

1) Console: a 40×80 grid of characters, input from keyboard, program launches on program execution.
2) Windows: with mouse and keyboard, input from a variety of controls, especially text boxes and buttons, program launches on events
3) Web server: HTML pages generated by servets, input from HTML forms, program launches when browser requests page

Console is easy, but not exciting.
Windows take forever to put together a simple form.
Web servers are a pain to deploy, for example:

- Write servlet (exetend HtttpServlet & override doGet)
- Write jps pages
- Write static pages
- In JBuilder, set project properties, set up a folder pointing at serlvet.jar
- Compile
- Create tags for web application in server.xml
- Create folder structure \webapps\YourApp\WEB-INF\Classes\package- Put files of package named ‘package’ into folder named ‘package’
- Figure out name of page, eg.

http://localhost:8080/YourApp/servlet/servlettest.myServlet

- Create an alias for a friendlier URL
- Put servlet into JAR

It’s no wonder that Java programmers get so excited about a tool like ANT.

Getting MS Explorer to Swing

I want to write an application that uses the Swing library and runs on any MS Explorer machine, without the client installing extra software or changing evironment variables, or spending a day dowloanding.

Here is what I’ve learned:

1) People complain about Swing, for being big & slow, but it has more features & better looks than VB forms. The other UI for java include: HTML, AWT, commercial & free non-Sun component libraries, & command line. For my main goal right now (showing off), these other options don’t measure up.
2) Mozilla 1.0 requires a manual file copy to get the Java plug-in to work
3) MSIE can do Swing if you unjar the file swingall.jar, but loading it from local on a fast machine takes a while. Also, you get a lot of security access errors as the swing form tries to figure out what kind of machine it is one (for plugable look and feel)
4) JBuilder has to be set to build for all VMs to get an applet that MSIE can open.
5) MSIE doesn’t seem to be able to open a jar archive without special software, although for some reason creating a CLASSPATH environment variable pointing to the swingall.jar file seems to work. (So a jar is OK if it local, bad if you download it? I don’t understand.)
6) Using jarg on javaswing reduces it from 2.2MB to 1.6MB, which is not much of an improvement & the applet gets a little broken in the shrinking process.
7) Putting java files into a jar is easier if you don’t use a manifest file & just use : jar cvf newjar.jar *
You execute this command in the root of all your classes & packages that you want in the jar.
8) Packages and jars are headaches, don’t try to include them in your build process if you are still learning. The errors caused by package and jar problems look a lot like other problems (namely they all give Class not found errors)
9) MSIE (using VM5) sometimes crashes the entire computer, I’m not sure if it was Swing related.
10) Command line programs should be run using lots of 1 line .bat files. Some applications have such complicated switch syntax it is like writting a mini program.
11) Downloading a .jar application and running it is fairly easy, two files often will suffice (the jar file & a batch file with
ava -jar myapp.jar
12)