Java (programming language): Difference between revisions

Content deleted Content added
Modulatum (talk | contribs)
mNo edit summary
m Disambiguating links to Object-orientation (link changed to Object-oriented programming) using DisamAssist.
 
Line 1:
{{Short description|Object-oriented programming language}}
{{redirect|Java language|the Indonesian spoken language|Javanese language}}
{{About|the object-oriented programming language|the software platform|Java (software platform)|the Indonesian island|Java|the Indonesian Language|Javanese (disambiguation){{!}}Javanese|other uses|Java (disambiguation)}}
{{distinguish|JavaScript}}
{{Distinguish|JavaScript}}
{{otheruses2|Java}}
{{Redirect|Openframe|the ten-pin bowling term|Open frame}}
{{ infobox programming language
{{Pp-semi-indef|small=yes}}
| name = Java
{{Use mdy dates|date=August 2017}}
| logo = [[Image:Java Logo.svg|100px]]
{{Infobox programming language
| paradigm = [[Object-oriented programming|Object-oriented]], [[Structured programming|structured]], [[Imperative programming|imperative]]
| name = Java
| year = [[1995]]
| logo = Java programming language logo.svg
| designer = [[Sun Microsystems]]
| logo size = 121px
| latest_release_version = Java Standard Edition 6 (1.6.0)
| logo caption =
| latest_release_date =
| paradigm = [[Programming paradigm#Multi-paradigm|Multi-paradigm]]: [[generic programming|generic]], [[Object-oriented programming|object-oriented]] ([[class-based programming|class-based]]), [[functional programming|functional]], [[imperative programming|imperative]], [[reflective programming|reflective]], [[concurrent computing|concurrent]]
| latest_test_version =
| year = {{Start date and age|1995|5|23}}<ref>{{cite magazine|url=https://www.forbes.com/sites/oracle/2015/05/20/javas-20-years-of-innovation/|title=Java's 20 Years of Innovation|magazine=Forbes|date=May 20, 2015|access-date=March 18, 2016|author=Binstock, Andrew|archive-url=https://web.archive.org/web/20160314102242/http://www.forbes.com/sites/oracle/2015/05/20/javas-20-years-of-innovation/|archive-date=March 14, 2016|url-status=live}}</ref>
| latest_test_date =
| discontinued = <!-- Set to yes if software is discontinued, otherwise omit. -->
| turing-complete = Yes
| ver layout = <!-- simple (default) or stacked -->
| typing = [[Type system|Static, strong, safe]], [[Nominative type system|nominative]]
| latest release version = {{wikidata|property|preferred|references|edit|Q251|P348|P548=Q2804309}}
| implementations = Numerous
| latest release date = {{Start date and age|{{wikidata|qualifier|preferred|single|Q251|P348|P548=Q2804309|P577}}}}
| influenced_by = [[Objective-C]], [[C++]], [[Smalltalk]], [[Eiffel (programming language)|Eiffel]]<ref>{{ cite web | authors = Gosling and McGilton | title = The Java Language Environment | date= May 1996 | url = http://java.sun.com/docs/white/langenv/ }}</ref>, [[Ada 83]], [[Mesa (programming language)|Mesa]]<ref>{{
| designer = [[James Gosling]]
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 }}</ref>, [[Modula-3]] <ref>http://www.computerworld.com.au/index.php/id;1422447371;pp;3;fp;4194304;fpid;1</ref>[[C Sharp (programming language)|C#]]<ref>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/]</ref>
| developer = [[Oracle Corporation]]
| influenced = [[C Sharp (programming language)|C#]], [[D programming language|D]], [[J sharp|J#]], [[Ada (programming language)|Ada&nbsp;2005]], [[ECMAScript]], [[PHP]], [[Scala (programming language)|Scala]]
| typing = [[type system|Static, strong, safe]], [[nominal type system|nominative]], [[manifest typing|manifest]]
| operating_system = [[Cross-platform]]
| memory management = [[Garbage collection (computer science)|Automatic garbage collection]]
| license = [[GNU General Public License]]&nbsp;/ [[Java Community Process]]
| influenced_by = [[CLU (programming language)|CLU]],<ref name="BarbaraLiskov">{{cite book |title=Program Development in Java – Abstraction, Specification, and Object-Oriented Design|author=[[Barbara Liskov]] with [[John Guttag]]|isbn=978-0-201-65768-5|publisher=USA, Addison Wesley|year=2000}}</ref> [[Simula67]],<ref name="BarbaraLiskov" /> [[Lisp (programming language)|Lisp]],<ref name="BarbaraLiskov" /> [[Smalltalk]],<ref name="BarbaraLiskov" /> [[Ada (programming language)|Ada 83]], [[C++]],<ref>{{cite web|url=https://books.google.com/books?id=0rUtBAAAQBAJ&pg=PAPA133|title=Cracking The Java Programming Interview :: 2000+ Java Interview Que/Ans|first=Harry H.|last=Chaudhary|access-date=2016-05-29|date=2014-07-28|archive-date=September 29, 2023|archive-url=https://web.archive.org/web/20230929040943/https://books.google.com/books?id=0rUtBAAAQBAJ&pg=PAPA133#v=onepage&q&f=false|url-status=live}}</ref> [[C Sharp (programming language)|C#]],<ref>Java&nbsp;5.0 added several new language features (the [[foreach loop|enhanced for loop]], [[object type (object-oriented programming)#Autoboxing|autoboxing]], [[variadic function|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/] {{Webarchive|url=https://web.archive.org/web/20110319065438/http://www.barrycornelius.com/papers/java5/|date=March 19, 2011}} [http://www.levenez.com/lang/] {{Webarchive|url=https://web.archive.org/web/20060107162045/http://www.levenez.com/lang/|date=January 7, 2006}}</ref> [[Eiffel (programming language)|Eiffel]],<ref>{{cite web|author1=Gosling, James|author2=McGilton, Henry|title=The Java Language Environment|date=May 1996|url=https://www.oracle.com/technetwork/java/langenv-140151.html|access-date=May 6, 2014|archive-url=https://web.archive.org/web/20140506214653/http://www.oracle.com/technetwork/java/langenv-140151.html|archive-date=May 6, 2014 |url-status=live}}</ref> [[Mesa (programming language)|Mesa]],<ref>{{cite web|author1=Gosling, James|author2=Joy, Bill |author3=Steele, Guy|author4=Bracha, Gilad|title=The Java Language Specification, 2nd Edition |url=https://java.sun.com/docs/books/jls/second_edition/html/intro.doc.html#237601|access-date=February 8, 2008|archive-url=https://web.archive.org/web/20110805051057/http://java.sun.com/docs/books/jls/second_edition/html/intro.doc.html#237601|archive-date=August 5, 2011 |url-status=live}}</ref> [[Modula-3]],<ref>{{cite web |url=http://www.computerworld.com.au/index.php/id;1422447371;pp;3;fp;4194304;fpid;1|title=The A-Z of Programming Languages: Modula-3 |publisher=Computerworld|access-date=2010-06-09|url-status=dead|archive-url=https://web.archive.org/web/20090105145818/http://www.computerworld.com.au/index.php/id%3B1422447371%3Bpp%3B3%3Bfp%3B4194304%3Bfpid%3B1|archive-date=January 5, 2009}}</ref> [[Oberon (programming language)|Oberon]],<ref>[[Niklaus Wirth]] stated on a number of public occasions, e.g. in a lecture at the Polytechnic Museum, Moscow in September 2005 (several independent first-hand accounts in Russian exist, e.g. one with an audio recording: {{cite web|author=Filippova, Elena|title=Niklaus Wirth's lecture at the Polytechnic Museum in Moscow|date=September 22, 2005|url=http://www.delphikingdom.com/asp/viewitem.asp?catalogid=1155|access-date=November 20, 2011|archive-date=December 1, 2020|archive-url=https://web.archive.org/web/20201201054813/http://www.delphikingdom.com/asp/viewitem.asp?catalogid=1155|url-status=live}}), that the Sun Java design team licensed the Oberon compiler sources a number of years prior to the release of Java and examined it: a (relative) compactness, type safety, garbage collection, no multiple inheritance for classes{{snd}} all these key overall design features are shared by Java and Oberon.</ref> [[Objective-C]],<ref>[[Patrick Naughton]] cites [[Objective-C]] as a strong influence on the design of the Java programming language, stating that notable direct derivatives include Java interfaces (derived from Objective-C's [[Objective-C#Protocols|protocol]]) and primitive wrapper classes. [http://cs.gmu.edu/~sean/stuff/java-objc.html] {{Webarchive|url=https://web.archive.org/web/20110713014816/http://cs.gmu.edu/~sean/stuff/java-objc.html|date=July 13, 2011}}</ref> [[UCSD Pascal]],<ref>{{cite web |url=http://www.fscript.org/prof/javapassport.pdf |quote=The project went ahead under the name ''green'' and the language was based on an old model of [[UCSD Pascal]], which makes it possible to generate interpretive code. |title=History of Java|work=Java Application Servers Report|author=TechMetrix Research|year=1999|archive-url=https://web.archive.org/web/20101229090912/http://www.fscript.org/prof/javapassport.pdf|archive-date=December 29, 2010|url-status=dead}}</ref><ref>{{cite magazine |title=A Conversation with James Gosling |magazine=[[ACM Queue]] |date=August 31, 2004 |url=http://queue.acm.org/detail.cfm?id=1017013 |publisher=[[Association for Computing Machinery]] |volume=2 |issue=5 |access-date=2010-06-09|archive-url=https://web.archive.org/web/20150716194245/http://queue.acm.org/detail.cfm?id=1017013|archive-date=July 16, 2015 |url-status=live}}</ref> [[Object Pascal]]<ref>{{cite report |author=((The Java Language Team)) |publisher=JavaSoft, Sun Microsystems, Inc. |url=http://java.sun.com/docs/white/delegates.html |quote=In the summer of 1996, Sun was designing the precursor to what is now the event model of the AWT and the JavaBeans component architecture. Borland contributed greatly to this process. We looked very carefully at Delphi Object Pascal and built a working prototype of bound method references in order to understand their interaction with the Java programming language and its APIs. |archive-url=https://web.archive.org/web/20120627043929/http://java.sun.com/docs/white/delegates.html |archive-date=2012-06-27 |url-status=dead |type=White Paper |title=About Microsoft's 'Delegates'}}</ref>
| website = http://java.sun.com
| influenced = [[Ada (programming language)|Ada 2005]], [[ArkTS]], [[BeanShell]], [[C Sharp (programming language)|C#]], [[Chapel (programming language)|Chapel]],<ref name="chplspec">{{cite web|title=Chapel spec (Acknowledgements)|url=http://chapel.cray.com/spec/spec-0.98.pdf|date=2015-10-01|access-date=2016-01-14|publisher=Cray Inc.|archive-url=https://web.archive.org/web/20160205114946/http://chapel.cray.com/spec/spec-0.98.pdf|archive-date=February 5, 2016|url-status=live}}</ref> [[Clojure]], [[ECMAScript]], [[Fantom (programming language)|Fantom]], [[Gambas]],<ref name="gambas">{{cite web|url=http://gambaswiki.org/wiki/doc/intro?nh&l=en|title=Gambas Documentation Introduction|publisher=Gambas Website|access-date=2017-10-09|archive-url=https://web.archive.org/web/20171009041815/http://gambaswiki.org/wiki/doc/intro?nh&l=en|archive-date=October 9, 2017|url-status=live}}</ref> [[Groovy (programming language)|Groovy]], [[Hack (programming language)|Hack]],<ref>{{cite magazine|url=http://www.infoworld.com/article/2610885/facebook-q-a--hack-brings-static-typing-to-php-world.html|title=Facebook Q&A: Hack brings static typing to PHP world|magazine=InfoWorld|date=March 26, 2014|access-date=2015-01-11|archive-url=https://web.archive.org/web/20150213220946/http://www.infoworld.com/article/2610885/facebook-q-a--hack-brings-static-typing-to-php-world.html|archive-date=February 13, 2015|url-status=live}}</ref> [[Haxe]], [[Visual J Sharp|J#]], [[JavaScript]], [[JS++]], [[Kotlin (programming language)|Kotlin]], [[PHP]], [[Python (programming language)|Python]], [[Scala (programming language)|Scala]], [[Seed7]], [[Vala (programming language)|Vala]]
| website = {{ubl|{{URL|oracle.com/java/}}|{{URL|java.com}}|{{URL|dev.java}}}}
| file_ext = .java, [[Java class file|.class]], [[JAR (file format)|.jar]], .jmod, [[WAR (file format)|.war]]
| wikibooks = Java Programming
}}
 
'''Java''' is a [[High-level programming language|high-level]], [[General-purpose programming language|general-purpose]], [[Memory safety|memory-safe]], [[object-oriented programming|object-oriented]] [[programming language]]. It is intended to let [[programmer]]s ''write once, run anywhere'' ([[Write once, run anywhere|WORA]]),<ref>{{cite web|title=Write once, run anywhere?|date=May 2, 2002 |publisher=[[Computer Weekly]] |url=http://www.computerweekly.com/Articles/2002/05/02/186793/write-once-run-anywhere.htm|access-date=2009-07-27|url-status=live|archive-date=August 13, 2021|archive-url=https://web.archive.org/web/20210813193857/https://www.computerweekly.com/feature/Write-once-run-anywhere}}</ref> meaning that [[compiler|compiled]] Java code can run on all platforms that support Java without the need to recompile.<ref name="design_goals">{{cite web |title=1.2 Design Goals of the Java Programming Language|date=January 1, 1999 |url=https://www.oracle.com/technetwork/java/intro-141325.html|access-date=2013-01-14|publisher=Oracle|archive-url=https://web.archive.org/web/20130123204103/http://www.oracle.com/technetwork/java/intro-141325.html|archive-date=January 23, 2013|url-status=live}}</ref> Java applications are typically compiled to [[Java bytecode|bytecode]] that can run on any [[Java virtual machine]] (JVM) regardless of the underlying [[computer architecture]]. The [[syntax (programming languages)|syntax]] of Java is similar to [[C (programming language)|C]] and [[C++]], but has fewer [[low-level programming language|low-level]] facilities than either of them. The Java runtime provides dynamic capabilities (such as [[Reflective programming|reflection]] and runtime code modification) that are typically not available in traditional compiled languages.
'''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]].
 
Java gained popularity shortly after its release, and has been a popular programming language since then.<ref>{{Cite web |last=Melanson |first=Mike |date=August 9, 2022 |title=Don't call it a comeback: Why Java is still champ |url=https://github.com/readme/featured/java-programming-language |url-status=live |archive-url=https://web.archive.org/web/20230825195416/https://github.com/readme/featured/java-programming-language |archive-date=August 25, 2023 |access-date=October 15, 2023 |website=[[GitHub]]}}</ref> Java was the third most popular programming language in {{As of|2022|bare=yes}} according to [[GitHub]].<ref>{{Cite web |title=The top programming languages |url=https://octoverse.github.com/2022/top-programming-languages |url-status=live |archive-url=https://web.archive.org/web/20230802203718/https://octoverse.github.com/2022/top-programming-languages |archive-date=2 August 2023 |access-date=15 October 2023 |website=The State of the Octoverse |publisher=[[GitHub]]}}</ref> Although still widely popular, there has been a gradual decline in use of Java in recent years with [[List of JVM languages|other languages using JVM]] gaining popularity.<ref name=":0">{{cite magazine |last=McMillan |first=Robert |date=August 1, 2013 |title=Is Java Losing Its Mojo? |url=https://www.wired.com/2013/01/java-no-longer-a-favorite/ |url-access=limited |url-status=live |magazine=[[wired.com|Wired]] |archive-url=https://web.archive.org/web/20170215115409/https://www.wired.com/2013/01/java-no-longer-a-favorite/ |archive-date=February 15, 2017 |access-date=October 15, 2023 |quote=}}</ref>
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]].
 
Java was designed by [[James Gosling]] at [[Sun Microsystems]]. It was released in May 1995 as a core component of Sun's [[Java (software platform)|Java platform]]. The original and [[reference implementation]] Java [[compiler]]s, virtual machines, and [[library (computing)|class libraries]] were released by Sun under [[proprietary license]]s. As of May 2007, in compliance with the specifications of the [[Java Community Process]], Sun had [[Software relicensing|relicensed]] most of its Java technologies under the [[GNU General Public License|GPL-2.0-only]] license. [[Oracle Corporation|Oracle]], which bought Sun in 2010, offers its own [[HotSpot (virtual machine)|HotSpot]] Java Virtual Machine. However, the official [[reference implementation]] is the [[OpenJDK]] JVM, which is open-source software used by most developers and is the default JVM for almost all Linux distributions.
== History ==
[[Image:Wave.svg|thumb|75px|Duke, the Java mascot]]
{{Main|Java (Sun)#History|Java version history}}
 
[[Java version history|Java 24]] is the version current {{as of|lc=y|2025|March}}. Java 8, 11, 17, and 21 are [[long-term support]] versions still under maintenance.
The Java language was created by [[James Gosling]] in June 1991 for use in one of his many [[set-top box]]
projects.<ref>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]].</ref> 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.<ref>http://blogs.sun.com/jonathan/entry/better_is_always_different.</ref> Gosling's goals were to implement a [[virtual machine]] and a language that had a familiar C/C++ style of notation.<ref>Heinz Kabutz, [http://www.artima.com/weblogs/viewpost.jsp?thread=7555 ''Once Upon an Oak'']. Artima, Retrieved [[April 29]], [[2007]].</ref> 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.
 
== History ==
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.<ref>[http://www.open-std.org/JTC1/SC22/JSG/ Java Study Group]</ref><ref>[http://csdl2.computer.org/comp/proceedings/hicss/2001/0981/05/09815015.pdf Why Java Was - Not - Standardized Twice]</ref><ref>[http://techupdate.zdnet.com/techupdate/stories/main/0,14179,2832719,00.html What is ECMA--and why Microsoft cares]</ref> Java remains a [[de facto]] standard that is controlled through the [[Java Community Process]].<ref>[http://www.jcp.org/en/home/index Java Community Process website]</ref> 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.
{{See also|Java (software platform)#History}}
[[File:Duke (Java mascot) waving.svg|thumb|upright=0.5|Duke, the Java mascot]]
[[File:James Gosling 2008.jpg|thumb|[[James Gosling]], the creator of Java, in 2008]]
 
[[James Gosling]], Mike Sheridan, and [[Patrick Naughton]] initiated the Java language project in June 1991.<ref>{{cite web |title=Java technology: The early years |last=Byous |first=Jon |date=c. 1998 |work=Sun Developer Network |publisher=[[Sun Microsystems]] |url=https://java.sun.com/features/1998/05/birthday.html |access-date=2005-04-22 |url-status=dead |archive-url=https://web.archive.org/web/20050420081440/http://java.sun.com/features/1998/05/birthday.html |archive-date=April 20, 2005}}</ref> Java was originally designed for interactive television, but it was too advanced for the digital cable television industry at the time.<ref>Object-oriented programming {{cite web |title=The History of Java Technology |date=c. 1995 |work=Sun Developer Network |url=http://www.java.com/en/javahistory/ |access-date=2010-04-30 |url-status=dead |archive-url=https://web.archive.org/web/20100210225651/http://www.java.com/en/javahistory/ |archive-date=February 10, 2010}}</ref> The language was initially called ''[[Oak (programming language)|Oak]]'' after an [[oak]] tree that stood outside Gosling's office. Later the project went by the name ''Green'' and was finally renamed ''Java'', from [[Java coffee]], a type of coffee from [[Indonesia]].<ref>{{cite web |last1=Murphy |first1=Kieron |date=1996-10-04 |url=https://www.infoworld.com/article/2077265/so-why-did-they-decide-to-call-it-java-.html |title=So why did they decide to call it Java? |work=[[JavaWorld]] |access-date=2020-07-13 |archive-date=July 13, 2020 |archive-url=https://web.archive.org/web/20200713234202/https://www.infoworld.com/article/2077265/so-why-did-they-decide-to-call-it-java-.html |url-status=live}}</ref> Gosling designed Java with a [[C (programming language)|C]]/[[C++]]-style syntax that system and application programmers would find familiar.<ref>Kabutz, Heinz; [http://www.artima.com/weblogs/viewpost.jsp?thread=7555 ''Once Upon an Oak''] {{Webarchive|url=https://web.archive.org/web/20070413072630/http://www.artima.com/weblogs/viewpost.jsp?thread=7555 |date=April 13, 2007}}. Artima. Retrieved April 29, 2007.</ref>
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.<ref>[http://open.itworld.com/4915/070508opsjava/page_1.html open.itworld.com - JAVAONE: Sun - The bulk of Java is open sourced<!-- Bot generated title -->]</ref>
 
Sun Microsystems released the first public implementation as Java 1.0 in 1996.<ref name="oraclejavahistory">{{cite web |url=http://www.sun.com/smi/Press/sunflash/1996-01/sunflash.960123.10561.xml |archive-url=https://web.archive.org/web/20070310235103/http://www.sun.com/smi/Press/sunflash/1996-01/sunflash.960123.10561.xml |url-status=dead |archive-date=2007-03-10 |title=JAVASOFT SHIPS JAVA 1.0 |access-date=2018-05-13}}</ref> It promised [[write once, run anywhere]] (WORA) functionality, providing no-cost run-times on popular [[Computing platform|platforms]]. Fairly secure and featuring configurable security, it allowed network- and file-access restrictions. Major [[web browser]]s soon incorporated the ability to run [[Java applet]]s within web pages, and Java quickly became popular. The Java 1.0 compiler was re-written [[Bootstrapping (compilers)|in Java]] by [[Arthur van Hoff]] to comply strictly with the Java 1.0 language specification.<ref>{{cite book |url={{Google books|rXGMFYXFDwMC|plainurl=yes}} |title=Object-oriented Programming with Java: Essentials and Applications |publisher=Tata McGraw-Hill Education |page=34}}</ref> With the advent of Java 2 (released initially as J2SE 1.2 in December 1998{{snd}} 1999), new versions had multiple configurations built for different types of platforms. [[Java 2 Enterprise Edition|J2EE]] included technologies and APIs for enterprise applications typically run in server environments, while J2ME featured APIs optimized for mobile applications. The desktop version was renamed J2SE. In 2006, for marketing purposes, Sun renamed new J2 versions as ''[[Java Platform, Enterprise Edition|Java EE]]'', ''[[Java Platform, Micro Edition|Java ME]]'', and ''[[Java Platform, Standard Edition|Java SE]]'', respectively.
== Philosophy ==
=== Primary goals ===
There were five primary goals in the creation of the Java language:<ref>[http://java.sun.com/docs/white/langenv/Intro.doc2.html 1.2 Design Goals of the JavaTM Programming Language]</ref>
 
In 1997, Sun Microsystems approached the [[ISO/IEC JTC 1]] standards body and later the [[Ecma International]] to formalize Java, but it soon withdrew from the process.<ref>{{cite web|url=http://www.open-std.org/JTC1/SC22/JSG/|title=JSG – Java Study Group|work=open-std.org|access-date=August 2, 2006|archive-url=https://web.archive.org/web/20060825082008/http://www.open-std.org/JTC1/SC22/JSG/|archive-date=August 25, 2006|url-status=live}}</ref><ref>{{cite web |title=Why Java Was – Not – Standardized Twice |url=http://www.computer.org/csdl/proceedings/hicss/2001/0981/05/09815015.pdf |access-date=June 3, 2018 |archive-url=https://web.archive.org/web/20140113101235/http://www.computer.org/csdl/proceedings/hicss/2001/0981/05/09815015.pdf |archive-date=January 13, 2014 |url-status=live}}</ref><ref>{{cite web |url=http://www.zdnet.com/news/what-is-ecma-and-why-microsoft-cares/298821 |title=What is ECMA—and why Microsoft cares |website=[[ZDNet]] |access-date=May 6, 2014 |archive-url=https://web.archive.org/web/20140506215226/http://www.zdnet.com/news/what-is-ecma-and-why-microsoft-cares/298821 |archive-date=May 6, 2014 |url-status=live}}</ref> Java remains a [[de facto standard|''de facto'' standard]], controlled through the [[Java Community Process]].<ref>{{cite web |url=http://www.jcp.org/en/home/index |title=Java Community Process website |publisher=Jcp.org |date=May 24, 2010 |access-date=2010-06-09 |archive-url=https://web.archive.org/web/20060808070528/http://www.jcp.org/en/home/index |archive-date=August 8, 2006 |url-status=live}}</ref> At one time, Sun made most of its Java implementations available without charge, despite their [[proprietary software]] status. Sun generated revenue from Java through the selling of licenses for specialized products such as the Java Enterprise System.
# 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.
 
On November 13, 2006, Sun released much of its Java virtual machine (JVM) as [[free and open-source software]] (FOSS), under the terms of the [[GNU General Public License|GPL-2.0-only]] license. On May 8, 2007, Sun finished the process, making all of its JVM's core code available under [[free software]]/open-source distribution terms, aside from a small portion of code to which Sun did not hold the copyright.<ref>{{cite web |url=http://grnlight.net/index.php/programming-articles/115-javaone-sun-the-bulk-of-java-is-open-sourced |title=JAVAONE: Sun – The bulk of Java is open sourced |publisher=GrnLight.net |access-date=2014-05-26 |archive-url=https://web.archive.org/web/20140527220942/http://grnlight.net/index.php/programming-articles/115-javaone-sun-the-bulk-of-java-is-open-sourced |archive-date=May 27, 2014 |url-status=usurped}}</ref>
=== Platform independence ===
{{main|Java Platform}}
 
Sun's vice-president Rich Green said that Sun's ideal role with regard to Java was as an ''evangelist''.<ref>{{cite web|url=http://onjava.com/pub/a/onjava/2002/04/17/evangelism.html|title=Sun's Evolving Role as Java Evangelist|publisher=[[O'Reilly Media]]|archive-url=https://web.archive.org/web/20100915162748/http://onjava.com/pub/a/onjava/2002/04/17/evangelism.html|archive-date=September 15, 2010|url-status=live|access-date=August 2, 2009
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.
}}</ref> Following [[Oracle Corporation]]'s acquisition of Sun Microsystems in 2009–10, Oracle has described itself as the steward of Java technology with a relentless commitment to fostering a community of participation and transparency.<ref>{{cite web |url=https://www.oracle.com/us/technologies/java/|title=Oracle and Java|work=oracle.com|publisher=Oracle Corporation |access-date=2010-08-23|quote=Oracle has been a leading and substantive supporter of Java since its emergence in 1995 and takes on the new role as steward of Java technology with a relentless commitment to fostering a community of participation and transparency. |url-status=dead|archive-url=https://web.archive.org/web/20100131091008/http://www.oracle.com/us/technologies/java/ |archive-date=January 31, 2010}}</ref> This did not prevent Oracle from filing a lawsuit against Google shortly after that for using Java inside the [[Android SDK]] (see the ''[[#Android|Android]]'' section).
 
On April 2, 2010, James Gosling resigned from [[Oracle Corporation|Oracle]].<ref>{{cite web|url=http://nighthacks.com/roller/jag/entry/time_to_move_on |title=Time to move on... |last=Gosling |first=James |date=April 9, 2010 |work=On a New Road |access-date=2011-11-16 |author-link=James Gosling |url-status=dead |archive-url=https://web.archive.org/web/20101105031239/http://nighthacks.com/roller/jag/entry/time_to_move_on |archive-date=November 5, 2010}}</ref>
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]].
 
In January 2016, Oracle announced that Java run-time environments based on JDK 9 will discontinue the browser plugin.<ref>{{cite web|url=https://blogs.oracle.com/java-platform-group/entry/moving_to_a_plugin_free|title=Moving to a Plugin-Free Web|first=Dalibor|last=Topic|access-date=March 15, 2016|archive-url=https://web.archive.org/web/20160316164325/https://blogs.oracle.com/java-platform-group/entry/moving_to_a_plugin_free|archive-date=March 16, 2016|url-status=live}}</ref>
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.
 
Java software runs on most devices from laptops to [[data center]]s, [[Video game console|game consoles]] to scientific [[supercomputer]]s.<ref>{{cite web|title=Learn About Java Technology|url=http://www.java.com/en/about/|publisher=Oracle|access-date=November 21, 2011|archive-url=https://web.archive.org/web/20111124090716/http://www.java.com/en/about/|archive-date=November 24, 2011|url-status=live}}</ref>
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.
 
[[Oracle Corporation|Oracle]] (and others) highly recommend uninstalling outdated and unsupported versions of Java, due to unresolved security issues in older versions.<ref>{{Cite web|url=https://www.java.com/en/download/faq/remove_olderversions.xml|title=Why should I uninstall older versions of Java from my system?|publisher=Oracle|access-date=2021-09-24|archive-date=February 12, 2018|archive-url=https://web.archive.org/web/20180212011608/https://java.com/en/download/faq/remove_olderversions.xml|url-status=live}}</ref>
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 optimized native code version of an application.
 
=== ImplementationsPrinciples ===
There were five primary goals in creating the Java language:<ref name="design_goals" />
# It must be simple, [[object-oriented programming|object-oriented]], and familiar.
# It must be [[Robustness (computer science)|robust]] and secure.
# It must be architecture-neutral and portable.
# It must execute with high performance.
# It must be [[Interpreter (computing)|interpreted]], [[thread (computing)|threaded]], and [[Dynamic programming language|dynamic]].
 
=== Versions ===
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<ref>[http://java.sun.com/javase/licensees.jsp Java SE - Licensees<!-- Bot generated title -->]</ref>, alternative Java environments are available for these and other platforms.
{{Main|Java version history}}
{{As of|2024|11}}, Java 8, 11, 17, and 21 are supported as [[long-term support]] (LTS) versions, with Java 25, releasing in September 2025, as the next scheduled LTS version.<ref>{{cite web |title=Oracle Java SE Support Roadmap |publisher=Oracle |date=September 13, 2021 |url=https://www.oracle.com/java/technologies/java-se-support-roadmap.html|access-date=September 18, 2021|archive-url=https://web.archive.org/web/20210919090451/https://www.oracle.com/java/technologies/java-se-support-roadmap.html |archive-date=2021-09-19|url-status=live}}</ref>
 
Oracle released the last zero-cost public update for the [[legacy system|legacy]] version [[Java 8]] LTS in January 2019 for commercial use, although it will otherwise still support Java&nbsp;8 with public updates for personal use indefinitely. Other vendors such as [[Adoptium]] continue to offer free builds of OpenJDK's long-term support (LTS) versions. These builds may include additional security patches and bug fixes.<ref>{{cite web |title=Temurin™ Support; Adoptium |url=https://adoptium.net/support/ |website=adoptium.net |access-date=29 March 2024 |archive-url=https://web.archive.org/web/20240329061257/https://adoptium.net/support/ |archive-date=29 March 2024 |url-status=live}}</ref>
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.<ref>{{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
}}</ref> 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.
 
Major release versions of Java, along with their release dates:
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.
 
{| class="wikitable"
=== Automatic memory management ===
! Version !! Date
{{See also|Garbage collection (computer science)}}
|-
| JDK [[beta version|Beta]] || 1995
|-
| JDK 1.0 || January 23, 1996<ref>{{cite web|url=http://www.sun.com/smi/Press/sunflash/1996-01/sunflash.960123.10561.xml |title=JAVASOFT SHIPS JAVA 1.0|website=sun.com |access-date=2008-02-05 |url-status=dead |archive-url=https://web.archive.org/web/20070310235103/http://www.sun.com/smi/Press/sunflash/1996-01/sunflash.960123.10561.xml |archive-date=March 10, 2007}}</ref>
|-
| JDK 1.1 || February 19, 1997
|-
| J2SE 1.2 || December 8, 1998
|-
| J2SE 1.3 || May 8, 2000
|-
| J2SE 1.4 || February 6, 2002
|-
| J2SE 5.0 || September 30, 2004
|-
| Java SE 6 || December 11, 2006
|-
| Java SE 7 || July 28, 2011
|-
| Java SE 8 (LTS) || March 18, 2014
|-
| Java SE 9 || September 21, 2017
|-
| Java SE 10 || March 20, 2018
|-
| Java SE 11 (LTS) || September 25, 2018<ref>{{cite news|url=https://blogs.oracle.com/java-platform-group/introducing-java-se-11|title=Introducing Java SE 11|first=Sharat|last=Chander|website=oracle.com|access-date=September 26, 2018|archive-url=https://web.archive.org/web/20180926093144/https://blogs.oracle.com/java-platform-group/introducing-java-se-11|archive-date=September 26, 2018|url-status=live}}</ref>
|-
| Java SE 12 || March 19, 2019
|-
| Java SE 13 || September 17, 2019
|-
| Java SE 14 || March 17, 2020
|-
| Java SE 15 || September 15, 2020<ref>{{cite news|url=https://blogs.oracle.com/java-platform-group/the-arrival-of-java-15|title=The Arrival of Java 15!|date=September 15, 2020|publisher=[[Oracle Corporation|Oracle]]|access-date=2020-09-15|archive-date=September 16, 2020|archive-url=https://web.archive.org/web/20200916092332/https://blogs.oracle.com/java-platform-group/the-arrival-of-java-15|url-status=live |last1=Chander |first1=Sharat }}</ref>
|-
| Java SE 16 || March 16, 2021
|-
| Java SE 17 (LTS) || September 14, 2021
|-
| Java SE 18 || March 22, 2022
|-
| Java SE 19 || September 20, 2022
|-
| Java SE 20 || March 21, 2023
|-
| Java SE 21 (LTS) || September 19, 2023<ref>{{Cite web|url=https://openjdk.org/projects/jdk/21/|title=JDK 21|website=openjdk.org|access-date=September 20, 2023|archive-date=September 20, 2023|archive-url=https://web.archive.org/web/20230920173515/https://openjdk.org/projects/jdk/21/|url-status=live}}</ref>
|-
| Java SE 22 || March 19, 2024
|-
| Java SE 23 || September 17, 2024
|-
| Java SE 24 || 18 March 2025<ref name="jdk24">{{cite web | url=https://openjdk.org/projects/jdk/24/ | title=JDK 24 }}</ref>
|}
 
== Editions ==
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.<ref>[http://www.research.att.com/~bs/bs_faq2.html#memory-leaks Stroustrup: C++ Style and Technique FAQ<!-- Bot generated title -->]</ref>
{{See also|Free Java implementations#Class library}}
{{Java platforms}}
Sun has defined and supports four editions of Java targeting different application environments and segmented many of its [[application programming interface|APIs]] so that they belong to one of the platforms. The platforms are:
* [[Java Card]] for smart-cards.<ref name="java_card">{{cite web |url=https://www.oracle.com/technetwork/java/embedded/javacard/overview/ |title=Java Card Overview |publisher=Oracle |work=Oracle Technology Network |access-date=December 18, 2014 |archive-url=https://web.archive.org/web/20150107034738/http://www.oracle.com/technetwork/java/embedded/javacard/overview/ |archive-date=January 7, 2015 |url-status=live}}</ref>
* [[Java Platform, Micro Edition]] (Java ME) – targeting environments with limited resources.<ref name="java_me">{{cite web |url=https://www.oracle.com/technetwork/java/embedded/javame/ |title=Java Platform, Micro Edition (Java ME) |publisher=Oracle |work=Oracle Technology Network |access-date=December 18, 2014 |archive-url=https://web.archive.org/web/20150104210546/http://www.oracle.com/technetwork/java/embedded/javame/ |archive-date=January 4, 2015 |url-status=live}}</ref>
* [[Java Platform, Standard Edition]] (Java SE) – targeting workstation environments.<ref name="java_se">{{cite web |url=https://www.oracle.com/technetwork/java/javase/overview/ |title=Java SE |publisher=Oracle |work=Oracle Technology Network |access-date=December 18, 2014 |archive-url=https://web.archive.org/web/20141224184532/http://www.oracle.com/technetwork/java/javase/overview/ |archive-date=December 24, 2014 |url-status=live}}</ref>
* [[Java Platform, Enterprise Edition]] (Java EE) – targeting large distributed enterprise or Internet environments.<ref name="java_ee">{{cite web |url=https://www.oracle.com/technetwork/java/javaee/overview/ |title=Java Platform, Enterprise Edition (Java EE) |publisher=Oracle |work=Oracle Technology Network |access-date=December 18, 2014 |archive-url=https://web.archive.org/web/20141217155326/http://www.oracle.com/technetwork/java/javaee/overview/ |archive-date=December 17, 2014 |url-status=live}}</ref>
 
The [[Class (computer programming)|classes]] in the Java APIs are organized into separate groups called [[Java package|packages]]. Each package contains a set of related [[Interface (Java)|interfaces]], classes, subpackages and [[exception handling|exceptions]].
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.
 
Sun also provided an edition called [[PersonalJava|Personal Java]] that has been superseded by later, standards-based Java ME configuration-profile pairings.
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.
 
== Execution system ==
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 JVM and bytecode ===
{{Main|Java (software platform)|Java virtual machine}}
<!-- we apparently have two main sections for what seems to be the same thing. Merge needed? -->
 
One design goal of Java is [[software portability|portability]], which means that programs written for the Java platform must run similarly on any combination of hardware and operating system with adequate run time support. This is achieved by compiling the Java language code to an intermediate representation called [[Java bytecode]], instead of directly to architecture-specific [[machine code]]. Java bytecode instructions are analogous to machine code, but they are intended to be executed by a [[virtual machine]] (VM) written specifically for the host hardware. [[End user|End-users]] commonly use a [[Java virtual machine|Java Runtime Environment]] (JRE) installed on their device for standalone Java applications or a web browser for [[Java applet]]s.
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.
 
Standard libraries provide a generic way to access host-specific features such as graphics, [[thread (computing)|threading]], and [[Computer network|networking]].
== Syntax ==
{{examplefarm}}
{{main|Java syntax}}
 
The use of universal bytecode makes porting simple. However, the overhead of [[Interpreter (computing)|interpreting]] bytecode into machine instructions made interpreted programs almost always run more slowly than native [[executable]]s. [[Just-in-time compilation|Just-in-time]] (JIT) compilers that compile byte-codes to machine code during runtime were introduced from an early stage. Java's Hotspot compiler is actually two compilers in one; and with [[GraalVM]] (included in e.g. Java 11, but removed as of Java 16) allowing [[tiered compilation]].<ref>{{Cite web |date=2021-08-06 |title=Deep Dive Into the New Java JIT Compiler – Graal {{!}} Baeldung |url=https://www.baeldung.com/graal-java-jit-compiler |access-date=2021-10-13 |website=www.baeldung.com |language=en-US |archive-date=October 28, 2021 |archive-url=https://web.archive.org/web/20211028165746/https://www.baeldung.com/graal-java-jit-compiler |url-status=live }}</ref> Java itself is platform-independent and is adapted to the particular platform it is to run on by a [[Java virtual machine]] (JVM), which translates the [[Java bytecode]] into the platform's machine language.<ref>{{cite web|url=http://www.programmerinterview.com/index.php/java-questions/jvm-platform-dependent/|title=Is the JVM (Java Virtual Machine) platform dependent or platform independent? What is the advantage of using the JVM, and having Java be a translated language?|publisher=Programmer Interview|access-date=2015-01-19|archive-url=https://web.archive.org/web/20150119144223/http://www.programmerinterview.com/index.php/java-questions/jvm-platform-dependent/ |archive-date=January 19, 2015|url-status=live}}</ref>
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 programPerformance ====
{{Main|Java performance}}
This is a minimal [[Hello world program]] in Java with [[syntax highlighting]]:
 
Programs written in Java have a reputation for being slower and requiring more memory than those written in [[C++]].<ref name=Jelovic>{{cite web |title=Why Java will always be slower than C++ |last=Jelovic |first=Dejan |url=http://www.jelovic.com/articles/why_java_is_slow.htm |access-date=2008-02-15 |url-status=dead |archive-url=https://web.archive.org/web/20080211111923/http://www.jelovic.com/articles/why_java_is_slow.htm |archive-date=February 11, 2008}}</ref><ref>{{cite web |last=Hundt |first=Robert |title=Loop Recognition in C++/Java/Go/Scala |url=https://days2011.scala-lang.org/sites/days2011/files/ws3-1-Hundt.pdf |access-date=2012-07-12 |url-status=live |archive-url=https://web.archive.org/web/20111116151424/https://days2011.scala-lang.org/sites/days2011/files/ws3-1-Hundt.pdf |archive-date=November 16, 2011}}</ref> However, Java programs' execution speed improved significantly with the introduction of [[just-in-time compilation]] in 1997/1998 for [[Java version history|Java&nbsp;1.1]],<ref>{{cite web |url=http://www.symantec.com/about/news/release/article.jsp?prid=19970407_03 |title=Symantec's Just-In-Time Java Compiler To Be Integrated into Sun JDK 1.1 |access-date=August 1, 2009 |archive-url=https://web.archive.org/web/20100628171748/http://www.symantec.com/about/news/release/article.jsp?prid=19970407_03 |archive-date=June 28, 2010 |url-status=dead}}</ref> the addition of language features supporting better code analysis (such as inner classes, the StringBuilder class, optional assertions, etc.), and optimizations in the Java virtual machine, such as [[HotSpot (virtual machine)|HotSpot]] becoming Sun's default JVM in 2000. With Java&nbsp;1.5, the performance was improved with the addition of the {{code|java.util.concurrent}} package, including [[lock-free]] implementations of the [[Java ConcurrentMap|ConcurrentMaps]] and other multi-core collections, and it was improved further with Java&nbsp;1.6.
<source lang="java">
// HelloWorld.java
public class HelloWorld
{
public static void main(String[] args)
{
System.out.println("Hello, world!");
}
}
</source>
 
=== Non-JVM ===
To execute a Java program, the code is saved as a file named <code>HelloWorld.java</code>. It must first be compiled into bytecode using a [[Java compiler]], which produces a file named <code>HelloWorld.class</code>. This class is then ''launched''.
Some platforms offer direct hardware support for Java; there are micro controllers that can run Java bytecode in hardware instead of a software Java virtual machine,<ref>{{Cite journal|last1=Salcic|first1=Zoran|last2=Park|first2=Heejong|last3=Teich|first3=Jürgen|last4=Malik|first4=Avinash|last5=Nadeem|first5=Muhammad|date=2017-07-22|title=Noc-HMP: A Heterogeneous Multicore Processor for Embedded Systems Designed in SystemJ|journal=ACM Transactions on Design Automation of Electronic Systems |volume=22|issue=4|pages=73|doi=10.1145/3073416|s2cid=11150290|issn=1084-4309}}</ref> and some [[ARM architecture family|ARM]]-based processors could have hardware support for executing Java bytecode through their [[Jazelle]] option, though support has mostly been dropped in current implementations of ARM.
 
=== Automatic memory management ===
The above example merits a bit of explanation.
Java uses an [[Garbage collection (computer science)|automatic garbage collector]] to manage memory in the [[object lifetime|object lifecycle]]. The programmer determines when objects are created, and the Java runtime is responsible for recovering the memory once objects are no longer in use. Once no references to an object remain, the [[unreachable memory]] becomes eligible to be freed automatically by the garbage collector. Something similar to a [[memory leak]] may still occur if a programmer's code holds a reference to an object that is no longer needed, typically when objects that are no longer needed are stored in containers that are still in use.{{sfn|Bloch|2018|loc=§Item 7: Eliminate obsolete object references|p=26-28}} If methods for a non-existent object are called, a [[null pointer]] exception is thrown.<ref>{{cite web |url=http://docs.oracle.com/javase/8/docs/api/java/lang/NullPointerException.html |title=NullPointerException |publisher=Oracle |access-date=2014-05-06 |archive-url=https://web.archive.org/web/20140506214735/http://docs.oracle.com/javase/8/docs/api/java/lang/NullPointerException.html |archive-date=May 6, 2014 |url-status=live}}</ref><ref>{{cite web |url=http://www.artima.com/designtechniques/exceptions.html |title=Exceptions in Java |publisher=Artima.com |access-date=2010-08-10 |archive-url=https://web.archive.org/web/20090121152332/http://www.artima.com/designtechniques/exceptions.html |archive-date=January 21, 2009 |url-status=live}}</ref>
* 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 <code>'''class'''</code> that is declared <code>'''public'''</code> is required to follow this convention. (In this case, the class <code>'''HelloWorld'''</code> is public, therefore the source must be stored in a file called ''HelloWorld.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]] <code>'''public'''</code> 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 <code>'''static'''</code> indicates that the method is a [[class method|static method]], associated with the class rather than object instances.
* The keyword <code>'''void'''</code> indicates that the main method does not return any value to the caller.
* The method name "<code>main</code>" 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 <code>main()</code> method.
* The main method must accept an [[array]] of '''{{Javadoc:SE|java/lang|String}}''' objects. By convention, it is referenced as <code>'''args'''</code> 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 <code>public static void main(String... args)</code>, allowing the main method to be invoked with an arbitrary number of <code>String</code> arguments. The effect of this alternate declaration is semantically identical (the <code>args</code> parameter is still an array of <code>String</code> 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 <code>public static void main(String[])</code> method. Stand-alone programs must declare this method explicitly. The <code>String[] args</code> parameter is an [[array]] of {{Javadoc:SE|java/lang|String}} objects containing any arguments passed to the class. The parameters to <code>main</code> 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 <code>out</code> 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]]).
 
One of the ideas behind Java's automatic memory management model is that programmers can be spared the burden of having to perform manual memory management. In some languages, memory for the creation of objects is implicitly allocated on the [[Stack (abstract data type)|stack]] or explicitly allocated and deallocated from the [[Memory management#DYNAMIC|heap]]. In the latter case, the responsibility of managing memory resides with the programmer. If the program does not deallocate an object, a [[memory leak]] occurs.{{sfn|Bloch|2018|loc=§Item 7: Eliminate obsolete object references|p=26-28}} If the program attempts to access or deallocate memory that has already been deallocated, the result is undefined and difficult to predict, and the program is likely to become unstable or crash. This can be partially remedied by the use of [[smart pointer]]s, but these add overhead and complexity. Garbage collection does not prevent [[logical address|logical memory]] leaks, i.e. those where the memory is still referenced but never used.{{sfn|Bloch|2018|loc=§Item 7: Eliminate obsolete object references|p=26-28}}
=== A more comprehensive example ===
<source lang="java">
// OddEven.java
import javax.swing.JOptionPane;
 
Garbage collection may happen at any time. Ideally, it will occur when a program is idle. It is guaranteed to be triggered if there is insufficient free memory on the heap to allocate a new object; this can cause a program to stall momentarily. Explicit memory management is not possible in Java.
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");
}
}
</source>
 
Java does not support C/C++ style [[pointer (computer programming)|pointer arithmetic]],<ref>Walter, A. (2010). Towards Certification of Java Applications for Safety Critical Projects. ''Proceedings of Embedded Real-Time Software and Systems, ERTS2'', 1-7.</ref> where object addresses can be arithmetically manipulated (e.g. by adding or subtracting an offset). This allows the garbage collector to relocate referenced objects and ensures type safety and security.
* 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 <code>'''OddEven'''</code> class declares a single <code>'''[[Java keywords#private|private]]'''</code> [[field (computer science)|field]] of type <code>'''int'''</code> named <code>'''input'''</code>. Every instance of the <code>OddEven</code> class has its own copy of the <code>input</code> field. The private declaration means that no other class can access (read or write) the <code>input</code> field.
* <code>'''OddEven()'''</code> is a <code>'''public'''</code> [[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 <code>String</code> that is converted to an <code>int</code> by the '''{{Javadoc:SE|java/lang|Integer|parseInt(String)}}''' method.
* The <code>'''calculate()'''</code> method is declared without the <code>static</code> keyword. This means that the method is invoked using a specific instance of the <code>OddEven</code> class. (The [[reference (computer science)|reference]] used to invoke the method is passed as an undeclared parameter of type <code>OddEven</code> named <code>'''[[Java keywords#this|this]]'''</code>.) The method tests the expression <code>input % 2 == 0</code> using the <code>'''[[Java keywords#if|if]]'''</code> keyword to see if the remainder of dividing the <code>input</code> 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 <code>input</code> field can be equivalently accessed as <code>this.input</code>, which explicitly uses the undeclared <code>this</code> parameter.)
* <code>'''OddEven number = new OddEven();'''</code> declares a local object [[reference (computer science)|reference]] variable in the <code>main</code> method named <code>number</code>. This variable can hold a reference to an object of type <code>OddEven</code>. The declaration initializes <code>number</code> by first creating an instance of the <code>OddEven</code> class, using the <code>'''[[Java keywords#new|new]]'''</code> keyword and the <code>OddEven()</code> constructor, and then assigning this instance to the variable.
* The statement <code>'''number.showDialog();'''</code> calls the calculate method. The instance of <code>OddEven</code> object referenced by the <code>number</code> [[local variable]] is used to invoke the method and passed as the undeclared <code>this</code> parameter to the <code>calculate</code> 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 <code>Integer.parseInt(String)</code>.
 
As in C++ and some other object-oriented languages, variables of Java's [[primitive data type]]s 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 commonly true for non-primitive data types (but see [[escape analysis]]). This was a conscious decision by Java's designers for performance reasons.
=== Applet ===
{{Main|Java applet}}
 
Java contains multiple types of garbage collectors. Since Java 9, HotSpot uses the [[Garbage-first collector|Garbage First Garbage Collector]] (G1GC) as the default.<ref>{{cite web |url=https://docs.oracle.com/javase/7/docs/technotes/guides/vm/performance-enhancements-7.html |title=Java HotSpot™ Virtual Machine Performance Enhancements |publisher=Oracle.com |access-date=2017-04-26 |archive-url=https://web.archive.org/web/20170529071720/http://docs.oracle.com/javase/7/docs/technotes/guides/vm/performance-enhancements-7.html |archive-date=May 29, 2017 |url-status=live}}</ref> However, there are also several other garbage collectors that can be used to manage the heap, such as the Z Garbage Collector (ZGC) introduced in Java 11, and Shenandoah GC, introduced in Java 12 but unavailable in Oracle-produced OpenJDK builds. Shenandoah is instead available in third-party builds of OpenJDK, such as [[Adoptium#Eclipse Temurin|Eclipse Temurin]]. For most applications in Java, G1GC is sufficient. In prior versions of Java, such as Java 8, the [https://docs.oracle.com/javase/8/docs/technotes/guides/vm/gctuning/parallel.html Parallel Garbage Collector] was used as the default garbage collector.
Java applets are programs that are embedded in other applications, typically in a Web page displayed in a [[Web browser]].
 
Having solved the memory management problem does not relieve the programmer of the burden of handling properly other kinds of resources, like network or database connections, file handles, etc., especially in the presence of exceptions.
<source lang="java">
// Hello.java
import java.applet.Applet;
import java.awt.Graphics;
 
== Syntax ==
public class Hello extends Applet {
{{Main|Java syntax}}
public void paint(Graphics gc) {
[[File:JavaUniverse.png|thumb|upright|This dependency graph of the Java Core classes was created with jdeps and [[Gephi]].]]
gc.drawString("Hello, world!", 65, 95);
The syntax of Java is largely influenced by [[C++]] and [[C (programming language)|C]]. Unlike C++, which combines the syntax for structured, generic, and object-oriented programming, Java was built almost exclusively as an object-oriented language.<ref name="design_goals" /> All code is written inside classes, and every data item is an object, with the exception of the primitive data types, (i.e. integers, floating-point numbers, [[Boolean data type|boolean values]], and characters), which are not objects for performance reasons. Java reuses some popular aspects of C++ (such as the {{java|printf}} method).
}
}
</source>
 
Unlike C++, Java does not support [[operator overloading]]<ref name="msdn_operator_overloading">{{cite web |url=http://msdn.microsoft.com/en-us/library/ms228498%28v=vs.90%29.aspx |title=Operator Overloading (C# vs Java) |publisher=Microsoft |work=C# for Java Developers |access-date=December 10, 2014 |archive-url=https://web.archive.org/web/20150107190007/http://msdn.microsoft.com/en-us/library/ms228498(v=vs.90).aspx |archive-date=January 7, 2015 |url-status=live}}</ref> or [[multiple inheritance]] for classes, though multiple inheritance is supported for [[interface (Java)|interfaces]].<ref name="oracle_multiple_inheritance">{{cite web |url=https://docs.oracle.com/javase/tutorial/java/IandI/multipleinheritance.html |title=Multiple Inheritance of State, Implementation, and Type |publisher=Oracle |work=The Java Tutorials |access-date=December 10, 2014 |archive-url=https://web.archive.org/web/20141109034520/https://docs.oracle.com/javase/tutorial/java/IandI/multipleinheritance.html |archive-date=November 9, 2014 |url-status=live}}</ref>
The <code>'''import'''</code> 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. <code>Applet</code>) instead of the ''fully qualified class name'' (i.e. <code>java.applet.Applet</code>).
 
Java uses [[Comment (computer programming)|comments]] similar to those of C++. There are three different styles of comments: a single line style marked with two slashes (<code>//</code>), a multiple line style opened with <code>/*</code> and closed with <code>*/</code>, and the [[Javadoc]] commenting style opened with <code>/**</code> and closed with <code>*/</code>. The Javadoc style of commenting allows the user to run the Javadoc executable to create documentation for the program and can be read by some [[integrated development environment]]s (IDEs) such as [[Eclipse (software)|Eclipse]] to allow developers to access documentation within the IDE.
The <code>Hello</code> class <code>'''extends'''</code> ([[subclass (computer science)|subclasses]]) the <code>'''Applet'''</code> class; the <code>Applet</code> class provides the framework for the host application to display and control the [[Object lifetime|lifecycle]] of the applet. The <code>Applet</code> 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]].
 
=== Hello world ===
The <code>Hello</code> 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 <code>paint()</code> method is passed a <code>'''Graphics'''</code> object that contains the graphic context used to display the applet. The <code>paint()</code> 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 (<code>'''65, 95'''</code>) from the upper-left corner in the applet's display.
The following is a simple example of a [["Hello, World!" program]] that writes a message to the [[standard output]]:
<syntaxhighlight lang="java" line="1">public class Example {
public static void main(String[] args) {
System.out.println("Hello World!");
}
}</syntaxhighlight>
 
== Special classes ==
<source lang="html4strict">
{{more citations needed|section|date=May 2019}}
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<!-- Hello.html -->
<html>
<head>
<title>Hello World Applet</title>
</head>
<body>
<applet code="Hello" width="200" height="200">
</applet>
</body>
</html>
</source>
 
=== Applet ===
An applet is placed in an [[HTML]] document using the '''<code><applet></code>''' [[HTML element]]. The <code>applet</code> tag has three attributes set: '''<code>code="Hello"</code>''' specifies the name of the <code>Applet</code> class and '''<code>width="200" height="200"</code>''' sets the pixel width and height of the applet. Applets may also be embedded in HTML using either the <code>object</code> or <code>embed</code> element<ref>[http://java.sun.com/docs/books/tutorial/deployment/applet/applettag.html Using the applet Tag (The Java Tutorials > Deployment > Applets)<!-- Bot generated title -->]</ref>, although support for these elements by Web browsers is inconsistent.<ref>[http://java.sun.com/docs/books/tutorial/deployment/applet/mixedbrowser.html Deploying Applets in a Mixed-Browser Environment (The Java Tutorials > Deployment > Applets)<!-- Bot generated title -->]</ref> However, the <code>applet</code> tag is deprecated, so the <code>object</code> tag is preferred where supported.
{{Main|Java applet}}
Java applets were programs embedded in other applications, mainly in web pages displayed in web browsers. The Java applet API was deprecated with the release of Java&nbsp;9 in 2017.<ref>{{Cite web |url=https://www.oracle.com/technetwork/java/javase/9-deprecated-features-3745636.html#JDK-8074165|title=Deprecated APIs, Features, and Options| publisher=Oracle |access-date=2019-05-31|archive-date=June 19, 2019|archive-url=https://web.archive.org/web/20190619200811/https://www.oracle.com/technetwork/java/javase/9-deprecated-features-3745636.html#JDK-8074165|url-status=live}}</ref><ref>{{Cite web|title=Applet (Java Platform SE 7)|url=https://docs.oracle.com/javase/7/docs/api/java/applet/Applet.html|website=Docs |publisher=Oracle |access-date=2020-05-01 |archive-date=August 2, 2020 |archive-url=https://web.archive.org/web/20200802033524/https://docs.oracle.com/javase/7/docs/api/java/applet/Applet.html |url-status=live}}</ref>
 
=== Servlet ===
The host application, typically a Web browser, instantiates the '''<code>Hello</code>''' 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 <code>paint</code> method is called by the AWT [[event dispatching thread]] whenever the display needs the applet to draw itself.
{{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 to requests from [[client (computing)|clients]]. Most of the time, this means generating [[HTML]] pages in response to [[Hypertext Transfer Protocol|HTTP]] requests, although there are a number of other standard servlet classes available, for example for [[WebSocket]] communication.
 
The Java servlet API has to some extent been superseded (but still used under the hood) by two standard Java technologies for web services:
=== '''Servlet''' ===
* the [[Java API for RESTful Web Services]] (JAX-RS 2.0) useful for AJAX, JSON and REST services, and
{{Main|Java Servlet}}
* the [[Java API for XML Web Services]] (JAX-WS) useful for [[SOAP]] [[Web Service]]s.
 
Typical implementations of these APIs on Application Servers or Servlet Containers use a standard servlet for handling all interactions with the [[HTTP]] requests and responses that delegate to the web service methods for the actual business logic.
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.
 
=== JavaServer Pages ===
<source lang="java">
// 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();
}
}
</source>
 
The '''<code>import</code>''' 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 <code>'''Hello'''</code> class <code>'''extends'''</code> the '''{{Javadoc:EE|javax/servlet|GenericServlet}}''' class; the <code>GenericServlet</code> class provides the interface for the [[server (computing)|server]] to forward requests to the servlet and control the servlet's lifecycle.
 
The <code>Hello</code> 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 <code>service()</code> 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 <code>service()</code> method declares that it <code>'''throws'''</code> 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 ([[Jakarta Server Pages|JSP]]) are [[server-side]] Java EE components that generate responses, typically [[HTML]] pages, to [[Hypertext Transfer Protocol|HTTP]] requests from [[client (computing)|clients]]. JSPs embed Java code in an HTML page by using the special [[delimiter]]s <code><%</code> and <code>%></code>. 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.<ref>{{Cite web|title=What Is a JSP Page? - The Java EE 5 Tutorial|url=https://docs.oracle.com/javaee/5/tutorial/doc/bnagy.html|website=docs.oracle.com|access-date=2020-05-01|archive-date=August 2, 2020|archive-url=https://web.archive.org/web/20200802003029/https://docs.oracle.com/javaee/5/tutorial/doc/bnagy.html|url-status=live}}</ref>
 
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 <code lang-java"><%</code> and <code lang-java">%></code>. 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 (Java)|Swing]] is a graphical user interface [[library (computing)|library]] for the Java SE platform. 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 (software)|Motif]] are supplied by Sun. [[Apple Inc.|Apple]] also provides an [[Aqua (user interface)|Aqua]] look and feel for [[macOS]]. Where prior implementations of these looks and feels may have been considered lacking, Swing in Java SE 6 addresses this problem by using more native [[Graphical control element|GUI widget]] drawing routines of the underlying platforms.<ref>{{Cite web|title=Trail: Creating a GUI With JFC/Swing (The Java Tutorials)|url=https://docs.oracle.com/javase/tutorial/uiswing/|website=docs.oracle.com|access-date=2020-05-01|archive-date=April 29, 2020|archive-url=https://web.archive.org/web/20200429104302/https://docs.oracle.com/javase/tutorial/uiswing/|url-status=live}}</ref>
 
=== JavaFX application ===
[[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:
{{Main|JavaFX}}
[[JavaFX]] is a [[Computing platform|software platform]] for creating and delivering [[Application software|desktop applications]], as well as [[rich web application]]s that can run across a wide variety of devices. JavaFX is intended to replace [[Swing (Java)|Swing]] as the standard [[graphical user interface]] (GUI) library for [[Java Platform, Standard Edition|Java SE]], but since JDK 11 JavaFX has not been in the core JDK and instead in a separate module.<ref>{{Cite web|title=Removed from JDK 11, JavaFX 11 arrives as a standalone module |work=InfoWorld |date=September 20, 2018 |url=https://www.infoworld.com/article/3305073/removed-from-jdk-11-javafx-11-arrives-as-a-standalone-module.html|access-date=2020-10-13|archive-date=October 14, 2020|archive-url=https://web.archive.org/web/20201014141716/https://www.infoworld.com/article/3305073/removed-from-jdk-11-javafx-11-arrives-as-a-standalone-module.html|url-status=live}}</ref> JavaFX has support for [[desktop computer]]s and [[web browser]]s on [[Microsoft Windows]], [[Linux]], and [[macOS]]. JavaFX does not have support for native OS look and feels.<ref>{{Cite web|title=Getting Started with JavaFX: Hello World, JavaFX Style |work=JavaFX 2 Tutorials and Documentation|url=https://docs.oracle.com/javafx/2/get_started/hello_world.htm |publisher=Oracle |access-date=2020-05-01|archive-date= August 2, 2020 |archive-url=https://web.archive.org/web/20200802013650/https://docs.oracle.com/javafx/2/get_started/hello_world.htm|url-status=live}}</ref>
 
=== Generics ===
<source lang="java">
{{Main|Generics in Java}}
// Hello.java (Java SE 5)
import java.awt.BorderLayout;
import javax.swing.*;
 
In 2004, [[generic programming|generics]] were added to the Java language, as part of J2SE 5.0. Prior to the introduction of generics, each variable declaration had to be of a specific type. For container classes, for example, this is a problem because there is no easy way to create a container that accepts only specific types of objects. Either the container operates on all subtypes of a class or interface, usually <code>Object</code>, or a different container class has to be created for each contained class. Generics allow compile-time type checking without having to create many container classes, each containing almost identical code. In addition to enabling more efficient code, certain runtime exceptions are prevented from occurring, by issuing compile-time errors. If Java prevented all runtime type errors (<code>ClassCastException</code>s) from occurring, it would be [[type safety|type safe]].
public class Hello extends JFrame {
public Hello() {
super("hello");
setDefaultCloseOperation(WindowConstants.EXIT_ON_CLOSE);
setLayout(new BorderLayout());
add(new JLabel("Hello, world!"));
pack();
}
 
In 2016, the type system of Java was proven [[soundness|unsound]] in that it is possible to use generics to construct classes and methods that allow assignment of an instance of one class to a variable of another unrelated class. Such code is accepted by the compiler, but fails at run time with a class cast exception.<ref>{{cite web|url=https://raw.githubusercontent.com/namin/unsound/master/doc/unsound-oopsla16.pdf|title=Java and Scala's Type Systems are Unsound|access-date=February 20, 2017 |archive-url=https://web.archive.org/web/20161128174902/https://raw.githubusercontent.com/namin/unsound/master/doc/unsound-oopsla16.pdf |archive-date=November 28, 2016|url-status=live}}</ref>
public static void main(String[] args) {
new Hello().setVisible(true);
}
}
</source>
 
The first '''<code>import</code>''' 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 '''<code>import</code>''' includes all of the public classes and interfaces from the '''{{Javadoc:SE|package=javax.swing|javax/swing}}''' package.
 
The <code>'''Hello'''</code> class <code>'''extends'''</code> the '''{{Javadoc:SE|javax/swing|JFrame}}''' class; the <code>JFrame</code> class implements a [[window (computing)|window]] with a [[title bar]] and a close [[Widget (computing)|control]].
 
The <code>'''Hello()'''</code> [[constructor (computer science)|constructor]] initializes the frame by first calling the superclass constructor, passing the parameter <code>"hello"</code>, 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 <code>JFrame</code> 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 <code>JFrame</code> 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 <code>BorderLayout</code>; 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 <code>BorderLayout</code>.
 
The <code>'''main()'''</code> method is called by the JVM when the program starts. It [[Instance (programming)|instantiates]] a new '''<code>Hello</code>''' 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 <code>'''true'''</code>. Note that once the frame is displayed, exiting the <code>main</code> 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.
 
=== Generics ===
{{Main|Generics in Java}}
 
== Criticism ==
{{Main|Criticism of Java}}
{{criticism-section}}
Criticisms directed at Java include the implementation of generics,<ref>{{cite web
{{main article|Criticism of Java}}
|last=Arnold
|first=Ken
|date=June 27, 2005
|title=Generics Considered Harmful
|url=https://weblogs.java.net/blog/arnold/archive/2005/06/generics_consid_1.html
|publisher=java.net
|access-date=September 10, 2015
|url-status=dead
|archive-url=https://web.archive.org/web/20071010002142/http://weblogs.java.net/blog/arnold/archive/2005/06/generics_consid_1.html
|archive-date=October 10, 2007
}}</ref> speed,<ref name=Jelovic /> the handling of unsigned numbers,<ref>{{cite web
|last=Owens |first=Sean R.
|url=http://darksleep.com/player/JavaAndUnsignedTypes.html
|archive-url=https://web.archive.org/web/20090220171410/http://darksleep.com/player/JavaAndUnsignedTypes.html
|archive-date=February 20, 2009
|title=Java and unsigned int, unsigned short, unsigned byte, unsigned long, etc. (Or rather, the lack thereof)
|access-date=2011-07-04
}}</ref> the implementation of floating-point arithmetic,<ref>{{cite web
|last=Kahan
|first=William
|date=March 1, 1998
|title=How Java's Floating-Point Hurts Everyone Everywhere – ACM 1998 Workshop on Java (Stanford)
|url=http://www.cs.berkeley.edu/~wkahan/JAVAhurt.pdf
|publisher=Electrical Engineering & Computer Science, University of California at Berkeley
|access-date=June 4, 2011
|archive-url=https://web.archive.org/web/20120905004527/http://www.cs.berkeley.edu/~wkahan/JAVAhurt.pdf
|archive-date=September 5, 2012
|url-status=live
}}</ref> and a history of security vulnerabilities in the primary Java VM implementation [[HotSpot (virtual machine)|HotSpot]].<ref>{{cite web
|url=http://blogs.technet.com/b/mmpc/archive/2010/10/18/have-you-checked-the-java.aspx
|title=Have you checked the Java?
|access-date=December 23, 2011
|archive-url=https://web.archive.org/web/20120921140402/http://blogs.technet.com/b/mmpc/archive/2010/10/18/have-you-checked-the-java.aspx
|archive-date=September 21, 2012
|url-status=dead
}}</ref>
Developers have criticized the complexity and verbosity of the Java Persistence API (JPA), a standard part of Java EE. This has led to increased adoption of higher-level abstractions like Spring Data JPA, which aims to simplify database operations and reduce boilerplate code. The growing popularity of such frameworks suggests limitations in the standard JPA implementation's ease-of-use for modern Java development.<ref>{{cite book
|last=Chidester
|first=Ashlan
|title=Java Persistence API, Jenkins and AWS
|url=https://www.vlebooks.com/vleweb/product/openreader?id=none&isbn=9798224253951
|access-date=September 16, 2024
|isbn=9798224253951
}}</ref>
 
== Class libraries ==
[[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.<ref>[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]]</ref><ref>[http://research.sun.com/techrep/2002/smli_tr-2002-114.pdf FreeTTS - A Performance Case Study], Willie Walker, Paul Lamere, Philip Kwok</ref> 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.
{{Main|Java Class Library}}
The [[Java Class Library]] is the [[standard library]], developed to support application development in Java. It is controlled by [[Oracle Corporation|Oracle]] in cooperation with others through the [[Java Community Process]] program.<ref>{{Citation|last=Cadenhead|first=Rogers|title=Understanding How Java Programs Work|date=2017-11-20|url=http://www.informit.com/articles/article.aspx?p=2832404&seqNum=4|access-date=2019-03-26|archive-date=August 13, 2021|archive-url=https://web.archive.org/web/20210813193850/https://www.informit.com/articles/article.aspx?p=2832404&seqNum=4|url-status=live}}</ref> Companies or individuals participating in this process can influence the design and development of the APIs. This process has been a subject of controversy during the 2010s.<ref>{{Cite news|url=https://www.theguardian.com/technology/2016/may/26/google-wins-copyright-lawsuit-oracle-java-code|title=Google wins six-year legal battle with Oracle over Android code copyright|last=Woolf|first=Nicky|date=2016-05-26|work=The Guardian|access-date=2019-03-26|language=en-GB|issn=0261-3077|archive-date=March 26, 2019|archive-url=https://web.archive.org/web/20190326203847/https://www.theguardian.com/technology/2016/may/26/google-wins-copyright-lawsuit-oracle-java-code|url-status=live}}</ref> The class library contains features such as:
* The core libraries, which include:
** [[Input/output]] (I/O or IO){{sfn|Bloch|2018|loc=§&nbsp;1 Introduction|pp=1-4}} and [[Non-blocking I/O (Java)|non-blocking I/O]] (NIO), or IO/NIO<ref>{{Cite web|url=https://docs.oracle.com/javase/8/docs/api/java/nio/package-summary.html|title=java.nio (Java Platform SE 8)|website=docs.oracle.com}}</ref>
** [[Computer network|Networking]]<ref>{{Cite web|url=https://docs.oracle.com/javase/8/docs/technotes/guides/net/|title=Java Networking|website=docs.oracle.com}}</ref> (new [[user agent]] (HTTP client) since Java 11<ref>{{Cite web|url=https://docs.oracle.com/en/java/javase/11/docs/api/java.net.http/java/net/http/HttpClient.html|title=HttpClient (Java SE 11 & JDK 11)|website=docs.oracle.com}}</ref>)
** [[Reflective programming]] (reflection)
** [[Concurrent computing]] (concurrency){{sfn|Bloch|2018|loc=§&nbsp;1 Introduction|pp=1-4}}
** [[Generics in Java|Generics]]
** Scripting, Compiler
** [[Functional programming]] ([[Lambda (programming)|Lambda]], streaming)
** [[Java collections framework|Collection libraries]] that implement [[data structure]]s such as [[List (abstract data type)|lists]], [[associative array|dictionaries]], [[tree structure|trees]], [[Set (abstract data type)|sets]], [[Queue (abstract data type)|queues]] and [[double-ended queue]], or [[Stack (abstract data type)|stacks]]<ref name="collections">{{cite web |url=http://docs.oracle.com/javase/8/docs/technotes/guides/collections/overview.html |title=Collections Framework Overview |publisher=Oracle |work=Java Documentation |access-date=December 18, 2014 |archive-url=https://web.archive.org/web/20141231132540/http://docs.oracle.com/javase/8/docs/technotes/guides/collections/overview.html |archive-date=December 31, 2014 |url-status=live}}</ref>
** [[XML]] Processing (Parsing, Transforming, Validating) libraries
** [[Computer security|Security]]<ref name="security">{{cite web |url=http://docs.oracle.com/javase/8/docs/technotes/guides/security/overview/jsoverview.html |title=Java Security Overview |publisher=Oracle |work=Java Documentation |access-date=December 18, 2014 |archive-url=https://web.archive.org/web/20150103045031/http://docs.oracle.com/javase/8/docs/technotes/guides/security/overview/jsoverview.html |archive-date=January 3, 2015 |url-status=live}}</ref>
** [[Internationalization and localization]] libraries<ref name="i18n">{{cite web |url=http://docs.oracle.com/javase/tutorial/i18n/ |title=Trail: Internationalization |publisher=Oracle |work=The Java Tutorials |access-date=December 18, 2014 |archive-url=https://web.archive.org/web/20141231053232/http://docs.oracle.com/javase/tutorial/i18n/ |archive-date=December 31, 2014 |url-status=live}}</ref>
* 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 [[Common Object Request Broker Architecture]] (CORBA) for distributed application development
** [[Java Management Extensions]] (JMX) for managing and monitoring applications
* [[User interface]] libraries, which include:
** The (heavyweight, or [[Native (computing)|native]]) [[Abstract Window 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
** [[JavaFX]]
* A platform dependent implementation of the Java virtual machine that is the means by which the bytecodes of the Java libraries and third-party applications are executed
* Plugins, which enable [[Java applet|applets]] to be run in web browsers
* [[Java Web Start]], which allows Java applications to be efficiently distributed to [[end user]]s across the Internet
* Licensing and documentation
 
== Documentation ==
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]] or [[Standard Widget Toolkit]] may be used for increased integration with the native windowing system.
{{Main|Javadoc}}
 
Javadoc is a comprehensive documentation system, created by [[Sun Microsystems]]. It provides developers with an organized system for documenting their code. Javadoc comments have an extra asterisk at the beginning, i.e. the delimiters are <code>/**</code> and <code>*/</code>, whereas the normal multi-line comments in Java are delimited by <code>/*</code> and <code>*/</code>, and single-line comments start with <code>//</code>.<ref name="javadoc_comments">{{cite web |url=https://www.oracle.com/technetwork/articles/java/index-137868.html |title=How to Write Doc Comments for the Javadoc Tool |publisher=Oracle |work=Oracle Technology Network |access-date=December 18, 2014 |archive-url=https://web.archive.org/web/20141218182906/http://www.oracle.com/technetwork/articles/java/index-137868.html |archive-date=December 18, 2014 |url-status=live}}</ref>
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.
 
== Implementations ==
Java suppresses several features (such as [[operator overloading]] and [[multiple inheritance]]) for ''classes'' in order to simplify the language and to prevent possible errors and anti-pattern design.
{{See also|Free Java implementations|List of Java compilers}}
{{More citations needed|section|date=September 2023}}
[[Oracle Corporation]] owns the official implementation of the Java SE platform, due to its acquisition of [[Sun Microsystems]] on January 27, 2010. This implementation is based on the original implementation of Java by Sun. The Oracle implementation is available for [[Microsoft Windows|Windows]], [[macOS]], [[Linux]], and [[Solaris (operating system)|Solaris]]. Because Java lacks any formal standardization recognized by [[Ecma International]], ISO/IEC, ANSI, or other third-party standards organizations, the Oracle implementation is the [[de facto standard]].
 
The Oracle implementation is packaged into two different distributions: The Java Runtime Environment (JRE) which contains the parts of the Java SE platform required to run Java programs and is intended for end users, and the [[Java Development Kit]] (JDK), which is intended for software developers and includes development tools such as the [[Java compiler]], [[Javadoc]], [[JAR (file format)|Jar]], and a [[debugger]]. Oracle has also released [[GraalVM]], a high performance Java dynamic compiler and interpreter.
== Target ==
{{Main|Java Runtime Environment}}
 
[[OpenJDK]] is another Java SE implementation that is licensed under the GNU GPL. The implementation started when Sun began releasing the Java source code under the GPL. As of Java SE 7, OpenJDK is the official Java reference implementation.
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]].
 
The goal of Java is to make all implementations of Java compatible. Historically, 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 [[Java remote method invocation]] (RMI) or [[Java Native Interface]] (JNI) and had added platform-specific features of their own. Sun sued in 1997, and, in 2001, won a settlement of US$20&nbsp;million, as well as a court order enforcing the terms of the license from Sun.<ref>{{cite news |last1=Niccolai |first1=James |date=2001-01-24 |title=Sun, Microsoft settle Java lawsuit |url=https://www.infoworld.com/article/2074908/sun-microsoft-settle-java-lawsuit.html |work=[[JavaWorld]] |agency=[[IDG News Service]] |access-date=2020-07-13 |archive-date=July 14, 2020 |archive-url=https://web.archive.org/web/20200714001541/https://www.infoworld.com/article/2074908/sun-microsoft-settle-java-lawsuit.html |url-status=live}}</ref> As a result, Microsoft no longer ships Java with [[Microsoft Windows|Windows]].
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.
 
Platform-independent Java is essential to [[Java Platform, Enterprise Edition|Java EE]], and an even more rigorous validation is required to certify an implementation. This environment enables portable server-side applications.
== Class libraries ==
 
== Use outside the Java platform ==
* 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 Java programming language requires the presence of a software platform in order for compiled programs to be executed.
** 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 (lightweight, 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 (heavyweight) [[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.
 
Oracle supplies the [[Java platform]] for use with Java. The [[Android SDK]] is an alternative software platform, used primarily for developing [[Android application]]s with its own GUI system.
== APIs ==
{{see also|Free Java implementations#Class library}}
 
=== Android ===
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:
The Java language is a key pillar in [[Android (operating system)|Android]], an [[open source software|open source]] [[mobile operating system]]. Although Android, built on the [[Linux kernel]], is written largely in C, the [[Android software development#SDK|Android SDK]] uses the Java language as the basis for Android applications but does not use any of its standard GUI, SE, ME or other established Java standards.<ref>{{cite web
|url=http://www.javalobby.org/nl/archive/jlnews_20071113o.html
|title=Google Android: Initial Impressions and Criticism
|date=November 13, 2007
|last=van Gurp
|first=Jilles
|work=Javalobby
|quote=''Frankly, I don't understand why Google intends to ignore the vast amount of existing implementation out there. It seems like a bad case of "not invented here" to me. Ultimately, this will slow adoption. There are already too many Java platforms for the mobile world and this is yet another one''
|access-date=March 7, 2009
|archive-date=August 28, 2008
|archive-url=https://web.archive.org/web/20080828111808/http://www.javalobby.org/nl/archive/jlnews_20071113o.html
|url-status=usurped
}}</ref> The bytecode language supported by the Android SDK is incompatible with Java bytecode and runs on its own virtual machine, optimized for low-memory devices such as [[smartphone]]s and [[tablet computer]]s. Depending on the Android version, the bytecode is either interpreted by the [[Dalvik (software)|Dalvik virtual machine]] or compiled into native code by the [[Android Runtime]].
 
Android does not provide the full Java SE standard library, although the Android SDK does include an independent implementation of a large subset of it. It supports Java&nbsp;6 and some Java&nbsp;7 features, offering an implementation compatible with the standard library ([[Apache Harmony]]).
* [[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.
 
==== Controversy ====
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.
{{See also|Oracle America, Inc. v. Google, Inc.}}
 
The use of Java-related technology in Android led to a legal dispute between Oracle and Google. On May 7, 2012, a San Francisco jury found that if APIs could be copyrighted, then Google had infringed Oracle's copyrights by the use of Java in Android devices.<ref>{{cite web |last=Mullin |first=Joe |title=Google guilty of infringement in Oracle trial; future legal headaches loom |url=https://arstechnica.com/tech-policy/news/2012/05/jury-rules-google-violated-copyright-law-google-moves-for-mistrial.ars |work=Law & Disorder |date=May 7, 2012 |publisher=Ars Technica |access-date=2012-05-08 |archive-url=https://web.archive.org/web/20120508134916/http://arstechnica.com/tech-policy/news/2012/05/jury-rules-google-violated-copyright-law-google-moves-for-mistrial.ars |archive-date=May 8, 2012 |url-status=live}}</ref> District Judge [[William Alsup]] ruled on May 31, 2012, that APIs cannot be copyrighted,<ref>{{cite web
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.
|title=Google wins crucial API ruling, Oracle's case decimated
|url=https://arstechnica.com/tech/2012/05/google-wins-crucial-api-ruling-oracles-case-decimated/
|first=Joe
|last=Mullin
|work=Ars Technica
|date=May 31, 2012
|access-date=2012-06-01
|archive-url=https://web.archive.org/web/20170312065520/https://arstechnica.com/tech-policy/2012/05/google-wins-crucial-api-ruling-oracles-case-decimated/
|archive-date=March 12, 2017
|url-status=live
}}</ref> but this was reversed by the United States Court of Appeals for the Federal Circuit in May 2014.<ref name="cnet appeals">{{cite news |url=https://www.cnet.com/news/court-sides-with-oracle-over-android-in-java-patent-appeal/ |title=Court sides with Oracle over Android in Java patent appeal |work=CNET |date=May 9, 2014 |access-date=2014-05-10 |author=Rosenblatt, Seth |archive-url=https://web.archive.org/web/20140510203805/http://www.cnet.com/news/court-sides-with-oracle-over-android-in-java-patent-appeal/ |archive-date=May 10, 2014 |url-status=live}}</ref> On May 26, 2016, the district court decided in favor of Google, ruling the copyright infringement of the Java API in Android constitutes fair use.<ref>{{cite web |last1=Mullin |first1=Joe |title=Google beats Oracle—Android makes "fair use" of Java APIs |url=https://arstechnica.com/tech-policy/2016/05/google-wins-trial-against-oracle-as-jury-finds-android-is-fair-use/ |access-date=2016-05-26 |website=Ars Technica |date=2016-05-26 |archive-url=https://web.archive.org/web/20170120164551/http://arstechnica.com/tech-policy/2016/05/google-wins-trial-against-oracle-as-jury-finds-android-is-fair-use/ |archive-date=January 20, 2017 |url-status=live}}</ref> In March 2018, this ruling was overturned by the Appeals Court, which sent down the case of determining the damages to federal court in San Francisco.<ref>{{cite web
|title="Google's use of the Java API packages was not fair," appeals court rules
|url=https://arstechnica.com/tech-policy/2018/03/googles-use-of-the-java-api-packages-was-not-fair-appeals-court-rules/
|first=Cyrus
|last=Farivar
|work=Ars Technica
|date=March 27, 2018
|access-date=2019-08-06
|archive-date=September 24, 2019
|archive-url=https://web.archive.org/web/20190924081919/https://arstechnica.com/tech-policy/2018/03/googles-use-of-the-java-api-packages-was-not-fair-appeals-court-rules/
|url-status=live
}}</ref>
Google filed a petition for [[Certiorari|writ of certiorari]] with the [[Supreme Court of the United States]] in January 2019 to challenge the two rulings that were made by the Appeals Court in Oracle's favor.<ref>{{cite web |url=https://arstechnica.com/tech-policy/2019/01/google-asks-supreme-court-to-overrule-disastrous-ruling-on-api-copyrights/ |title=Google asks Supreme Court to overrule disastrous ruling on API copyrights |first=Timothy |last=Lee |date=April 23, 2019 |access-date=April 23, 2019 |work=[[Ars Technica]] |archive-date=April 23, 2019 |archive-url=https://web.archive.org/web/20190423084450/https://arstechnica.com/tech-policy/2019/01/google-asks-supreme-court-to-overrule-disastrous-ruling-on-api-copyrights/ |url-status=live}}</ref> On April 5, 2021, the Court ruled 6–2 in Google's favor, that its use of Java APIs should be considered [[fair use]]. However, the court refused to rule on the copyrightability of APIs, choosing instead to determine their ruling by considering Java's API copyrightable "purely for argument's sake."<ref>{{Cite web |url=https://www.supremecourt.gov/opinions/20pdf/18-956_d18f.pdf |title=''Google LLC v. Oracle America, Inc'' 593 U. S. ____ (2021) |access-date=April 6, 2021 |archive-date=April 5, 2021 |archive-url=https://web.archive.org/web/20210405140150/https://www.supremecourt.gov/opinions/20pdf/18-956_d18f.pdf |url-status=live}}</ref>
 
== See also ==
{{Portal|Computer programming}}
 
* [[C Sharp (programming language)|C#]]
* [[C++]]
* [[Dalvik (software)|Dalvik]], used in old Android versions, replaced by non-JIT [[Android Runtime]]
* [[Java Heterogeneous Distributed Computing]]
* [[List of Java APIs]]
* [[List of Java frameworks]]
* [[List of JVM languages]]
* [[List of Java virtual machines]]
* [[Comparison of C Sharp and Java|Comparison of C# and Java]]
* [[Comparison of Java and C++]]
* [[Comparison of programming languages]]
* [[Comparison of Java and C Sharp]]
* [[Groovy (programming language)]]
* [[Jython]]
* [[JRuby]]
* [[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]]
 
== Notes ==
 
{{reflist|2}}
 
== References ==
{{Reflist}}
 
== Bibliography ==
{{refbegin}}
{{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]].
* {{Cite book |last=Bloch |first=Joshua |year=2018|title=Effective Java: Programming Language Guide |edition=Third |publisher=Addison-Wesley |isbn=978-0-13-468599-1}}
* [[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{{Cite book |last1=Gosling]], [[|first1=James |last2=Joy |first2=Bill |author-link2=Bill Joy]], [[|last3=Steele |first3=Guy L. Steele, Jr. |author-link3=Guy L. Steele]], andJr. [[|first4=Gilad |last4=Bracha]], ''|author-link4=Gilad Bracha |year=2005 |title=The Java languageLanguage specification'',Specification third|url=https://java.sun.com/docs/books/jls/ |edition.=3rd |publisher=Addison-Wesley, 2005. ISBN |isbn=0-321-24678-0 (see|access-date=February also8, [2019 |archive-date=February 14, 2012 |archive-url=https://web.archive.org/web/20120214061826/http://java.sun.com/docs/books/jls/index.html online edition of the specification].|url-status=live}}
* {{Cite book |last1=Gosling |first1=James |last2=Joy |first2=Bill |last3=Steele |first3=Guy |last4=Bracha |first4=Gilad |last5=Buckley |first5=Alex |title=The Java® Language Specification |date=2014 |edition=Java SE 8 |url=https://docs.oracle.com/javase/specs/jls/se8/jls8.pdf |access-date=November 18, 2014 |archive-date=October 21, 2014 |archive-url=https://web.archive.org/web/20141021061951/http://docs.oracle.com/javase/specs/jls/se8/jls8.pdf |url-status=live}}
* 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]).
* {{Cite book |last1=Lindholm |first1=Tim |last2=Yellin |first2=Frank |year=1999 |title=The Java Virtual Machine Specification |url=https://java.sun.com/docs/books/vmspec/2nd-edition/html/VMSpecTOC.doc.html |edition=2nd |publisher=Addison-Wesley |isbn=0-201-43294-3 |access-date=February 8, 2019 |archive-date=September 25, 2011 |archive-url=https://web.archive.org/web/20110925050249/http://java.sun.com/docs/books/vmspec/2nd-edition/html/VMSpecTOC.doc.html |url-status=live}}
{{refend}}
{{Refend}}
 
== External links ==
{{Sister project links |wikt=Java |display=Java |commons=Category:Java (programming language) |b=Java Programming |n=no |s=no |voy=no |species=no |v=Java |d=Q251}}
{{Wikibooks|Java Programming}}
{{wikiversity|Java Platform, Enterprise Edition/Java EE Tutorial}}
{{Wikiversity|java}}
* {{Official website|jdk.java.net}}, OpenJDK, Oracle
* [http://www.java.com/ Java home page]
* [httphttps://javaadoptium.sun.comnet/ JavaJDK forbuilds, developersAdoptium]
* {{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 (Sunsoftware platform)}}
{{Sun Microsystems}}
{{FOSSOracle}}
{{Oracle FOSS}}
{{Programming languages}}
{{Authority control}}
 
[[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-orientedConcurrent programming languages]]
[[Category:Java platform|Programming language]]
[[Category:Java specification requests|Programming language]]
[[Category:JVM programming languages]]
[[Category:JVMMulti-paradigm programming languagelanguages]]
[[Category:Curly bracketObject-oriented programming languages|*]]
[[Category:Programming languages created in 1995]]
[[am:ጃቫ (java)]]
[[Category:Programming languages]]
[[ar:جافا]]
[[Category:Statically typed programming languages]]
[[az:Java]]
[[Category:Sun Microsystems]]
[[bn:জাভা (প্রোগ্রামিং ভাষা)]]
[[Category:Compiled programming languages]]
[[be:Java]]
[[Category:American inventions]]
[[be-x-old:Java]]
<!-- Hidden categories below -->
[[bs:Java programski jezik]]
[[bgCategory:Articles with example Java code]]
[[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:ജാവാ പ്രോഗ്രാമിങ് ഭാഷ]]
[[mr:जावा प्रोग्रॅमिंग लँग्वेज]]
[[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)]]
[[kaa:Java (programmalastırıw tili)]]
[[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]]