Deprecated List (JBoss Server API) - JBoss 4.0.1 sp1 server API Documentation 英文版文档

Overview

Package

Class

Use

Tree

Deprecated

Index

Help

PREV NEXT

FRAMES NO FRAMES

Deprecated API

Deprecated Classes
org.jboss.ejb.plugins.EntityMultiInstanceInterceptor 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). This interceptor used org.jboss.ejb.TxEntityMap to compensate the absence of a real per transaction cache implementation. 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 instance interceptors role is to acquire a context representing the target object from the cache.
org.jboss.ejb.plugins.EntityMultiInstanceSynchronizationInterceptor 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.
org.jboss.proxy.compiler.ProxyAssembler Use `ProxyCompiler` or Jakarta BCEL instead.
org.jboss.ejb.TxEntityMap this class was useful only for Instance Per Transaction containers and was used to check whether the instance is associated with the tx. There is org.jboss.ejb.plugins.PerTxEntityInstanceCache which is a per tx implementation of org.jboss.ejb.EntityCache which should be used with IPT containers. (alex@jboss.org) This class provides a way to find out what entities of a certain type that are contained in within a transaction. It is attached to a specific instance of a container. This class interfaces with the static GlobalTxEntityMap. EntitySynchronizationInterceptor registers tx/entity pairs through this class. Used in EntitySynchronizationInterceptor.

Deprecated Methods

org.jboss.ejb.EnterpriseContext.EJBContextImpl.getCallerIdentity()


org.jboss.ejb.EnterpriseContext.EJBContextImpl.getEnvironment()


org.jboss.ejb.EnterpriseContext.EJBContextImpl.isCallerInRole(Identity)

Deprecated Constructors

org.jboss.verifier.factory.DefaultEventFactory()
Use the other constructor with a specific Message Bundle for your own verification logic!