1. Every Session Bean class should be public and concrete as EJB container creates instances of the Bean
2. EJB Container must create instances of Bean so constructor should not be private or protected
3. Though Need of finalize method is less, but if needed cleanup code should be placed in ejbRemove or ejbPassivate method.

 Related Tips

• Accessing a Secure Enterprise Bean From a Java Client or Through Java Web Start Technology
• Accessing an EJB from an applet
• Accessing bean components from JSP
• Accessing EJB from a servlet within the same container
• An example of a simple JSP page
• Automated code generation
• Automated update of EJB deployment descriptor
• Bean with Indexed Properties and Accessing Indexed values through JSP Bean tags