Given by Nancy J. McCracken,Tom Scavo,Geoffrey C. Fox at Jackson State CSC499 on Spring 1998. Foils prepared 12 Feb 98
Outside Index
Summary of Material
Overview including History and alpha versus production issues |
Comparison of Java and Javascript |
Overall Java Philosophy and Features including security etc. |
And in Remaining Parts of Tutorial!!
|
Outside Index
Summary of Material
Instructors: Geoffrey Fox |
Nancy McCracken |
Tom Scavo |
Syracuse University |
111 College Place |
Syracuse |
New York 13244-4100 |
Overview including History of Java Development |
Comparison of Java and JavaScript |
Overall Java Philosophy and Features including security etc. |
Java Programming Language |
Object-Oriented and Class Structure |
Exceptions and Threads |
Application and Applet Programming |
Abstract Windowing Toolkit |
Networking and I/O |
Futures and HPCC Implications |
What is Java?
|
Java is interesting because
|
The Web is becoming the dominant software development arena; this will drive Java as the best supported, most widely taught language
|
The original resource was the The Java Language Specification by Sun Microsystems, Inc., March 1995 updated to October 1995 but superceded by Gosling and Arnold Book
|
Sun's web site http://www.javasoft.com/ has plenty of references including
|
Most of the books cited earlier have CDROMs with examples and the JDK. |
Browsers (HotJava, Netscape 2.0/3.0/4.0, Microsoft IE) supporting Java allow arbitrarily sophisticated dynamic multimedia applications called Applets, written in Java, to be embedded in regular HTML pages and activated on each exposure of a given page. |
Applets are incorporated into web pages with
|
Steps to running a Java Applet:
|
Using a Browser
|
Using appletviewer
|
Java applications are compiled and run on a machine just like any other general-purpose programming language such as C/C++. No web server or network are required although Java applications may also use network connections for distributed computing |
All Java programs are written into a file with a ".java" extension |
Java Applications are ".java" files with a main() method, which is excuted first |
To compile and run a Java application:
|
The tools javac and java are part of JDK, which is available from Sun and has been ported to many platforms (Solaris, IRIX, AIX, and Windows 95/NT) |
Since Java is object-oriented, programs are organized into modules called classes, which may have data in variables and functions called methods. |
Java applets are classes written in Java, which are intended not to run as stand-alone programs (as applications do) but as subprograms of a browser that is already managing a window |
Applets should NOT have a main() method but rather methods init(), start(), paint() etc. that are invoked by the browser |
The applet should be run through javac compiler producing a ".class" file as before: javac MyApplet.java |
Also, create an HTML file (say "MyApplet.html") with an <APPLET> tag that loads "MyApplet.class" |
Two ways to run an applet:
|
This way we develop where JDK installed but run almost anywhere! |
Given the following HTML |
<APPLET CODE="StockGraph.class"
|
</APPLET> |
Runs the "StockGraph.class" executable as an applet |
WIDTH and HEIGHT are attributes that are passed along to the applet |
If the optional CODEBASE attribute is provided, then load the executable from the directory specified by CODEBASE
|
Tag and attribute names are case insensitive |
<APPLET CODE="StockGraph.class" WIDTH=200 HEIGHT=200
|
Put text here for browsers that do not support Java |
</APPLET> |
ALT specifies text to be displayed if the browser understands the <APPLET> tag, but unable to run applets (i.e., Java-disabled) |
NAME specifies the name of this instance of the applet; this makes it possible for applets on the same page to find and communicate with each other, and for JavaScript to communicate with Java, for example |
ALIGN specifies the alignment of the applet. The possible values are the same as those available in the <IMG> tag (top, middle, bottom, texttop, absmiddle, baseline, absbottom, left, right).
|
VSPACE and HSPACE specifies the vertical and horizontal spacing in pixels, around the applet space. |
The applet tag can be followed by parameters:
|
The Java program accesses this information by
|
Typically this processing would be in the init() method of the applet |
Java applets can call methods to display graphics on the screen (within the browser window). This example overrides a public method paint() (defined in a superclass of Applet) and calls a method drawString() defined in the class Graphics. |
The file must have the same name as your applet (e.g., HelloWorldApplet.java). Now run the compiler (javac), getting a bytecode file HelloWorldApplet.class, which is placed in a web directory (not a CGI directory!). |
Starts in 1991 by Project Green --- a group at Sun detaches from the main campus as a semi-autonomous task force focused on operating software for consumer electronic devices such as smart set-top boxes |
Gosling (creator of UNIX emacs and Sun NeWS, which had major conceptual impact both on current Java and Telescript models) realizes that C++ is not adequate and initiates development of a new language Oak, later renamed as Java. |
A PDA (Personal Digital Assistant -- codename *7) based on Oak/Java ready in 1993. Green Team incorporates as FirstPerson, Inc. |
*7 proposal to Time-Warner rejected in 1993. 3DO deal falls through in 1994. FirstPerson, Inc. dissolves. |
Small group (~30 people, now Java Team) continues development and decides to adapt Oak as a Web technology. |
An experimental web browser written in Java, called WebRunner and later renamed as HotJava, ready in 1994. |
Alpha release of Java and browser HotJava April '95. |
Netscape licences Java in May '95 and builds Java into Netscape 2.0 -- This confuses ownership and openness of Java |
Beta JDK (Java Development Kit) published in summer/fall '95. It is better software but lower functionality than Alpha. |
First Java books appear in fall '95 such as a popular overview by SAMS and technical book "Java!" by Tim Ritchey, edited by New Riders. |
Dec 4 1995 Business Week cover story on "Software Revolution --- The Web Changes Everything" exposes Java as a breakthrough force in the expanding Web/Internet. Also points out that "Java as a business" is yet to be defined. |
In next week, SGI, IBM, Adobe, Macromedia, and finally Microsoft adopt/license Java. Java goes into open standards process and is adopted by Web community. |
Teach Yourself Java in 21 Days, 2nd ed., by Laura Lemay and Charles L. Perkins, Sams.net Publishing, is a "how-to" book at the intermediate programming level, greatly expanded from the original edition. |
Java in a Nutshell, by David Flanagan, is a language reference book in the familiar O'Reilly series. The 2nd edition of this book omits many examples from the first edition to make room for a large section on JDK 1.1 - currently best book reference. A separate book of examples is available. |
Java, How to Program, by Deitel & Deitel, Prentice-Hall, starts with beginning programming concepts and progresses rapidly through Java language. It has the most programming exercises and also has companion teaching multimedia tools |
The Java Programming Language, by Ken Arnold and James Gosling, Addison-Wesley, May 1996, has lots of details on the language basics for intermediate and advanced programmers. It covers threads and I/O packages, but not applets or windowing packages.
|
Java Primer Plus, supercharging Web applications with the Java programming language, by Paul M. Tyma, Gabriel Torok, and Troy Downing, Sams.net, doesn't assume a lot of programming background, has chatty explanations and still covers lots of programming detail. |
There are now many books in the Java Series from SunSoft Press, Prentice-Hall. Here are the first five:
|
* this title is great, but what happened to "express Java", "Percolating through Java", and "Java for Drips"? |
The beta version of Java, Version 1.0 of JDK released January 96 by JavaSoft |
JDK 1.0 becomes the Internet standard and so compatible with ongoing Java implementations by all licensees, most notably Netscape and Microsoft. JDK version 1.0.2 includes:
|
A substantial new version of Java released in March 97 |
This release includes many developments by Sun and partner companies such as IBM. There are minimal changes to the language --- primarily development of new classes to support enterprise computing. |
Included in JDK 1.1 are: core library (including source), Java compiler (javac), Java interpreter (java), Java runtime interpreter (jre), appletviewer, debugger (jdb), disassembler (javap), documentation generator (javadoc), C header and stub file generator (javah), archive tool (jar), signing tool (javakey), plus numerous other tools (native2ascii, rmic, rmiregistry, serialver, and updateAWT)
|
http://java.sun.com/products/jdk/1.1 |
Originally, the Java interpreter was incorporated into browsers such as those from Netscape and Microsoft, but the Web server remained a standard one. |
Now Web servers are being developed in Java itself. This leads to more natural integration of the use of Java applets on the Web browsers and Java applications running on the Web server machine.
|
Netscape renames LiveScript as JavaScript. The latter is fully interpreted (code can be included directly in HTML file) and used for overall customization of client |
Use Java for detailed programming and JavaScript for overall integration of client interface, for example |
JavaScript: Interpreted by client and NOT compiled |
Java: Compiled on server before execution on client
|
JavaScript: Object-based, no classes or inheritance; built-in extensible objects |
Java: Object-oriented; programs consist of object classes with inheritance |
JavaScript: Tightly integrated with HTML |
Java: Applets distinct from HTML but invoked from HTML pages |
JavaScript: Loosely typed---in general, variables not declared |
Java: Strongly typed---all variables must be declared |
JavaScript: dynamic binding---object references determined at runtime |
Java: static binding---object references determined at compile time |
Java and JavaScript are secure and cannot write to disk |
JavaScript has most user interface components of Java (buttons, frames, etc.), even mouse actions in JS 1.2 |
Document The Java: A White Paper by Sun Microsystems -- October 1995 draft by James Gosling and Henry McGilton -- expounds on the original design of Java: |
Simple and familiar |
Object-oriented |
Architecture-neutral |
Portable |
Somewhat Interpreted |
Distributed |
Robust |
Secure |
High performance |
Multi Threaded |
Dynamic |
Java omits several rarely used, poorly understood, and confusing features of C++, including operator overloading, multiple inheritance, pointers, and automatic type coercions. |
It adds automatic garbage collection, which makes dynamic programming easier in Java than in C or C++.
|
It also adds 'Interface' construct, an Objective C concept, which often compensates for the lack of multiple inheritance by allowing method calling syntax to be "inherited". |
The resulting language is familiar, as it looks like C++, but is simpler and hence easier to program in. |
It also results in a much smaller kernel, which is suitable for Java ports to consumer electronic devices. Base (alpha) interpreter is ~40Kb, libraries and threads add additional 175Kb. |
Java model can be viewed as a C++ subset, with some dynamic elements inherited from Objective-C (method overloading, garbage collection). |
Structures, Unions and Functions are absorbed into data and methods of Java classes -- Java is Simple! |
The strength of Java object-oriented model is not its sophistication, but in simplicity and the extensive class library associated with the system (some 250 public classes were released initially). |
Java class also plays a role of a communication entity in the Web embedding model. Applet classes identify themselves by names in the HTML applet tag. Applet downloads other classes, present in the applet source. Hence, the Java class names play the role of addressing mode for the distributed Java code database. |
C/C++ programming in a heterogeneous network environment requires use and compatibility across several vendor platforms and the corresponding compilers. This problem is solved in Java by designing platform-independent binary representation called Java bytecode written for the "Java Virtual Machine" |
Java compiler (written in Java and platform-independent) reads Java source and generates Java bytecodes (.class files). These bytecodes are shipped to client machines upon browser request. |
Each client machine must run Java interpreter, which performs runtime execution of Java bytecodes. Java interpreter is written in POSIX compliant ANSI C and needs to be ported to and conventionally compiled (once) on each individual platform. |
Once the interpreter is ported, application developers don't need to worry at all about platform specificity and differences between native compilers. |
Java language offers a uniform abstract (virtual) machine model, which is identical for all platforms |
SUN owns the Java Virtual Machine (see online report) -- it is universal, but classes can be added by any user |
Unlike C/C++ where various integers match the architecture of a physical machine at hand, Java byte, char, short, int and long are always of the same size, equal to 8, 16, 16(unicode), 32 and 64 bits, respectively.
|
Differences between vendor specific windowing environments (X Windows, MS Windows, Macintosh) are removed in terms of the Abstract Windowing Toolkit (AWT) metaphor. |
AWT is given by ~60 Java classes (alpha) which offer a universal GUI programming model, portable between UNIX, PC and Mac, and translated automatically to native windowing systems on individual platforms by Java interpreters. |
Java represents a compromise between fully compiled (like C/C++) and fully interpreted (like Smalltalk or Perl) models. |
Java "compiler" produces a binary bytecode output that is portable and much smaller than the real binary for a specific machine (typical bytecode size is on the order of the original source code, within a factor of 2). |
Java "interpreter" executes this bytecode and is therefore less dynamic than e.g. Perl interpreter (which performs an equivalent bytecode construction internally and on-the-fly when reading the program source). |
In general, the compilation process is: a) time consuming and b) platform specific. Hence, interpreters are built and used to facilitate a) rapid prototyping and/or b) portability. Java model is focused on platform independence but the development throughput is also reasonable since the Java compiler is fast and generates compact bytecode output. |
Popular TCP/IP based protocols such as FTP or HTTP are supported in terms of network protocol classes.
|
Distributed computing model of Java is mainly client-server, with Java compiler preparing the bytecodes on the server side, and the Java interpreter executing the bytecodes on the client side. |
Java enforces compiler-time type checking and eliminates some error prone constructs of C/C++. |
Pointer arithmetic is totally eliminated, which allows e.g. runtime checking of array subscripts and enforces security of the Java model. |
Explicit declarations are always required, i.e., C-style implicit declarations are forbidden. This allows the Java complier to perform early error detection and give good error messages. |
Rapid prototyping in Java is less natural than in JavaScript, Lisp, Tcl, Smalltalk, or Perl, but the software quality assurance of Java is higher than in these more dynamic and 'forgiving' languages. |
Java bytecodes are shipped across the network and executed on client machines. Security is therefore a critical issue and strongly enforced in Java.
|
Modifications of the C++ model such as eliminating pointer arithmetic and type coercion were dictated mainly by the security requirements. |
Most viruses are based on acquiring access to private/protected sectors of computer memory, which is impossible in Java. |
Java bytecodes are executed on the client side by the Java interpreter, which operates exclusively on virtual memory. Hence, unless there are security bugs in the Java interpreter itself, the model is safe and users cannot create security holes by incorrectly or maliciously writing applets. |
The bytecodes sent across network are verified on the client, which prevents evil/corrupted classes from causing problems |
Java interpreter performs on-the-fly runtime execution of the Java bytecodes, which results typically in a satisfactory performance.
|
Support for generating native machine code out of Java bytecodes, viewed as intermediate compiler form, is also provided and useful for performance demanding applications. |
The performance of the machine code, generated from Java bytecodes, is comparable to that offered by typical C/C++ compilers on the same platform. |
Several of these concepts are in fact similar as in the OSF/ANDF project. Using ANDF terminology, we would call Java compiler a 'producer', and the machine code generator discussed here, an 'installer'. Default Java working mode doesn't use installers but directly interprets the intermediate form (this mode is supported in ANDF by GAI -- Generalized ANDF Interpreter). |
Java/HotJava system implements ANDF concepts for the Java language. |
Java model offers preemptive multithreading, implemented in terms of the Thread class. Thread methods offer a set of synchronization primitives based on monitor and conditional variable paradigm by C.A.R. Hoare. Java threads inherit some features from the pioneering Cedar/Mesa System by Xerox Park that gave birth to Macintosh and object-oriented programming. |
A typical use of Java multithreading in applet programming is to have several independent but related simulations (e.g. various sorting algorithms), running concurrently in an applet window. Multithreading is also used internally by the browser to handle multiple document dynamics. |
Another interesting application domain are multi-HotJava environments such as collaboratories or games. |
Java threads don't have built-in point-to-point communication primitives. Various thread communication environments can be provided by coupling the thread and network protocol objects. |
Java model is more dynamic than C++ and closer to Smalltalk or Perl. |
Subclasses don't need to to be recompiled after superclass implementation is updated. |
C++ has "fragile superclass" problem where children must recompiled if anything changes (method/instance variable) in a superclass or referenced class -- Java resolves references at runtime and avoids this. |
Classes have runtime representation (implemented in terms of the Class class), which allows one to look up type of a given object instance at runtime (in C cannot know if pointer is to integer or browser!) |