Loading...- Problems with Earlier versions of EJB
- Handling of unnecessary exceptions
- Required knowledge of JNDI
- Several unnecessary callbacks
- Limited use of Object oriented concepts
- Container involved complex development and maintenance
- Cannot be tested outside a container. Teing inside was a nightmare
- Deployment developer maintenance complex and error prone
- EJB 3.0
- Uses metadata annotations to ask container to generate much of the boiler plate code
-
@Author("Debu Panda")
@Bean
public class MySessionBean - Uses Plain old Java Objects and Interfaces
- Developer only needs to implement one
interface (Entity, Session or Message) in javax.ejb.package. - Use stateless, stateful, message driven or Enity to annotate class
- No need to implement EJBObject or EJBLocalObject
- Can either supply bussiness interfaces to EJB or have them auto generated during deployment
- Read more at http://www.theserverside.com/articles/article.tss?l=SimplifyingEJB3&News07_05_05-click
Read more...
