Bryan, I would say that the expected behaviour is ambiguous. The spec would need to be clarified.
Bryan Pendleton wrote: > 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". > > > > =========================================================================== 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".
