Java (programming language)
{{redirect|Java language|the Indonesian spoken language|Javanese language}}
{{distinguish|JavaScript}}
{{otheruses2|Java}}
{{ infobox programming language
| name = Java
| logo = [[Image:Java Logo.svg|100px]]
| paradigm = [[Object-oriented programming|Object-oriented]], [[Structured programming|structured]], [[Imperative programming|imperative]]
| year = 1995
| designer = [[Sun Microsystems]]
| latest_release_version = Java Standard Edition 6 (1.6.0)
| latest_release_date =
| latest_test_version =
| latest_test_date =
| turing-complete = Yes
| typing = [[Type system|Static, strong, safe]], [[Nominative type system|nominative]]
| implementations = Numerous
| influenced_by = [[Objective-C]], [[C++]], [[Smalltalk]], [[Eiffel (programming language)|Eiffel]]{{ cite web | authors = Gosling and McGilton | title = The Java Language Environment | date= May 1996 | url = http://java.sun.com/docs/white/langenv/ }}, [[Ada 83]], [[Mesa (programming language)|Mesa]]{{
cite web | authors = J. Gosling, B. Joy, G. Steele, G. Brachda | title = The Java Language Specification, 2nd Edition | url= http://java.sun.com/docs/books/jls/second_edition/html/intro.doc.html#237601 }}, [[C Sharp (programming language)|C#]]Java 5.0 added several new language features (the [[foreach|enhanced for loop]], [[autoboxing]], [[varargs]] and [[Java annotation|annotations]]), after they were introduced in the similar (and competing) [[C Sharp (programming language)|C#]] language. [http://www.barrycornelius.com/papers/java5/][http://www.levenez.com/lang/]
| influenced = [[C Sharp (programming language)|C#]], [[D programming language|D]], [[J sharp|J#]], [[Ada (programming language)|Ada 2005]], [[ECMAScript]], [[PHP]], [[Scala (programming language)|Scala]]
| operating_system = [[Cross-platform]]
| license = [[GNU General Public License]] / [[Java Community Process]]
| website = http://java.sun.com
}}
'''Java''' is a [[programming language]] originally developed by [[Sun Microsystems]] and released in 1995 as a core component of Sun Microsystems' [[Java (Sun)|Java platform]]. The language derives much of its [[Syntax of programming languages|syntax]] from [[C (programming language)|C]] and [[C++]] but has a simpler [[object model]] and fewer low-level facilities. Java applications are typically [[compiler|compiled]] to [[bytecode]] that can run on any [[Java virtual machine]] (JVM) regardless of [[computer architecture]].
The original and [[reference implementation]] Java [[compiler]]s, virtual machines, and [[library (computing)|class libraries]] were developed by Sun from 1995. As of May 2007, in compliance with the specifications of the [[Java Community Process]], Sun made available most of their Java technologies as [[free software]] under the [[GNU General Public License]]. Others have also developed alternative implementations of these Sun technologies, such as the [[GNU Compiler for Java]] and [[GNU Classpath]].
== History ==
[[Image:Wave.svg|thumb|75px|Duke, the Java mascot]]
{{Main|Java (Sun)#History|Java version history}}
The Java language was created by [[James Gosling]] in June 1991 for use in one of his many [[set-top box]]
projects.Jon Byous, [http://java.sun.com/features/1998/05/birthday.html ''Java technology: The early years'']. Sun Developer Network, no date [ca. 1998]. Retrieved [[April 22]], [[2005]]. The language was initially called ''Oak'', after an [[oak tree]] that stood outside Gosling's office—and also went by the name ''Green''—and ended up later being renamed to ''Java'', from a list of random words.http://blogs.sun.com/jonathan/entry/better_is_always_different. Gosling's goals were to implement a [[virtual machine]] and a language that had a familiar C/C++ style of notation.Heinz Kabutz, [http://www.artima.com/weblogs/viewpost.jsp?thread=7555 ''Once Upon an Oak'']. Artima, Retrieved [[April 29]], [[2007]]. The first public implementation was Java 1.0 in 1995. It promised "[[Write once, run anywhere|Write Once, Run Anywhere]]" (WORA), providing no-cost runtimes on popular platforms. It was fairly secure and its security was configurable, allowing network and file access to be restricted. Major web browsers soon incorporated the ability to run secure Java ''[[applet]]s'' within web pages. Java quickly became popular. With the advent of ''Java 2'', new versions had multiple configurations built for different types of platforms. For example, ''[[J2EE]]'' was for enterprise applications and the greatly stripped down version ''[[J2ME]]'' was for mobile applications. ''[[J2SE]]'' was the designation for the Standard Edition. In 2006, for marketing purposes, new ''J2'' versions were renamed ''Java EE'', ''Java ME'', and ''Java SE'', respectively.
In 1997, Sun Microsystems approached the [[International Organization for Standardization#JTC1|ISO/IEC JTC1 standards body]] and later the [[Ecma International]] to formalize Java, but it soon withdrew from the process.[http://www.open-std.org/JTC1/SC22/JSG/ Java Study Group][http://csdl2.computer.org/comp/proceedings/hicss/2001/0981/05/09815015.pdf Why Java Was - Not - Standardized Twice][http://techupdate.zdnet.com/techupdate/stories/main/0,14179,2832719,00.html What is ECMA--and why Microsoft cares] Java remains a [[de facto]] standard that is controlled through the [[Java Community Process]].[http://www.jcp.org/en/home/index Java Community Process website] At one time, Sun made most of its Java implementations available without charge although they were [[proprietary software]]. Sun's revenue from Java was generated by the selling of licenses for specialized products such as the Java Enterprise System. Sun distinguishes between its [[Software Development Kit|Software Development Kit (SDK)]] and [[HotSpot|Runtime Environment (JRE)]] that is a subset of the SDK, the primary distinction being that in the JRE, the compiler, utility programs, and many necessary header files are not present.
On [[13 November]] [[2006]], Sun released much of Java as [[free software|free]] and [[open-source software|open-source]] software under the terms of the [[GNU General Public License]] (GPL). On [[8 May]] [[2007]] Sun finished the process, making all of Java's core code free and open-source, aside from a small portion of code to which Sun did not hold the copyright.[http://open.itworld.com/4915/070508opsjava/page_1.html open.itworld.com - JAVAONE: Sun - The bulk of Java is open sourced]
== Philosophy ==
=== Primary goals ===
There were five primary goals in the creation of the Java language:[http://java.sun.com/docs/white/langenv/Intro.doc2.html 1.2 Design Goals of the JavaTM Programming Language]
# It should use the [[object-oriented programming]] methodology.
# It should allow the same program to be [[execution (computers)|executed]] on multiple [[operating system]]s.
# It should contain built-in support for using [[computer network]]s.
# It should be designed to execute code from [[remote procedure call|remote source]]s securely.
# It should be easy to use by selecting what were considered the good parts of other object-oriented languages.
=== Platform independence ===
{{main|Java Platform}}
One characteristic, [[Cross-platform|platform independence]], means that [[computer program|program]]s written in the Java language must run similarly on any supported hardware/operating-system platform. One should be able to write a program once, compile it once, and run it anywhere.
This is achieved by most Java [[compiler]]s by compiling the Java language code ''halfway'' (to [[Java bytecode]]) – simplified machine instructions specific to the Java platform. The code is then run on a [[virtual machine]] (VM), a program written in native code on the host hardware that [[Interpreter (computing)|interprets]] and executes generic Java bytecode. (In some JVM versions, bytecode can also be compiled to native code, either before or during program execution, resulting in faster execution.) Further, standardized libraries are provided to allow access to features of the host machines (such as graphics, [[thread (computer science)|threading]] and [[Computer network|networking]]) in unified ways. Note that, although there is an explicit compiling stage, at some point, the Java bytecode is interpreted or converted to native [[machine code]] by the [[Just-in-time compilation|JIT compiler]].
The first implementations of the language used an interpreted virtual machine to achieve [[Porting|portability]]. These implementations produced programs that ran slower than programs compiled to native executables, for instance written in C or C++, so the language suffered a reputation for poor performance. More recent JVM implementations produce programs that run significantly faster than before, using multiple techniques.
One technique, known as ''just-in-time compilation'' (JIT), translates the Java bytecode into native code at the time that the program is run, which results in a program that executes faster than interpreted code but also incurs compilation overhead during execution. More sophisticated VMs use ''[[dynamic recompilation]]'', in which the VM can analyze the behavior of the running program and selectively recompile and optimize critical parts of the program. Dynamic recompilation can achieve optimizations superior to static compilation because the dynamic compiler can base optimizations on knowledge about the runtime environment and the set of loaded classes, and can identify the ''hot spots'' (parts of the program, often inner loops, that take up the most execution time). JIT compilation and dynamic recompilation allow Java programs to take advantage of the speed of native code without losing portability.
Another technique, commonly known as ''static compilation'', is to compile directly into native code like a more traditional compiler. Static Java compilers, such as [[GCJ]], translate the Java language code to native [[object code]], removing the intermediate bytecode stage. This achieves good performance compared to interpretation, but at the expense of portability; the output of these compilers can only be run on a single [[Computer architecture|architecture]]. Some see avoiding the VM in this manner as defeating the point of developing in Java; however it can be useful to provide both a generic [[bytecode]] version, as well as an optimised native code version of an application.
=== Implementations ===
Sun Microsystems officially licenses the Java Standard Edition platform for [[Microsoft Windows]], [[Linux]], and [[Solaris (operating system)|Solaris]]. Through a network of third-party vendors and licensees[http://java.sun.com/javase/licensees.jsp Java SE - Licensees], alternative Java environments are available for these and other platforms. To qualify as a certified Java licensee, an implementation on any particular platform must pass a rigorous suite of validation and compatibility tests. This method enables a guaranteed level of compliance and platform through a trusted set of commercial and non-commercial partners.
Sun's trademark license for usage of the Java brand insists that all implementations be "compatible". This resulted in a legal dispute with [[Microsoft]] after Sun claimed that the Microsoft implementation did not support the [[Java remote method invocation|RMI]] and [[Java Native Interface|JNI]] interfaces and had added platform-specific features of their own. Sun sued in 1997, and in 2001 won a settlement of $20 million as well as a court order enforcing the terms of the license from Sun.{{cite news
| authorlink =
| author = James Niccolai
| title = Sun, Microsoft settle Java lawsuit
| url = http://www.javaworld.com/javaworld/jw-01-2001/jw-0124-iw-mssuncourt.html
| work = JavaWorld
| publisher = [[IDG]]
| date = January 23, 2001
| accessdate = 2008-07-09
}} As a result, Microsoft no longer ships Java with [[Microsoft Windows|Windows]], and in recent versions of Windows, [[Internet Explorer]] cannot support Java applets without a third-party plugin. However, Sun and others have made available Java run-time systems at no cost for those and other versions of Windows.
Platform-independent Java is essential to the [[Java Enterprise Edition]] strategy, and an even more rigorous validation is required to certify an implementation. This environment enables portable server-side applications, such as [[Web service]]s, [[servlet]]s, and [[Enterprise JavaBean]]s, as well as with [[Embedded system]]s based on [[OSGi]], using [[Embedded Java]] environments. Through the new [[GlassFish]] project, Sun is working to create a fully functional, unified [[open-source]] implementation of the Java EE technologies.
=== Automatic memory management ===
{{See also|Garbage collection (computer science)}}
One of the ideas behind Java's automatic memory management model is that programmers be spared the burden of having to perform manual memory management. In some languages the programmer allocates memory for the creation of objects stored on the [[heap]] and the responsibility of later deallocating that memory also resides with the programmer. If the programmer forgets to deallocate memory or writes code that fails to do so, a [[memory leak]] occurs and the program can consume an arbitrarily large amount of memory. Additionally, if the program attempts to deallocate the region of memory more than once, the result is undefined and the program may become unstable and may crash. Finally, in non garbage collected environments, there is a certain degree of overhead and complexity of user-code to track and finalize allocations. Often developers may box themselves into certain designs to provide reasonable assurances that memory leaks will not occur.[http://www.research.att.com/~bs/bs_faq2.html#memory-leaks Stroustrup: C++ Style and Technique FAQ]
In Java, this potential problem is avoided by [[automatic garbage collection]]. The programmer determines when objects are created, and the Java runtime is responsible for managing the [[object lifetime|object's lifecycle]]. The program or other objects can reference an object by holding a reference to it (which, from a low-level point of view, is its address on the heap). When no references to an object remain, the [[unreachable object]] is eligible for release by the Java garbage collector - it may be freed automatically by the garbage collector at any time. Memory leaks may still occur if a programmer's code holds a reference to an object that is no longer needed—in other words, they can still occur but at higher conceptual levels.
The use of garbage collection in a language can also affect programming paradigms. If, for example, the developer assumes that the cost of memory allocation/recollection is low, they may choose to more freely construct objects instead of pre-initializing, holding and reusing them. With the small cost of potential performance penalties (inner-loop construction of large/complex objects), this facilitates thread-isolation (no need to synchronize as different threads work on different object instances) and data-hiding. The use of transient immutable value-objects minimizes side-effect programming.
Comparing Java and [[C++]], it is possible in C++ to implement similar functionality (for example, a memory management model for specific classes can be designed in C++ to improve speed and lower memory fragmentation considerably), with the possible cost of adding comparable runtime overhead to that of Java's garbage collector, and of added development time and application complexity if one favors manual implementation over using an existing third-party library. In Java, garbage collection is built-in and virtually invisible to the developer. That is, developers may have no notion of when garbage collection will take place as it may not necessarily correlate with any actions being explicitly performed by the code they write. Depending on intended application, this can be beneficial or disadvantageous: the programmer is freed from performing low-level tasks, but at the same time loses the option of writing lower level code. Additionally, the garbage collection capability demands some attention to tuning the JVM, as large heaps will cause apparently random stalls in performance.
Java does not support [[pointer (computing)|pointer arithmetic]] as is supported in, for example, C++. This is because the garbage collector may relocate referenced objects, invalidating such pointers. Another reason that Java forbids this is that type safety and security can no longer be guaranteed if arbitrary manipulation of pointers is allowed.
== Syntax ==
{{main|Java syntax}}
The syntax of Java is largely derived from [[C++]]. Unlike C++, which combines the syntax for structured, generic, and object-oriented programming, Java was built exclusively as an object oriented language. As a result, almost everything is an object and all code is written inside a class. The exceptions are the intrinsic data types (ordinal and real numbers, boolean values, and characters), which are not classes for performance reasons.
=== Hello, world program ===
This is a minimal [[Hello world program]] in Java with [[syntax highlighting]]:
// Hello.java
public class Hello {
public static void main(String[] args) {
System.out.println("Hello, world!");
}
}
To execute a Java program, the code is saved as a file named Hello.java. It must first be compiled into bytecode using a [[Java compiler]], which produces a file named Hello.class. This class is then ''launched''.
The above example merits a bit of explanation.
* All executable statements in Java are written inside a class, including stand-alone programs.
* Source files are by convention named the same as the class they contain, appending the mandatory suffix ''.java''. A '''class''' that is declared '''public''' is required to follow this convention. (In this case, the class '''Hello''' is public, therefore the source must be stored in a file called ''Hello.java'').
* The compiler will generate a class file for each class defined in the source file. The name of the class file is the name of the class, with ''.class'' appended. For class file generation, anonymous classes are treated as if their name was the concatenation of the name of their enclosing class, a ''$'', and an integer.
* The [[Java keywords|keyword]] '''public''' denotes that a method can be called from code in other classes, or that a class may be used by classes outside the class hierarchy.
* The keyword '''static''' indicates that the method is a [[class method|static method]], associated with the class rather than object instances.
* The keyword '''void''' indicates that the main method does not return any value to the caller.
* The method name "main" is not a keyword in the Java language. It is simply the name of the method the Java launcher calls to pass control to the program. Java classes that run in managed environments such as applets and [[Enterprise Java Beans]] do not use or need a main() method.
* The main method must accept an [[array]] of '''{{Javadoc:SE|java/lang|String}}''' objects. By convention, it is referenced as '''args''' although any other legal identifier name can be used. Since Java 5, the main method can also use [[varargs|variable arguments]], in the form of public static void main(String... args), allowing the main method to be invoked with an arbitrary number of String arguments. The effect of this alternate declaration is semantically identical (the args parameter is still an array of String objects), but allows an alternate syntax for creating and passing the array.
* The Java launcher launches Java by loading a given class (specified on the command line) and starting its public static void main(String[]) method. Stand-alone programs must declare this method explicitly. The String[] args parameter is an [[array]] of {{Javadoc:SE|java/lang|String}} objects containing any arguments passed to the class. The parameters to main are often passed by means of a [[command line]].
* The printing facility is part of the Java standard library: The '''{{Javadoc:SE|java/lang|System}}''' class defines a public static field called '''{{Javadoc:SE|name=out|java/lang|System|out}}'''. The out object is an instance of the {{Javadoc:SE|java/io|PrintStream}} class and provides the method '''{{Javadoc:SE|name=println(String)|java/io|PrintStream|println(java.lang.String)}}''' for displaying data to the screen while creating a new line ([[standard streams|standard out]]).
=== A more comprehensive example ===
// OddEven.java
import javax.swing.JOptionPane;
public class OddEven {
public static void main(String[] args) {
// This is the main method. It gets called when this class is run through a Java interpreter.
OddEven number = new OddEven();
/* This line of code creates a new instance of this class called "number" and
* initializes it, and the next line of code calls the "showDialog()" method,
* which brings up a prompt to ask you for a number
*/
number.showDialog();
}
private int input; // A whole number("int" means integer)
// "input" is the number that the user gives to the computer
public OddEven() {
/* This is the constructor method. It gets called when an object of the OddEven type
* is created.
*/
}
public void showDialog() {
try
/* This makes sure nothing goes wrong. If something does,
* the interpreter skips to "catch" to see what it should do.
*/
{
input = Integer.parseInt(JOptionPane.showInputDialog("Please Enter A Number"));
calculate();
/*
* The code above brings up a JOptionPane, which is a dialog box
* The String returned by the "showInputDialog()" method is converted into
* an integer, making the program treat it as a number instead of a word.
* After that, this method calls a second method, calculate() that will
* display either "Even" or "Odd."
*/
}
catch (NumberFormatException e)
/* This means that there was a problem with the format of the number
* (Like if someone were to type in 'Hello world' instead of a number).
*/
{
System.err.println("ERROR: Invalid input. Please type in a numerical value.");
}
}
private void calculate() {
if (input % 2 == 0)
System.out.println("Even");
/* When this gets called, it sends a message to the interpreter.
* The interpreter usually shows it on the command prompt (For Windows users)
* or the terminal (For Linux users).(Assuming it's open)
*/
else
System.out.println("Odd");
}
}
* The '''[[Java keywords#import|import]]''' statement imports the '''{{Javadoc:SE|javax/swing|JOptionPane}}''' class from the '''{{Javadoc:SE|package=javax.swing|javax/swing}}''' package.
* The '''OddEven''' class declares a single '''[[Java keywords#private|private]]''' [[field (computer science)|field]] of type '''int''' named '''input'''. Every instance of the OddEven class has its own copy of the input field. The private declaration means that no other class can access (read or write) the input field.
* '''OddEven()''' is a '''public''' [[constructor (computer science)|constructor]]. Constructors have the same name as the enclosing class they are declared in, and unlike a method, have no [[return type]]. A constructor is used to initialize an [[object (computer science)|object]] that is a newly created instance of the class. The dialog returns a String that is converted to an int by the '''{{Javadoc:SE|java/lang|Integer|parseInt(String)}}''' method.
* The '''calculate()''' method is declared without the static keyword. This means that the method is invoked using a specific instance of the OddEven class. (The [[reference (computer science)|reference]] used to invoke the method is passed as an undeclared parameter of type OddEven named '''[[Java keywords#this|this]]'''.) The method tests the expression input % 2 == 0 using the '''[[Java keywords#if|if]]''' keyword to see if the remainder of dividing the input field belonging to the instance of the class by two is zero. If this expression is true, then it prints '''Even'''; if this expression is false it prints '''Odd'''. (The input field can be equivalently accessed as this.input, which explicitly uses the undeclared this parameter.)
* '''OddEven number = new OddEven();''' declares a local object [[reference (computer science)|reference]] variable in the main method named number. This variable can hold a reference to an object of type OddEven. The declaration initializes number by first creating an instance of the OddEven class, using the '''[[Java keywords#new|new]]''' keyword and the OddEven() constructor, and then assigning this instance to the variable.
* The statement '''number.showDialog();''' calls the calculate method. The instance of OddEven object referenced by the number [[local variable]] is used to invoke the method and passed as the undeclared this parameter to the calculate method.
* For simplicity, [[error handling]] has been ignored in this example. Entering a value that is not a number will cause the program to crash. This can be avoided by catching and handling the {{Javadoc:SE|java/lang|NumberFormatException}} thrown by Integer.parseInt(String).
=== Applet ===
{{Main|Java applet}}
Java applets are programs that are embedded in other applications, typically in a Web page displayed in a [[Web browser]].
// Hello.java
import java.applet.Applet;
import java.awt.Graphics;
public class Hello extends Applet {
public void paint(Graphics gc) {
gc.drawString("Hello, world!", 65, 95);
}
}
The '''import''' statements direct the [[Java compiler]] to include the '''{{Javadoc:SE|package=java.applet|java/applet|Applet}}''' and '''{{Javadoc:SE|package=java.awt|java/awt|Graphics}}''' classes in the compilation. The import statement allows these classes to be referenced in the [[source code]] using the ''simple class name'' (i.e. Applet) instead of the ''fully qualified class name'' (i.e. java.applet.Applet).
The Hello class '''extends''' ([[subclass (computer science)|subclasses]]) the '''Applet''' class; the Applet class provides the framework for the host application to display and control the [[Object lifetime|lifecycle]] of the applet. The Applet class is an [[Abstract Windowing Toolkit]] (AWT) {{Javadoc:SE|java/awt|Component}}, which provides the applet with the capability to display a [[graphical user interface]] (GUI) and respond to user [[event-driven programming|events]].
The Hello class [[method overriding (programming)|overrides]] the '''{{Javadoc:SE|name=paint(Graphics)|java/awt|Container|paint(java.awt.Graphics)}}''' method inherited from the {{Javadoc:SE|java/awt|Container}} [[superclass (computer science)|superclass]] to provide the code to display the applet. The paint() method is passed a '''Graphics''' object that contains the graphic context used to display the applet. The paint() method calls the graphic context '''{{Javadoc:SE|name=drawString(String, int, int)|java/awt|Graphics|drawString(java.lang.String,%20int,%20int)}}''' method to display the '''"Hello, world!"''' string at a [[pixel]] offset of ('''65, 95''') from the upper-left corner in the applet's display.
Hello World Applet
An applet is placed in an [[HTML]] document using the '''''' [[HTML element]]. The applet tag has three attributes set: '''code="Hello"''' specifies the name of the Applet class and '''width="200" height="200"''' sets the pixel width and height of the applet. Applets may also be embedded in HTML using either the object or embed element[http://java.sun.com/docs/books/tutorial/deployment/applet/applettag.html Using the applet Tag (The Java Tutorials > Deployment > Applets)], although support for these elements by Web browsers is inconsistent.[http://java.sun.com/docs/books/tutorial/deployment/applet/mixedbrowser.html Deploying Applets in a Mixed-Browser Environment (The Java Tutorials > Deployment > Applets)] However, the applet tag is deprecated, so the object tag is preferred where supported.
The host application, typically a Web browser, instantiates the '''Hello''' applet and creates an {{Javadoc:SE|java/applet|AppletContext}} for the applet. Once the applet has initialized itself, it is added to the AWT display hierarchy. The paint method is called by the AWT [[event dispatching thread]] whenever the display needs the applet to draw itself.
=== '''Servlet''' ===
{{Main|Java Servlet}}
Java Servlet technology provides Web developers with a simple, consistent mechanism for extending the functionality of a Web server and for accessing existing business systems. Servlets are [[server-side]] Java EE components that generate responses (typically [[HTML]] pages) to requests (typically [[HTTP]] requests) from [[client (computing)|client]]s. A servlet can almost be thought of as an applet that runs on the server side—without a face.
// Hello.java
import java.io.*;
import javax.servlet.*;
public class Hello extends GenericServlet {
public void service(ServletRequest request, ServletResponse response)
throws ServletException, IOException {
response.setContentType("text/html");
final PrintWriter pw = response.getWriter();
pw.println("Hello, world!");
pw.close();
}
}
The '''import''' statements direct the Java compiler to include all of the public classes and [[interface (Java)|interfaces]] from the '''{{Javadoc:SE|package=java.io|java/io}}''' and '''{{Javadoc:EE|package=javax.servlet|javax/servlet}}''' [[Java package|packages]] in the compilation.
The '''Hello''' class '''extends''' the '''{{Javadoc:EE|javax/servlet|GenericServlet}}''' class; the GenericServlet class provides the interface for the [[server (computing)|server]] to forward requests to the servlet and control the servlet's lifecycle.
The Hello class overrides the '''{{Javadoc:EE|name=service(ServletRequest, ServletResponse)|javax/servlet|Servlet|service(javax.servlet.ServletRequest,javax.servlet.ServletResponse)}}''' method defined by the {{Javadoc:EE|javax/servlet|Servlet}} [[Interface (Java)|interface]] to provide the code for the service request handler. The service() method is passed a '''{{Javadoc:EE|javax/servlet|ServletRequest}}''' object that contains the request from the client and a '''{{Javadoc:EE|javax/servlet|ServletResponse}}''' object used to create the response returned to the client. The service() method declares that it '''throws''' the [[exception handling|exceptions]] {{Javadoc:EE|javax/servlet|ServletException}} and {{Javadoc:SE|java/io|IOException}} if a problem prevents it from responding to the request.
The '''{{Javadoc:EE|name=setContentType(String)|javax/servlet|ServletResponse|setContentType(java.lang.String)}}''' method in the response object is called to set the [[MIME]] content type of the returned data to '''"text/html"'''. The '''{{Javadoc:EE|name=getWriter()|javax/servlet|ServletResponse|getWriter()}}''' method in the response returns a '''{{Javadoc:SE|java/io|PrintWriter}}''' object that is used to write the data that is sent to the client. The '''{{Javadoc:SE|name=println(String)|java/io|PrintWriter|println(java.lang.String)}}''' method is called to write the '''"Hello, world!"''' string to the response and then the '''{{Javadoc:SE|name=close()|java/io|PrintWriter|close()}}''' method is called to close the print writer, which causes the data that has been written to the stream to be returned to the client.
=== JavaServer Page ===
{{Main|JavaServer Pages}}
JavaServer Pages (JSPs) are [[server-side]] Java EE components that generate responses, typically [[HTML]] pages, to [[HTTP]] requests from [[client (computing)|client]]s. JSPs embed Java code in an HTML page by using the special [[delimiter]]s <% and %>. A JSP is compiled to a Java ''servlet'', a Java application in its own right, the first time it is accessed. After that, the generated servlet creates the response.
=== Swing application ===
{{Main|Swing (Java)}}
Swing is a graphical user interface [[library (computer science)|library]] for the Java SE platform. This example Swing application creates a single window with "Hello, world!" inside:
// Hello.java (Java SE 5)
import java.awt.BorderLayout;
import javax.swing.*;
public class Hello extends JFrame {
public Hello() {
super("hello");
setDefaultCloseOperation(WindowConstants.EXIT_ON_CLOSE);
setLayout(new BorderLayout());
add(new JLabel("Hello, world!"));
pack();
}
public static void main(String[] args) {
new Hello().setVisible(true);
}
}
The first '''import''' statement directs the Java compiler to include the {{Javadoc:SE|java/awt|BorderLayout}} class from the {{Javadoc:SE|package=java.awt|java/awt}} package in the compilation; the second '''import''' includes all of the public classes and interfaces from the '''{{Javadoc:SE|package=javax.swing|javax/swing}}''' package.
The '''Hello''' class '''extends''' the '''{{Javadoc:SE|javax/swing|JFrame}}''' class; the JFrame class implements a [[window (computing)|window]] with a [[title bar]] and a close [[Widget (computing)|control]].
The '''Hello()''' [[constructor (computer science)|constructor]] initializes the frame by first calling the superclass constructor, passing the parameter "hello", which is used as the window's title. It then calls the '''{{Javadoc:SE|name=setDefaultCloseOperation(int)|javax/swing|JFrame|setDefaultCloseOperation(int)}}''' method inherited from JFrame to set the default operation when the close control on the title bar is selected to '''{{Javadoc:SE|javax/swing|WindowConstants|EXIT_ON_CLOSE}}''' — this causes the JFrame to be disposed of when the frame is closed (as opposed to merely hidden), which allows the JVM to exit and the program to terminate. Next, the [[Layout manager|layout]] of the frame is set to a BorderLayout; this tells Swing how to arrange the components that will be added to the frame. A '''{{Javadoc:SE|javax/swing|JLabel}}''' is created for the string '''"Hello, world!"''' and the '''{{Javadoc:SE|name=add(Component)|java/awt|Container|add(java.awt.Component)}}''' method inherited from the {{Javadoc:SE|java/awt|Container}} superclass is called to add the label to the frame. The '''{{Javadoc:SE|name=pack()|java/awt|Window|pack()}}''' method inherited from the {{Javadoc:SE|java/awt|Window}} superclass is called to size the window and lay out its contents, in the manner indicated by the BorderLayout.
The '''main()''' method is called by the JVM when the program starts. It [[Instance (programming)|instantiates]] a new '''Hello''' frame and causes it to be displayed by calling the '''{{Javadoc:SE|name=setVisible(boolean)|java/awt|Component|setVisible(boolean)}}''' method inherited from the {{Javadoc:SE|java/awt|Component}} superclass with the boolean parameter '''true'''. Note that once the frame is displayed, exiting the main method does not cause the program to terminate because the AWT [[event dispatching thread]] remains active until all of the Swing top-level windows have been disposed.
== Criticism ==
{{main article|Criticism of Java}}
[[Java performance|Java's performance]] has improved substantially since the early versions, and performance of [[JIT compiler]]s relative to native compilers has in some tests been shown to be quite similar.[http://www.idiom.com/~zilla/Computer/javaCbenchmark.html Performance of Java versus C++], J.P.Lewis and Ulrich Neumann, Computer Graphics and Immersive Technology Lab, [[University of Southern California]][http://www.kano.net/javabench/ The Java is Faster than C++ and C++ Sucks Unbiased Benchmark][http://research.sun.com/techrep/2002/smli_tr-2002-114.pdf FreeTTS - A Performance Case Study], Willie Walker, Paul Lamere, Philip Kwok The performance of the compilers does not necessarily indicate the performance of the compiled code; only careful testing can reveal the true performance issues in any system.
The default [[look and feel]] of [[Graphical User Interface|GUI]] applications written in Java using the [[Swing (Java)|Swing]] toolkit is very different from native applications. It is possible to specify a different look and feel through the [[pluggable look and feel]] system of Swing. Clones of [[Microsoft Windows|Windows]], [[GTK]] and [[Motif (widget toolkit)|Motif]] are supplied by Sun. [[Apple Computer|Apple]] also provides an [[Aqua (theme)|Aqua]] look and feel for [[Mac OS X]]. Though prior implementations of these looks and feels have been considered lacking,{{Fact|date=May 2008}} Swing in Java SE 6 addresses this problem by using more native [[Widget (computing)|widget]] drawing routines of the underlying platforms. Alternatively, third party toolkits such as [[wx4j]], [[Qt (toolkit)|Qt Jambi]] or [[Standard Widget Toolkit|SWT]] may be used for increased integration with the native windowing system.
As in C++ and some other object-oriented languages, variables of Java's [[primitive type]]s were not originally objects. Values of primitive types are either stored directly in fields (for objects) or on the [[Stack-based memory allocation|stack]] (for methods) rather than on the heap, as is the common case for objects (but see [[Escape analysis]]). This was a conscious decision by Java's designers for performance reasons. Because of this, Java was not considered to be a pure object-oriented programming language. However, as of Java 5.0, [[Object type|autoboxing]] enables programmers to write as if primitive types are their wrapper classes, with their object-oriented counterparts representing classes of their own, and freely interchange between them for improved flexibility.
Java suppresses several features (such as [[operator overloading]] and [[multiple inheritance]]) for ''classes'' in order to simplify the language, to "save the programmers from themselves", and to prevent possible errors and anti-pattern design. This has been a source of criticism,{{Fact|date=May 2008}} relating to a lack of low-level features, but some of these limitations may be worked around. Java ''interfaces'' have always had multiple inheritance.
== Resources ==
=== Java Runtime Environment ===
{{Main|Java Runtime Environment}}
The Java Runtime Environment, or ''JRE'', is the software required to run any [[Application software|application]] deployed on the Java Platform. [[End-user]]s commonly use a JRE in [[Software package (programming)|software package]]s and Web browser [[plugin]]s. Sun also distributes a superset of the JRE called the Java 2 [[SDK]] (more commonly known as the JDK), which includes development tools such as the [[Java compiler]], [[Javadoc]], [[JAR (file format)|Jar]] and [[debugger]].
One of the unique advantages of the concept of a runtime engine is that errors (exceptions) should not 'crash' the system. Moreover, in runtime engine environments such as Java there exist tools that attach to the runtime engine and every time that an exception of interest occurs they record debugging information that existed in memory at the time the exception was thrown (stack and heap values). These [[Automated Exception Handling]] tools provide 'root-cause' information for exceptions in Java programs that run in production, testing or development environments.
==== Components ====
* Java [[Library (computer science)|libraries]] are the compiled [[byte code]]s of [[source code]] developed by the JRE implementor to support application development in Java. Examples of these libraries are:
** The core libraries, which include:
*** Collection libraries that implement [[data structure]]s such as [[List (computing)|lists]], [[associative array|dictionaries]], [[tree structure|trees]] and [[Set (computer science)|sets]]
*** [[XML]] Processing (Parsing, Transforming, Validating) libraries
*** Security
*** [[i18n|Internationalization and localization]] libraries
** The integration libraries, which allow the application writer to communicate with external systems. These libraries include:
*** The [[Java Database Connectivity]] (JDBC) [[Application Programming Interface|API]] for database access
*** [[Java Naming and Directory Interface]] (JNDI) for lookup and discovery
*** [[Java remote method invocation|RMI]] and [[CORBA]] for distributed application development
** [[User Interface]] libraries, which include:
*** The (heavyweight, or [[native mode|native]]) [[Abstract Windowing Toolkit]] (AWT), which provides [[graphical user interface|GUI]] components, the means for laying out those components and the means for handling events from those components
*** The (lightweight) [[Swing (Java)|Swing]] libraries, which are built on AWT but provide (non-native) implementations of the AWT widgetry
*** APIs for audio capture, processing, and playback
* A platform dependent implementation of [[Java virtual machine]] (JVM) that is the means by which the byte codes of the Java libraries and third party applications are executed
* Plugins, which enable [[Java applet|applet]]s to be run in [[Web browser]]s
* [[Java Web Start]], which allows Java applications to be efficiently distributed to [[end user]]s across the [[Internet]]
* Licensing and documentation
=== APIs ===
{{see also|Free Java implementations#Class library}}
Sun has defined three platforms targeting different application environments and segmented many of its [[application programming interface|API]]s so that they belong to one of the platforms. The platforms are:
* [[Java Platform, Micro Edition]] (Java ME) — targeting environments with limited resources,
* [[Java Platform, Standard Edition]] (Java SE) — targeting workstation environments, and
* [[Java Platform, Enterprise Edition]] (Java EE) — targeting large distributed enterprise or Internet environments.
The [[Class (computer science)|classes]] in the Java APIs are organized into separate groups called [[Java package|packages]]. Each package contains a set of related [[Interface (Java)|interface]]s, classes and [[exception handling|exceptions]]. Refer to the separate platforms for a description of the packages available.
The set of APIs is controlled by Sun Microsystems in cooperation with others through the [[Java Community Process]] program. Companies or individuals participating in this process can influence the design and development of the APIs. This process has been a subject of controversy.
== See also ==
* [[Comparison of programming languages]]
* [[Comparison of Java and C Sharp]]
* [[C Sharp (programming language)|C#]]
* [[Groovy (programming language)]]
* [[Jython| Jython (Java implementation of Python)]]
* [[JRuby| JRuby (Java implementation of Ruby)]]
* [[Pnuts]]
* [[Join Java]]
* [[JavaOne]]
* [[Javapedia]]
* [[List of integrated development environments]]
* [[List of Java virtual machines]]
* [[List of Java APIs]]
* [[List of Java scripting languages]]
* [[Java Posse]]
* [[Java version history]]
* [[Swing (Java)]]
== Notes ==
{{reflist|2}}
== References ==
{{refbegin}}
* Jon Byous, [http://java.sun.com/features/1998/05/birthday.html ''Java technology: The early years'']. Sun Developer Network, no date [ca. 1998]. Retrieved [[April 22]], [[2005]].
* [[James Gosling]], [https://duke.dev.java.net/green/ ''A brief history of the Green project'']. Java.net, no date [ca. Q1/1998]. Retrieved [[April 29]], [[2007]].
* [[James Gosling]], [[Bill Joy]], [[Guy L. Steele, Jr.|Guy Steele]], and [[Gilad Bracha]], ''The Java language specification'', third edition. Addison-Wesley, 2005. ISBN 0-321-24678-0 (see also [http://java.sun.com/docs/books/jls/index.html online edition of the specification].
* Tim Lindholm and Frank Yellin. ''The Java Virtual Machine specification'', second edition. Addison-Wesley, 1999. ISBN 0-201-43294-3 (see also [http://java.sun.com/docs/books/vmspec/2nd-edition/html/VMSpecTOC.doc.html online edition of the specification]).
{{refend}}
== External links ==
{{Wikibooks|Java Programming}}
{{Wikiversity|java}}
* [http://www.java.com/ Java home page]
* [http://java.sun.com/ Java for developers]
* {{Javadoc:SE}}
* [https://duke.dev.java.net/green/ A Brief History of the Green Project]
* [http://sunsite.uakom.sk/sunworldonline/swol-07-1995/swol-07-java.html Java: The Inside Story]
* [http://cs.gmu.edu/~sean/stuff/java-objc.html Java Was Strongly Influenced by Objective-C]
* [http://www.wired.com/wired/archive/3.12/java.saga.html The Java Saga]
* [http://ei.cs.vt.edu/~wwwbtb/book/chap1/java_hist.html A history of Java]
* [http://www.blinkenlights.com/classiccmp/javaorigin.html The Long Strange Trip to Java]
* [http://computing.open.ac.uk/m254/ M254 Java Everywhere] (free open content documents from the [http://www.open.ac.uk/ Open University])
* [http://java.sun.com/docs/books/jls/download/langspec-3.0.pdf Java Language Specification (pdf)]
{{Java (Sun)}}
{{Sun Microsystems}}
{{FOSS}}
[[Category:Java programming language| ]]
[[Category:Java platform|Programming language]]
[[Category:Java specification requests|Programming language]]
[[Category:C programming language family]]
[[Category:Sun Microsystems]]
[[Category:Concurrent programming languages]]
[[Category:Class-based programming languages]]
[[Category:Object-oriented programming languages]]
[[Category:JVM programming languages]]
[[Category:JVM programming language]]
[[am:ጃቫ (java)]]
[[ar:جافا]]
[[az:Java]]
[[bn:জাভা (প্রোগ্রামিং ভাষা)]]
[[be:Java]]
[[be-x-old:Java]]
[[bs:Java programski jezik]]
[[bg:Java]]
[[ca:Java (llenguatge de programació)]]
[[cs:Java]]
[[co:Java]]
[[da:Java (programmeringssprog)]]
[[de:Java (Programmiersprache)]]
[[et:Java]]
[[el:Java]]
[[es:Lenguaje de programación Java]]
[[eo:Java]]
[[eu:Java (programazio lengoaia)]]
[[fa:جاوا (زبان برنامهنویسی)]]
[[fr:Java (langage)]]
[[ga:Java]]
[[gl:Linguaxe Java]]
[[ko:자바 (프로그래밍 언어)]]
[[hr:Java (programski jezik)]]
[[id:Java]]
[[ia:Java (linguage de programmation)]]
[[is:Java (forritunarmál)]]
[[it:Java (linguaggio)]]
[[he:Java]]
[[ka:ჯავა (პროგრამირების ენა)]]
[[ht:Java]]
[[lv:Java (valoda)]]
[[lt:Java (kalba)]]
[[hu:Java (programozási nyelv)]]
[[mk:Јава (програмски јазик)]]
[[ml:ജാവാ പ്രോഗ്രാമിങ് ഭാഷ]]
[[ms:Java]]
[[cdo:Java]]
[[nl:Java (programmeertaal)]]
[[ja:Java]]
[[no:Java (programmeringsspråk)]]
[[nn:Programmeringsspråket Java]]
[[uz:Java]]
[[pl:Java]]
[[pt:Java (linguagem de programação)]]
[[ro:Java (limbaj de programare)]]
[[ru:Java]]
[[sq:Java (gjuhë programimi)]]
[[si:ජාවා (පරිගණක ක්රමලේඛන බස)]]
[[simple:Java (programming language)]]
[[sk:Java]]
[[sl:Programski jezik java]]
[[sr:Јава (програмски језик)]]
[[fi:Java]]
[[sv:Java (programmeringsspråk)]]
[[tl:Java (wikang pamprograma)]]
[[ta:ஜாவா நிரலாக்க மொழி]]
[[te:జావా]]
[[th:ภาษาจาวา]]
[[vi:Java (ngôn ngữ lập trình)]]
[[tr:Java (programlama dili)]]
[[bug:Java]]
[[uk:Java]]
[[bat-smg:Java]]
[[zh:Java]]