User: mnf999
Date: 01/06/15 15:58:06
Added: doco_files jaws.dtd jboss.dtd
Log:
Adding the new files
Revision Changes Path
1.1 newsite/doco_files/jaws.dtd
Index: jaws.dtd
===================================================================
<!--
Architecture of jaws.xml
<jaws>
<datasource />
<type-mapping />
<type-mappings>
<type-mapping>
<name />
<mapping>
<java-type />
<jdbc-type />
<sql-type />
</mapping>
</type-mapping>
</type-mappings>
<default-entity>
<create-table />
<remove-table />
<tuned-updates />
<read-only />
<time-out />
</default-entity>
<enterprise-beans>
<entity>
<ejb-name />
<table-name />
<create-table />
<remove-table />
<tuned-updates />
<read-only />
<time-out />
<cmp-field>
<field-name />
<column-name />
<sql-type />
<jdbc-type />
</cmp-field>
<finder>
<name />
<query />
<order />
</finder>
</entity>
</enterprise-beans>
</jaws>
-->
<!--
The jaws element is the root element of the jaws.xml file. The main
xml file is ejb-jar.xml, and jaws contains additional information to
customize jaws.
In jaws.xml you can:
- specify which datasource to use for your application, and the type
mappings between java objects and jdbc/sql types.
- set general options in default-entity
- set the options for your beans in enterprise-beans.
All the information you provide here is optional. Most of will already
be set in standardjaws.xml. This file is included in the jboss
distribution and will set most defaults for you. It will always be
processed before your jaws.xml file.
-->
<!ELEMENT jaws (datasource?, type-mapping?, type-mappings?,
default-entity?, enterprise-beans?)>
<!--
The datasource element is used to tell jaws the jndi name of the
datasource to use for your application. You can only use one
datasource for all the cmp entities of your application, if you want
to use more you will have to split it into 2 applications.
The datasource jndi names are defined in jboss.conf. They are
printed by jboss on start-up. For example, if you see ("out of the
box" installation)
[DataSource] Connection pool for
jdbc:idb:../conf/instantdb.properties bound to InstantDB
[DataSource] Connection pool for
jdbc:HypersonicSQL:hsql://localhost bound to Hypersonic
then you can use
<datasource>InstantDB</datasource>
or
<datasource>Hypersonic</datasource>
Used in: jaws
-->
<!ELEMENT datasource (#PCDATA)>
<!--
The type-mapping element tells jaws which type-mapping to use with
the specified datasource. Its value must correspond to one of the
type mappings of the <type-mappings> element of either jaws.xml or
standardjaws.xml.
The currently available type-mappings in standardjaws.xml are:
- Hypersonic SQL
- InstantDB
- Oracle
- PointBase
- PostgreSQL
- SOLID
- mySQL
- DB2/400
- MS SQLSERVER
See: type-mappings
Used in: jaws
-->
<!ELEMENT type-mapping (#PCDATA)>
<!--
The type-mappings element is used to define type mappings that you
can later use in the type-mapping element. This element is mainly
used in standardjaws.xml, where we define type mappings for the most
common databases.
However, you may want to add a type-mapping for your particular
database: in this case, do it here, and please consider sharing it
with the jboss community: post your type mapping on the jaws mailing
list (mailto:[EMAIL PROTECTED]) so that we include it with the
defaults in our next distribution.
See: type-mapping
Used in: jaws
-->
<!ELEMENT type-mappings (type-mapping*)>
<!--
The type-mapping element is used to define a set of mappings
between java types (objects) and jdbc/sql types.
The name of the mapping can then be used in the type-mapping
element for your application.
There is one mapping element for each java type.
See: mapping
Used in: type-mappings
-->
<!ELEMENT type-mapping (name, mapping*)>
<!--
The name element gives the name of the type-mapping. This name
can later be used to specify the type-mapping to use for your
application.
Used in: type-mapping
-->
<!ELEMENT name (#PCDATA)>
<!--
The mapping element represent a mapping between a java type, a
jdbc type and a sql type.
When jaws stores the value of a cmp field, it examines the type
(java class) of this value and tries to find a mapping for this
class in the type-mapping for the application. If jaws cannot
find one, it uses the generic java.lang.Object mapping.
The sql type is only used when jaws creates the table for your
bean.
The jdbc type is used to store and retrieve values, using the
jdbc API (PreparedStatement.setObject, ResultSet.getObject)
Used in: type-mapping
-->
<!--
The java-type element gives the java class being mapped.
Example: <java-type>java.lang.Boolean</java-type>
Used in: mapping
-->
<!ELEMENT java-type (#PCDATA)>
<!--
The jdbc-type element gives the jdbc type to map the java-type
to. The jdbc-type is used for storing/retrieving data. Its
value must be one of the types defined in java.sql.Types.
Example: <jdbc-type>BIT</jdbc-type>
Used in: mapping
-->
<!ELEMENT jdbc-type (#PCDATA)>
<!--
The sql-type element gives the sql type to map the java-type
to. The sql type will only be used to create the table for
your bean. Its value must be a sql type understandable by
your database.
Example: <sql-type>CHAR(5)</sql-type>
Used in: mapping
-->
<!ELEMENT sql-type (#PCDATA)>
<!--
The default-entity element is used to set general options that will
be used for all of your beans. You can specify:
- whether to create a table for your bean on deployment.
- whether to remove (drop) the table on undeployment.
- whether to use tuned updates for your beans.
- whether your beans are read-only
- the timeout four the read only state.
The default-entity elements are set in standardjaws.xml (see the
children elements for defaults). However you can override the
standards here.
You can specify all these options, plus other ones, on a per bean
basis, in the entity elements in the enterprise-beans section.
See: entity
Used in: jaws
-->
<!ELEMENT default-entity (create-table?, remove-table?,
tuned-updates?, read-only?, time-out?)>
<!--
The create-table element tells jaws to create a table for your
bean on deployment. If the table already exists, jaws will tell it
to you, and proceed.
Its value must be one of the following:
- <create-table>true</create-table>
- <create-table>false</create-table>
The create-table element is set to true in the default-entity
element in standardjaws.xml.
Used in: default-entity, entity
-->
<!ELEMENT create-table (#PCDATA)>
<!--
The remove-table element tells jaws to remove (drop) the table
of your bean on deployment.
Its value must be one of the following:
- <remove-table>true</remove-table>
- <remove-table>false</remove-table>
The remove-table element is set to false in the default-entity
element in standardjaws.xml.
Note that if you change the cmp-fields of your bean, you will
have to drop the table and create a new one when you redeploy.
You can either drop the table manually or set remove-table to true
Used in: default-entity, entity
-->
<!ELEMENT remove-table (#PCDATA)>
<!--
The tuned-update element tells jaws whether or not to use tuned
updates for your beans.
If you use tuned updates, jaws will only update in the database
the fields that have actually changed. If you don't, jaws will
perform an UPDATE statement with all fields values set.
The value of the tuned-updates element must be one of the
following:
- <tuned-updates>true</tuned-updates>
- <tuned-updates>false</tuned-updates>
The tuned-updates element is set to true in the default-entity
element in standardjaws.xml.
Used in: default-entity, entity
-->
<!ELEMENT tuned-updates (#PCDATA)>
<!--
The read-only element tells if JAWS must allow client applications
to update values / create entities. Its value must be true or
false. Default is false (updates allowed)
Used in: default-entity, entity
-->
<!ELEMENT read-only (#PCDATA)>
<!--
The time-out element is only used if read-only is set to true. In
this case, JAWS will not load the state of the bean from the
database more than once every <time-out> milliseconds.
Used in: default-entity, entity
-->
<!ELEMENT time-out (#PCDATA)>
<!--
The enterprise-beans holds the information to customize jaws for
each of your entities.
Used in: jaws
-->
<!ELEMENT enterprise-beans (entity*)>
<!--
The entity element if used to customize jaws for this particular
entity bean.
This element must correspond to an entity element in the
enterprise-beans section of your ejb-jar.xml file. The ejb-jar.xml
and the jaws.xml views of this bean must have the same ejb-name.
The information contained here will be processed after the one in
default-entity. Thus, the values set here will override the
defaults.
You can set here:
- all the fields of the default-entity (see corresponding
elements in the default-entity section)
- the table name to use for this bean
- additional data about your cmp fields
- user-defined finders.
See: default-entity
Used in: enterprise-beans
-->
<!ELEMENT entity (ejb-name, table-name?, create-table?,
remove-table?, tuned-updates?, read-only?, time-out?, cmp-field*,
finder*)>
<!--
The ejb-name element gives the name of the entity bean being
customized. It must correspond to the ejb-name of a jaws
managed cmp entity in ejb-jar.xml.
Used in: entity
-->
<!ELEMENT ejb-name (#PCDATA)>
<!--
The table-name element gives the name of the table to use for
storing instances of this entity.
If you don't specify it, jaws will use the ejb-name of the
entity (with '.' changed into '_' to avoid db-specific issues)
The principal use of this element is to be able to use an
already existing database.
Used in: entity
-->
<!ELEMENT table-name (#PCDATA)>
<!--
The cmp-field element tells jaws additional information on how
to map this cmp-field in the database.
This cmp-field must correspond to a cmp-field with the same
field-name in the corresponding entity section in ejb-jar.xml.
You can specify the column name to use, and override the
jdbc-type / sql-type for this field.
Used in: entity
-->
<!ELEMENT cmp-field (field-name, column-name?, jdbc-type?,
sql-type?)>
<!--
The field-name element gives the name of this cmp-field. Its
value must match the field-name of a cmp-field in ejb-jar.xml.
Used in: cmp-field
-->
<!ELEMENT field-name (#PCDATA)>
<!--
The column-name element gives the name of the column to use
in the table for this cmp-field.
If you don't set it, jaws will use the name of the field.
The principal use of this element is to be able to use an
already existing database.
Used in: cmp-field
-->
<!ELEMENT column-name (#PCDATA)>
<!--
The finder element allows you to declare a customized finder for
your bean.
The finder is defined in the home interface of your bean. Jaws
will then generate SQL SELECT queries everytime you call this
finder.
You must specify the name of the finder, the WHERE part and the
ORDER BY part of the SELECT query.
Used in: entity
-->
<!ELEMENT finder (name, query, order)>
<!--
The name element gives the name of the finder, as it appears
in the home interface.
Used in: finder
-->
<!ELEMENT name (#PCDATA)>
<!--
The query element gives the WHERE part of the query to execute
for this finder. Don't insert the WHERE keyword.
You can use {0}, {1}... to refer to the arguments of the
finder method.
Example:
<query>teacherName = {0} and studentCount > {1}</query>
Used in: finder
-->
<!ELEMENT query (#PCDATA)>
<!--
The order element gives the ORDER BY part of the query to
execute for this finder. Don't insert the ORDER BY words. You
may insert such words as ASC, DESC...
Example:
<order>studentCount DESC, teacherName</order>
Used in: finder
-->
<!ELEMENT order (#PCDATA)>
1.1 newsite/doco_files/jboss.dtd
Index: jboss.dtd
===================================================================
<?xml version='1.0' encoding='UTF-8' ?>
<!--
Overview of the architecture of jboss.xml
<jboss>
<secure />
<enterprise-beans>
<entity>
<ejb-name />
<jndi-name />
<resource-ref>
<res-ref-name />
<resource-name />
</resource-ref>
</entity>
<session>
<ejb-name />
<jndi-name />
<resource-ref>
<res-ref-name />
<resource-name />
</resource-ref>
</session>
</enterprise-beans>
<resource-managers>
<resource-manager>
<res-name />
<res-jndi-name />
</resource-manager>
<resource-manager>
<res-name />
<res-url />
</resource-manager>
</resource-managers>
<container-configurations>
<container-configuration>
<container-name />
<container-invoker />
<container-interceptors />
<instance-pool />
<instance-cache />
<persistence-manager />
<transaction-manager />
<container-invoker-conf />
<container-cache-conf />
<container-pool-conf />
<commit-option />
<role-mapping-manager/>
<authentication-module/>
</container-configuration>
</container-configurations>
</jboss>
-->
<!--
The jboss element is the root element of the jboss.xml file. It
contains all the information used by jboss but not described in the
ejb-jar.xml file. All of it is optional.
1- the application assembler can define custom container configurations
for the beans. Standard configurations are provided in standardjboss.xml
2- the deployer can override the jndi names under which the beans are
deployed
3- the deployer can specify runtime jndi names for resource managers.
-->
<!ELEMENT jboss (secure? , enterprise-beans? , resource-managers? ,
container-configurations?)>
<!--
The secure element tells the container to enforce ejb1.1 restrictions
It must be one of the following :
<secure>true</secure>
<secure>false</secure>
Used in: jboss
-->
<!ELEMENT secure (#PCDATA)>
<!--
The enterprise-beans element contains additional information about
the beans. These informations, such as jndi names, resource managers and
container configurations, are specific to jboss and not described in
ejb-jar.xml.
jboss will provide a standard behaviour if no enterprise-beans element
is found, see container-configurations, jndi-name and resource-managers
for defaults.
Used in: jboss
-->
<!ELEMENT enterprise-beans (session | entity)+>
<!--
The entity element holds information specific to jboss and not declared
in ejb-jar.xml about an entity bean, such as jndi name, container
configuration, and resource managers. (see tags for details)
The bean should already be declared in ejb-jar.xml, with the same
ejb-name.
Used in: enterprise-beans
-->
<!ELEMENT entity (ejb-name , jndi-name? , configuration-name? , ejb-ref* ,
resource-ref*)>
<!--
The session element holds information specific to jboss and not declared
in ejb-jar.xml about a session bean, such as jndi name, container
configuration, and resource managers. (see tags for details)
The bean should already be declared in ejb-jar.xml, with the same
ejb-name.
Used in: enterprise-beans
-->
<!ELEMENT session (ejb-name , jndi-name? , configuration-name? , ejb-ref* ,
resource-ref*)>
<!--
The ejb-name element gives the name of the bean, it must correspond to
an ejb-name element in ejb-jar.xml
Used in: entity and session
-->
<!ELEMENT ejb-name (#PCDATA)>
<!--
The jndi-name element gives the actual jndi name under which the bean will
be deployed. It is provided by the deployer. If not, jboss will assume
"jndi-name" = "ejb-name"
Used in: entity and session
-->
<!ELEMENT jndi-name (#PCDATA)>
<!--
The configuration-name element gives the name of the container
configuration for this bean. It must match one of the container-name
tags in the container-configurations section, or one of the standard
configurations. If none is provided, jboss will automatically use the
right standard configuration, see container-configurations.
Used in: entity and session
-->
<!ELEMENT configuration-name (#PCDATA)>
<!--
The ejb-ref element is used to give the jndi-name of an external
ejb reference. In the case of an external ejb reference, you don't
provide a ejb-link element in ejb-jar.xml, but you provide a jndi-name
in jboss.xml
Used in: entity, session
-->
<!ELEMENT ejb-ref (ejb-ref-name , jndi-name)>
<!--
The ejb-ref-name element is the name of the ejb reference as given in
ejb-jar.xml.
Used in: ejb-ref
-->
<!ELEMENT ejb-ref-name (#PCDATA)>
<!--
The jndi-name element gives the deployed name of the reference. The
general form is
<jndi-name>t3://otherserver/application/beanB</jndi-name>
Used in: ejb-ref
(It's commented out here because it appears above and you
can't declare an element more than once per DTD)
-->
<!-- <!ELEMENT jndi-name (#PCDATA)> -->
<!--
The resource-ref element gives a mapping between the "code name"
of a resource (res-ref-name, provided by the Bean Developper) and
its "xml name" (resource-name, provided by the Application Assembler).
If no resource-ref is provided, jboss will assume that
"xml-name" = "code name"
See resource-managers.
Used in: session, entity
-->
<!ELEMENT resource-ref (res-ref-name , resource-name)>
<!--
The res-ref-name element gives the "code name" of a resource. It is
provided by the Bean Developper. See resource-managers for the actual
configuration of the resource.
Used in: resource-ref
-->
<!ELEMENT res-ref-name (#PCDATA)>
<!--
The resource-name element gives the "xml name" of the resource. It is
provided by the Application Assembler. See resource-managers for the
actual configuration of the resource.
Used in: resource-ref
-->
<!ELEMENT resource-name (#PCDATA)>
<!--
The resource-managers element is used to declare resource managers.
A resource has 3 names:
- the "code name" is the name used in the code of the bean, supplied by
the Bean Developper in the resource-ref section of the ejb-jar.xml file
- the "xml name" is an intermediary name used by the Application Assembler
to identify resources in the XML file.
- the "runtime jndi name" is the actual jndi-name or url of the deployed
resource, it is supplied by the Deployer.
The mapping between the "code name" and the "xml name" is given
in the resource-ref section for the bean. If not, jboss will assume that
"xml name" = "code name".
The mapping between the "xml name" and the "runtime jndi name" is given in
a resource-manager section. If not, and if the datasource is of type
javax.sql.DataSource, jboss will look for a javax.sql.DataSource in the jndi
tree.
Used in: jboss
-->
<!ELEMENT resource-managers (resource-manager*)>
<!--
The resource-manager element is used to provide a mapping between the
"xml name" of a resource (res-name) and its "runtime jndi name"
(res-jndi-name or res-url according to the type of the resource).
If it is not provided, and if the type of the resource is
javax.sql.DataSource, jboss will look for a javax.sql.DataSource in the
jndi tree.
See resource-managers.
Used in: resource-managers
-->
<!ELEMENT resource-manager (res-name , (res-jndi-name | res-url))>
<!--
The res-class attribute is used to indicate which implementation
class should be used for the specified resource manager.
-->
<!ATTLIST resource-manager res-class CDATA #REQUIRED>
<!--
The res-name element gives the "xml name" of a resource, it is provided
by the Application Assembler. See resource-managers.
Used in: resource-manager
-->
<!ELEMENT res-name (#PCDATA)>
<!--
The res-jndi-name element is the "deployed jndi name" of a resource, it
is provided by the Deployer. See resource-managers.
Used in: resource-manager
-->
<!ELEMENT res-jndi-name (#PCDATA)>
<!--
The res-url element is the "runtime jndi name" as a url of the resource.
It is provided by the Deployer. See resource-managers.
Used in: resource-manager
-->
<!ELEMENT res-url (#PCDATA)>
<!--
The container-configurations element declares the different possible
container configurations that the beans can use. standardjboss.xml
provides 4 standard configurations with the following container-names:
- Standard CMP EntityBean
- Standard BMP EntityBean
- Standard Stateless SessionBean
- Standard Stateful SessionBean
These standard configurations will automatically be used if no custom
configuration is specified.
The application assembler can define advanced custom configurations here.
Used in: jboss
-->
<!ELEMENT container-configurations (container-configuration*)>
<!--
The container-configuration element describes a configuration for the
container.
The different plugins to use are declared here, as well as their
configurations. The configuration-class attribute is no longer used.
Used in: container-configurations
-->
<!ELEMENT container-configuration (container-name, call-logging, container-invoker,
container-interceptors?, instance-pool?, instance-cache? , persistence-manager? ,
transaction-manager? , container-invoker-conf? , container-cache-conf? ,
container-pool-conf?,
commit-option? , role-mapping-manager? , authentication-module?)>
<!--
The configuration-class attribute is used to indicate the
implementation class that will be loaded for this configuration.
This usually indicates what type of bean the configuration
applies to.
-->
<!ATTLIST container-configuration configuration-class CDATA #IMPLIED>
<!--
The container-name element gives the name of the configuration being
defined. Beans may refer to this name in their configuration-name tag.
Used in: container-configuration
-->
<!ELEMENT container-name (#PCDATA)>
<!--
The call-logging element tells if the container must log every method
invocation for this bean or not. Its value must be trus or false.
Used in: container-configuration
-->
<!ELEMENT call-logging (#PCDATA)>
<!--
The container-invoker element gives the class name of the container
invoker jboss must use for in this configuration. This class must
implement the org.jboss.ejb.ContainerInvoker interface. The default is
org.jboss.ejb.plugins.jrmp13.server.JRMPContainerInvoker, it may be
changed to org.jboss.ejb.plugins.jrmp12.server.JRMPContainerInvoker if
no 1.3 VM is available
Used in: container-configuration
-->
<!ELEMENT container-invoker (#PCDATA)>
<!-- The container-interceptors element gives the chain of Interceptors
(instances of org.jboss.ejb.Interceptor) that are associated with the container.
The declared order of the interceptor elements corresponds to the order of the
interceptor chain.
Used in: container-configuration
-->
<!ELEMENT container-interceptors (interceptor+)>
<!-- The interceptor element specifies an instance of org.jboss.ejb.Interceptor
that is to be added to the container interceptor stack.
Used in: container-interceptors
-->
<!ELEMENT interceptor (#PCDATA)>
<!-- The transaction attribute is used to indicate what type of container its
interceptor applies to. It is an enumerated value that can take on one of: Bean,
Container or Both. A value of Bean indicates that the interceptor should only be
added to a container for bean-managed transaction.
A value of Container indicates that the interceptor should only be added to a
container for container-managed transactions.
A value of Both indicates that the interceptor should be added to all
containers. This is the default value if the transaction attribute is not
explictlygiven.
-->
<!ATTLIST interceptor transaction (Bean | Container | Both ) "Both">
<!-- 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 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 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
invoker, JRMPContainerInvoker.
Used in: container-configuration
-->
<!ELEMENT container-invoker-conf (Optimized , RMIObjectPort)>
<!--
This element is only valid if the container invoker is
JRMPContainerInvoker.
The Optimized element tells if the container invoker to bypass RMI layers
when the client is local (same VM as the server). This optimizes RMI calls.
Its value must be true or false.
Used in: container-invoker-conf for JRMPContainerInvoker
-->
<!ELEMENT Optimized (#PCDATA)>
<!--
The RMIObjectPort element indicates what port the RMI objects
created by this container should listen on. Any number of objects
in the same VM can use the same port. However, objects in
different VMs cannot use the same port. You may set this value
to 0 to use anyonmous ports (that is, each object just picks a
free port to use). If you want to run jBoss more than once on
the same machine, you must either create separate configurations
with separate ports, or set all the configurations to use
anonymous port. The standard jBoss setting is "4444".
Its value must an integer (0, or a valid port number). Note that
normal user on a UNIX system cannot access privileged ports (<1024)
Used in: container-invoker-conf for JRMPContainerInvoker
-->
<!ELEMENT RMIObjectPort (#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.
The default instance caches, NoPassivationEntityInstanceCache and
NoPassivationStatefulSessionInstanceCache, have no configuration
available.
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.
Used in: container-cache-conf (when cache-policy is the LRU cache)
-->
<!ELEMENT cache-policy-conf (min-capacity , max-capacity , overager-period ,
resizer-period , max-bean-age , 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 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 MaximumSize
configuration.
Used in: container-configuration
-->
<!ELEMENT container-pool-conf (MaximumSize , MinimumSize)>
<!--
This element is only valid if the instance pool is a subclass of
AbstractInstancePool.
The MaximumSize element gives the maximum number of instance to
keep in the pool. Its value must be an integer.
Used in: container-pool-conf for AbstractInstancePool subclasses
-->
<!ELEMENT MaximumSize (#PCDATA)>
<!--
This element is only valid if the instance pool is a subclass of
AbstractInstancePool.
The MinimumSize element gives the minimum number of instance to
keep in the pool. Its value must be an integer.
Used in: container-pool-conf for AbstractInstancePool subclasses
-->
<!ELEMENT MinimumSize (#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 or C.
- 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.
See ejb1.1 specification for details (p118).
Used in: container-configuration
-->
<!ELEMENT commit-option (#PCDATA)>
<!--
The role-mapping-manager element specifies the JNDI name of the
org.jboss.security.RealmMapping implementation that is to be used by the
container SecurityInterceptor.
Used in: container-configuration
-->
<!ELEMENT role-mapping-manager (#PCDATA)>
<!--
The authentication-module element specifies the JNDI name of the
org.jboss.security.EJBSecurityManager implementation that is to be used
by the container SecurityInterceptor.
Used in: container-configuration
-->
<!ELEMENT authentication-module (#PCDATA)>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
