Which of the following statements are true about EJB transaction?
A. create and remove methods in session beans do not have transaction attributes.
With EJB 3.0, I don't see any create method for the beans. We use dependency injection or lookup to create it.
And also, we don't remove the bean. We use @Remove to annotate a method to indicate what the container should implement when the bean is removed.
I think a bean cannot be removed by the application developer.
This is an ancient question from the time of EJB2.x....
From the specs:
4.3.5 The Optional SessionBean Interface This specification requires that the ejbRemove, ejbActivate, and ejbPassivate methods of the SessionBean interface, and the ejbCreate method of a stateless session bean be treated as PreDestroy, PostActivate, PrePassivate and PostConstruct life cycle callback interceptor methods, respectively. If the session bean implements the SessionBean interface, the PreDestroy annotation can only be applied to the ejbRemove method; the PostActivate annotation can only be applied to the ejbActivate method; the PrePassivate annotation can only be applied to the ejbPassivate method.
Try 100 things. 2 will work out, but you will never know in advance which 2. This tiny ad might be one:
ScroogeXHTML - small and flexible RTF to HTML converter library