Jothi Shankar Kumar wrote:How come you are annotating TransactionAttributes for a POJO like BaseClass??
Jothi Shankar Kumar wrote:But the original poster did not mention anything about it??
A transaction management type cannot be speciﬁed for EJB 3.0 entities. EJB 3.0 entities execute within
the transactional context of the caller.
Raf Szczypiorski wrote:But, there is never any interface specified, not by the implements keyword, or in the @Stateless annotation, so is this a valid bean at all? If it is not, there are no transaction attributes used anyways, as the container will not instantiate this bean... Correct me if I am wrong.
The session bean class may have superclasses and/or superinterfaces. If the session bean has
superclasses, the business methods, lifecycle callback interceptor methods, the timeout call-
back method, the methods of the optional SessionSynchronization interface, the
Init or ejbCreate<METHOD> methods, the Remove methods, and the methods of the
SessionBean interface, may be deﬁned in the session bean class, or in any of its super-
classes. A session bean class must not have a superclass that is itself a session bean class.
EJB3 in action page 78, Section 3.1.3, 4th bullet
A session bean class can subclass another session bean or any other POJO.
A session bean class must not have a superclass that is itself a session bean class.