User: mulder  
  Date: 00/11/14 13:41:34

  Modified:    documentation jboss.dtd
  Log:
  Now a complete and valid DTD.
  
  Revision  Changes    Path
  1.2       +126 -17   newsite/documentation/jboss.dtd
  
  Index: jboss.dtd
  ===================================================================
  RCS file: /products/cvs/ejboss/newsite/documentation/jboss.dtd,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- jboss.dtd 2000/11/12 20:33:36     1.1
  +++ jboss.dtd 2000/11/14 21:41:34     1.2
  @@ -81,7 +81,6 @@
   <!ELEMENT jboss (secure?, enterprise-beans?, resource-managers?, 
   container-configurations?)>
   
  -
     <!--
     The secure element tells the container to enforce ejb1.1 restrictions
     It must be one of the following : 
  @@ -183,16 +182,19 @@
           Used in: ejb-ref
           -->
           <!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)>
  +<!--    <!ELEMENT jndi-name (#PCDATA)> -->
         
         
         <!-- 
  @@ -204,7 +206,7 @@
          
         See resource-managers.
         
  -      Used in: resource-ref
  +      Used in: session, entity
         -->
         <!ELEMENT resource-ref (res-ref-name, resource-name)>
         
  @@ -229,16 +231,18 @@
           <!ELEMENT resource-name (#PCDATA)>
   
       
  -  <-- 
  +  <!--
     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 Developper in the resource-ref section of the ejb-jar.xml file
  +    the Bean Developper 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 / url of the deployed 
  -  resource, it is supplied by the Deployer.
  +    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
  @@ -266,8 +270,13 @@
       
       Used in: resource-managers
       -->
  -    <!ELEMENT resource-manager (res-name, (res-jndi-name | res-url)>
  -    
  +    <!ELEMENT resource-manager (res-name, (res-jndi-name | res-url))>
  +
  +    <!--
  +    The res-class attribute is used to indicate which implementation
  +    class should be used for the specified resource manager.
  +    -->
  +    <!ATTLIST resource-manager res-class CDATA #REQUIRED>
       
         <!--
         The res-name element gives the "xml name" of a resource, it is provided 
  @@ -327,6 +336,14 @@
       container-invoker, instance-pool?, instance-cache?, persistence-manager?, 
       transaction-manager?, container-invoker-conf?, container-cache-conf?, 
       container-pool-conf?, commit-option?)>
  +
  +    <!--
  +    The configuration-class attribute is used to indicate the
  +    implementation class that will be loaded for this configuration.
  +    This usually indicates what type of bean the configuration
  +    applies to.
  +    -->
  +    <!ATTLIST container-configuration configuration-class CDATA #IMPLIED>
       
       
         <!--
  @@ -372,7 +389,7 @@
         Used in: container-configuration
         -->
         <!ELEMENT instance-pool (#PCDATA)>
  -      
  +       
         
         <!--
         The instance-cache element gives the class name of the instance cache
  @@ -385,7 +402,7 @@
         
         Used in: container-configuration
         -->
  -      <!ELEMENT instance-cache (#PCDATA)>
  +     <!ELEMENT instance-cache (#PCDATA)>
         
         
         <!--
  @@ -428,7 +445,7 @@
         
         Used in: container-configuration
         -->
  -      <!ELEMENT container-invoker-conf (Optimized)>
  +      <!ELEMENT container-invoker-conf (Optimized, RMIObjectPort)>
         
   
           <!-- 
  @@ -442,6 +459,25 @@
           Used in: container-invoker-conf for JRMPContainerInvoker
           -->
           <!ELEMENT Optimized (#PCDATA)>
  +
  +
  +     <!--
  +     The RMIObjectPort element indicates what port the RMI objects
  +     created by this container should listen on.  Any number of objects
  +     in the same VM can use the same port.  However, objects in
  +     different VMs cannot use the same port.  You may set this value
  +     to 0 to use anyonmous ports (that is, each object just picks a
  +     free port to use).  If you want to run jBoss more than once on
  +     the same machine, you must either create separate configurations
  +     with separate ports, or set all the configurations to use
  +     anonymous port.  The standard jBoss setting is "4444".
  +
  +        Its value must an integer (0, or a valid port number).  Note that
  +     normal user on a UNIX system cannot access privileged ports (<1024)
  +        
  +        Used in: container-invoker-conf for JRMPContainerInvoker
  +     -->
  +        <!ELEMENT RMIObjectPort (#PCDATA)>
         
         
         <!-- 
  @@ -457,7 +493,68 @@
   
         Used in: container-configuration
         -->
  -      <!ELEMENT container-cache-conf>
  +      <!ELEMENT container-cache-conf (cache-policy?, cache-policy-conf?)>
  +
  +        <!--
  +        The implementation class for the cache policy, which controls
  +        when instances will be passivated, etc.
  +
  +        Used in: container-cache-conf
  +     -->
  +        <!ELEMENT cache-policy (#PCDATA)>
  +
  +     <!--
  +     The configuration settings for the selected cache policy.  This
  +     is currently only valid for the LRU cache.
  +
  +        Used in: container-cache-conf (when cache-policy is the LRU cache)
  +     -->
  +        <!ELEMENT cache-policy-conf (min-capacity, max-capacity,
  +        overager-period,resizer-period,max-bean-age,max-cache-miss-period,
  +     min-cache-miss-period,cache-load-factor)>
  +
  +       <!--
  +       The minimum capacity of this cache
  +       -->
  +       <!ELEMENT min-capacity (#PCDATA)>
  +
  +       <!--
  +       The maximum capacity of this cache
  +       -->
  +       <!ELEMENT max-capacity (#PCDATA)>
  +
  +       <!--
  +       The period of the overager's runs
  +       -->
  +       <!ELEMENT overager-period (#PCDATA)>
  +
  +       <!--
  +       The period of the resizer's runs
  +       -->
  +       <!ELEMENT resizer-period (#PCDATA)>
  +
  +       <!--
  +       The age after which a bean is automatically passivated
  +       -->
  +       <!ELEMENT max-bean-age (#PCDATA)>
  +
  +       <!--
  +       Shrink cache capacity if there is a cache miss every or more
  +       this member's value
  +       -->
  +       <!ELEMENT max-cache-miss-period (#PCDATA)>
  +
  +       <!--
  +       Enlarge cache capacity if there is a cache miss every or less
  +       this member's value
  +       -->
  +       <!ELEMENT min-cache-miss-period (#PCDATA)>
  +
  +       <!--
  +       The resizer will always try to keep the cache capacity so that
  +       the cache is this member's value loaded of cached objects
  +       -->
  +       <!ELEMENT cache-load-factor (#PCDATA)>
         
         
         <!-- 
  @@ -473,7 +570,7 @@
   
         Used in: container-configuration
         -->
  -      <!ELEMENT container-pool-conf (MaximumSize)>
  +      <!ELEMENT container-pool-conf (MaximumSize, MinimumSize)>
     
          
           <!-- 
  @@ -486,6 +583,18 @@
           Used in: container-pool-conf for AbstractInstancePool subclasses
           -->
           <!ELEMENT MaximumSize (#PCDATA)> 
  +  
  +       
  +        <!-- 
  +        This element is only valid if the instance pool is a subclass of
  +        AbstractInstancePool.
  +
  +        The MinimumSize element gives the minimum number of instance to
  +        keep in the pool. Its value must be an integer.
  +
  +        Used in: container-pool-conf for AbstractInstancePool subclasses
  +        -->
  +        <!ELEMENT MinimumSize (#PCDATA)> 
   
   
         <!--
  
  
  

Reply via email to