EJB Information

Use the following information to enter data in each field on the tab:

Field | Description
--- | ---
EJB Name | Enter the bean's base name. This is specified in the `<ejb-name>` element of the `ejb-jar.xml` file and is for display only.
Primary Key Class | Enter the primary key. This is specified in the `<prim-key-class>` element of the `ejb-jar.xml` file and is for display only.

Unknown Primary Key Class

Check this option if you choose not to specify the primary key class or the primary key fields for an entity bean with container managed persistence.

For example, select this field if the entity bean does not have a natural primary key or you want the deployer to select the primary key fields at deployment time. For more information, see "Unknown Primary Key Class Support".

Local Interface | Enter the local interface. This is specified in the `<local>` element of the `ejb-jar.xml` file and is for display only.
Local Home Interface | Enter the local home interface. This is specified in the `<local-home>` element of the `ejb-jar.xml` file and is for display only.
Remote Interface | Enter the remote interface. This is specified in the `<remote>` element of the `ejb-jar.xml` file and is for display only.
Remote Home Interface | Enter the remote interface. This is specified in the `<home>` element of the `ejb-jar.xml` file and is for display only.
Change Deferral | Use these options to specify how TopLink updates the database for this EJB descriptor.
Defer All Changes | Specify not to send changes to the database until the JTA transaction is committed. This is the default TopLink behavior. This is the most efficient option that results in the least amount of data source interaction.

Defer Updates Only

Specify to send changes to the database immediately after any insert or delete operation, but do not send changes to the data source for update operations until the JTA transaction is committed.

Select this option for backwards compatibility with some EJB containers, such as OC4J. For more information, see "Nondeferred Changes").

Use this option with caution as it will require the data source transaction and locks to be held longer and may cause referential integrity issues.

Defer None | Specify to send all changes to the database immediately. This is the least efficient option that generates the greatest amount of data source interaction. Select this option for backwards compatibility with some EJB containers, such as OC4J. For more information, see "Nondeferred Changes").

Insert New Objects After

Specify to send new object insert changes to the database after bean life cycle method `ejbCreate` (default) or `ejbPostCreate`. This is only relevant when not deferring changes (see "Configuring Change Policy").

If non-null foreign key constraints cannot be satisfied when the insert is performed after `ejbCreate`, you may consider configuring TopLink CMP to do the insert after `ejbPostCreate`, if supported by your container. For more information, see "Creating a New Entity Bean and ejbCreate / ejbPostCreate Methods".

See Also

  Configuring a Descriptor With EJB Information