Entity Bean CMP Properties dialog box

This is a feature of JBuilder Enterprise.

The Entity Bean CMP Properties dialog box lets you set and modify the container-managed persistence (CMP) properties for the bean.

To display the Entity Bean CMP dialog,

  1. Click the top of the entity bean representation in the EJB Designer.
  2. Click the Properties button.

Note: The properties displayed in the dialog box are relevant only to the Borland Enterprise Server.

Property Description
ejb.maxBeansInCache Specifies the maximum number of beans in the Option A cache (see ejb.transactionCommitMode which follows). If the cache exceeds this limit, entities will be moved to the ready pool by calling ejbPassivate(). The default setting is 1000..
ejb.ejb.cacheCreate Attempts to cache entity bean creates until the transaction commits. The default value is is true. Set this property to false for applications that must know right away if a create will succeed.
ejb.maxBeansInPool Specifies the maximum number of beans in the ready pool. If the ready pool exceeds this limit, entities are removed from the container. The default setting is 1000.
ejb.transactionCommitMode Indicates the disposition of an entity bean with respect to a transaction. The values are:

A or Exclusive -- This entity has exclusive access to the particular table in the database. Thus, the state of the bean at the end of the last committed transaction can be assumed to be the state of the bean at the beginning of the next transaction. The beans are cached across transactions.

B or Shared --This entity shares access to the particular table in the database. However, for performance reasons, a particular bean remains associated with a particular primary key between transactions to avoid extraneous calls to ejbActivate() and ejbPassivate() between transactions. The bean stays in the active pool. This setting is the default.

C or None -- This entity shares access to the particular table in the database. A particular bean does not remain associated with a particular primary key between transactions, but goes back to the ready pool after every transaction. This is generally not a useful setting.

For more information about these properties, see the Borland Enterprise Server documentation.