User: stark
Date: 01/03/05 02:47:31
Modified: src/resources/org/jboss/metadata jboss.dtd
Log:
Added an application level security-domain element
Revision Changes Path
1.3 +10 -1 jboss/src/resources/org/jboss/metadata/jboss.dtd
Index: jboss.dtd
===================================================================
RCS file: /products/cvs/ejboss/jboss/src/resources/org/jboss/metadata/jboss.dtd,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- jboss.dtd 2001/01/30 01:11:00 1.2
+++ jboss.dtd 2001/03/05 10:47:31 1.3
@@ -6,6 +6,7 @@
<jboss>
<secure />
+ <security-domain />
<enterprise-beans>
@@ -77,7 +78,7 @@
3- the deployer can specify runtime jndi names for resource managers.
-->
-<!ELEMENT jboss (secure? , enterprise-beans? , resource-managers? ,
container-configurations?)>
+<!ELEMENT jboss (secure? , security-domain?, enterprise-beans? , resource-managers?
, container-configurations?)>
<!--
The secure element tells the container to enforce ejb1.1 restrictions
@@ -88,6 +89,14 @@
Used in: jboss
-->
<!ELEMENT secure (#PCDATA)>
+
+<!-- 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
+the domain. One can still override these interfaces at the container
+level using the authentication-module and role-mapping-manager elements.
+-->
+<!ELEMENT security-domain (#PCDATA)>
<!--
The enterprise-beans element contains additional information about
