Re: Can a RuntimeException ever be an Application Exception?

[Ashwani Kalra]

Title: RE: Can a RuntimeException ever be an Application Exception?

-----Original Message-----
From: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED]]On Behalf Of Sourabh Ahuja
Sent: Wednesday, October 03, 2001 9:56 AM
To: [EMAIL PROTECTED]
Subject: Re: Can a RuntimeException ever be an Application Exception?

HI,

RuntimeException extends from super class Exception. When you say throws Exception then RuntimeException is also included in it. 

THis is not his point. He is asking why that is happening.

 

Cheers,
Sourabh

-----Original Message-----
From: Bryan Pendleton [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 03, 2001 3:50 AM
To: [EMAIL PROTECTED]
Subject: Can a RuntimeException ever be an Application Exception?

Hello,

I am having a bit of trouble understanding the rules
in chapter 12 of the EJB 1.1 spec.

Specifically, I declared a method on my Remote Interface,
and caused that method to throw a RuntimeException, and
my app server appeared to treat my RuntimeException as
a System Exception.

THEN, I added the line:

       throws Exception

to my method on my Remote Interface and my Bean Class.
This was the only change I made to my test setup.

When I added "throws Exception" to my method, my app server's
behavior changed, and it treated the RuntimeException
as an Application Exception.

So my question is: if I state "throws Exception" on my
Remote Interface method, does that make *every* subclass
of Exception into an Application Exception, including
RuntimeException? Or is RuntimeException always supposed
to be special-cased?

thanks,

bryan

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".