Skip Headers

# CMP

Previous

Next

When using CMP with any of the application servers for which TopLink provides CMP integration (see "Application Server Support"), indirection does not affect enterprise beans' passivation and activation within the same JVM.

However, when you serialize an indirection-enabled enterprise bean from one JVM to another (for example, from server to client), untriggered indirection objects appear as null values at deserialization time. You must code your client to handle this scenario and to distinguish between an attribute that is `null` because it was null in the data source, and an attribute that is null because of an untriggered indireciton object.

Note:

When using EJB 3.0 persistence with OC4J, indirection does not affect enterprise beans' passivation and activation, nor does it affect detachment from and attachment to a persistence manager within the same JVM.

However, when you serialize an indirection-enabled EJB 3.0 beans from one JVM to another, (for example, from server to client), untriggered indirection objects appear as null values at deserialization time. To avoid this, configure your client to use the same Java agent that OC4J uses (see "Configuring ValueHolder Indirection With EJB 3.0 on OC4J").