User: starksm 
  Date: 01/06/12 18:17:32

  Modified:    src/resources/org/jboss/metadata jboss.dtd
  Log:
  Deprecate use of the authentication-module and role-mapping-manager at
  the container-configuration level in favor of security-domain as specifying
  these functions independently is of little use.
  
  Revision  Changes    Path
  1.11      +14 -9     jboss/src/resources/org/jboss/metadata/jboss.dtd
  
  Index: jboss.dtd
  ===================================================================
  RCS file: /cvsroot/jboss/jboss/src/resources/org/jboss/metadata/jboss.dtd,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- jboss.dtd 2001/06/10 20:54:48     1.10
  +++ jboss.dtd 2001/06/13 01:17:31     1.11
  @@ -61,8 +61,7 @@
         <container-pool-conf />
         <commit-option />
         <optiond-refresh-rate />
  -      <role-mapping-manager/>
  -      <authentication-module/>
  +      <security-domain/>
       </container-configuration>
   
     </container-configurations>
  @@ -93,11 +92,15 @@
     -->
   <!ELEMENT enforce-ejb-restrictions (#PCDATA)>
   
  -<!-- The security-domain element allows one to specify a module wide
  -security manager domain. It specifies the JNDI name of the security
  +<!-- The security-domain element 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.
  +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
  +level using the security-domain element at the container-configuration
  +level.
  +
  +  Used in: jboss, container-configuration
   -->
   <!ELEMENT security-domain (#PCDATA)>
   
  @@ -368,7 +371,7 @@
       
       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? , optiond-refresh-rate? 
, (role-mapping-manager , authentication-module?)?)>
  +<!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? , optiond-refresh-rate? 
, (security-domain | (role-mapping-manager , authentication-module))?)>
   
   <!--
       The configuration-class attribute is used to indicate the
  @@ -717,7 +720,8 @@
   <!--
         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.
  +      container SecurityInterceptor. Its use is deprecated in favor of the
  +      security-domain element.
   
         Used in: container-configuration
         -->
  @@ -726,7 +730,8 @@
   <!--
         The authentication-module element specifies the JNDI name of the
         org.jboss.security.EJBSecurityManager implementation that is to be used
  -      by the container SecurityInterceptor.
  +      by the container SecurityInterceptor. Its use is deprecated in favor of
  +      the security-domain element.
   
         Used in: container-configuration
         -->
  
  
  

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to