jboss_3_0.dtd

《J2EE企业级应用开发》一书的配套源代码

  The metricsEnabled attributes is used to indicate if the interceptor
  should only be included when the org.jboss.ejb.ContainerFactory metricsEnabled
  flag is set to true. The allowed values are true and false with false being the
  default if metricsEnabled is not explicitly given.
-->
<!ATTLIST interceptor metricsEnabled  (true | false )  "false">

<!--
  The instance-pool element gives the class name of the instance pool
  jboss must use for in this configuration. This class must implement
  the org.jboss.ejb.InstancePool interface. The defaults are:
  - org.jboss.ejb.plugins.EntityInstancePool for entity beans
  - org.jboss.ejb.plugins.StatelessSessionInstancePool for stateless
  session beans.
  - no pool is used for stateful session beans
  
  Used in: container-configuration
-->
<!ELEMENT instance-pool (#PCDATA)>

<!--
  The instance-cache element gives the class name of the instance cache
  jboss must use for in this configuration. This class must implement
  the org.jboss.ejb.InstanceCache interface. The defaults are:
  - org.jboss.ejb.plugins.NoPassivationEntityInstanceCache for entity beans
  - org.jboss.ejb.plugins.NoPassivationStatefulSessionInstanceCache for
  stateful session beans.
  - no cache is used for stateless session beans
  
  Used in: container-configuration
-->
<!ELEMENT instance-cache (#PCDATA)>

<!--
  The persistence-manager element gives the class name of the persistence
  manager / persistence store jboss must use for in this configuration.
  This class must implement:
  - org.jboss.ejb.EntityPersistenceStore for CMP Entity Beans (default is
  org.jboss.ejb.plugins.jaws.JAWSPersistenceManager)
  - org.jboss.ejb.EntityPersistenceManager for BMP entity beans (default
  is org.jboss.ejb.plugins.BMPPersistenceManager)
  - org.jboss.ejb.StatefulSessionPersistenceManager for stateless session
  beans.
  - no persistence-manager is used for stateless session beans
  
  Used in: container-configuration
-->
<!ELEMENT persistence-manager (#PCDATA)>

<!--
  The locking-policy element gives the class name of the EJB lock
  implementation JBoss must use for in this configuration. This class must
  implement  the org.jboss.ejb.BeanLock interface. The default is
  org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.
  
  Used in: container-configuration
-->
<!ELEMENT locking-policy (#PCDATA)>

<!--
  The transaction-manager element gives the class name of the transaction
  manager jboss must use for in this configuration. This class must implement
  the javax.transaction.TransactionManager interface. The default is
  org.jboss.tm.TxManager.
  
  Used in: container-configuration
-->
<!ELEMENT transaction-manager (#PCDATA)>

<!--
  The web-class-loader element gives the class name of the web classloader
  jboss must use for in this configuration. This class must be a subclass
  of org.jboss.web.WebClassLoader. The default is org.jboss.web.WebClassLoader.
  
  Used in: container-configuration
-->
<!ELEMENT web-class-loader (#PCDATA)>

<!--
  The container-invoker-conf element holds configuration data for the
  container invoker.
  jboss does not read directly the subtree for this element: instead,
  it is passed to the container invoker instance (if it implements
  org.jboss.metadata.XmlLoadable) for it to load its parameters.
  
  The Optimized tag described here only relates to the default container
  invokers, ProxyFactory, ProxyFactoryHA and JMSContainerInvoker.
  
  Used in: container-configuration
-->
<!ELEMENT container-invoker-conf (JMSProviderAdapterJNDI? , ServerSessionPoolFactoryJNDI? , MaximumSize? , MaxMessages? , MDBConfig?)>

<!--
  Used in: container-invoker-conf for JMSContainerInvoker
-->
<!ELEMENT JMSProviderAdapterJNDI (#PCDATA)>

<!--
  Used in: container-invoker-conf for JMSContainerInvoker
-->
<!ELEMENT ServerSessionPoolFactoryJNDI (#PCDATA)>

<!--
  Used in: container-invoker-conf for JMSContainerInvoker
-->
<!ELEMENT MaxMessages (#PCDATA)>

<!--
  Used in: container-invoker-conf for JMSContainerInvoker
-->
<!ELEMENT MDBConfig (ReconnectIntervalSec , DLQConfig?)>

<!--
  Used in: MDBConfig
-->
<!ELEMENT ReconnectIntervalSec (#PCDATA)>

<!--
  Used in: MDBConfig
-->
<!ELEMENT DLQConfig (DestinationQueue , MaxTimesRedelivered , TimeToLive)>

<!--
  Used in: DLQConfig
-->
<!ELEMENT DestinationQueue (#PCDATA)>

<!--
  Used in: DLQConfig
-->
<!ELEMENT MaxTimesRedelivered (#PCDATA)>

<!--
  Used in: DLQConfig
-->
<!ELEMENT TimeToLive (#PCDATA)>

<!--
  The container-cache-conf element holds dynamic configuration data
  for the instance cache.
  jboss does not read directly the subtree for this element: instead,
  it is passed to the instance cache instance (if it implements
  org.jboss.metadata.XmlLoadable) for it to load its parameters.
  
  Used in: container-configuration
-->
<!ELEMENT container-cache-conf (cache-policy? , cache-policy-conf?)>

<!--
  The implementation class for the cache policy, which controls
  when instances will be passivated, etc.
  
  Used in: container-cache-conf
-->
<!ELEMENT cache-policy (#PCDATA)>

<!--
  The configuration settings for the selected cache policy.  This
  is currently only valid for the LRU cache.
  When the cache is the LRU one for the stateful container, the elements
  remover-period and max-bean-life specifies the period of the remover
  task that removes stateful beans (that normally have been passivated)
  that have age greater than the specified max-bean-life element.

  Used in: container-cache-conf (when cache-policy is the LRU cache)
-->
<!ELEMENT cache-policy-conf (min-capacity , max-capacity , remover-period? , max-bean-life? , overager-period , max-bean-age , resizer-period , max-cache-miss-period , min-cache-miss-period , cache-load-factor)>

<!--
  The minimum capacity of this cache
-->
<!ELEMENT min-capacity (#PCDATA)>

<!--
  The maximum capacity of this cache
-->
<!ELEMENT max-capacity (#PCDATA)>

<!--
  The period of the overager's runs
-->
<!ELEMENT overager-period (#PCDATA)>

<!--
  The period of the remover's runs
-->
<!ELEMENT remover-period (#PCDATA)>

<!--
  The max-bean-life specifies the period of the remover
  task that removes stateful beans (that normally have been passivated)
  that have age greater than the specified max-bean-life element.
-->
<!ELEMENT max-bean-life (#PCDATA)>

<!--
  The period of the resizer's runs
-->
<!ELEMENT resizer-period (#PCDATA)>

<!--
  The age after which a bean is automatically passivated
-->
<!ELEMENT max-bean-age (#PCDATA)>

<!--
  Shrink cache capacity if there is a cache miss every or more
  this member's value
-->
<!ELEMENT max-cache-miss-period (#PCDATA)>

<!--
  Enlarge cache capacity if there is a cache miss every or less
  this member's value
-->
<!ELEMENT min-cache-miss-period (#PCDATA)>

<!--
  The resizer will always try to keep the cache capacity so that
  the cache is this member's value loaded of cached objects
-->
<!ELEMENT cache-load-factor (#PCDATA)>

<!--
  The container-pool-conf element holds configuration data for the
  instance pool.
  jboss does not read directly the subtree for this element: instead,
  it is passed to the instance pool instance (if it implements
  org.jboss.metadata.XmlLoadable) for it to load its parameters.
  
  The default instance pools, EntityInstancePool and
  StatelessSessionInstancePool, both accept the following configuration.
  
  Used in: container-configuration
-->
<!ELEMENT container-pool-conf (MaximumSize , feeder-policy , feeder-policy-conf)>

<!--
  The capacity of the Pool.  The pool feeder will feed the pool with new
  instances, the pool size being limited by this value.  For pools where
  reclaim is possible, the pool will also be feed when the instance is
  free to be reused.
  This is not an hard limit, if instances are needed when the pool is at
  its MaximumSize, new instances will be created following the demand.
  
  Used in: container-pool-conf
-->
<!ELEMENT MaximumSize (#PCDATA)>

<!--
  This element is only valid if the instance pool is a subclass of
  AbstractInstancePool.
  
  The feeder-policy element gives the Class that implements InstancePoolFeeder
  and is responsible to feed the pool with new instances of bean.
  If not present, no thread are started and the pool will have a size of 1.
  
  TimedInstancePoolFeeder is the first implementation available.
  
  Used in: container-pool-conf for AbstractInstancePool subclasses
-->
<!ELEMENT feeder-policy (#PCDATA)>

<!--
  This element describes properties that the InstancePoolFeeder implementation
  will read to configure itself (XmlLoadable).
  
  Note: the 3 attributes are hardcoded here for TimedInstancePoolFeeder.
  
  Used in: container-pool-conf for InstancePoolFeeder implementations
-->
<!ELEMENT feeder-policy-conf (increment , period)>

<!--
  The pool feeder will feed the pool with this number of new instances at
  a regular period.
  
  Used in: feeder-policy-conf
-->
<!ELEMENT increment (#PCDATA)>

<!--
  The interval of time (in milliseconds) the pool feeder look if the pool
  has come to its maximum size (capacity) and if not, will feed it with
  a particular number of new instances (increment).
  
  Used in: feeder-policy-conf
-->
<!ELEMENT period (#PCDATA)>

<!--
  This option is only used for entity container configurations.
  
  The commit-option element tells the container which option to use for transactions.
  Its value must be A, B C, or D.
  
  - option A: the entiry instance has exclusive access to the database. The instance
  stays ready after a transaction.
  - option B: the entity instance does not have exclusive access to the database.
  The state is loaded before the next transaction.
  - option C: same as B, except the container does not keep the instance after commit:
  a passivate is immediately performed after the commit.
  
  - option D: a lazy update. default is every 30 secs.
               can be updated with <optiond-refresh-rate>
  
  See ejb1.1 specification for details (p118).
  
  Used in: container-configuration
-->
<!ELEMENT commit-option (#PCDATA)>

<!--
  This element is used to specify the refresh rate of commit option d
-->
<!ELEMENT optiond-refresh-rate (#PCDATA)>