Instead of putting data access code in entity bean itself it might be better to put code in another class and calling it from Entity Bean due to following reasons.

1. In case underlying data model or data access mechanism changes then it might be very impractical to change source code in entity bean.
2. DAO is better option for writing such code and calls these classes directly into entity bean.

 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