Tham khảo tài liệu 'building java enterprise applications volume i: architecture phần 3', công nghệ thông tin, kỹ thuật lập trình phục vụ nhu cầu học tập, nghiên cứu và làm việc hiệu quả | Building Java Enterprise Applications Volume I Architecture Example 4-1. The EntityAdapter Helper Class package import import public class EntityAdapter implements EntityBean protected EntityContext entityContext public void ejbActivate public void ejbPassivate public void ejbLoad public void ejbStore public void ejbRemove public void setEntityContext EntityContext entityContext entityContext public void unsetEntityContext entityContext null public EntityContext getEntityContext return entityContext If you have any implementation classes that need to provide special behavior for a callback you can override the adapter class overriding still allows you to leave out any callbacks that are not implemented keeping code clean. In addition I ve introduced the package in this class. All the entity beans created for the example can be put into this base package in a subpackage using the bean s name for example office or user with the EntityAdapter class in the util subpackage of the same structure. So entity and session beans end up prefaced with or . This is the same naming scheme you ll see in Sun s PetStore and most other enterprise applications. In addition to package naming I follow standard practices for the actual bean class names. This entails using the actual name of the data object as the name of an entity bean s remote interface. In the case of an office the interface name simply becomes Office. The home interface has Home appended to it resulting in OfficeHome and the bean implementation itself gets the word Bean added to it resulting in OfficeBean. And with this last detail covered you re ready to move to the bean code for the office classes. 59 Building Java Enterprise Applications Volume I Architecture The Remote Interface Once the naming has been determined it is simple to code the .
