Is it acceptible to declare a common superclass exception of the bean implementation's declared exceptions on the remote (or home) interfaces, rather than listing explicitly all of the individual declared exceptions?
i.e. If A and B extend C, and C extends Exception, Remote Interface: void methodA() throws C; Implementation: void methodA() throws A, B Is this mentioned in the spec anywhere? I couldn't find it. JBoss gives a load of warnings with this but deploys it OK. ============================================================================== This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. All information is the view of the individual and not necessarily the company. If you are not the intended recipient you are hereby notified that any dissemination, distribution, or copying of this communication and its attachments is strictly prohibited. If you have received this email in error please notify: [EMAIL PROTECTED] ============================================================================== =========================================================================== 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".
