Update of
/cvsroot/xdoclet/xdoclet/modules/jboss/src/xdoclet/modules/jboss/ejb/resources
In directory sc8-pr-cvs1:/tmp/cvs-serv11256/resources
Modified Files:
jboss_3_0.dtd jboss_3_2.dtd jbosscmp-jdbc_3_0.dtd
Added Files:
jbosscmp-jdbc_4_0.dtd
Log Message:
- updated JBoss DTDs
- added new JBoss versions to the JBoss subtask
--- NEW FILE: jbosscmp-jdbc_4_0.dtd ---
<?xml version='1.0' encoding='UTF-8' ?>
<!--
This is the XML DTD for the jbosscmp-jdbc deployment descriptor.
<!DOCTYPE jbosscmp-jdbc PUBLIC
"-//JBoss//DTD JBOSSCMP-JDBC 4.0//EN"
"http://www.jboss.org/j2ee/dtd/jbosscmp-jdbc_4_0.dtd";>
-->
<!--
The root element of JBossCMP-JDBC configuration files.
-->
<!ELEMENT jbosscmp-jdbc (defaults?, enterprise-beans?, relationships?,
dependent-value-classes?, type-mappings?, entity-commands?)>
<!--
The optional defaults elements contains the default values for
entities, and relationships.
-->
<!ELEMENT defaults ((datasource, datasource-mapping)?, create-table?,
remove-table?, read-only?, read-time-out?, row-locking?,
pk-constraint?, fk-constraint?, preferred-relation-mapping?,
read-ahead?, list-cache-max?, fetch-size?, unknown-pk?,
create-entity-command?, entity-command?)>
<!--
The optional datasource element contains the jndi-name used to lookup
the datasource. All database connections used by an entity or relation table are
obtained from the datasource.
-->
<!ELEMENT datasource (#PCDATA)>
<!--
The optional datasource-mapping element contains the name of the type mapping
that will be used for this datasource.
-->
<!ELEMENT datasource-mapping (#PCDATA)>
<!--
Should the persistence manager attempt to create tables if they are
not present?
The create-table element must be one of the two following:
<create-table>true</create-table>
<create-table>false</create-table>
-->
<!ELEMENT create-table (#PCDATA)>
<!--
Should the persistence manager attempt to remove tables during shutdown?
The remove-table element must be one of the two following:
<remove-table>true</remove-table>
<remove-table>false</remove-table>
-->
<!ELEMENT remove-table (#PCDATA)>
<!--
Is the entity or cmp-field read-only?
The read-only element must be one of the two following:
<read-only>true</read-only>
<read-only>false</read-only>
-->
<!ELEMENT read-only (#PCDATA)>
<!--
Specifies the ammount of time that a read-only field is considered
valid (milliseconds).
-->
<!ELEMENT read-time-out (#PCDATA)>
<!--
Should select statements the SELECT ... FOR UPDATE syntax?
The row-locking element must be one of the two following:
<row-locking>true</row-locking>
<row-locking>false</row-locking>
-->
<!ELEMENT row-locking (#PCDATA)>
<!--
Should a foreign key constraint be added for this relationship role?
The fk-constraint element must be one of the two following:
<fk-constraint>true</fk-constraint>
<fk-constraint>false</fk-constraint>
-->
<!ELEMENT fk-constraint (#PCDATA)>
<!--
Should a primary key constraint be added when creating tables?
The pk-constraint element must be one of the two following:
<pk-constraint>true</pk-constraint>
<pk-constraint>false</pk-constraint>
-->
<!ELEMENT pk-constraint (#PCDATA)>
<!--
Specifies the preferred mapping style for relationships.
The preferred-relation-mapping element must be one of the two following:
<preferred-relation-mapping>foreign-key</preferred-relation-mapping>
<preferred-relation-mapping>relation-table</preferred-relation-mapping>
-->
<!ELEMENT preferred-relation-mapping (#PCDATA)>
<!--
Specifies the read ahead strategy.
<read-ahead>
<strategy>on-load</strategy>
<page-size>255</page-size>
<eager-load-group>*</eager-load-group>
</read-ahead>
-->
<!ELEMENT read-ahead (strategy, page-size?, eager-load-group?)>
<!--
Specifies the strategy used to read-ahead data in queries.
The strategy element must be one of the two following:
<strategy>none</strategy>
<strategy>on-load</strategy>
<strategy>on-find</strategy>
-->
<!ELEMENT strategy (#PCDATA)>
<!--
Specifies the number of entities that will be read in a single
read-ahead load query.
-->
<!ELEMENT page-size (#PCDATA)>
<!--
Specifies the number of simultaneous queries that can be tracked by
the cache for an entity.
-->
<!ELEMENT list-cache-max (#PCDATA)>
<!--
Specifies the number of entities to read in one round-trip to
the underlying datastore.
-->
<!ELEMENT fetch-size (#PCDATA)>
<!--
The enterprise-beans element contains the entity elements that will
be configured.
-->
<!ELEMENT enterprise-beans (entity+)>
<!--
The entity element contains the configuration of an entity
-->
<!ELEMENT entity (ejb-name, (datasource, datasource-mapping)?, create-table?,
remove-table?, read-only?, read-time-out?, row-locking?,
pk-constraint?, read-ahead?, list-cache-max?, fetch-size?, table-name?,
cmp-field*, load-groups?, eager-load-group?, lazy-load-groups?,
query*, unknown-pk?, entity-command?, optimistic-locking?, audit?)>
<!--
Name of the entity being configured. This must match an entity declared
in the ejb-jar.xml file.
-->
<!ELEMENT ejb-name (#PCDATA)>
<!--
This is the name of the table that will hold data for this entity.
Each entity instance will be stored in one row of this table.
-->
<!ELEMENT table-name (#PCDATA)>
<!--
The cmp-field element contains the configuration of a cmp-field.
-->
<!ELEMENT cmp-field (field-name, read-only?, read-time-out?,
column-name?, not-null?, ((jdbc-type, sql-type) | (property+))?,
auto-increment? )>
<!--
Name of the cmp-field being configured. This must match a cmp-field
declared for this entity in the ejb-jar.xml file.
-->
<!ELEMENT field-name (#PCDATA)>
<!--
The name of the column that will hold the data for this field.
-->
<!ELEMENT column-name (#PCDATA)>
<!--
If present the field will not allow a field value.
-->
<!ELEMENT not-null EMPTY>
<!--
This is the JDBC type that is used when setting parameters in a JDBC
PreparedStatement or loading data from a JDBC ResultSet for this
cmp-field. The valid types are defined in java.sql.Types.
-->
<!ELEMENT jdbc-type (#PCDATA)>
<!--
This is the SQL type that is used in create table statements for
this field. Valid sql-types are only limited by your database vendor.
-->
<!ELEMENT sql-type (#PCDATA)>
<!--
The property element contains the configuration of a dependent
value class property of a cmp-field that is the type of a dependent
value class.
-->
<!ELEMENT property (property-name, column-name?, not-null?,
(jdbc-type, sql-type)?)>
<!--
Name of the property being configured. In a dependent-value-class
element this must match a JavaBean property of the class. In a
cmp-field element this must match a flattened propety of the
dependent-value-class field type.
-->
<!ELEMENT property-name (#PCDATA)>
<!--
Contains the named load groups.
-->
<!ELEMENT load-groups (load-group+)>
<!--
A named group of fields that will be loaded together.
-->
<!ELEMENT load-group (description?, load-group-name, field-name+)>
<!--
Contains the name of a load group.
-->
<!ELEMENT load-group-name (#PCDATA)>
<!--
Contains the name of the load group that will eager loaded for this entity.
-->
<!ELEMENT eager-load-group (#PCDATA)>
<!--
Contains the names of the groups that will be lazy loaded together.
-->
<!ELEMENT lazy-load-groups (load-group-name+)>
<!--
Descriptive text.
-->
<!ELEMENT description (#PCDATA)>
<!--
The query element contains the configuration of a query.
-->
<!ELEMENT query (description?, query-method,
(jboss-ql | dynamic-ql | declared-sql)?, read-ahead?)>
<!--
The query method that being configured. This must match a
query-method declared for this entity in the ejb-jar.xml file.
-->
<!ELEMENT query-method (method-name, method-params)>
<!--
The name of the query method that is being configured.
-->
<!ELEMENT method-name (#PCDATA)>
<!--
The method-parameters contains the parameters of the method that is
being configured. Method parameters must be in the same order as the
method and have the same type.
-->
<!ELEMENT method-params (method-param*)>
<!--
The java class of one parameter for a query.
An example follows:
<method-param>java.lang.String</method-param>
-->
<!ELEMENT method-param (#PCDATA)>
<!--
JBossQL query. JBossQL is a superset of EJB-QL.
-->
<!ELEMENT jboss-ql (#PCDATA)>
<!--
Dynamic JBossQL query. The JBossQL is passed to the query and compiled
on the fly.
-->
<!ELEMENT dynamic-ql EMPTY>
<!ATTLIST dynamic-ql useNewCompiler CDATA #IMPLIED>
<!--
Explicitly declared sql fragments.
-->
<!ELEMENT declared-sql (select?, from?, where?, order?, other?)>
<!--
Delcares what is to be selected. A finder may only have the distinct element.
-->
<!ELEMENT select (distinct?, (ejb-name, field-name?)?, alias?)>
<!--
Delared additional SQl to append to the generated from clause.
Example: <from>, FullAddressEJB as a</from>
-->
<!ELEMENT from (#PCDATA)>
<!--
If the empty distinct element is present, the SELECT DISTINCT
syntax will be used. This syntax is used by default for ejbSelect
methods that return a java.util.Set.
-->
<!ELEMENT distinct EMPTY>
<!--
Declares the where clause for the query.
Example: <where>TITLE={0} OR ARTIST={0} OR TYPE={0} OR NOTES={0}</where>
-->
<!ELEMENT where (#PCDATA)>
<!--
Declares the order clause for the query.
Example: <order>TITLE</order>
-->
<!ELEMENT order (#PCDATA)>
<!--
Declares the other sql that is appended to the end of a query.
Example: <other>LIMIT 100 OFFSET 200</other>
-->
<!ELEMENT other (#PCDATA)>
<!--
Declare the alias to use for the main select table.
Example: <alias>my_table</alias>
-->
<!ELEMENT alias (#PCDATA)>
<!--
The relationships element contains the ejb-relation elements that will
be configured.
-->
<!ELEMENT relationships (ejb-relation+)>
<!--
The ejb-relation element contains the configuration of an
ejb-relation.
-->
<!ELEMENT ejb-relation (ejb-relation-name, read-only?, read-time-out?,
(foreign-key-mapping | relation-table-mapping)?,
(ejb-relationship-role, ejb-relationship-role)?)>
<!--
Name of the ejb-relation being configured. This must match an
ejb-relation declared in the ejb-jar.xml file.
-->
<!ELEMENT ejb-relation-name (#PCDATA)>
<!--
Specifies that the ejb-relation should be mapped with foreign-keys.
This mapping is not available for many-to-many relationships.
-->
<!ELEMENT foreign-key-mapping EMPTY>
<!--
Specifies that the ejb-relation should be mapped with a relation-table.
-->
<!ELEMENT relation-table-mapping (table-name?,
(datasource, datasource-mapping)?, create-table?, remove-table?,
row-locking?, pk-constraint?)>
<!--
The ejb-rejationship-role element contains the configuration of an
ejb-relationship-role.
-->
<!ELEMENT ejb-relationship-role (ejb-relationship-role-name,
fk-constraint?, key-fields?, read-ahead?)>
<!--
Name of the ejb-relationship-role being configured. This must match
an ejb-relationship-role declared for this ejb-relation in the
ejb-jar.xml file.
-->
<!ELEMENT ejb-relationship-role-name (#PCDATA)>
<!--
Contains the key fields. The interperation of the key fields depends
on the mapping style of the relationship.
-->
<!ELEMENT key-fields (key-field*)>
<!--
The key-field element declared the configuration of a key field.
The field-name element must match the field-name of one of the
primary key fields of the this entity.
-->
<!ELEMENT key-field (field-name,
((column-name, (jdbc-type, sql-type)?) | (property*))
)>
<!--
Contains the known dependent value classes.
-->
<!ELEMENT dependent-value-classes (dependent-value-class*)>
<!--
The dependent-value-class element contains the configuration of a
dependent value class.
-->
<!ELEMENT dependent-value-class (description?, class, property+)>
<!--
Name of the java class to which the dependent value class configuration
applies.
-->
<!ELEMENT class (#PCDATA)>
<!--
The type-mappings element contains the java to sql mappings.
-->
<!ELEMENT type-mappings (type-mapping+)>
<!--
The type-mapping element contains a named java to sql mapping.
This includes both type mapping and function mapping.
-->
<!ELEMENT type-mapping (name, row-locking-template, pk-constraint-template,
fk-constraint-template, alias-header-prefix, alias-header-suffix,
alias-max-length, subquery-supported, true-mapping, false-mapping,
function-mapping*, mapping+, entity-commands*)>
<!--
Name of the type-mapping.
-->
<!ELEMENT name (#PCDATA)>
<!--
This is the template used to create a row lock on the selected rows. The
arguments supplied are as follows:
1. Select clause
2. From clasue; the order of the tables is currently not guarenteed
3. Where clause
If row locking is not supported in select statement this element should be
empty. The most common form of row locking is select for update as in the
example that follows:
SELECT ?1 FROM ?2 WHERE ?3 FOR UPDATE
-->
<!ELEMENT row-locking-template (#PCDATA)>
<!--
This is the template used to create a primary key constraint in the create
table statement. The arguments supplied are as follows:
1. Primary key constraint name; which is always pk_{table-name}
2. Comma sepperated list of primary key column names
If a primary key constraint clause is not supported in a create table statement
this element should be empty. The most common form of a primary key constraint
follows:
CONSTRAINT ?1 PRIMARY KEY (?2)
-->
<!ELEMENT pk-constraint-template (#PCDATA)>
<!--
This is the template used to create a foreign key constraint in sepperate
statement. The arguments supplied are as follows:
1. Table name
2. Foreign key constraint name; which is always fk_{table-name}_{cmr-field-name}
3. Comma sepperated list of foreign key column names
4. References table name
5. Comma sepperated list of the referenced primary key column names
If the datasource does not support foreign key constraints this element should
be empty. The most common form of a foreign key constraint follows:
ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)
-->
<!ELEMENT fk-constraint-template (#PCDATA)>
<!--
An alias header is prepended to a generated table alias by the EJB-QL compiler
to prevent name collisions. An alias header is constructed as folows:
alias-header-prefix + int_counter + alias-header-suffix
-->
<!ELEMENT alias-header-prefix (#PCDATA)>
<!ELEMENT alias-header-suffix (#PCDATA)>
<!ELEMENT alias-max-length (#PCDATA)>
<!--
Does this type-mapping support subqueries. Some EJB-QL opperators are mapped
to exists subqueries. If subquery is false the EJB-QL compiler will use a
left join and is null.
The subquery-supported element must be one of the two following:
<create-table>true</create-table>
<create-table>false</create-table>
-->
<!ELEMENT subquery-supported (#PCDATA)>
<!--
The true and false mappings are the mappings for true and false in EJB-QL
queries.
-->
<!ELEMENT true-mapping (#PCDATA)>
<!ELEMENT false-mapping (#PCDATA)>
<!--
Specifies the mapping from a java type to a jdbc and a sql type.
-->
<!ELEMENT mapping (java-type, jdbc-type, sql-type)>
<!--
Specifies the java class type to be mapped.
-->
<!ELEMENT java-type (#PCDATA)>
<!--
Specifies the mapping from an EJB-QL function to a sql function.
-->
<!ELEMENT function-mapping (function-name, function-sql)>
<!--
The name of the function to be mapped.
-->
<!ELEMENT function-name (#PCDATA)>
<!--
The sql to which the function is mapped. The sql can contain
parameters specified with a question mark followed by the base one
parameter number. For example, function mapping for concat in Oracle
follows:
<function-mapping>
<function-name>concat</function-name>
<function-sql>(?1 || ?2)</function-sql>
</function-mapping>
-->
<!ELEMENT function-sql (#PCDATA)>
<!--
Unknown primary key configuration
-->
<!ELEMENT unknown-pk (unknown-pk-class, field-name?, read-only?, read-time-out?,
column-name?, (jdbc-type, sql-type)?, auto-increment? )>
<!--
The unknown primary key class.
-->
<!ELEMENT unknown-pk-class (#PCDATA)>
<!--
If present the field will auto-incremented by the database
-->
<!ELEMENT auto-increment EMPTY>
<!--
This element declares available for entity commands
-->
<!ELEMENT entity-commands (entity-command*)>
<!--
This element represents an entity command
-->
<!ELEMENT entity-command (attribute*)>
<!--
This attribute specifies the command name
-->
<!ATTLIST entity-command name CDATA #REQUIRED>
<!--
This attribute specifies the command class
-->
<!ATTLIST entity-command class CDATA #IMPLIED>
<!--
The attribute for create-method.
-->
<!ELEMENT attribute (#PCDATA)>
<!--
The name of the attribute
-->
<!ATTLIST attribute name CDATA #REQUIRED>
<!--
Optimistic locking configuration
-->
<!ELEMENT optimistic-locking (
group-name |
modified-strategy |
read-strategy |
((version-column | timestamp-column | (key-generator-factory, field-type)),
field-name?, column-name?, (jdbc-type, sql-type)?)
)>
<!--
Optimistic locking field group name.
This name must match one of the entity's load-group-name.
The fields in this group will be used for optimistic locking.
-->
<!ELEMENT group-name (#PCDATA)>
<!--
Optimistic locking modified strategy.
This means the fields that were modified during transaction
will be used for optimistic locking
-->
<!ELEMENT modified-strategy EMPTY>
<!--
Optimistic locking read strategy.
This strategy implies that the fields that were read/changed
in the transaction will be used for optimistic locking
-->
<!ELEMENT read-strategy EMPTY>
<!--
Optimistic locking version column strategy.
Setting this element will add to entity bean additional version field
of type java.lang.Long that will be used for optimistic locking.
Each update of the entity will increase the value of this field.
-->
<!ELEMENT version-column EMPTY>
<!--
Optimistic locking timestamp column strategy.
Setting this element will add to entity bean additional field of type
java.util.Date that will be used for optimistic locking.
Each update of the entity will set the value of this field to the current
time.
-->
<!ELEMENT timestamp-column EMPTY>
<!--
Optimistic locking field type.
The type for locking field in optimistic locking.
-->
<!ELEMENT field-type (#PCDATA)>
<!--
Key generator factory JNDI name.
This element specifies the JNDI name of key generator factory that is
used to obtain key generator for locking column used in optimistic locking.
-->
<!ELEMENT key-generator-factory (#PCDATA)>
<!--
Audit fields, choose the audit fields
The created by and updated by require a caller principal
The fields can also be cmp fields, use the same field-name
-->
<!ELEMENT audit (created-by?, created-time?, updated-by?, updated-time?)>
<!--
Created by principal, default is audit_created_by
-->
<!ELEMENT created-by (field-name?, column-name?, (jdbc-type, sql-type)?)>
<!--
Created time, default is audit_created_time
-->
<!ELEMENT created-time (field-name?, column-name?, (jdbc-type, sql-type)?)>
<!--
Updated by principal, default is audit_updated_by
-->
<!ELEMENT updated-by (field-name?, column-name?, (jdbc-type, sql-type)?)>
<!--
Updated time, default is audit_updated_time
-->
<!ELEMENT updated-time (field-name?, column-name?, (jdbc-type, sql-type)?)>
Index: jboss_3_0.dtd
===================================================================
RCS file:
/cvsroot/xdoclet/xdoclet/modules/jboss/src/xdoclet/modules/jboss/ejb/resources/jboss_3_0.dtd,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -r1.4 -r1.5
*** jboss_3_0.dtd 11 Feb 2003 10:06:09 -0000 1.4
--- jboss_3_0.dtd 19 Mar 2003 18:50:08 -0000 1.5
***************
*** 27,31 ****
<jndi-name />
<local-jndi-name />
! <read-only>
<home-invoker>
<bean-invoker>
--- 27,31 ----
<jndi-name />
<local-jndi-name />
! <read-only>
<home-invoker>
<bean-invoker>
***************
*** 119,123 ****
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
--- 119,123 ----
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
***************
*** 141,145 ****
<!ELEMENT enforce-ejb-restrictions (#PCDATA)>
! <!--
The security-domain element specifies the JNDI name of the security
manager that implements the EJBSecurityManager and RealmMapping for
--- 141,145 ----
<!ELEMENT enforce-ejb-restrictions (#PCDATA)>
! <!--
The security-domain element specifies the JNDI name of the security
manager that implements the EJBSecurityManager and RealmMapping for
***************
*** 154,158 ****
<!ELEMENT security-domain (#PCDATA)>
! <!--
The unauthenticated-principal element specifies the name of the principal
that will be returned by the EJBContext.getCallerPrincipal() method if there
--- 154,158 ----
<!ELEMENT security-domain (#PCDATA)>
! <!--
The unauthenticated-principal element specifies the name of the principal
that will be returned by the EJBContext.getCallerPrincipal() method if there
***************
*** 208,212 ****
The bean should already be declared in ejb-jar.xml, with the same
ejb-name.
!
Used in: enterprise-beans
-->
--- 208,212 ----
The bean should already be declared in ejb-jar.xml, with the same
ejb-name.
!
Used in: enterprise-beans
-->
***************
*** 218,255 ****
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, session, and message-driven
-->
<!ELEMENT ejb-name (#PCDATA)>
! <!--
! The jndi-name element gives the actual jndi name under which
! the bean will be deployed when used in the entity, session and
! message-driven elements. If it is not provided jboss will assume
! "jndi-name" = "ejb-name"
!
! When used in the ejb-ref, resource-ref, resource-env-ref elements
! this specifies the jndi name to which the reference should link.
!
! Used in: entity, session and message-driven
! ejb-ref, resource-ref, resource-env-ref
-->
<!ELEMENT jndi-name (#PCDATA)>
! <!--
The JNDI name under with the local home interface should be bound
!
! Used in: entity and session
-->
<!ELEMENT local-jndi-name (#PCDATA)>
! <!--
! The read-only element flags an entity bean as read only.
! The bean will never be ejbStored. Defaults to false.
It must be one of the following :
<read-only>true</read-only>
<read-only>false</read-only>
! Used in: entity
-->
<!ELEMENT read-only (#PCDATA)>
--- 218,254 ----
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, session, and message-driven
-->
<!ELEMENT ejb-name (#PCDATA)>
! <!--
! The jndi-name element gives the actual jndi name under which
! the bean will be deployed when used in the entity, session and
! message-driven elements. If it is not provided jboss will assume
! "jndi-name" = "ejb-name"
!
! When used in the ejb-ref, resource-ref, resource-env-ref elements
! this specifies the jndi name to which the reference should link.
!
! Used in: entity, session and message-driven
! ejb-ref, resource-ref, resource-env-ref
-->
<!ELEMENT jndi-name (#PCDATA)>
! <!--
The JNDI name under with the local home interface should be bound
!
! Used in: entity and session
-->
<!ELEMENT local-jndi-name (#PCDATA)>
! <!-- The read-only element flags an entity bean or a method as read only.
! Such a bean or method will never trigger a store. Defaults to false.
It must be one of the following :
<read-only>true</read-only>
<read-only>false</read-only>
! Used in: entity, method-attributes
-->
<!ELEMENT read-only (#PCDATA)>
***************
*** 273,277 ****
configurations. If no element is provided, jboss will automatically use the
right standard configuration, see container-configurations.
!
Note: unlike earlier releases, this element may not be specified as an
empty element to achieve the same effect as not specifying the element.
--- 272,276 ----
configurations. If no element is provided, jboss will automatically use the
right standard configuration, see container-configurations.
!
Note: unlike earlier releases, this element may not be specified as an
empty element to achieve the same effect as not specifying the element.
***************
*** 305,309 ****
provide a ejb-link element in ejb-jar.xml, but you provide a jndi-name
in jboss.xml
!
Used in: entity, session, and message-driven
-->
--- 304,308 ----
provide a ejb-link element in ejb-jar.xml, but you provide a jndi-name
in jboss.xml
!
Used in: entity, session, and message-driven
-->
***************
*** 313,317 ****
The ejb-ref-name element is the name of the ejb reference as given in
ejb-jar.xml.
!
Used in: ejb-ref
-->
--- 312,316 ----
The ejb-ref-name element is the name of the ejb reference as given in
ejb-jar.xml.
!
Used in: ejb-ref
-->
***************
*** 322,326 ****
of a env resource (res-ref-name, provided by the Bean Developer) and
its deployed JNDI name.
!
Used in: session, entity, message-driven
-->
--- 321,325 ----
of a env resource (res-ref-name, provided by the Bean Developer) and
its deployed JNDI name.
!
Used in: session, entity, message-driven
-->
***************
*** 330,334 ****
The resource-env-ref-name element gives the "code name" of a resource. It is
provided by the Bean Developer.
!
Used in: resource-env-ref
-->
--- 329,333 ----
The resource-env-ref-name element gives the "code name" of a resource. It is
provided by the Bean Developer.
!
Used in: resource-env-ref
-->
***************
*** 339,343 ****
It is provided by the deployer. If not, jboss will assume clustered = False
Possible values: "True", "False" (default)
!
Used in: entity and session
-->
--- 338,342 ----
It is provided by the deployer. If not, jboss will assume clustered = False
Possible values: "True", "False" (default)
!
Used in: entity and session
-->
***************
*** 347,351 ****
The cluster-config element allows to specify cluster specific settings.
WARNING: session-state-manager-jndi-name is only for SFSB.
!
Used in: session, entity
-->
--- 346,350 ----
The cluster-config element allows to specify cluster specific settings.
WARNING: session-state-manager-jndi-name is only for SFSB.
!
Used in: session, entity
-->
***************
*** 358,362 ****
a JNDI name. Given name will be prefixed by "/HASessionState/" by the container to
get
the actual JNDI name of the HAPartition. If not, jboss will assume partition-name
= "DefaultPartition".
!
Used in: entity and session (in clustered-config element)
-->
--- 357,361 ----
a JNDI name. Given name will be prefixed by "/HASessionState/" by the container to
get
the actual JNDI name of the HAPartition. If not, jboss will assume partition-name
= "DefaultPartition".
!
Used in: entity and session (in clustered-config element)
-->
***************
*** 367,371 ****
to load balance calls in the home proxy.
If not, jboss will assume home-load-balance-policy =
"org.jboss.ha.framework.interfaces.RoundRobin".
!
Used in: entity and session (in clustered-config element)
-->
--- 366,370 ----
to load balance calls in the home proxy.
If not, jboss will assume home-load-balance-policy =
"org.jboss.ha.framework.interfaces.RoundRobin".
!
Used in: entity and session (in clustered-config element)
-->
***************
*** 378,382 ****
- for EB and SFSB : bean-load-balance-policy =
"org.jboss.ha.framework.interfaces.RoundRobin"
- for SLSB : bean-load-balance-policy =
"org.jboss.ha.framework.interfaces.RoundRobin"
!
Used in: entity and session (in clustered-config element)
-->
--- 377,381 ----
- for EB and SFSB : bean-load-balance-policy =
"org.jboss.ha.framework.interfaces.RoundRobin"
- for SLSB : bean-load-balance-policy =
"org.jboss.ha.framework.interfaces.RoundRobin"
!
Used in: entity and session (in clustered-config element)
-->
***************
*** 388,392 ****
This *is* a JNDI name (not like the partition-name element).
If not, jboss will assume partition-name = "/HASessionState/Default".
!
Used in: session (in clustered-config element)
-->
--- 387,391 ----
This *is* a JNDI name (not like the partition-name element).
If not, jboss will assume partition-name = "/HASessionState/Default".
!
Used in: session (in clustered-config element)
-->
***************
*** 406,416 ****
<!ELEMENT method-name (#PCDATA)>
- <!-- The read-only element specifies that the given method(s) do not affect
- the state of the bean. The should be either true or false.
-
- Used in: method-attributes
- -->
- <!ELEMENT read-only (#PCDATA)>
-
<!--
The resource-ref element gives a mapping between the "code name"
--- 405,408 ----
***************
*** 419,425 ****
If no resource-ref is provided, jboss will assume that
"xml-name" = "code name"
!
See resource-managers.
!
Used in: entity, session, and message-driven
-->
--- 411,417 ----
If no resource-ref is provided, jboss will assume that
"xml-name" = "code name"
!
See resource-managers.
!
Used in: entity, session, and message-driven
-->
***************
*** 430,434 ****
provided by the Bean Developer. See resource-managers for the actual
configuration of the resource.
!
Used in: resource-ref
-->
--- 422,426 ----
provided by the Bean Developer. See resource-managers for the actual
configuration of the resource.
!
Used in: resource-ref
-->
***************
*** 439,443 ****
provided by the Application Assembler. See resource-managers for the
actual configuration of the resource.
!
Used in: resource-ref
-->
--- 431,435 ----
provided by the Application Assembler. See resource-managers for the
actual configuration of the resource.
!
Used in: resource-ref
-->
***************
*** 446,469 ****
<!--
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 Developer 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
-->
--- 438,461 ----
<!--
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 Developer 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
-->
***************
*** 477,483 ****
javax.sql.DataSource, jboss will look for a javax.sql.DataSource in the
jndi tree.
!
See resource-managers.
!
Used in: resource-managers
-->
--- 469,475 ----
javax.sql.DataSource, jboss will look for a javax.sql.DataSource in the
jndi tree.
!
See resource-managers.
!
Used in: resource-managers
-->
***************
*** 487,491 ****
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
-->
--- 479,483 ----
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
-->
***************
*** 495,499 ****
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
-->
--- 487,491 ----
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
-->
***************
*** 503,507 ****
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
-->
--- 495,499 ----
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
-->
***************
*** 532,543 ****
- jdk 1.2.2 BMP EntityBean
- Standard message Driven Bean
!
The standard configurations will automatically be used if no custom
configuration is specified.
The jdk 1.2.2 configurations are defined for backwards compatability.
!
The application assembler can define advanced custom configurations here.
!
Used in: jboss
-->
--- 524,535 ----
- jdk 1.2.2 BMP EntityBean
- Standard message Driven Bean
!
The standard configurations will automatically be used if no custom
configuration is specified.
The jdk 1.2.2 configurations are defined for backwards compatability.
!
The application assembler can define advanced custom configurations here.
!
Used in: jboss
-->
***************
*** 549,553 ****
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
-->
--- 541,545 ----
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
-->
***************
*** 573,577 ****
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
-->
--- 565,569 ----
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
-->
***************
*** 581,585 ****
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
-->
--- 573,577 ----
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
-->
***************
*** 590,612 ****
invoker jboss must use for in this configuration. This class must
implement the org.jboss.ejb.ContainerInvoker interface. The default is
! org.jboss.proxy.ejb.ProxyFactory for entity and session beans and
org.jboss.ejb.plugins.jms.JMSContainerInvoker for message driven beans.
Containers supporting clustering use org.jboss.proxy.ejb.ProxyFactoryHA.
!
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 client-interceptors defines the home and bean client side interceptor chain
--- 582,604 ----
invoker jboss must use for in this configuration. This class must
implement the org.jboss.ejb.ContainerInvoker interface. The default is
! org.jboss.proxy.ejb.ProxyFactory for entity and session beans and
org.jboss.ejb.plugins.jms.JMSContainerInvoker for message driven beans.
Containers supporting clustering use org.jboss.proxy.ejb.ProxyFactoryHA.
!
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 client-interceptors defines the home and bean client side interceptor chain
***************
*** 635,647 ****
<!ELEMENT bean (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,
--- 627,639 ----
<!ELEMENT bean (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,
***************
*** 656,660 ****
<!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
--- 648,652 ----
<!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
***************
*** 672,676 ****
session beans.
- no pool is used for stateful session beans
!
Used in: container-configuration
-->
--- 664,668 ----
session beans.
- no pool is used for stateful session beans
!
Used in: container-configuration
-->
***************
*** 685,689 ****
stateful session beans.
- no cache is used for stateless session beans
!
Used in: container-configuration
-->
--- 677,681 ----
stateful session beans.
- no cache is used for stateless session beans
!
Used in: container-configuration
-->
***************
*** 701,705 ****
beans.
- no persistence-manager is used for stateless session beans
!
Used in: container-configuration
-->
--- 693,697 ----
beans.
- no persistence-manager is used for stateless session beans
!
Used in: container-configuration
-->
***************
*** 711,715 ****
implement the org.jboss.ejb.BeanLock interface. The default is
org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.
!
Used in: container-configuration
-->
--- 703,707 ----
implement the org.jboss.ejb.BeanLock interface. The default is
org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.
!
Used in: container-configuration
-->
***************
*** 721,725 ****
the javax.transaction.TransactionManager interface. The default is
org.jboss.tm.TxManager.
!
Used in: container-configuration
-->
--- 713,717 ----
the javax.transaction.TransactionManager interface. The default is
org.jboss.tm.TxManager.
!
Used in: container-configuration
-->
***************
*** 730,734 ****
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
-->
--- 722,726 ----
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
-->
***************
*** 741,748 ****
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
-->
--- 733,740 ----
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
-->
***************
*** 800,804 ****
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
-->
--- 792,796 ----
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
-->
***************
*** 808,812 ****
The implementation class for the cache policy, which controls
when instances will be passivated, etc.
!
Used in: container-cache-conf
-->
--- 800,804 ----
The implementation class for the cache policy, which controls
when instances will be passivated, etc.
!
Used in: container-cache-conf
-->
***************
*** 888,895 ****
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
-->
--- 880,887 ----
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
-->
***************
*** 903,907 ****
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
-->
--- 895,899 ----
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
-->
***************
*** 911,921 ****
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
-->
--- 903,913 ----
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
-->
***************
*** 925,931 ****
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
-->
--- 917,923 ----
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
-->
***************
*** 935,939 ****
The pool feeder will feed the pool with this number of new instances at
a regular period.
!
Used in: feeder-policy-conf
-->
--- 927,931 ----
The pool feeder will feed the pool with this number of new instances at
a regular period.
!
Used in: feeder-policy-conf
-->
***************
*** 944,948 ****
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
-->
--- 936,940 ----
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
-->
***************
*** 951,958 ****
<!--
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.
--- 943,950 ----
<!--
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.
***************
*** 961,970 ****
- 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
-->
--- 953,962 ----
- 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
-->
Index: jboss_3_2.dtd
===================================================================
RCS file:
/cvsroot/xdoclet/xdoclet/modules/jboss/src/xdoclet/modules/jboss/ejb/resources/jboss_3_2.dtd,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -r1.1 -r1.2
*** jboss_3_2.dtd 13 Feb 2003 19:41:27 -0000 1.1
--- jboss_3_2.dtd 19 Mar 2003 18:50:09 -0000 1.2
***************
*** 90,94 ****
<container-configuration>
<container-name />
- <container-invoker />
<container-interceptors />
<client-interceptors />
--- 90,93 ----
***************
*** 96,103 ****
<instance-cache />
<persistence-manager />
- <transaction-manager />
<web-class-loader />
<locking-policy />
- <container-invoker-conf />
<container-cache-conf />
<container-pool-conf />
--- 95,100 ----
***************
*** 111,114 ****
--- 108,112 ----
</jboss>
-->
+
<!--
The jboss element is the root element of the jboss.xml file. It
***************
*** 124,129 ****
-->
<!ELEMENT jboss (enforce-ejb-restrictions? , security-domain? ,
! unauthenticated-principal? , enterprise-beans? , resource-managers? ,
! container-configurations?)>
<!--
--- 122,127 ----
-->
<!ELEMENT jboss (enforce-ejb-restrictions? , security-domain? ,
! unauthenticated-principal? , enterprise-beans?, resource-managers? ,
! invoker-proxy-bindings?, container-configurations?)>
<!--
***************
*** 158,161 ****
--- 156,180 ----
<!ELEMENT unauthenticated-principal (#PCDATA)>
+ <!-- The invoker-proxy-bindings defines the invokers available for use with
+ the ejb container configurations.
+ -->
+ <!ELEMENT invoker-proxy-bindings (invoker-proxy-binding*)>
+ <!-- The invoker-proxy-binding defines an invoker service and proxy factory
+ -->
+ <!ELEMENT invoker-proxy-binding (name, invoker-mbean, proxy-factory,
proxy-factory-config)>
+ <!-- The name gives a unique name for the invoker-proxy-binding
+ -->
+ <!ELEMENT name (#PCDATA)>
+ <!-- The invoker-mbean gives the JMX ObjectName of the invoker MBean service
+ -->
+ <!ELEMENT invoker-mbean (#PCDATA)>
+ <!-- The org.jboss.ejb.EJBProxyFactory implementation class
+ -->
+ <!ELEMENT proxy-factory (#PCDATA)>
+ <!-- The proxy-factory-config defines the client-interceptors stack to use
+ for the various EJB proxies.
+ -->
+ <!ELEMENT proxy-factory-config (client-interceptors)>
+
<!--
The enterprise-beans element contains additional information about
***************
*** 170,174 ****
Used in: jboss
-->
! <!ELEMENT enterprise-beans (session | entity | message-driven)+>
<!--
--- 189,193 ----
Used in: jboss
-->
! <!ELEMENT enterprise-beans (session | entity | message-driven)*>
<!--
***************
*** 182,188 ****
-->
<!ELEMENT entity (ejb-name , jndi-name? , local-jndi-name? , read-only? ,
! configuration-name? , security-proxy? , ejb-ref* , resource-ref* ,
resource-env-ref* , method-attributes? , clustered? , cluster-config?,
! cache-invalidation? , cache-invalidation-config?)>
<!--
--- 201,207 ----
-->
<!ELEMENT entity (ejb-name , jndi-name? , local-jndi-name? , read-only? ,
! configuration-name? , invoker-bindings?, security-proxy? , ejb-ref* , resource-ref*
,
resource-env-ref* , method-attributes? , clustered? , cluster-config?,
! cache-invalidation? , cache-invalidation-config?, depends*)>
<!--
***************
*** 196,201 ****
-->
<!ELEMENT session (ejb-name , jndi-name? , local-jndi-name?, configuration-name?,
! security-proxy? , ejb-ref* , resource-ref* , resource-env-ref* , clustered? ,
! cluster-config?, method-attributes?)>
<!--
--- 215,220 ----
-->
<!ELEMENT session (ejb-name , jndi-name? , local-jndi-name?, configuration-name?,
! invoker-bindings?, security-proxy? , ejb-ref* , resource-ref* , resource-env-ref* ,
clustered? ,
! cluster-config?, method-attributes?, depends*)>
<!--
***************
*** 208,214 ****
Used in: enterprise-beans
-->
! <!ELEMENT message-driven (ejb-name , destination-jndi-name , mdb-user? ,
! mdb-passwd? , mdb-client-id? , mdb-subscription-id? , configuration-name? ,
! security-proxy? , ejb-ref* , resource-ref* , resource-env-ref*)>
<!--
--- 227,234 ----
Used in: enterprise-beans
-->
! <!ELEMENT message-driven (ejb-name , destination-jndi-name ,
! mdb-user?, mdb-passwd? , mdb-client-id? , mdb-subscription-id? ,
! configuration-name? , invoker-bindings?,
! security-proxy? , ejb-ref* , resource-ref* , resource-env-ref*, depends*)>
<!--
***************
*** 266,269 ****
--- 286,294 ----
<!ELEMENT configuration-name (#PCDATA)>
+ <!-- The depends element gives a JMX ObjectName of a service on which the
+ container or ejb depends.
+ -->
+ <!ELEMENT depends (#PCDATA)>
+
<!ELEMENT destination-jndi-name (#PCDATA)>
***************
*** 339,343 ****
<!--
! The idempotent element is used in method-attributes but I don't know what it is for
-->
<!ELEMENT idempotent (#PCDATA)>
--- 364,369 ----
<!--
! The idempotent element is used in method-attributes to indicate that a method
! is completely stateless. Really the same as read-only and should be dropped.
-->
<!ELEMENT idempotent (#PCDATA)>
***************
*** 356,360 ****
WARNING: session-state-manager-jndi-name is only for SFSB.
! Used in: session, entity
-->
<!ELEMENT cluster-config (partition-name? , home-load-balance-policy? ,
--- 382,386 ----
WARNING: session-state-manager-jndi-name is only for SFSB.
! Used in: session, entity, container-configuration
-->
<!ELEMENT cluster-config (partition-name? , home-load-balance-policy? ,
***************
*** 549,565 ****
- IIOP CMP 2.x EntityBean
- IIOP CMP EntityBean
- - jdk 1.2.2 CMP EntityBean
- Standard Stateless SessionBean
- Clustered Stateless SessionBean
- IIOP Stateless SessionBean
- - jdk 1.2.2 Stateless SessionBean
- Standard Stateful SessionBean
- Clustered Stateful SessionBean
- IIOP Stateful SessionBean
- - jdk 1.2.2 Stateful SessionBean
- Standard BMP EntityBean
- Clustered BMP EntityBean
- IIOP BMP EntityBean
- - jdk 1.2.2 BMP EntityBean
- Standard message Driven Bean
--- 575,587 ----
***************
*** 567,572 ****
configuration is specified.
- The jdk 1.2.2 configurations are defined for backwards compatability.
-
The application assembler can define advanced custom configurations here.
--- 589,592 ----
***************
*** 583,591 ****
Used in: container-configurations
-->
! <!ELEMENT container-configuration (container-name , call-logging? ,
container-invoker? ,
! container-interceptors? , client-interceptors? , instance-pool? , instance-cache? ,
! persistence-manager? , transaction-manager? , web-class-loader? , locking-policy? ,
! container-invoker-conf? , container-cache-conf? , container-pool-conf? ,
! commit-option? , optiond-refresh-rate? , security-domain?)>
<!-- The extends attribute gives the container-name value of the configuration the
container-configuration
--- 603,611 ----
Used in: container-configurations
-->
! <!ELEMENT container-configuration (container-name , call-logging?,
container-interceptors? ,
! instance-pool? , instance-cache? , persistence-manager? , web-class-loader? ,
! locking-policy? , container-cache-conf? , container-pool-conf? ,
! commit-option? , optiond-refresh-rate? , security-domain?, cluster-config?,
! depends*)>
<!-- The extends attribute gives the container-name value of the configuration the
container-configuration
***************
*** 612,616 ****
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
-->
--- 632,636 ----
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
-->
***************
*** 618,633 ****
<!--
! 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.proxy.ejb.ProxyFactory for entity and session beans and
! org.jboss.ejb.plugins.jms.JMSContainerInvoker for message driven beans.
! Containers supporting clustering use org.jboss.proxy.ejb.ProxyFactoryHA.
!
! 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.
--- 638,657 ----
<!--
! The invoker-bindings element gives the invokers configuration for an
! ejb container.
!
! Used in: entity, session, message-driven, container-configuration
-->
! <!ELEMENT invoker-bindings (invoker+)>
! <!--
! -->
! <!ELEMENT invoker (invoker-proxy-binding-name, jndi-name?, ejb-ref*)>
! <!-- The invoker-proxy-binding-name elements maps to the name element of
! a invoker-proxy-binding definition.
! -->
! <!ELEMENT invoker-proxy-binding-name (#PCDATA)>
!
! <!--
The container-interceptors element gives the chain of Interceptors
(instances of org.jboss.ejb.Interceptor) that are associated with the container.
***************
*** 642,648 ****
The client-interceptors defines the home and bean client side interceptor chain
! Used in: container-configuration
-->
! <!ELEMENT client-interceptors (home , bean)>
<!--
--- 666,672 ----
The client-interceptors defines the home and bean client side interceptor chain
! Used in: proxy-factory-config
-->
! <!ELEMENT client-interceptors (home , bean, list-entity?)>
<!--
***************
*** 667,678 ****
<!--
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,
--- 691,712 ----
<!--
+ The list-entity element gives the chain of interceptors
+ (instances of org.jboss.proxy.Interceptor) that are associated with the remote
+ proxy and operate in the client VM. The declared order of the interceptor
+ elements corresponds to the order of the interceptor chain.
+
+ Used in: client-interceptors
+ -->
+ <!ELEMENT list-entity (interceptor+)>
+
+ <!--
The interceptor element specifies an instance of org.jboss.ejb.Interceptor
that is to be added to the container interceptor stack.
!
! Used in: home, bean, list-entity
-->
<!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,
***************
*** 748,761 ****
<!--
- 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
--- 782,785 ----
***************
*** 767,830 ****
<!--
- 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.
--- 791,794 ----
***************
*** 926,931 ****
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
--- 890,896 ----
Used in: container-configuration
-->
! <!ELEMENT container-pool-conf (MinimumSize?, MaximumSize , feeder-policy? ,
feeder-policy-conf?)>
+ <!ELEMENT MinimumSize (#PCDATA)>
<!--
The capacity of the Pool. The pool feeder will feed the pool with new
Index: jbosscmp-jdbc_3_0.dtd
===================================================================
RCS file:
/cvsroot/xdoclet/xdoclet/modules/jboss/src/xdoclet/modules/jboss/ejb/resources/jbosscmp-jdbc_3_0.dtd,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -r1.4 -r1.5
*** jbosscmp-jdbc_3_0.dtd 1 Oct 2002 19:19:04 -0000 1.4
--- jbosscmp-jdbc_3_0.dtd 19 Mar 2003 18:50:10 -0000 1.5
***************
*** 12,16 ****
-->
<!ELEMENT jbosscmp-jdbc (defaults?, enterprise-beans?, relationships?,
! dependent-value-classes?, type-mappings?, entity-commands?)>
<!--
--- 12,16 ----
-->
<!ELEMENT jbosscmp-jdbc (defaults?, enterprise-beans?, relationships?,
! dependent-value-classes?, type-mappings?)>
<!--
***************
*** 21,26 ****
remove-table?, read-only?, read-time-out?, row-locking?,
pk-constraint?, fk-constraint?, preferred-relation-mapping?,
! read-ahead?, list-cache-max?, fetch-size?, unknown-pk?,
! create-entity-command?, entity-command?)>
--- 21,25 ----
remove-table?, read-only?, read-time-out?, row-locking?,
pk-constraint?, fk-constraint?, preferred-relation-mapping?,
! read-ahead?, list-cache-max?, fetch-size?)>
***************
*** 173,177 ****
pk-constraint?, read-ahead?, list-cache-max?, fetch-size?, table-name?,
cmp-field*, load-groups?, eager-load-group?, lazy-load-groups?,
! query*, unknown-pk?, entity-command?)>
<!--
--- 172,176 ----
pk-constraint?, read-ahead?, list-cache-max?, fetch-size?, table-name?,
cmp-field*, load-groups?, eager-load-group?, lazy-load-groups?,
! query*)>
<!--
***************
*** 193,198 ****
-->
<!ELEMENT cmp-field (field-name, read-only?, read-time-out?,
! column-name?, not-null?, ((jdbc-type, sql-type) | (property+))?,
! auto-increment? )>
--- 192,196 ----
-->
<!ELEMENT cmp-field (field-name, read-only?, read-time-out?,
! column-name?, not-null?, ((jdbc-type, sql-type) | (property+))? )>
***************
*** 493,497 ****
fk-constraint-template, alias-header-prefix, alias-header-suffix,
alias-max-length, subquery-supported, true-mapping, false-mapping,
! function-mapping*, mapping+, entity-commands*)>
<!--
--- 491,495 ----
fk-constraint-template, alias-header-prefix, alias-header-suffix,
alias-max-length, subquery-supported, true-mapping, false-mapping,
! function-mapping*, mapping+)>
<!--
***************
*** 609,655 ****
<!ELEMENT function-sql (#PCDATA)>
- <!--
- Unknown primary key configuration
- -->
- <!ELEMENT unknown-pk (unknown-pk-class, read-only?, read-time-out?,
- column-name?, (jdbc-type, sql-type)?, auto-increment? )>
-
- <!--
- The unknown primary key class.
- -->
- <!ELEMENT unknown-pk-class (#PCDATA)>
-
- <!--
- If present the field will auto-incremented by the database
- -->
- <!ELEMENT auto-increment EMPTY>
-
- <!--
- This element declares available for entity commands
- -->
- <!ELEMENT entity-commands (entity-command*)>
-
- <!--
- This element represents an entity command
- -->
- <!ELEMENT entity-command (attribute*)>
-
- <!--
- This attribute specifies the command name
- -->
- <!ATTLIST entity-command name CDATA #REQUIRED>
-
- <!--
- This attribute specifies the command class
- -->
- <!ATTLIST entity-command class CDATA #IMPLIED>
-
- <!--
- The attribute for create-method.
- -->
- <!ELEMENT attribute (#PCDATA)>
-
- <!--
- The name of the attribute
- -->
- <!ATTLIST attribute name CDATA #REQUIRED>
--- 607,608 ----
-------------------------------------------------------
This SF.net email is sponsored by: Does your code think in ink?
You could win a Tablet PC. Get a free Tablet PC hat just for playing.
What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
_______________________________________________
xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
