glassfish 0.1.1-universal-java-1.5

data/lib/dtds/sun-application_1_3-0.dtd

@@ -0,0 +1,30 @@
+
+<!--
+This is the root element of the runtime descriptor document.
+-->
+<!ELEMENT sun-application (web*, pass-by-reference?, unique-id?, security-role-mapping*) >
+
+<!ELEMENT web (web-uri, context-root)>
+<!ELEMENT web-uri (#PCDATA)>
+<!ELEMENT context-root (#PCDATA)>
+
+<!-- Pass by Reference semantics:  EJB spec requires pass by value,
+     which will be the default mode of operation. This can be set 
+     to true for non-compliant and possibly higher performance. 
+     For a stand-alone, this can be set at this level. By setting 
+     a similarly named element at sun-application, it can apply to 
+     all the enclosed ejb modules. Allowed values are true and 
+     false. Default will be false.
+ -->
+<!ELEMENT pass-by-reference (#PCDATA)>
+
+<!-- Automatically generated and updated at deployment/redeployment 
+     Needs to be unqiue in the system.
+  -->
+<!ELEMENT unique-id (#PCDATA)>
+
+<!ELEMENT security-role-mapping (role-name, (principal-name | group-name)+)>
+
+<!ELEMENT role-name (#PCDATA)>
+<!ELEMENT principal-name (#PCDATA)>
+<!ELEMENT group-name (#PCDATA)>

data/lib/dtds/sun-application_1_4-0.dtd

@@ -0,0 +1,44 @@
+
+<!-- The PUBLIC ID (defined in DOCTYPE) associated with this dtd is:
+     "-//Sun Microsystems, Inc.//DTD Application Server 8.0 J2EE Application 1.4//EN"; 
+-->
+
+<!--
+This is the root element of the runtime descriptor document.
+-->
+<!ELEMENT sun-application (web*, pass-by-reference?, unique-id?, security-role-mapping*, realm?) >
+
+<!ELEMENT web (web-uri, context-root)>
+<!ELEMENT web-uri (#PCDATA)>
+<!ELEMENT context-root (#PCDATA)>
+
+<!-- Pass by Reference semantics:  EJB spec requires pass by value,
+     which will be the default mode of operation. This can be set 
+     to true for non-compliant and possibly higher performance. 
+     For a stand-alone, this can be set at this level. By setting 
+     a similarly named element at sun-application, it can apply to 
+     all the enclosed ejb modules. Allowed values are true and 
+     false. Default will be false.
+ -->
+<!ELEMENT pass-by-reference (#PCDATA)>
+
+<!-- Automatically generated and updated at deployment/redeployment 
+     Needs to be unqiue in the system.
+  -->
+<!ELEMENT unique-id (#PCDATA)>
+
+<!ELEMENT security-role-mapping (role-name, (principal-name | group-name)+)>
+
+<!ELEMENT role-name (#PCDATA)>
+<!ELEMENT principal-name (#PCDATA)>
+<!ELEMENT group-name (#PCDATA)>
+
+<!-- 
+  realm: Allows specifying an optional authentication realm name which will
+    be used to process all authentication requests associated with this
+    application. If this element is not specified (or if it is given but
+    does not match the name of a configured realm) then the default realm
+    set in the server instances security-service element will be used
+    instead.
+-->
+<!ELEMENT realm (#PCDATA)>

data/lib/dtds/sun-application_5_0-0.dtd

@@ -0,0 +1,51 @@
+
+<!--
+  XML DTD for Sun Application Server specific Java EE Application
+  deployment descriptor. This is a companion DTD to application_5.xsd
+
+  It must include a DOCTYPE of the following form:
+
+  <!DOCTYPE sun-application PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 9.0 Java EE Application 5.0//EN" "http://www.sun.com/software/appserver/dtds/sun-application_5_0-0.dtd">
+
+-->
+
+<!--
+This is the root element of the runtime descriptor document.
+-->
+<!ELEMENT sun-application (web*, pass-by-reference?, unique-id?, security-role-mapping*, realm?) >
+
+<!ELEMENT web (web-uri, context-root)>
+<!ELEMENT web-uri (#PCDATA)>
+<!ELEMENT context-root (#PCDATA)>
+
+<!-- Pass by Reference semantics:  EJB spec requires pass by value,
+     which will be the default mode of operation. This can be set 
+     to true for non-compliant and possibly higher performance. 
+     For a stand-alone, this can be set at this level. By setting 
+     a similarly named element at sun-application, it can apply to 
+     all the enclosed ejb modules. Allowed values are true and 
+     false. Default will be false.
+ -->
+<!ELEMENT pass-by-reference (#PCDATA)>
+
+<!-- Automatically generated and updated at deployment/redeployment 
+     Needs to be unqiue in the system.
+  -->
+<!ELEMENT unique-id (#PCDATA)>
+
+<!ELEMENT security-role-mapping (role-name, (principal-name | group-name)+)>
+
+<!ELEMENT role-name (#PCDATA)>
+<!ELEMENT principal-name (#PCDATA)>
+<!ATTLIST principal-name class-name CDATA #IMPLIED>
+<!ELEMENT group-name (#PCDATA)>
+
+<!-- 
+  realm: Allows specifying an optional authentication realm name which will
+    be used to process all authentication requests associated with this
+    application. If this element is not specified (or if it is given but
+    does not match the name of a configured realm) then the default realm
+    set in the server instances security-service element will be used
+    instead.
+-->
+<!ELEMENT realm (#PCDATA)>

data/lib/dtds/sun-cmp-mapping_1_0.dtd

@@ -0,0 +1,100 @@
+
+<!-- This file maps at least one set of beans to tables and columns in a 
+     specific db schema
+-->
+<!ELEMENT sun-cmp-mappings ( sun-cmp-mapping+ ) >
+
+<!-- At least one bean is mapped to database columns in the named schema -->
+<!ELEMENT sun-cmp-mapping ( schema, entity-mapping+) >
+
+<!-- A cmp bean has a name, a primary table, one or more fields, zero or 
+     more relationships, and zero or more secondary tables, plus flags for 
+     consistency checking.
+ 
+     If the consistency checking flag element is not present, then none 
+     is assumed 
+--> 
+<!ELEMENT entity-mapping (ejb-name, table-name, cmp-field-mapping+, 
+        cmr-field-mapping*, secondary-table*, consistency?)>
+
+<!ELEMENT consistency (none | check-modified-at-commit | lock-when-loaded |
+        check-all-at-commit | lock-when-modified | 
+        (lock-when-modified, check-all-at-commit) ) >
+
+<!ELEMENT read-only EMPTY>
+
+<!-- A cmp-field-mapping has a field, one or more columns that it maps to.  
+     The column can be from a bean's primary table or any defined secondary 
+     table.  If a field is mapped to multiple columns, the column listed first
+     is used as the SOURCE for getting the value from the database.  The 
+     columns are updated in their order.  A field may also be marked as 
+     read-only.  It may also participate in a hierarchial or independent 
+     fetch group. If the fetched-with element is not present, the field 
+     is assumed to be a member of the default hierarchial fetch group.
+-->
+<!ELEMENT cmp-field-mapping (field-name, column-name+, read-only?, 
+        fetched-with?) >
+            
+<!-- The java identifier of a field. Must match the value of the field-name 
+     sub-element of the cmp-field that is being mapped. 
+-->
+<!ELEMENT field-name (#PCDATA) >
+
+<!-- The java identifier of a field.  Must match the value of the 
+     cmr-field-name sub-element of the cmr-field tat is being mapped. 
+-->
+<!ELEMENT cmr-field-name (#PCDATA) >
+
+<!-- The ejb-name from the standard EJB-jar DTD--> 
+<!ELEMENT ejb-name (#PCDATA) >
+
+<!-- The COLUMN name of a column from the primary table, or the table 
+     qualified name (TABLE.COLUMN) of a column from a secondary or related 
+     table
+--> 
+<!ELEMENT column-name (#PCDATA) >
+
+<!-- Holds the fetch group configuration for fields and relationships -->
+<!ELEMENT fetched-with (level | named-group | none) >
+
+<!-- The name of an independent fetch group.  All the fields and relationships 
+  that are part of a named-group are fetched at the same time-->
+<!ELEMENT named-group (#PCDATA) >
+
+<!-- A hierarchial fetch group.  The value of this element must be an integer.
+     Fields and relationships that belong to a hierachial fetch group of equal
+     (or lesser) value are fetched at the same time. The value of level must
+     be greater than zero.
+-->
+<!ELEMENT level (#PCDATA) >
+
+<!-- The name of a database table -->
+<!ELEMENT table-name (#PCDATA) >
+
+<!-- a bean's secondary tables -->
+<!ELEMENT secondary-table (table-name, column-pair+) >
+
+<!-- the pair of columns -->
+<!ELEMENT column-pair (column-name, column-name) >
+
+<!-- cmr-field mapping.  A cmr field has a name and one or more column 
+     pairs that define the relationship. The relationship can also 
+     participate in a fetch group.
+     
+     If the fetched-with element is not present, the value,
+          <fetched-with><none/></fetched-with>
+     is assumed. 
+-->
+<!ELEMENT cmr-field-mapping (cmr-field-name, column-pair+, fetched-with? ) >
+
+<!-- The path name to the schema file--> 
+<!ELEMENT schema (#PCDATA) >
+
+<!-- flag elements for consistency levels -->
+
+<!-- note: none is also a sub-element of the fetched-with tag -->
+<!ELEMENT none EMPTY >
+<!ELEMENT check-modified-at-commit EMPTY >
+<!ELEMENT check-all-at-commit EMPTY>
+<!ELEMENT lock-when-modified EMPTY>
+<!ELEMENT lock-when-loaded EMPTY >

data/lib/dtds/sun-cmp-mapping_1_1.dtd

@@ -0,0 +1,99 @@
+
+<!-- This file maps at least one set of beans to tables and columns in a 
+     specific db schema
+-->
+<!ELEMENT sun-cmp-mappings ( sun-cmp-mapping+ ) >
+
+<!-- At least one bean is mapped to database columns in the named schema -->
+<!ELEMENT sun-cmp-mapping ( schema, entity-mapping+) >
+
+<!-- A cmp bean has a name, a primary table, one or more fields, zero or 
+     more relationships, and zero or more secondary tables, plus flags for 
+     consistency checking.
+ 
+     If the consistency checking flag element is not present, then none 
+     is assumed 
+--> 
+<!ELEMENT entity-mapping (ejb-name, table-name, cmp-field-mapping+, 
+        cmr-field-mapping*, secondary-table*, consistency?)>
+
+<!ELEMENT consistency (none | check-modified-at-commit | lock-when-loaded |
+        check-all-at-commit | (lock-when-modified, check-all-at-commit?) ) >
+
+<!ELEMENT read-only EMPTY>
+
+<!-- A cmp-field-mapping has a field, one or more columns that it maps to.  
+     The column can be from a bean's primary table or any defined secondary 
+     table.  If a field is mapped to multiple columns, the column listed first
+     is used as the SOURCE for getting the value from the database.  The 
+     columns are updated in their order.  A field may also be marked as 
+     read-only.  It may also participate in a hierarchial or independent 
+     fetch group. If the fetched-with element is not present, the field 
+     is assumed to be a member of the default hierarchial fetch group.
+-->
+<!ELEMENT cmp-field-mapping (field-name, column-name+, read-only?, 
+        fetched-with?) >
+            
+<!-- The java identifier of a field. Must match the value of the field-name 
+     sub-element of the cmp-field that is being mapped. 
+-->
+<!ELEMENT field-name (#PCDATA) >
+
+<!-- The java identifier of a field.  Must match the value of the 
+     cmr-field-name sub-element of the cmr-field tat is being mapped. 
+-->
+<!ELEMENT cmr-field-name (#PCDATA) >
+
+<!-- The ejb-name from the standard EJB-jar DTD--> 
+<!ELEMENT ejb-name (#PCDATA) >
+
+<!-- The COLUMN name of a column from the primary table, or the table 
+     qualified name (TABLE.COLUMN) of a column from a secondary or related 
+     table
+--> 
+<!ELEMENT column-name (#PCDATA) >
+
+<!-- Holds the fetch group configuration for fields and relationships -->
+<!ELEMENT fetched-with (level | named-group | none) >
+
+<!-- The name of an independent fetch group.  All the fields and relationships 
+  that are part of a named-group are fetched at the same time-->
+<!ELEMENT named-group (#PCDATA) >
+
+<!-- A hierarchial fetch group.  The value of this element must be an integer.
+     Fields and relationships that belong to a hierachial fetch group of equal
+     (or lesser) value are fetched at the same time. The value of level must
+     be greater than zero.
+-->
+<!ELEMENT level (#PCDATA) >
+
+<!-- The name of a database table -->
+<!ELEMENT table-name (#PCDATA) >
+
+<!-- a bean's secondary tables -->
+<!ELEMENT secondary-table (table-name, column-pair+) >
+
+<!-- the pair of columns -->
+<!ELEMENT column-pair (column-name, column-name) >
+
+<!-- cmr-field mapping.  A cmr field has a name and one or more column 
+     pairs that define the relationship. The relationship can also 
+     participate in a fetch group.
+     
+     If the fetched-with element is not present, the value,
+          <fetched-with><none/></fetched-with>
+     is assumed. 
+-->
+<!ELEMENT cmr-field-mapping (cmr-field-name, column-pair+, fetched-with? ) >
+
+<!-- The path name to the schema file--> 
+<!ELEMENT schema (#PCDATA) >
+
+<!-- flag elements for consistency levels -->
+
+<!-- note: none is also a sub-element of the fetched-with tag -->
+<!ELEMENT none EMPTY >
+<!ELEMENT check-modified-at-commit EMPTY >
+<!ELEMENT check-all-at-commit EMPTY>
+<!ELEMENT lock-when-modified EMPTY>
+<!ELEMENT lock-when-loaded EMPTY >

data/lib/dtds/sun-cmp-mapping_1_2.dtd

@@ -0,0 +1,106 @@
+
+<!-- This file maps at least one set of beans to tables and columns in a 
+     specific db schema
+-->
+<!ELEMENT sun-cmp-mappings ( sun-cmp-mapping+ ) >
+
+<!-- At least one bean is mapped to database columns in the named schema -->
+<!ELEMENT sun-cmp-mapping ( schema, entity-mapping+) >
+
+<!-- A cmp bean has a name, a primary table, one or more fields, zero or 
+     more relationships, and zero or more secondary tables, plus flags for 
+     consistency checking.
+ 
+     If the consistency checking flag element is not present, then none 
+     is assumed 
+--> 
+<!ELEMENT entity-mapping (ejb-name, table-name, cmp-field-mapping+, 
+        cmr-field-mapping*, secondary-table*, consistency?)>
+
+<!ELEMENT consistency (none | check-modified-at-commit | lock-when-loaded |
+        check-all-at-commit | (lock-when-modified, check-all-at-commit?) |
+        check-version-of-accessed-instances) >
+
+<!ELEMENT read-only EMPTY>
+
+<!-- A cmp-field-mapping has a field, one or more columns that it maps to.  
+     The column can be from a bean's primary table or any defined secondary 
+     table.  If a field is mapped to multiple columns, the column listed first
+     is used as the SOURCE for getting the value from the database.  The 
+     columns are updated in their order.  A field may also be marked as 
+     read-only.  It may also participate in a hierarchial or independent 
+     fetch group. If the fetched-with element is not present, the value,
+          <fetched-with><default/></fetched-with>
+     is assumed.
+-->
+<!ELEMENT cmp-field-mapping (field-name, column-name+, read-only?, 
+        fetched-with?) >
+            
+<!-- The java identifier of a field. Must match the value of the field-name 
+     sub-element of the cmp-field that is being mapped. 
+-->
+<!ELEMENT field-name (#PCDATA) >
+
+<!-- The java identifier of a field.  Must match the value of the 
+     cmr-field-name sub-element of the cmr-field tat is being mapped. 
+-->
+<!ELEMENT cmr-field-name (#PCDATA) >
+
+<!-- The ejb-name from the standard EJB-jar DTD--> 
+<!ELEMENT ejb-name (#PCDATA) >
+
+<!-- The COLUMN name of a column from the primary table, or the table 
+     qualified name (TABLE.COLUMN) of a column from a secondary or related 
+     table
+--> 
+<!ELEMENT column-name (#PCDATA) >
+
+<!-- Holds the fetch group configuration for fields and relationships -->
+<!ELEMENT fetched-with (default | level | named-group | none) >
+
+<!-- Sub element of fetched-with. Implies that a field belongs to the default
+     hierarchical fetch group. -->
+<!ELEMENT default EMPTY>
+
+<!-- A hierarchial fetch group.  The value of this element must be an integer.
+     Fields and relationships that belong to a hierachial fetch group of equal
+     (or lesser) value are fetched at the same time. The value of level must
+     be greater than zero.
+-->
+<!ELEMENT level (#PCDATA) >
+
+<!-- The name of an independent fetch group.  All the fields and relationships 
+  that are part of a named-group are fetched at the same time-->
+<!ELEMENT named-group (#PCDATA) >
+
+<!-- The name of a database table -->
+<!ELEMENT table-name (#PCDATA) >
+
+<!-- a bean's secondary tables -->
+<!ELEMENT secondary-table (table-name, column-pair+) >
+
+<!-- the pair of columns -->
+<!ELEMENT column-pair (column-name, column-name) >
+
+<!-- cmr-field mapping.  A cmr field has a name and one or more column 
+     pairs that define the relationship. The relationship can also 
+     participate in a fetch group.
+     
+     If the fetched-with element is not present, the value,
+          <fetched-with><none/></fetched-with>
+     is assumed. 
+-->
+<!ELEMENT cmr-field-mapping (cmr-field-name, column-pair+, fetched-with? ) >
+
+<!-- The path name to the schema file--> 
+<!ELEMENT schema (#PCDATA) >
+
+<!-- flag elements for consistency levels -->
+
+<!-- note: none is also a sub-element of the fetched-with tag -->
+<!ELEMENT none EMPTY >
+<!ELEMENT check-modified-at-commit EMPTY >
+<!ELEMENT check-all-at-commit EMPTY>
+<!ELEMENT lock-when-modified EMPTY>
+<!ELEMENT lock-when-loaded EMPTY >
+<!ELEMENT check-version-of-accessed-instances (column-name+) >

data/lib/dtds/sun-connector_1_0-0.dtd

@@ -0,0 +1,66 @@
+
+<!-- The PUBLIC ID (defined in DOCTYPE) associated with this dtd is:
+     "-//Sun Microsystems, Inc.//DTD Sun ONE Application Server 7.0 Connector 1.0//EN";
+-->
+
+<!ENTITY % boolean "(yes | no | on | off | 1 | 0 | true | false)">
+
+<!-- Each deployed Resource Adapter (RAR) Module, will have ias-ra.xml 
+     associated with it, which specifies several dynamic configuration 
+     properties. Key aspects are pool sizing and security role maps.
+ -->
+<!ELEMENT sun-connector (resource-adapter, role-map?)>
+
+<!-- Resource adapter configuration 
+
+     jndi-name          name by which, this adapter will appear in JNDI tree
+     max-pool-size      maximum size of connection to EIS
+     steady-pool-size   initial and minimum number of connections to be maintained
+     max-wait-in-millis if a connection is not readily found, caller will have to 
+                        wait this long, before a connection is created. A value of
+                        0 implies, wait till a connection becomes available. If the
+                        pool is completely utilized and the timer expires, an 
+                        exception will be delivered to the application.
+
+     idle-timeout-in-seconds A timer thread periodically removed unused connections.
+                             The interval at which this thread runs. All idle 
+                             connections will be removed, while mainataining
+                             the configured steady-pool-size.
+-->
+<!ELEMENT resource-adapter (description?, property*)>
+<!ATTLIST resource-adapter jndi-name                        CDATA     #REQUIRED
+                           max-pool-size                    CDATA     "32"
+                           steady-pool-size                 CDATA     "4" 
+                           max-wait-time-in-millis          CDATA     "10000" 
+                           idle-timeout-in-seconds          CDATA     "1000">
+
+<!-- Perform mapping from principal received during Servlet/EJB 
+     authentication, to credentials accepted by the EIS. This 
+     mapping is optional. The map consists of several 2-tuples
+     map-id is the name of the mapping
+ -->
+<!ELEMENT role-map (description?, map-element*)>
+<!ATTLIST role-map map-id   CDATA  #REQUIRED>
+                
+
+<!-- It is possible to map multiple (server) principal to the 
+     same backend principal. 
+-->
+<!ELEMENT map-element (principal+, backend-principal)>
+
+<!-- Principal of the Servlet and EJB client -->
+<!ELEMENT principal (description?)>
+<!ATTLIST principal user-name CDATA #REQUIRED>
+ 
+<!-- Backend EIS principal -->
+<!ELEMENT backend-principal EMPTY> 
+<!ATTLIST backend-principal user-name  CDATA #REQUIRED
+                            password   CDATA #REQUIRED
+                            credential CDATA #REQUIRED>
+
+<!ELEMENT description (#PCDATA)>
+
+<!-- Syntax for supplying properties as name value pairs -->
+<!ELEMENT property EMPTY>
+<!ATTLIST property name  CDATA  #REQUIRED
+                   value CDATA  #REQUIRED>