1. CSC 243 - Java Programming, Spring, 2009
Welcome to Java Programming!
Tuesday, January 13, 2009

2. What are we planning to do?
We will transport ourselves from C++ to Java programming in a series of graceful steps.
We will use modular construction techniques, with the assistance of Java classes and interfaces.
We will learn how to get leverage from the massive Java class library.
We will learn to use programming tools such as Eclipse.
We will enter the realm of graphical user interface (GUI) and other event-driven programming.

3. References
has downloads from our textbook.
GNU make
docs.
has on-line docs.
class lib.
/export/home/faculty/parson/JavaLang on bill.kutztown.edu
Make sure that /usr/jdk/jdk1.6.0_02/bin is near the front of UNIX PATH.
Follow instructions in the JavaShellSetup.pdf document (accessible via my home page at to set up and verify your Java compilation environment

4. Java programs run on a Java Virtual Machine (JVM)
Java source program, FILE.java
javac –g FILE.java (creates FILE.class)
java PACKAGE.FILE
where PACKAGE is a subdirectory under ~/JavaLang
This runs PACKAGE.FILE on an interpreted JVM.

5. Categories of Java Virtual Machines
Java EE (Enterprise Edition) comes with enterprise level class libraries, for example, large database and server infrastructure
Java SE (Standard Edition) is the typical configuration for non-corporate users, including single users
Java ME (Micro Edition) is for embedded devices. It has a small and special-purpose class library.

6. Varieties of Java “programs”
Stand-alone applications run like C++ programs.
Applets run inside a web browser (GUI).
Servlets run inside a web server (HTML).
Java Frameworks can select and load Java plugins (components) at run time.
Java can run on small footprint embedded devices (for example, cell phones).

7. First example Java program
CountArgString counts distinct, non-overlapping occurrences of a string in a file
/export/home/faculty/parson/JavaLang/week1/lecture1
Make sure you “cp –pr ~parson/JavaLang ~/JavaLang” to get JavaLang into your home directory
Make sure CLASSPATH include your $HOME/JavaLang
makefile drives execution of compile and test steps
gmake build to compile Java files
gmake test to run test cases
gmake clean to clean up test output and compiled files