Extending EJB Exception

[Nikhil Jain]

Is it possible to extend an exception from EJBException & still be an ApplicationException

For ex

@ApplicationExcetion
public class MyException extends EJBException{
}

Technical this should be possible as EJBException extends RuntimeException.

But in one of the mock exams the above concept seems to incorrect

[Benoît de Chateauvieux]

Hi Anu Tilwalli,

I read in the specs (14.1.1):

An application exception may be a subclass (direct or indirect) of java.lang.Exception (i.e., a �checked exception�), or an application exception class may be defined as a subclass of the java.lang.RuntimeException (an �unchecked exception�). An application exception may not be a subclass of the java.rmi.RemoteException. The java.rmi.RemoteException and its subclasses are reserved for system exceptions.

So, I think that a subclass of EJBException annotated as ApplicationExcetion will be an application exception.

But I've just tested it with my JBoss.
I have created this Bean:

@Stateless
public class EjbExceptionTest implements EjbExceptionTestRemote {
public void test() throws MyException {
throw new MyException();
}

@PreDestroy
public void preDestroy() {
System.out.println("Destroyed");
}
}

And the exception:

@ApplicationException
public class MyException extends EJBException {}

When it extends Exception, I don't see the destroy in the console.
--> It's an application exception

When it extends EJBException appears a "[STDOUT] Destroyed".
--> It's a system exception.


So, the theory says that you can extends EJBException but the reality shows that it's not true.

Beno�t