Develop enterprise beans

For more information on how to design a J2EE application and the enterprise beans that it needs, see these topics:

• To learn the extentions to the EJB specifications included in WAS, see WebSphere extensions to the Enterprise JavaBeans specification.
• Before developing entity beans with container-managed persistence (CMP), read Concurrency control.
• For best practices, see Best practices for developing enterprise beans

There are two basic approaches to selecting tools for developing enterprise beans:

• Use one of the available integrated development environments (IDEs). IDE tools automatically generate significant parts of the enterprise bean code and contain integrated tools for packaging and testing enterprise beans. IBM WebSphere Studio Application Developer is the recommended IDE.
• If you have decided to develop enterprise beans without an IDE, you need at least an ASCII text editor. You can also use a Java development tool that does not support enterprise bean development. You can then use tools available in the Java Software Development Kit (SDK) and in this WAS to assemble, test, and deploy the beans.

These steps primarily support the second approach, development without an IDE.

1. If necessary, migrate any pre-existing code to the required version of the Enterprise JavaBeans specification. For more information, see Migrate enterprise bean code to the supported specification.

2. Write and compile the components of the enterprise bean.

   • At a minimum, an EJB 1.1 session bean requires a bean class, a home interface, and a remote interface. An EJB 1.1 entity bean requires a bean class, a primary-key class, a home interface, and a remote interface.

   • At a minimum, an EJB 2.0 session bean requires a bean class, a home or local home interface, and a remote or local interface. An EJB 2.0 entity bean requires a bean class, a primary-key class, a remote home or local home interface, and a remote or local interface. The types of interfaces go together: If you implement a local interface, define a local home interface as well.

   • Available only through EJB 2.0, a message-driven bean requires only a bean class.

   • For each entity bean, complete work to handle persistence operations.
     Create a database schema for the entity bean's persistent data.

     • For entity beans with container-managed persistence(CMP), store the bean's persistent data in one of the supported databases. The Application Assembly Tool automatically generates SQL code for creating database tables for CMP entity beans. If your CMP beans require complex database mappings, it is recommended that you use the IBM WebSphere Studio Application Developer product to generate code for the database tables.

     • For entity beans with bean-managed persistence (BMP), you can create the database and database table by using the database tools or use an existing database and database table.

     For more information on creating databases and database tables, consult your database documentation.

   • CMP entity beans for EJB 2.0 only Define finder queries with EJB Query Language (EJB QL). With EJB QL, you define finders in terms of CMP fields and container-managed relationships, as follows:

     • Public finders are visible in the bean's home interface. Implemented in the bean class, they return only remote interfaces and collection types.

     • Private finders, expressed as SELECT statements, are used only within the bean class. They can return both local and remote interfaces, dependent values, other CMP field types, and collection types.

   • (CMP entity beans for EJB 1.1 only: an IBM extension) Create a finder helper interface for each CMP entity bean that contains specialized finder methods (other than the findByPrimaryKey method).
     The following logic is required for each finder method (other than the findByPrimaryKey method) contained in the home interface of an entity bean with CMP:

     • The logic must be defined in a public interface named Name BeanFinderHelper , where Name is the name of the enterprise bean (for example, AccountBeanFinderHelper).
     • The logic must be contained in a String constant named findMethodName WhereClause , where findMethodName is the name of the finder method. The String constant can contain zero or more question marks (?) that are replaced from left to right with the value of the finder method's arguments when that method is called.