best java training institute bangalore Marathahalli

An exception (or exceptional event) is a problem that arises during the execution of a program. When an Exception occurs the normal flow of the program is disrupted and the program/Application terminates abnormally, which is not recommended, therefore, these exceptions are to be handled.rnAn exception can occur for many different reasons. Following are some scenarios where an exception occurs. • A user has entered an invalid data. • A file that needs to be opened cannot be found. • A network connection has been lost in the middle of communications or the JVM has run out of memory.rnSome of these exceptions are caused by user error, others by programmer error, and others by physical resources that have failed in some manner.rnBased on these, we have three categories of Exceptions. You need to understand them to know how exception handling works in Java programming. • Checked exceptions − A checked exception is an exception that occurs at the compile time, these are also called as compile time exceptions. These exceptions cannot simply be ignored at the time of compilation, the programmer should take care of (handle) these exceptions. rn1. Use a single, system-wide exception classrnInstead of creating separate classes for each exception type, create just one. And make it extend RuntimeException. This will reduce your class count and remove the need to declare exceptions you aren’t going to handle anyway.rnI know what you’re thinking: How will I tell exceptions apart if they’re all the same type? And how will I track type-specific properties? Read on!rn2. Use enums for error codesrnMost of us were trained to put the cause of an exception into its message. This is fine when reviewing log files (ugh), but it does have drawbacks:rn1. Messages can’t be translated (unless you’re Google).rn2. Messages can’t be easily mapped to user-friendly text.rn3. Messages can’t be inspected programmatically.rnPutting info in the message also leaves the wording up to each developer, which can lead to different phrases for the same failure. rnA better approach is to use enums to indicate the exception’s type. Create one enum for each category of errors (payments, authentication, etc.). Make the enums implement an ErrorCode interface and reference it as a field in the exception.rnWhen throwing exceptions, simply pass in the appropriate enum. rnNow when you need to test for a specific case, just compare the exception’s code with the enum.rn3. Add error numbers to enumsrnIn some cases a numerical error code can be associated with each exception. HTTP responses for example. For those cases, add a getNumber method to the ErrorCode interface and implement it in each enum. learn java tutorial rnNumbering can be globally unique across all enums or each enum can be responsible for numbering itself. You can even use the implicit ordinal() method or load numbers from a file or database.rn4. Add dynamic fields to your exceptionsrnGood exception handling means also recording relevant data, not just the stack trace. Doing this will save you big time when trying to diagnose and reproduce errors. And customers won’t have to tell you what they were doing when your app stopped working (you’ll already know and hopefully have fixed it).rnThe easiest way to do this is to add a java.util.Map field to the exception. The new field’s job will be to hold all your exception related data by name. You’ll also need to add a generic setter method following the fluent interface pattern. rn5. Prevent unnecessary nestingrnLong, redundant stack traces help no one. Even worse, they waste your time and resources. When rethrowing exceptions, call a static wrap method instead of the exception’s constructor . The wrap method will be responsible for deciding when to nest exceptions and when to just return the original instance.rn6. Use a central logger with a web dashboardrnConsider this tip a bonus. Depending on your situation, getting access to production logs could be quite a hassle. A hassle that may involve multiple go-betweens (since many developers don’t have access to production environments).rnThings get worse if you’re in a multi-server environment. Finding the right server — or determining that the problem only affects one server — can be quite a headache.rnMy recommendations are:rn1. Aggregate your logs in a single place, preferably a database.rn2. Make that database accessible from a web browser.rnThere are many ways to do this and may products to choose from: log collectors, remote loggers, JMX agents, system monitoring software, etc. You can even build it yourself. The main thing is that you do it soon. Once you have it, you’ll be able to: • Troubleshoot issues in a matter of seconds. • Have a URL for each exception that you can bookmark or email around. • Enable your support staff to determine root causes without involving you. • Prevent testers from creating multiple tickets for the same bug. Plus they’ll have an exception URL to put in their ticket. • Save money for your business. • Keep your weekend and reputation intact.