Skip Headers

# Unsupported weblogic-ejb-jar.xml File Tags

Previous

Next

The `weblogic-ejb-jar.xml` file includes several tags that TopLink either does not support or does not require:

- `concurrency-strategy`: This tag specifies how WebLogic manages concurrent users for a given bean. Because TopLink manages concurrent access internally, it does not require this tag.

  For more information about the TopLink concurrency strategy, see "Configuring Locking Policy".

- `db-is-shared`: Because TopLink does not make any assumptions about the exclusivity of database access, TopLink does not require this tag. TopLink addresses multiuser access issues through various locking and refreshing policies.

- `delay-updates-until-end-of-tx`: TopLink always delays updates until the end of a transaction, and does not require this tag.

- `finders-load-bean`: TopLink always loads the bean upon execution of the finder, and does not require this tag.

- `pool`: TopLink does not use a pooling strategy for entity beans. This avoids object-identity problems that can occur due to pooling.

- `lifecycle`: This element manages beans that follow a pooling strategy. Because TopLink does not use a pooling strategy, TopLink ignores this tag.

- `is-modified-method-name`: TopLink does not require a bean developer-defined method to detect changes in the object state.

- `isolation-level`: Because isolation level settings for the cache or database transactions are specified in the TopLink project, TopLink ignores this tag.

- `cache`: Because you define TopLink cache properties in TopLink Workbench, this tag is unnecessary.