Understanding EJB Support in an OOM

PowerDesigner simplifies the development process by transparently handling EJB concepts and enforcing the EJB programming contract through the following levels of support:

Automatic initialization: occurs whenever a class or interface is attached to an EJB
Synchronization: occurs between interfaces and classes already attached to a component

For more information on the linked method, see Understanding EJB synchronization.
Model checks: the Check Model feature validates a given model and complements synchronization by offering auto-fixes. You can check your model at any time using the Check Model feature from the Tools menu.

For more information on the Check Model feature, see Checking an OOM.
Template based code generation: supports the programming contract defined in the specification and allows you to customize generated code. EJB specific templates can be found in the Java object language in the Profile/Component/Templates category, available from Language > Edit Current Object Language .

For more information, see sections Responsibilities of the Bean Provider, in all chapters related to Bean component contract in the Enterprise JavaBeans 2.0 specification from Sun Microsystems, Inc.

At a higher level, PowerDesigner supports different approaches to assist you in the component development process including:

Forward engineering: from an OOM to a PDM. It provides the ability to create and reverse EJBs in a OOM, generate the corresponding PDM, O/R Mapping and generate code
Reverse engineering: from a PDM (database) to an OOM. It provides the ability to create and reverse tables in a PDM, generate corresponding classes, create EJB from given classes and generate code

Understanding EJB Initialization
When creating an EJB, the role of the initialization process is to initialize classes and interfaces with respect to the EJB programming contract. It instantiates the classes and interfaces together with their methods.
Understanding EJB Synchronization
Synchronization maintains the coherence of the whole model whenever a change is applied. It occurs progressively as the following model items are modified:
Understanding EJB Code Generation
The code generation mechanism is only described for Entity beans CMP in this section since the code generated is handled and stored in the Container. With Entity beans BMP, session beans and message-driven beans, the code generated is highly dependent on the bean developer's input, it would thus not be possible to introduce each possible configuration here.

Parent topic: Enterprise Java Beans (EJBs) V2