Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How to throw an Exception when your method signature doesn't allow to throw Exception?

Tags:

I have a method like this:

public void getSomething(){ ... } 

I want to throw an Exception inside getSomething(). The compiler will not allow me to do that because my method doesn't allow Exception to be thrown in there. But I need to throw a subclass of Exception for my testing (I can't throw Unchecked Exception). This is clearly a hack but I need it for my testing. I tried EasyMock but it doesn't allow me to do that either. Any ideas how to do that?

Thanks, Sean Nguyen

like image 345
Sean Nguyen Avatar asked Aug 13 '12 21:08

Sean Nguyen


People also ask

How do you throw an exception without adding in signature?

When an exception is cached in a catch block, you can re-throw it using the throw keyword (which is used to throw the exception objects). If you re-throw the exception, just like in the case of throws clause this exception now, will be generated at in the method that calls the current one.

Is throws exception part of method signature?

Common checked exceptions are IOException and SQLException. Checked exceptions must be listed in the throws part of the method signature if you don't handle them yourself.

How do I add an exception to a signature?

To use a method that declares an exception in its signature, you MUST either: provide exception handling codes in a " try-catch " or " try-catch-finally " construct, or. not handling the exception in the current method, but declare the exception to be thrown up the call stack for the next higher-level method to handle.

How do you throw an exception from a method?

Throwing an exception is as simple as using the "throw" statement. You then specify the Exception object you wish to throw. Every Exception includes a message which is a human-readable error description. It can often be related to problems with user input, server, backend, etc.


2 Answers

Method 1:

This post by Alexey Ragozin describes how to use a generics trick to throw an undeclared checked exception. From that post:

public class AnyThrow {      public static void throwUnchecked(Throwable e) {         AnyThrow.<RuntimeException>throwAny(e);     }      @SuppressWarnings("unchecked")     private static <E extends Throwable> void throwAny(Throwable e) throws E {         throw (E)e;     } } 

The trick relies on throwUnchecked "lying" to the compiler that the type E is RuntimeException with its call to throwAny. Since throwAny is declared as throws E, the compiler thinks that particular call can just throw RuntimeException. Of course, the trick is made possible by throwAny arbitrarily declaring E and blindly casting to it, allowing the caller to decide what its argument is cast to - terrible design when coding sanely. At runtime, E is erased and has no meaning.

As you noted, doing such a thing is a huge hack and you should document its use very well.


Method 2:

You can also use sun.misc.Unsafe to this end. First you must implement a method that uses reflection to return that class's instance:

private static Unsafe getUnsafe() {     try {         Field theUnsafeField = Unsafe.class.getDeclaredField("theUnsafe");         theUnsafeField.setAccessible(true);         return (Unsafe)theUnsafeField.get(null);     }     catch (NoSuchFieldException e) {         throw new RuntimeException(e);     }     catch (IllegalAccessException e) {         throw new RuntimeException(e);     } } 

This is necessary as calling Unsafe.getUnsafe() will typically throw a SecurityException. Once you have the instance of Unsafe you can put its terrifying capabilities to use:

Unsafe unsafe = getUnsafe(); unsafe.throwException(new Exception()); 

Credit goes to this answer on the post https://stackoverflow.com/questions/5574241/interesting-uses-of-sun-misc-unsafe. I thought I'd mention this for completeness but it's probably better just to use the trick above instead of allowing Unsafe into your code.


Method 3:

In the comments of the linked answer about using Unsafe, @bestsss points out a much simpler trick using the deprecated method Thread.stop(Throwable):

Thread.currentThread().stop(new Exception()); 

In this case you would use @SuppressWarnings("deprecation") and once again document very fiercely. Again, I prefer the first trick for its (relative) cleanliness.

like image 153
Paul Bellora Avatar answered Oct 08 '22 01:10

Paul Bellora


Java has two kinds of exceptions, checked and unchecked. You must declare checked exceptions, but you don't have to declare unchecked exceptions.

RuntimeException is the basic unchecked exception, so you can throw that without declaring it.

public void getSomething(){    throw new RuntimeException("I don't have to be declared in the method header!"); } 

As a side note, you probably don't want to throw a raw RuntimeException, but subclass it to something more specific to your needs. Any subclass of RuntimeException will be unchecked as well.

like image 33
Oleksi Avatar answered Oct 08 '22 03:10

Oleksi