<<MessageProcessor>> classes

The UML to EJB transformation transforms a class with the <<MessageProcessor>> stereotype into a message-driven bean with a bean name that is equal to the name of the source UML class and with default data. The transformation generates the following Java class:

The transformation generates the class in the package folder that is generated for the parent package of the source UML class. If you create a UML model without packages, the transformation creates a default package named ejbs.

The transformation generates the bean class file in the source tree of the target EJB project.

The transformation adds data that defines the message-driven bean to the deployment descriptor (ejb-jar.xml).

Generalization relationships

If the source UML class for the message-driven bean has a generalization relationship (such as an extends relationship) with another UML class with the <<MessageProcessor>> stereotype, the message-driven bean that the class represents becomes the EJB superclass  for the entity bean to be generated.

Realization relationships

Ignored.

Attributes

The transformation transforms attributes on the source UML class into Java properties in the bean class. For more information about how the attributes are transformed, see the UML to Java transformation documentation. If the type of the attribute is of another enterprise bean, the EJB transformation does not generate a field and association for the session bean. Instead, the transformation writes a message to the log file that states that the source attribute will not be transformed.

Operations

The transformation transforms operations on the source UML class into typical Java methods, just as though the message-driven bean were a Java class.

Inner classes

Ignored.

Inner interfaces

Ignored.

Terms of use | Feedback
(C) Copyright IBM Corporation 2004.
All Rights Reserved.