User: starksm
Date: 01/11/27 22:25:28
Modified: src/resources/org/jboss/metadata Tag: Branch_2_4
jboss-web.dtd jboss_2_4.dtd
Log:
Update the dtd comments
Revision Changes Path
No revision
No revision
1.3.4.2 +1 -1 jboss/src/resources/org/jboss/metadata/jboss-web.dtd
Index: jboss-web.dtd
===================================================================
RCS file: /cvsroot/jboss/jboss/src/resources/org/jboss/metadata/jboss-web.dtd,v
retrieving revision 1.3.4.1
retrieving revision 1.3.4.2
diff -u -r1.3.4.1 -r1.3.4.2
--- jboss-web.dtd 2001/11/20 09:42:58 1.3.4.1
+++ jboss-web.dtd 2001/11/28 06:25:27 1.3.4.2
@@ -13,7 +13,7 @@
<!-- The security-domain element allows one to specify a module wide
security manager domain. It specifies the JNDI name of the security
-manager that implements the EJBSecurityManager and RealmMapping for
+manager that implements the AuthenticationManager and RealmMapping for
the domain.
-->
<!ELEMENT security-domain (#PCDATA)>
1.1.2.9 +69 -86 jboss/src/resources/org/jboss/metadata/jboss_2_4.dtd
Index: jboss_2_4.dtd
===================================================================
RCS file: /cvsroot/jboss/jboss/src/resources/org/jboss/metadata/jboss_2_4.dtd,v
retrieving revision 1.1.2.8
retrieving revision 1.1.2.9
diff -u -r1.1.2.8 -r1.1.2.9
--- jboss_2_4.dtd 2001/11/09 10:43:45 1.1.2.8
+++ jboss_2_4.dtd 2001/11/28 06:25:28 1.1.2.9
@@ -7,8 +7,8 @@
"-//JBoss//DTD JBOSS 2.4//EN"
"http://www.jboss.org/j2ee/dtd/jboss_2_4.dtd";>
-$Id: jboss_2_4.dtd,v 1.1.2.8 2001/11/09 10:43:45 starksm Exp $
-$Revision: 1.1.2.8 $
+$Id: jboss_2_4.dtd,v 1.1.2.9 2001/11/28 06:25:28 starksm Exp $
+$Revision: 1.1.2.9 $
Overview of the architecture of jboss.xml
@@ -102,7 +102,7 @@
<!ELEMENT enforce-ejb-restrictions (#PCDATA)>
<!-- The security-domain element specifies the JNDI name of the security
-manager that implements the EJBSecurityManager and RealmMapping for
+manager that implements the AuthenticationManager and RealmMapping for
the domain. When specified at the jboss level it specifies the security
domain for all j2ee components in the deployment unit.
One can override the global security-domain at the container
@@ -167,21 +167,24 @@
-->
<!ELEMENT message-driven (ejb-name , destination-jndi-name , configuration-name? ,
security-proxy? , ejb-ref* , resource-ref* , resource-env-ref*)>
-<!--
- The ejb-name element gives the name of the bean, it must correspond to
- an ejb-name element in ejb-jar.xml
+<!-- 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. It is provided by the deployer. If not, jboss will assume
- "jndi-name" = "ejb-name"
-
- Used in: entity and session
- -->
+<!-- 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)>
<!--
@@ -225,17 +228,6 @@
<!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-env-ref element gives a mapping between the "code name"
of a env resource (res-ref-name, provided by the Bean Developper) and
its deployed JNDI name.
@@ -253,17 +245,6 @@
<!ELEMENT resource-env-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).
@@ -358,22 +339,22 @@
-->
<!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:
+<!-- The container-configurations element declares the different
+possible container configurations that the beans can use.
+standardjboss.xml provides 5 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.
+ - Standard Message Driven Bean
+
+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*)>
<!--
@@ -410,16 +391,14 @@
-->
<!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
+<!-- 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.
Used in: container-configuration
- -->
+-->
<!ELEMENT container-invoker (#PCDATA)>
<!-- The container-interceptors element gives the chain of Interceptors
@@ -438,17 +417,17 @@
-->
<!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.
+<!-- 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 explicitly given.
-->
-<!ATTLIST interceptor transaction (Bean | Container | Both ) "Both">
+<!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
@@ -470,21 +449,21 @@
-->
<!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
+<!-- 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.EntityInstanceCache for entity beans
+ - org.jboss.ejb.plugins.StatefulSessionInstanceCache 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
+<!-- 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
@@ -499,25 +478,24 @@
-->
<!ELEMENT persistence-manager (#PCDATA)>
-<!--
- The locking-policy element gives the class name of the EJB lock
+<!-- The locking-policy element gives the class name of the EJB lock
implementation JBoss must use for in this configuration. This class must
implement the org.jboss.ejb.BeanLock interface. The default is
org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.
Used in: container-configuration
-->
-<!ELEMENT transaction-manager (#PCDATA)>
+<!ELEMENT locking-policy (#PCDATA)>
-<!--
- The transaction-manager element gives the class name of the transaction
+
+<!-- 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 locking-policy (#PCDATA)>
+-->
+<!ELEMENT transaction-manager (#PCDATA)>
<!--
The container-invoker-conf element holds configuration data for the
@@ -610,6 +588,14 @@
<!ELEMENT JMSProviderAdapterJNDI (#PCDATA)>
+<!-- The ssl-domain element specifies the JNDI name of a
+org.jboss.security.SecurityDomain implementation. It is used
+by the custom SSL socket factory implementations.
+
+ Used in: container-invoker-conf for JRMPContainerInvoker
+-->
+<!ELEMENT ssl-domain (#PCDATA)>
+
<!ELEMENT ServerSessionPoolFactoryJNDI (#PCDATA)>
<!ELEMENT MaxMessages (#PCDATA)>
@@ -788,13 +774,10 @@
<!--
The authentication-module element specifies the JNDI name of the
- org.jboss.security.EJBSecurityManager implementation that is to be used
+ org.jboss.security.AuthenticationManager implementation that is to be used
by the container SecurityInterceptor. Its use is deprecated in favor of
the security-domain element.
Used in: container-configuration
-->
<!ELEMENT authentication-module (#PCDATA)>
-
-<!ELEMENT ssl-domain (#PCDATA)>
-
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
