Skip to main content

Get current executing method name in Java




//Get method name using Java.lang.Class.getEnclosingMethod()

    public static void getMethodNameUsingClassInstance() {
        String methodNameUsingClassInstance =
            new Object() {}.getClass().getEnclosingMethod().getName();
        System.out.println("Current Method Execution Name Using Class Instance - " +
            methodNameUsingClassInstance);
    }


//Get method name using StackTraceElement.getMethodName()

    public static void getMethodNameUsingStackTraceElement() {
        StackTraceElement stackTraceElements[] = (new Throwable()).getStackTrace();
        System.out.println("Current Method Execution Name Using StackTraceElement - " +
            stackTraceElements[0].getMethodName());
    }


//Get method name using Thread.currentThread().getStackTrace()

    public static void getMethodNameUsingCurrentThread() {
        System.out.println("Current Method Execution Name using Current Thread - " +
            Thread.currentThread().getStackTrace()[1].getMethodName());
    }

Comments

Post a Comment

Popular posts from this blog

JUnit – Run unit test in an Sequence / Order

In JUnit, we can use @FixMethodOrder(MethodSorters.xxx) to run the test methods in a sequence or order.

import org.junit.FixMethodOrder;import org.junit.Test;import org.junit.runners.MethodSorters;importstatic org.hamcrest.CoreMatchers.is;importstatic org.junit.Assert.assertThat;//Sorts by method name@FixMethodOrder(MethodSorters.NAME_ASCENDING)publicclassExecutionOrderTest{@TestpublicvoidtestB(){assertThat(1+1,is(2));}@Testpublicvoidtest1(){assertThat(1+1,is(2));}@TestpublicvoidtestA
Post a Comment
Read more

Create Runnable Jar - Eclipse Options

When exporting to a Runnable Jar, there are three options in eclipse Helios. Extract required libraries into JARPackage required libraries into JARCopy required libraries into sub folder next to JAR. What are differences : Extract required libraries into JAR - Extracts the actual .class files from the libraries your app uses and puts those .class files inside the runnable JAR. So, the runnable JAR will not only contain the .class files of your application, but also the .class files of all the libraries your application uses. Package required libraries into JAR - Puts the actual JAR files of the libraries into your runnable JAR. Normally, a JAR file within a JAR file cannot be loaded by the JVM. But Eclipse adds special classes to the runnable JAR to make this possible. Copy required libraries into sub folder next to JAR - Keeps the library JARs completely separate from the runnable JAR, so the runnable JAR will only contain the .class files of your application. Option #2 is convenient be…
Post a Comment
Read more