A Specific Coding Practice Discussed Java Questions Exception Your Questions on Java Example

\| Interview Questions on Java \|	\| Coding Tips on Java \|	\| Your Questions on Java \|	\| EJB \|	\| Servlet and JSP \|	\| Hibernate Tutorial \|	\| Spring Tutorials \|	\| Java Design Patterns \|	\| J2EE Design Patterns \|	\| Apache ANT \|
\| Apache DBCP \|	\| Struts Struts 2 Example Tutorial \|	\| Apache Beehive JdbcControl \|	\| Apache Log4j \|	\| Apache Axis \|	\| Open Source Project Ideas \|	\| Web Technology \|	\| J2EE Technology \|	\| Java News \|	\| Spring Hibernate Example \|
\| JavaScript Tips \|

Struts Tutorials: Struts2 Tag CheckBoxList
, Checkbox, Iterator, IF Struts2 Tag Library Example Struts2 Tiles Example Struts2 Tiles I18N Example Struts2 Questions Struts Tiles I18N Example Struts Eclipse MVC Struts2 Tags Struts2 Example and Tutorial Struts MVC Struts2 Validation
Hibernate Tutorials: Hibernate Case Study Class Hierarchy Persist Example Using Hibernate Interceptor Hibernate Questions with Answer Hibernate Many-to-Many Mapping Example Hibernate one-to-many Mapping Example Hibernate and ORM tools Spring Hibernate Example Hibernate SessionFactory Example Hibernate Mapping Class Hierarchy Hibernate Questions Hibernate SessionFactory Questions Spring Hibernate Example: Spring Hibernate Case Study

Tags/Keywords : A-Specific-Coding-Practice-Discussed - Java-Questions-Exception - Your-Questions-on-Java Example
Author : Amit
Date (Year/Month/Date): 2010-06-13 Question : What will happen if there is an exception is raised within the try block only to be caught in the catch block, but another exception is raised within the finally block, then which exception will be thrown back to the caller program, the one that is raised initially within the try block, or the one that is raised in finally block afterwards?? Think and please do share your thought on this question, by using following comments writing section: In order to explain this question and try out myself I wrote an example as follows: Test.java

public class Test
{
        public Test() throws Exception{
                try{
                        String[] str = new String[2];
                        str[4]="test";
                }catch(Exception ne){
                        System.out.println("test");
                        throw ne;
                }finally{
                        String st = null;
                        st.toString();
                }
        }
        public static void main(String[] args) 
        {
                try{
                new Test();
                }catch(Exception e){
                        e.printStackTrace();
                }
        }
}

In the above code, the section marked as green bold, raised an java.lang.ArrayIndexOutOfBoundsException. The section/line of code marked as brown bold, raises an exception as java.lang.NullPointerException. As the bold red color code above throws the java.lang.ArrayIndexOutOfBoundsException , there could be quite reasonable point just to justify why the exception raised within the finally block only is thrown back to the main method, and this is the answer. This is a very interesting point as this could be a valid point to be noted while doing code review and/ or code walk through, as this type of code can be easily eat up any exception thrown within the try block and representing an unpredictable behavior by sending out some other exception, and this may result in hiding the original cause of the exception. Please do share your view point on this very topic, by writing your comments below.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners This web site's Terms of Use and Disclaimer : This web site provides some of the information about various technologies, example code, tips, tutorials etc. Like any printed materials, content of these pages may become out of date over a period of time. Therefore all visitor/users of this web site are requested/advised to refer to the originating parties/sources for the latest changes and happenings for detailed information. This information is not intended to be a substitute for the original reference provided by the originating parties/sources. These examples with source code or without source code, have not been thoroughly tested under all conditions. Interview-questions-tips-forum.net therefore, cannot guarantee or imply reliability of these example source code or programs. By accessing and using this website in any ways, including, without limitation, browsing the website pages, using any information, using any content and/or downloading any materials, you agree to and are bound by the terms of use described in this page and Usage Terms and Conditions. If you do not agree to all of the terms and conditions contained in the terms of use described in this page and Usage Terms and Conditions, do not use this website in any manner. If you are using the website on behalf of your employer, you represent that you are authorized to accept these Terms of Use on your employer's behalf. All Trademarks are property of their respective owner. Appropriate measure is being taken for providing accurate and up-to-date information but like any printed materials, these blog(s)/contents may eventually be outdated one day, so if you are using any of these information, please refer original content/documentation from respective sources. And under no circumstances shall the Author of these contents and/or this web site be liable for any loss, damage, expense incurred or suffered which is claimed to have occurred because of usage of the contents of this web site. If you have any questions/queries/feedback/suggestions then please write to this web site owner at contact.