User: alborini
  Date: 01/04/25 05:35:01

  Modified:    src/docs jbosssx.xml
  Log:
  Small correction.
  
  Revision  Changes    Path
  1.8       +2 -2      manual/src/docs/jbosssx.xml
  
  Index: jbosssx.xml
  ===================================================================
  RCS file: /cvsroot/jboss/manual/src/docs/jbosssx.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- jbosssx.xml       2001/04/09 22:53:16     1.7
  +++ jbosssx.xml       2001/04/25 12:35:00     1.8
  @@ -1,6 +1,6 @@
   <?xml version = "1.0" encoding = "UTF-8"?>
   
  -<!-- Version: $Revision: 1.7 $ -->
  +<!-- Version: $Revision: 1.8 $ -->
   <?xml-stylesheet href = 
'file:///D:/usr/local/src/cvsroot/jBoss/manual/src/docs/jboss.xsl' type = 'text/xsl'?>
   <chapter id = "JBossSX">   
        <title>JBossSX Security Extension Framework</title>   
  @@ -408,7 +408,7 @@
                <para>The default security implementation that JBoss comes 
preconfigured with consists of a JMX service MBean and a JAAS based implementation of 
the EJBSecurityManager and RealmMapping interfaces. The JMX bean is 
org.jboss.security.plugins.JaasSecurityManagerService and the security interfaces 
implementation is org.jboss.security.plugins.JaasSecurityManager. The JMX service 
MBean handles configurable aspects of the security manager and integrates the security 
manager into the JNDI namespace.</para>
                <section>
                        <title>Enabling EJB Security</title>
  -                     <para>Even though there is a preconfigured security manager 
with the JBoss distribution, by default none of the EJB container configurations 
require security. The reason for this is that security may not be required and there 
is no way to provide a reasonable default setup. To secure your EJBs you must either 
change the default container configurations or specify the container configuration at 
deployment time. The standard container configuration is found in the 
config/config-name/standardjboss.xml directory of the JBoss distribution tree. The 
<quote>config-name</quote> value is <quote>default</quote> by default. When specifying 
container configurations at deployment time you include a jboss.xml descriptor in your 
ear or ejb-jar META-INF directory. The key DTD elements for security configuration 
elements is given <xref linkend = "sx.jboss.security-config.dtd"/>
  +                     <para>Even though there is a preconfigured security manager 
with the JBoss distribution, by default none of the EJB container configurations 
require security. The reason for this is that security may not be required and there 
is no way to provide a reasonable default setup. To secure your EJBs you must either 
change the default container configurations or specify the container configuration at 
deployment time. The standard container configuration is found in the 
conf/config-name/standardjboss.xml directory of the JBoss distribution tree. The 
<quote>config-name</quote> value is <quote>default</quote> by default. When specifying 
container configurations at deployment time you include a jboss.xml descriptor in your 
ear or ejb-jar META-INF directory. The key DTD elements for security configuration 
elements is given <xref linkend = "sx.jboss.security-config.dtd"/>
                        </para>
                        <figure id = "sx.jboss.security-config.dtd">   
                                <title>standardjboss.xml/jboss.xml Deployment 
Descriptor Security        Configuration Elements</title>   
  
  
  

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

Reply via email to