Overview | Package | Class | Use | Tree | Deprecated | Index | Help
PREV NEXT | FRAMES NO FRAMES

## Uses of Class
org.jboss.ejb.plugins.EntitySynchronizationInterceptor

Packages that use EntitySynchronizationInterceptor
org.jboss.ejb.plugins | Package description goes here.

Uses of EntitySynchronizationInterceptor in org.jboss.ejb.plugins

Subclasses of EntitySynchronizationInterceptor in org.jboss.ejb.plugins
`class` | `EntityMultiInstanceSynchronizationInterceptor` Deprecated. this interceptor was used with Instance Per Transaction containers which do not use a global cache but cache instances per transaction and always passivate instances at commit time (commit option C). The only difference from the EntityInstanceInterceptor is that it uses specific instance Synchronization implementation which always passivates the instance at commit time which is equivalent to commit option C in standard container. Now, the differences between IPT and standard container are: org.jboss.ejb.plugins.PerTxEntityInstanceCache as the cache implementation; NoLock as the locking policy; empty container-cache-conf element. (alex@jboss.org) The role of this interceptor is to synchronize the state of the cache with the underlying storage. It does this with the ejbLoad and ejbStore semantics of the EJB specification. In the presence of a transaction this is triggered by transaction demarcation. It registers a callback with the underlying transaction monitor through the JTA interfaces. If there is no transaction the policy is to store state upon returning from invocation. The synchronization polices A,B,C of the specification are taken care of here. WARNING: critical code, get approval from senior developers before changing.

Overview | Package | Class | Use | Tree | Deprecated | Index | Help
PREV NEXT | FRAMES NO FRAMES

Copyright © 2002 JBoss Group, LLC. All Rights Reserved.