JAVA: Exception - Revision history

Unknown user: /* Bagaimana JVM menangani Exception? */

2022-05-10T05:27:45Z

Bagaimana JVM menangani Exception?

← Older revision		Revision as of 05:27, 10 May 2022
Line 60:		Line 60:
	==Bagaimana JVM menangani Exception?==		==Bagaimana JVM menangani Exception?==

	Default Exception Handling: Whenever inside a method, if an exception has occurred, the method creates an Object known as an Exception Object and hands it off to the run-time system(JVM). The exception object contains the name and description of the exception and the current state of the program where the exception has occurred. Creating the Exception Object and handling it in the run-time system is called throwing an Exception. There might be a list of the methods that had been called to get to the method where an exception occurred. This ordered list of the methods is called Call Stack. Now the following procedure will happen.		'''Default Exception Handling:''' Kapan pun di dalam suatu method, jika exception telah terjadi, method tersebut membuat Object yang dikenal sebagai Exception Object dan menyerahkannya ke run-time system (JVM). Exception object berisi nama dan deskripsi exception dan status program saat ini di mana exception telah terjadi. Membuat Exception Object dan menanganinya dalam run-time system disebut throwing an Exception. Mungkin ada daftar method yang dipanggil untuk sampai ke method di mana exception terjadi. Daftar method yang diurutkan ini disebut Call Stack. Selanjutnya, prosedur berikut akan terjadi.

	~~Penanganan Pengecualian Default:~~ Kapan pun di dalam suatu ~~metode~~, jika ~~pengecualian~~ telah terjadi, ~~metode~~ tersebut membuat ~~Objek~~ yang dikenal sebagai ~~Objek Pengecualian~~ dan menyerahkannya ke ~~sistem~~ run-time (JVM). ~~Objek pengecualian~~ berisi nama dan deskripsi ~~pengecualian~~ dan status program saat ini di mana ~~pengecualian~~ telah terjadi. Membuat ~~Objek Pengecualian~~ dan menanganinya dalam ~~sistem~~ run-time disebut ~~melempar Pengecualian~~. Mungkin ada daftar ~~metode~~ yang dipanggil untuk sampai ke ~~metode~~ di mana ~~pengecualian~~ terjadi. Daftar ~~metode~~ yang diurutkan ini disebut Call Stack. ~~Sekarang~~ prosedur berikut akan terjadi.


	* The run-time system searches the call stack to find the method that contains a block of code that can handle the occurred exception. The block of the code is called an Exception handler.
	* The run-time system starts searching from the method in which the exception occurred, and proceeds through the call stack in the reverse order in which methods were called.
	* If it finds an appropriate handler then it passes the occurred exception to it. An appropriate handler means the type of the exception object thrown matches the type of the exception object it can handle.
	* If the run-time system searches all the methods on the call stack and couldn’t have found the appropriate handler then the run-time system handover the Exception Object to the default exception handler, which is part of the run-time system. This handler prints the exception information in the following format and terminates the program abnormally.


	* Sistem run-time mencari tumpukan panggilan untuk menemukan metode yang berisi blok kode yang dapat menangani pengecualian yang terjadi. Blok kode tersebut disebut Exception handler.
	* Sistem run-time mulai mencari dari metode di mana pengecualian terjadi, dan melanjutkan melalui tumpukan panggilan dalam urutan terbalik di mana metode dipanggil.
	* Jika menemukan penangan yang sesuai maka melewati pengecualian yang terjadi padanya. Handler yang sesuai berarti jenis objek pengecualian yang dilempar cocok dengan jenis objek pengecualian yang dapat ditanganinya.
	* Jika sistem run-time mencari semua metode pada tumpukan panggilan dan tidak dapat menemukan handler yang sesuai, maka sistem run-time akan menyerahkan Objek Pengecualian ke handler eksepsi default, yang merupakan bagian dari sistem run-time. Handler ini mencetak informasi pengecualian dalam format berikut dan menghentikan program secara tidak normal.



			* Run-time system mencari call stack untuk menemukan method yang berisi block code yang dapat menangani exception yang terjadi. Block code tersebut disebut Exception handler.
			* Run-time system mulai mencari dari method di mana exception terjadi, dan melanjutkan melalui call stack dalam urutan terbalik di mana method dipanggil.
			* Jika menemukan penangan yang sesuai maka melewati exception yang terjadi padanya. Handler yang sesuai berarti jenis exception object yang dilempar cocok dengan jenis exception object yang dapat ditanganinya.
			* Jika run-time system mencari semua method pada call stack dan tidak dapat menemukan handler yang sesuai, maka run-time system akan menyerahkan exception object ke default exception handler, yang merupakan bagian dari run-time system. Handler ini mencetak informasi exception dalam format berikut dan menghentikan program secara tidak normal.


Line 83:		Line 71:
	... ...... .. // Call Stack		... ...... .. // Call Stack

	~~Look at the below~~ diagram ~~to understand the flow of the~~ call stack.		Lihatlah diagram di bawah ini untuk memahami aliran call stack.

	[[File:Call-stack.png\|center\|300px\|thumb\|call stack]]		[[File:Call-stack.png\|center\|300px\|thumb\|call stack]]


	~~Illustration~~:		Ilustrasi:

	// Java Program to Demonstrate How Exception Is Thrown		// Java Program to Demonstrate How Exception Is Thrown
Line 186:		Line 174:
	}		}
	}		}

	Output		Output
	/ by zero		/ by zero

Unknown user: /* User-Defined Exception: */

2022-05-10T05:19:18Z

User-Defined Exception:

← Older revision		Revision as of 05:19, 10 May 2022
Line 49:		Line 49:
	===User-Defined Exception:===		===User-Defined Exception:===

	~~Sometimes~~, ~~the~~ built-in ~~exceptions in Java are not able to describe a certain situation. In such cases, users can also create exceptions which are called ‘user-defined Exceptions’.~~		Terkadang, built-in exception di Java tidak dapat menggambarkan situasi tertentu. Dalam kasus seperti itu, pengguna juga dapat membuat exception yang disebut 'user-defined Exception'.

	~~Terkadang, pengecualian bawaan~~ di Java tidak dapat menggambarkan situasi tertentu. Dalam kasus seperti itu, pengguna juga dapat membuat ~~pengecualian~~ yang disebut '~~Pengecualian yang ditentukan pengguna~~'.

	~~The advantages of Exception Handling in Java are as follows:~~

	Kelebihan Exception Handling di Java adalah sebagai berikut:		Kelebihan Exception Handling di Java adalah sebagai berikut:

	* Provision to Complete Program Execution
	* Easy Identification of Program Code and Error-Handling Code
	* Propagation of Errors
	* Meaningful Error Reporting
	* Identifying Error Types

	* Ketentuan untuk Menyelesaikan Eksekusi Program		* Ketentuan untuk Menyelesaikan Eksekusi Program
	* Identifikasi Kode Program dan Kode Penanganan ~~Kesalahan~~ yang Mudah		* Identifikasi Kode Program dan Kode Penanganan Error yang Mudah
	* Penyebaran Kesalahan		* Penyebaran Kesalahan
	* Pelaporan Kesalahan yang Berarti		* Pelaporan Kesalahan yang Berarti

Unknown user: /* Built-in Exception: */

2022-05-10T05:17:56Z

Built-in Exception:

← Older revision		Revision as of 05:17, 10 May 2022
Line 44:		Line 44:
	Built-in exception adalah exception yang tersedia di Java Library. Exception ini cocok untuk menjelaskan situasi error tertentu.		Built-in exception adalah exception yang tersedia di Java Library. Exception ini cocok untuk menjelaskan situasi error tertentu.

	* Checked Exception: Exception yang diperiksa disebut compile-time exception karena exception ini diperiksa pada waktu kompilasi oleh kompiler.		* '''Checked Exception:''' Exception yang diperiksa disebut compile-time exception karena exception ini diperiksa pada waktu kompilasi oleh kompiler.
			* '''Unchecked Exception:''' Unchecked exception berlawanan dengan Checked exception. Kompiler tidak akan memeriksa exception ini pada waktu kompilasi. Dengan kata sederhana, jika sebuah program mengeluarkan unchecked exception, dan bahkan jika kita tidak menangani atau mendeklarasikannya, program tersebut tidak akan memberikan error kompilasi.
	* Unchecked Exception: ~~The unchecked exceptions are just opposite to the checked exceptions. The compiler will not check these exceptions at compile time. In simple words, if a program throws an unchecked~~ exception~~, and even if we didn’t handle or declare it, the program would not give a compilation error.~~

	~~Pengecualian yang tidak dicentang~~ berlawanan dengan ~~pengecualian yang dicentang~~. Kompiler tidak akan memeriksa ~~pengecualian~~ ini pada waktu kompilasi. Dengan kata sederhana, jika sebuah program mengeluarkan ~~pengecualian yang tidak dicentang~~, dan bahkan jika kita tidak menangani atau mendeklarasikannya, program tersebut tidak akan memberikan ~~kesalahan~~ kompilasi.

	===User-Defined Exception:===		===User-Defined Exception:===

Unknown user: /* Built-in Exception: */

2022-05-10T05:16:15Z

Built-in Exception:

← Older revision		Revision as of 05:16, 10 May 2022
Line 44:		Line 44:
	Built-in exception adalah exception yang tersedia di Java Library. Exception ini cocok untuk menjelaskan situasi error tertentu.		Built-in exception adalah exception yang tersedia di Java Library. Exception ini cocok untuk menjelaskan situasi error tertentu.

	* Checked Exception: ~~Checked exceptions are called~~ compile-time ~~exceptions because these exceptions are checked at compile-time by the compiler.~~		* Checked Exception: Exception yang diperiksa disebut compile-time exception karena exception ini diperiksa pada waktu kompilasi oleh kompiler.

	~~Pengecualian yang diperiksa disebut pengecualian waktu kompilasi~~ karena ~~pengecualian~~ ini diperiksa pada waktu kompilasi oleh kompiler.

	* Unchecked Exception: The unchecked exceptions are just opposite to the checked exceptions. The compiler will not check these exceptions at compile time. In simple words, if a program throws an unchecked exception, and even if we didn’t handle or declare it, the program would not give a compilation error.		* Unchecked Exception: The unchecked exceptions are just opposite to the checked exceptions. The compiler will not check these exceptions at compile time. In simple words, if a program throws an unchecked exception, and even if we didn’t handle or declare it, the program would not give a compilation error.

Unknown user: /* Built-in Exception: */

2022-05-10T04:54:49Z

Built-in Exception:

← Older revision		Revision as of 04:54, 10 May 2022
Line 42:		Line 42:
	===Built-in Exception:===		===Built-in Exception:===

	Built-in ~~exceptions are the exceptions that are available in Java libraries. These exceptions are suitable to explain certain error situations.~~		Built-in exception adalah exception yang tersedia di Java Library. Exception ini cocok untuk menjelaskan situasi error tertentu.

	~~Pengecualian bawaan~~ adalah ~~pengecualian~~ yang tersedia di ~~perpustakaan~~ Java. ~~Pengecualian~~ ini cocok untuk menjelaskan situasi ~~kesalahan~~ tertentu.

	* Checked Exception: Checked exceptions are called compile-time exceptions because these exceptions are checked at compile-time by the compiler.		* Checked Exception: Checked exceptions are called compile-time exceptions because these exceptions are checked at compile-time by the compiler.
Line 53:		Line 51:

	Pengecualian yang tidak dicentang berlawanan dengan pengecualian yang dicentang. Kompiler tidak akan memeriksa pengecualian ini pada waktu kompilasi. Dengan kata sederhana, jika sebuah program mengeluarkan pengecualian yang tidak dicentang, dan bahkan jika kita tidak menangani atau mendeklarasikannya, program tersebut tidak akan memberikan kesalahan kompilasi.		Pengecualian yang tidak dicentang berlawanan dengan pengecualian yang dicentang. Kompiler tidak akan memeriksa pengecualian ini pada waktu kompilasi. Dengan kata sederhana, jika sebuah program mengeluarkan pengecualian yang tidak dicentang, dan bahkan jika kita tidak menangani atau mendeklarasikannya, program tersebut tidak akan memberikan kesalahan kompilasi.


	===User-Defined Exception:===		===User-Defined Exception:===

Unknown user: /* How Does JVM handle an Exception? */

2022-05-10T03:28:25Z

How Does JVM handle an Exception?

← Older revision		Revision as of 03:28, 10 May 2022
Line 77:		Line 77:
	* Mengidentifikasi Jenis Kesalahan		* Mengidentifikasi Jenis Kesalahan

	==~~How Does~~ JVM ~~handle an~~ Exception?==		==Bagaimana JVM menangani Exception?==

	Default Exception Handling: Whenever inside a method, if an exception has occurred, the method creates an Object known as an Exception Object and hands it off to the run-time system(JVM). The exception object contains the name and description of the exception and the current state of the program where the exception has occurred. Creating the Exception Object and handling it in the run-time system is called throwing an Exception. There might be a list of the methods that had been called to get to the method where an exception occurred. This ordered list of the methods is called Call Stack. Now the following procedure will happen.		Default Exception Handling: Whenever inside a method, if an exception has occurred, the method creates an Object known as an Exception Object and hands it off to the run-time system(JVM). The exception object contains the name and description of the exception and the current state of the program where the exception has occurred. Creating the Exception Object and handling it in the run-time system is called throwing an Exception. There might be a list of the methods that had been called to get to the method where an exception occurred. This ordered list of the methods is called Call Stack. Now the following procedure will happen.

			Penanganan Pengecualian Default: Kapan pun di dalam suatu metode, jika pengecualian telah terjadi, metode tersebut membuat Objek yang dikenal sebagai Objek Pengecualian dan menyerahkannya ke sistem run-time (JVM). Objek pengecualian berisi nama dan deskripsi pengecualian dan status program saat ini di mana pengecualian telah terjadi. Membuat Objek Pengecualian dan menanganinya dalam sistem run-time disebut melempar Pengecualian. Mungkin ada daftar metode yang dipanggil untuk sampai ke metode di mana pengecualian terjadi. Daftar metode yang diurutkan ini disebut Call Stack. Sekarang prosedur berikut akan terjadi.


	* The run-time system searches the call stack to find the method that contains a block of code that can handle the occurred exception. The block of the code is called an Exception handler.		* The run-time system searches the call stack to find the method that contains a block of code that can handle the occurred exception. The block of the code is called an Exception handler.
Line 85:		Line 88:
	* If it finds an appropriate handler then it passes the occurred exception to it. An appropriate handler means the type of the exception object thrown matches the type of the exception object it can handle.		* If it finds an appropriate handler then it passes the occurred exception to it. An appropriate handler means the type of the exception object thrown matches the type of the exception object it can handle.
	* If the run-time system searches all the methods on the call stack and couldn’t have found the appropriate handler then the run-time system handover the Exception Object to the default exception handler, which is part of the run-time system. This handler prints the exception information in the following format and terminates the program abnormally.		* If the run-time system searches all the methods on the call stack and couldn’t have found the appropriate handler then the run-time system handover the Exception Object to the default exception handler, which is part of the run-time system. This handler prints the exception information in the following format and terminates the program abnormally.


			* Sistem run-time mencari tumpukan panggilan untuk menemukan metode yang berisi blok kode yang dapat menangani pengecualian yang terjadi. Blok kode tersebut disebut Exception handler.
			* Sistem run-time mulai mencari dari metode di mana pengecualian terjadi, dan melanjutkan melalui tumpukan panggilan dalam urutan terbalik di mana metode dipanggil.
			* Jika menemukan penangan yang sesuai maka melewati pengecualian yang terjadi padanya. Handler yang sesuai berarti jenis objek pengecualian yang dilempar cocok dengan jenis objek pengecualian yang dapat ditanganinya.
			* Jika sistem run-time mencari semua metode pada tumpukan panggilan dan tidak dapat menemukan handler yang sesuai, maka sistem run-time akan menyerahkan Objek Pengecualian ke handler eksepsi default, yang merupakan bagian dari sistem run-time. Handler ini mencetak informasi pengecualian dalam format berikut dan menghentikan program secara tidak normal.





	Exception in thread "xxx" Name of Exception : Description		Exception in thread "xxx" Name of Exception : Description
Line 194:		Line 207:
	Output		Output
	/ by zero		/ by zero


	==Referensi==		==Referensi==

	* https://www.geeksforgeeks.org/exceptions-in-java/		* https://www.geeksforgeeks.org/exceptions-in-java/

Unknown user: /* Tipe Exception */

2022-05-10T03:27:22Z

Tipe Exception

← Older revision		Revision as of 03:27, 10 May 2022
Line 38:		Line 38:
	* User-Defined Exception		* User-Defined Exception

	~~Let us discuss the above-defined listed exception that is as follows~~:		Mari kita bahas pengecualian terdaftar yang ditentukan di atas yaitu sebagai berikut:

	===Built-in ~~Exceptions~~:===		===Built-in Exception:===

	Built-in exceptions are the exceptions that are available in Java libraries. These exceptions are suitable to explain certain error situations.		Built-in exceptions are the exceptions that are available in Java libraries. These exceptions are suitable to explain certain error situations.
	* Checked Exceptions: Checked exceptions are called compile-time exceptions because these exceptions are checked at compile-time by the compiler.
	* Unchecked Exceptions: The unchecked exceptions are just opposite to the checked exceptions. The compiler will not check these exceptions at compile time. In simple words, if a program throws an unchecked exception, and even if we didn’t handle or declare it, the program would not give a compilation error.

	~~Note~~: ~~For~~ checked vs unchecked exception, ~~see Checked vs Unchecked Exceptions~~		Pengecualian bawaan adalah pengecualian yang tersedia di perpustakaan Java. Pengecualian ini cocok untuk menjelaskan situasi kesalahan tertentu.

			* Checked Exception: Checked exceptions are called compile-time exceptions because these exceptions are checked at compile-time by the compiler.

			Pengecualian yang diperiksa disebut pengecualian waktu kompilasi karena pengecualian ini diperiksa pada waktu kompilasi oleh kompiler.

			* Unchecked Exception: The unchecked exceptions are just opposite to the checked exceptions. The compiler will not check these exceptions at compile time. In simple words, if a program throws an unchecked exception, and even if we didn’t handle or declare it, the program would not give a compilation error.

			Pengecualian yang tidak dicentang berlawanan dengan pengecualian yang dicentang. Kompiler tidak akan memeriksa pengecualian ini pada waktu kompilasi. Dengan kata sederhana, jika sebuah program mengeluarkan pengecualian yang tidak dicentang, dan bahkan jika kita tidak menangani atau mendeklarasikannya, program tersebut tidak akan memberikan kesalahan kompilasi.


			===User-Defined Exception:===

	~~===User-Defined Exceptions:===~~
	Sometimes, the built-in exceptions in Java are not able to describe a certain situation. In such cases, users can also create exceptions which are called ‘user-defined Exceptions’.		Sometimes, the built-in exceptions in Java are not able to describe a certain situation. In such cases, users can also create exceptions which are called ‘user-defined Exceptions’.

			Terkadang, pengecualian bawaan di Java tidak dapat menggambarkan situasi tertentu. Dalam kasus seperti itu, pengguna juga dapat membuat pengecualian yang disebut 'Pengecualian yang ditentukan pengguna'.

	The advantages of Exception Handling in Java are as follows:		The advantages of Exception Handling in Java are as follows:

			Kelebihan Exception Handling di Java adalah sebagai berikut:

	* Provision to Complete Program Execution		* Provision to Complete Program Execution
	* Easy Identification of Program Code and Error-Handling Code		* Easy Identification of Program Code and Error-Handling Code
Line 57:		Line 70:
	* Meaningful Error Reporting		* Meaningful Error Reporting
	* Identifying Error Types		* Identifying Error Types

			* Ketentuan untuk Menyelesaikan Eksekusi Program
			* Identifikasi Kode Program dan Kode Penanganan Kesalahan yang Mudah
			* Penyebaran Kesalahan
			* Pelaporan Kesalahan yang Berarti
			* Mengidentifikasi Jenis Kesalahan

	==How Does JVM handle an Exception?==		==How Does JVM handle an Exception?==

Unknown user at 03:22, 10 May 2022

2022-05-10T03:22:56Z

← Older revision		Revision as of 03:22, 10 May 2022
Line 1:		Line 1:
	'''Exception Handling''' in Java ~~is one of the effective means to handle the~~ runtime ~~errors so that the regular flow of the application can be preserved~~. Java Exception Handling ~~is a mechanism to handle~~ runtime ~~errors such as~~ ClassNotFoundException, IOException, SQLException, RemoteException, ~~etc~~.		'''Exception Handling''' di Java adalah salah satu cara yang efektif untuk menangani kesalahan runtime sehingga aliran reguler aplikasi dapat dipertahankan. Java Exception Handling adalah mekanisme untuk menangani kesalahan runtime seperti ClassNotFoundException, IOException, SQLException, RemoteException, dll.

	'''Exception''' ~~is an unwanted or unexpected event~~, ~~which occurs during the execution of a~~ program ~~i.e at run time~~, ~~that disrupts the~~ normal ~~flow of the program’s instructions~~. ~~Exceptions can be caught and handled by the~~ program. ~~When an~~ exception ~~occurs within a~~ method, ~~it creates an~~ object. ~~This object is called the~~ exception object. ~~It contains information about the~~ exception ~~such as the name and description of the~~ exception ~~and the state of the~~ program ~~when the~~ exception ~~occurred~~.		'''Exception''' adalah peristiwa yang tidak diinginkan atau tidak terduga, yang terjadi selama eksekusi program yaitu pada saat dijalankan, yang mengganggu aliran normal instruksi program. Exception dapat ditangkap dan ditangani oleh program. Ketika exception terjadi dalam suatu method, ini akan menciptakan sebuah object. Object ini disebut exception object. Ini berisi informasi tentang exception seperti nama dan deskripsi exception dan status program saat exception terjadi.

	~~Major reasons why an~~ exception ~~Occurs~~		Penyebab utama mengapa sebuah exception terjadi
	* ~~Invalid~~ user ~~input~~		* Input user yang salah/invalid
	* Device ~~failure~~		* Kegagalan Device
	* Loss of network ~~connection~~		* Loss dari sambungan network
	* ~~Physical limitations~~ (out of disk memory)		* Keterbatasan fisik (out of disk memory)
	* ~~Code errors~~		* Error code
	* ~~Opening an unavailable~~ file		* Membuka file yang tidak ada

	'''Errors''' ~~represent irrecoverable conditions such as~~ Java virtual machine (JVM) ~~running out of memory~~, memory leaks, stack overflow errors, library incompatibility, infinite recursion, ~~etc~~. ~~Errors are usually beyond the control of the~~ programmer ~~and we should not try to handle errors~~.		'''Errors''' mewakili kondisi yang tidak dapat dipulihkan seperti Java virtual machine (JVM) kehabisan memori, memory leaks, stack overflow errors, library incompatibility, infinite recursion, dll. Kesalahan biasanya di luar kendali programmer dan kita sebaiknya tidak mencoba menangani error.

	~~Let us discuss the most important part which is the differences between~~ Error ~~and~~ Exception ~~that is as follows~~:		Mari kita bahas bagian terpenting yang merupakan perbedaan antara Error dan Exception yaitu sebagai berikut:
	* '''Error:''' ~~An Error indicates a serious problem that a reasonable application should not try to catch~~.		* '''Error:''' Kesalahan menunjukkan masalah serius yang sebaiknya tidak ditangkap oleh aplikasi yang baik.
	* '''Exception:''' ~~Exception indicates conditions that a reasonable application might try to catch~~.		* '''Exception:''' menunjukkan kondisi yang mungkin dapat / dicoba ditangkap oleh aplikasi yang wajar.

	==Exception ~~Hierarchy~~==
	~~All~~ exception ~~and~~ error ~~types are subclasses of~~ class Throwable, ~~which is the~~ base class ~~of the hierarchy~~. ~~One branch is headed by~~ Exception. ~~This class is used for exceptional conditions that user programs should catch~~. NullPointerException ~~is an example of such an exception~~. ~~Another branch~~, Error ~~is used by the~~ Java run-time system(JVM) ~~to indicate errors having to do with the~~ run-time environment ~~itself~~(JRE). StackOverflowError ~~is an example of such an~~ error.		==Hirarki Exception==

			Semua jenis exception dan error adalah subclass dari class Throwable, yang merupakan base class dari sebuah hirarki. Satu cabang adalah Exception. Class ini digunakan untuk kondisi luar biasa yang harus ditangkap oleh program. NullPointerException adalah contoh pengecualian semacam itu. Cabang lain, Error digunakan oleh Java run-time system (JVM) untuk menunjukkan error yang berkaitan dengan run-time environment itu sendiri (JRE). StackOverflowError adalah contoh error tersebut.

	[[File:Exception-in-java1.png\|center\|300px\|thumb\|Exception Hierarchy in Java]]		[[File:Exception-in-java1.png\|center\|300px\|thumb\|Exception Hierarchy in Java]]

	==~~Types of Exceptions~~==		==Tipe Exception==

	Java ~~defines several types of exceptions that relate to its various~~ class ~~libraries~~. Java ~~also allows users to define their own exceptions~~.		Java mendefinisikan beberapa jenis exception yang berhubungan dengan berbagai class library. Java juga memungkinkan pengguna untuk menentukan exception mereka sendiri.

	[[File:Type-of-Exception-in-Java.jpg\|center\|300px\|thumb\|Types of Exceptions]]		[[File:Type-of-Exception-in-Java.jpg\|center\|300px\|thumb\|Types of Exceptions]]


	~~Exceptions can be Categorized in two ways~~:		Exception dapat di kategorikan dalam dua hal:

	* Built-in ~~Exceptions~~		* Built-in Exception
	** Checked Exception		** Checked Exception
	** Unchecked Exception		** Unchecked Exception
	* User-Defined ~~Exceptions~~		* User-Defined Exception

	Let us discuss the above-defined listed exception that is as follows:		Let us discuss the above-defined listed exception that is as follows:

Unknown user at 03:08, 10 May 2022

2022-05-10T03:08:44Z

← Older revision		Revision as of 03:08, 10 May 2022
Line 14:		Line 14:

	Let us discuss the most important part which is the differences between Error and Exception that is as follows:		Let us discuss the most important part which is the differences between Error and Exception that is as follows:
	* Error: An Error indicates a serious problem that a reasonable application should not try to catch.		* '''Error:''' An Error indicates a serious problem that a reasonable application should not try to catch.
	* Exception: Exception indicates conditions that a reasonable application might try to catch.		* '''Exception:''' Exception indicates conditions that a reasonable application might try to catch.

	==Exception Hierarchy==		==Exception Hierarchy==
Line 39:		Line 39:

	===Built-in Exceptions:===		===Built-in Exceptions:===

	Built-in exceptions are the exceptions that are available in Java libraries. These exceptions are suitable to explain certain error situations.		Built-in exceptions are the exceptions that are available in Java libraries. These exceptions are suitable to explain certain error situations.
	* Checked Exceptions: Checked exceptions are called compile-time exceptions because these exceptions are checked at compile-time by the compiler.		* Checked Exceptions: Checked exceptions are called compile-time exceptions because these exceptions are checked at compile-time by the compiler.
	* Unchecked Exceptions: The unchecked exceptions are just opposite to the checked exceptions. The compiler will not check these exceptions at compile time. In simple words, if a program throws an unchecked exception, and even if we didn’t handle or declare it, the program would not give a compilation error.		* Unchecked Exceptions: The unchecked exceptions are just opposite to the checked exceptions. The compiler will not check these exceptions at compile time. In simple words, if a program throws an unchecked exception, and even if we didn’t handle or declare it, the program would not give a compilation error.

	Note: For checked vs unchecked exception, see Checked vs Unchecked Exceptions		Note: For checked vs unchecked exception, see Checked vs Unchecked Exceptions

Line 48:		Line 50:

	The advantages of Exception Handling in Java are as follows:		The advantages of Exception Handling in Java are as follows:
			* Provision to Complete Program Execution
			* Easy Identification of Program Code and Error-Handling Code
			* Propagation of Errors
			* Meaningful Error Reporting
			* Identifying Error Types

			==How Does JVM handle an Exception?==

	~~Provision to Complete Program Execution~~
	~~Easy Identification of Program Code and Error-Handling Code~~
	~~Propagation of Errors~~
	~~Meaningful Error Reporting~~
	~~Identifying Error Types~~
	~~How Does JVM handle an Exception?~~
	Default Exception Handling: Whenever inside a method, if an exception has occurred, the method creates an Object known as an Exception Object and hands it off to the run-time system(JVM). The exception object contains the name and description of the exception and the current state of the program where the exception has occurred. Creating the Exception Object and handling it in the run-time system is called throwing an Exception. There might be a list of the methods that had been called to get to the method where an exception occurred. This ordered list of the methods is called Call Stack. Now the following procedure will happen.		Default Exception Handling: Whenever inside a method, if an exception has occurred, the method creates an Object known as an Exception Object and hands it off to the run-time system(JVM). The exception object contains the name and description of the exception and the current state of the program where the exception has occurred. Creating the Exception Object and handling it in the run-time system is called throwing an Exception. There might be a list of the methods that had been called to get to the method where an exception occurred. This ordered list of the methods is called Call Stack. Now the following procedure will happen.

	The run-time system searches the call stack to find the method that contains a block of code that can handle the occurred exception. The block of the code is called an Exception handler.		* The run-time system searches the call stack to find the method that contains a block of code that can handle the occurred exception. The block of the code is called an Exception handler.
	The run-time system starts searching from the method in which the exception occurred, and proceeds through the call stack in the reverse order in which methods were called.		* The run-time system starts searching from the method in which the exception occurred, and proceeds through the call stack in the reverse order in which methods were called.
	If it finds an appropriate handler then it passes the occurred exception to it. An appropriate handler means the type of the exception object thrown matches the type of the exception object it can handle.		* If it finds an appropriate handler then it passes the occurred exception to it. An appropriate handler means the type of the exception object thrown matches the type of the exception object it can handle.
	If the run-time system searches all the methods on the call stack and couldn’t have found the appropriate handler then the run-time system handover the Exception Object to the default exception handler, which is part of the run-time system. This handler prints the exception information in the following format and terminates the program abnormally.		* If the run-time system searches all the methods on the call stack and couldn’t have found the appropriate handler then the run-time system handover the Exception Object to the default exception handler, which is part of the run-time system. This handler prints the exception information in the following format and terminates the program abnormally.
	Exception in thread "xxx" Name of Exception : Description
	... ...... .. // Call Stack		Exception in thread "xxx" Name of Exception : Description
			... ...... .. // Call Stack

	Look at the below diagram to understand the flow of the call stack.		Look at the below diagram to understand the flow of the call stack.

	call stack		[[File:Call-stack.png\|center\|300px\|thumb\|call stack]]


	Illustration:		Illustration:
Line 92:		Line 98:
	Let us see an example that illustrates how a run-time system searches for appropriate exception handling code on the call stack.		Let us see an example that illustrates how a run-time system searches for appropriate exception handling code on the call stack.

	~~Example~~:		Contoh:


	// Java Program to Demonstrate Exception is Thrown		// Java Program to Demonstrate Exception is Thrown

Unknown user at 22:34, 9 May 2022

2022-05-09T22:34:28Z

← Older revision		Revision as of 22:34, 9 May 2022
Line 22:		Line 22:
	[[File:Exception-in-java1.png\|center\|300px\|thumb\|Exception Hierarchy in Java]]		[[File:Exception-in-java1.png\|center\|300px\|thumb\|Exception Hierarchy in Java]]

	Types of Exceptions		==Types of Exceptions==

	Java defines several types of exceptions that relate to its various class libraries. Java also allows users to define their own exceptions.		Java defines several types of exceptions that relate to its various class libraries. Java also allows users to define their own exceptions.

	Types of Exceptions		[[File:Type-of-Exception-in-Java.jpg\|center\|300px\|thumb\|Types of Exceptions]]


	Exceptions can be Categorized in two ways:		Exceptions can be Categorized in two ways:

	Built-in Exceptions		* Built-in Exceptions
	Checked Exception		** Checked Exception
	Unchecked Exception		** Unchecked Exception
	User-Defined Exceptions		* User-Defined Exceptions

	Let us discuss the above-defined listed exception that is as follows:		Let us discuss the above-defined listed exception that is as follows:

	A. Built-in Exceptions:		===Built-in Exceptions:===
	Built-in exceptions are the exceptions that are available in Java libraries. These exceptions are suitable to explain certain error situations.		Built-in exceptions are the exceptions that are available in Java libraries. These exceptions are suitable to explain certain error situations.
			* Checked Exceptions: Checked exceptions are called compile-time exceptions because these exceptions are checked at compile-time by the compiler.
	Checked Exceptions: Checked exceptions are called compile-time exceptions because these exceptions are checked at compile-time by the compiler.		* Unchecked Exceptions: The unchecked exceptions are just opposite to the checked exceptions. The compiler will not check these exceptions at compile time. In simple words, if a program throws an unchecked exception, and even if we didn’t handle or declare it, the program would not give a compilation error.

	Unchecked Exceptions: The unchecked exceptions are just opposite to the checked exceptions. The compiler will not check these exceptions at compile time. In simple words, if a program throws an unchecked exception, and even if we didn’t handle or declare it, the program would not give a compilation error.
	Note: For checked vs unchecked exception, see Checked vs Unchecked Exceptions		Note: For checked vs unchecked exception, see Checked vs Unchecked Exceptions

	B. User-Defined Exceptions:		===User-Defined Exceptions:===
	Sometimes, the built-in exceptions in Java are not able to describe a certain situation. In such cases, users can also create exceptions which are called ‘user-defined Exceptions’.		Sometimes, the built-in exceptions in Java are not able to describe a certain situation. In such cases, users can also create exceptions which are called ‘user-defined Exceptions’.