It's the intent of the EJB specification although it's not stated explicitly. It's something we'll
need to make clearer in EJB 3.1. The issue is that context plays a large role in processing
annotations. @ApplicationException is an ejb-jar level construct, so placing it outside the
ejb-jar is a problem, in the same way that putting @Stateless on a class outside an ejb-jar
would be an issue.
--ken
[Message sent by forum member 'ksak' (ksak)]
http://forums.java.net/jive/thread.jspa?messageID=216796