First Commit from Source Code Reply

gnpdev/sim/build/building/sim-classes/weblogic/servlet/internal/dd/web-jar.dtd

@@ -0,0 +1,689 @@
+<!--
+The web-app element is the root of the deployment descriptor for
+a web application
+-->
+
+<!ELEMENT web-app (icon?, display-name?, description?,
+distributable?, context-param*, filter*, filter-mapping*, listener*,
+servlet*, servlet-mapping*, session-config?,
+mime-mapping*, welcome-file-list?, error-page*, taglib*,
+resource-env-ref*, resource-ref*, security-constraint*, login-config?,
+security-role*,
+env-entry*, ejb-ref*)>
+
+<!--
+Declares a filter in the web application. The filter is mapped to
+either a servlet or a URL pattern in the filter-mapping element,
+using the filter-name value to reference. Filters can access the
+initialization parameters declared in the deployment descriptor at
+runtime via the FilterConfig interface.
+-->
+<!ELEMENT filter (icon?, filter-name, display-name?, description?,
+filter-class, init-param*)>
+
+<!--
+The logical name of the filter. This name is used to map the filter.
+-->
+<!ELEMENT filter-name (#PCDATA)>
+
+<!--
+The fully qualified classname of the filter.
+-->
+<!ELEMENT filter-class (#PCDATA)>
+
+<!--
+Declaration of the filter mappings in this web application. The
+container uses the filter-mapping declarations to decide which
+filters to apply to a request, and in what order. The container
+matches the request URI to a Servlet in the normal way. To determine
+which filters to apply it matches filter-mapping declarations either
+on servlet-name, or on url-pattern for each filter-mapping element,
+depending on which style is used. The order in which filters are
+invoked is the order in which filter-mapping declarations that match
+a request URI for a servlet appear in the list of filter-mapping
+elements.The filter-name value must be the value of the <filter-name>
+sub-elements of one of the <filter> declarations in the
+deployment descriptor.
+-->
+<!ELEMENT filter-mapping (filter-name, (url-pattern | servlet-name))>
+
+<!--
+The icon element contains a small-icon and a large-icon element
+which specify the location within the web application for a small and
+large image used to represent the web application in a GUI tool. At a
+minimum, tools must accept GIF and JPEG format images.
+-->
+
+<!ELEMENT icon (small-icon?, large-icon?)>
+
+<!--
+The small-icon element contains the location within the web
+application of a file containing a small (16x16 pixel) icon image.
+-->
+
+<!ELEMENT small-icon (#PCDATA)>
+
+<!--
+The large-icon element contains the location within the web
+application of a file containing a large (32x32 pixel) icon image.
+-->
+
+<!ELEMENT large-icon (#PCDATA)>
+
+<!--
+The display-name element contains a short name that is intended
+to be displayed by GUI tools
+-->
+
+<!ELEMENT display-name (#PCDATA)>
+
+<!--
+The description element is used to provide descriptive text about
+the parent element.
+-->
+
+<!ELEMENT description (#PCDATA)>
+
+<!--
+The distributable element, by its presence in a web application
+deployment descriptor, indicates that this web application is
+programmed appropriately to be deployed into a distributed servlet
+container
+-->
+
+<!ELEMENT distributable EMPTY>
+
+<!--
+The context-param element contains the declaration of a web
+application's servlet context initialization parameters.
+-->
+
+<!ELEMENT context-param (param-name, param-value, description?)>
+
+<!--
+The param-name element contains the name of a parameter.
+-->
+
+<!ELEMENT param-name (#PCDATA)>
+
+<!--
+The param-value element contains the value of a parameter.
+-->
+
+<!ELEMENT param-value (#PCDATA)>
+
+<!--
+The listener element indicates the deployment properties for a web
+application listener bean.
+-->
+<!ELEMENT listener (listener-class)>
+
+<!--
+The listener-class element declares a class in the application must
+be registered as a web application listener bean.
+-->
+<!ELEMENT listener-class (#PCDATA)>
+
+<!--
+The servlet element contains the declarative data of a
+servlet. If a jsp-file is specified and the load-on-startup element is
+present, then the JSP should be precompiled and loaded.
+-->
+
+<!ELEMENT servlet (icon?, servlet-name, display-name?, description?,
+(servlet-class|jsp-file), init-param*, load-on-startup?, security-role-ref*)>
+
+<!--
+The servlet-name element contains the canonical name of the
+servlet.
+-->
+
+<!ELEMENT servlet-name (#PCDATA)>
+
+<!--
+The servlet-class element contains the fully qualified class name
+of the servlet.
+-->
+
+<!ELEMENT servlet-class (#PCDATA)>
+
+<!--
+The jsp-file element contains the full path to a JSP file within
+the web application.
+-->
+
+<!ELEMENT jsp-file (#PCDATA)>
+
+<!--
+The init-param element contains a name/value pair as an
+initialization param of the servlet
+-->
+
+<!ELEMENT init-param (param-name, param-value, description?)>
+
+<!--
+The load-on-startup element indicates that this servlet should be
+loaded on the startup of the web application. The optional contents of
+these element must be a positive integer indicating the order in which
+the servlet should be loaded. Lower integers are loaded before higher
+integers. If no value is specified, or if the value specified is not a
+positive integer, the container is free to load it at any time in the
+startup sequence.
+-->
+
+<!ELEMENT load-on-startup (#PCDATA)>
+
+<!--
+The servlet-mapping element defines a mapping between a servlet
+and a url pattern
+-->
+
+<!ELEMENT servlet-mapping (servlet-name, url-pattern)>
+
+<!--
+The url-pattern element contains the url pattern of the
+mapping. Must follow the rules specified in Section 11.2 of the Servlet
+API Specification.
+-->
+
+<!ELEMENT url-pattern (#PCDATA)>
+
+<!--
+The session-config element defines the session parameters for
+this web application.
+-->
+
+<!ELEMENT session-config (session-timeout?)>
+
+<!--
+The session-timeout element defines the default session timeout
+interval for all sessions created in this web application. The
+specified timeout must be expressed in a whole number of minutes.
+-->
+
+<!ELEMENT session-timeout (#PCDATA)>
+
+<!--
+The mime-mapping element defines a mapping between an extension
+and a mime type.
+-->
+
+<!ELEMENT mime-mapping (extension, mime-type)>
+
+<!--
+The extension element contains a string describing an
+extension. example: "txt"
+-->
+
+<!ELEMENT extension (#PCDATA)>
+
+<!--
+The mime-type element contains a defined mime type. example:
+"text/plain"
+-->
+
+<!ELEMENT mime-type (#PCDATA)>
+
+<!--
+The welcome-file-list contains an ordered list of welcome files
+elements.
+-->
+
+<!ELEMENT welcome-file-list (welcome-file+)>
+
+<!--
+The welcome-file element contains file name to use as a default
+welcome file, such as index.html
+-->
+
+<!ELEMENT welcome-file (#PCDATA)>
+
+<!--
+The taglib element is used to describe a JSP tag library.
+-->
+
+<!ELEMENT taglib (taglib-uri, taglib-location)>
+
+<!--
+The taglib-uri element describes a URI, relative to the location
+of the web.xml document, identifying a Tag Library used in the Web
+Application.
+-->
+
+<!ELEMENT taglib-uri (#PCDATA)>
+
+<!--
+the taglib-location element contains the location (as a resource
+relative to the root of the web application) where to find the Tag
+Libary Description file for the tag library.
+-->
+
+<!ELEMENT taglib-location (#PCDATA)>
+
+<!--
+The error-page element contains a mapping between an error code
+or exception type to the path of a resource in the web application
+-->
+
+<!ELEMENT error-page ((error-code | exception-type), location)>
+
+<!--
+The error-code contains an HTTP error code, ex: 404
+-->
+
+<!ELEMENT error-code (#PCDATA)>
+
+<!--
+The exception type contains a fully qualified class name of a
+Java exception type.
+-->
+
+<!ELEMENT exception-type (#PCDATA)>
+
+<!--
+The location element contains the location of the resource in the
+web application
+-->
+
+<!ELEMENT location (#PCDATA)>
+
+<!-- The resource-env-ref element contains a declaration of an
+component's reference to an administered object associated with a
+resource in the component's environment. It consists of an optional
+description, the resource environment reference name, and an indica-tion
+of the resource environment reference type expected by the
+component's code.
+Examples:
+<resource-env-ref>
+<resource-env-ref-name>jms/StockQueue </resource-env-ref-name>
+<resource-env-ref-type>javax.jms.Queue </resource-env-ref-type>
+</resource-env-ref>
+-->
+
+<!ELEMENT resource-env-ref (description?, resource-env-ref-name, resource-env-ref-type)>
+
+<!-- The resource-env-ref-name element specifies the name of a
+resource environment reference; its value is the environment entry
+name used in code.
+-->
+<!ELEMENT resource-env-ref-name (#PCDATA)>
+
+<!-- The resource-env-ref-type element specifies the type of a
+resource environment reference. Web containers in J2EE are required
+to support javax.jms.Topic and javax.jms.Queue
+-->
+<!ELEMENT resource-env-ref-type (#PCDATA)>
+
+<!--
+The resource-ref element contains a declaration of a Web
+Application's reference to an external resource.
+-->
+
+<!ELEMENT resource-ref (description?, res-ref-name, res-type, res-auth,
+res-sharing-scope?)>
+
+<!--
+The res-ref-name element specifies the name of the resource
+factory reference name.
+-->
+
+<!ELEMENT res-ref-name (#PCDATA)>
+
+<!--
+The res-type element specifies the (Java class) type of the data
+source.
+-->
+
+<!ELEMENT res-type (#PCDATA)>
+
+<!--
+The res-auth element indicates whether the application component
+code performs resource signon programmatically or whether the
+container signs onto the resource based on the principle mapping
+information supplied by the deployer. The allowed values are
+<res-auth>Application</res-auth>
+<res-auth>Container</res-auth>
+for those respective cases.
+-->
+
+<!ELEMENT res-auth (#PCDATA)>
+
+<!--
+The res-sharing-scope element specifies whether connections
+obtained through the given resource manager connection factory
+reference can be shared. The value of this element, if specified,
+must be one of the two following: <res-sharing-scope>Shareable</res-sharing-scope>
+<res-sharing-scope>Unshareable</res-sharing-scope> The default value is Shareable.
+-->
+
+<!ELEMENT res-sharing-scope (#PCDATA)>
+
+<!--
+The security-constraint element is used to associate security
+constraints with one or more web resource collections
+-->
+
+<!ELEMENT security-constraint (display-name?, web-resource-collection+,
+auth-constraint?, user-data-constraint?)>
+
+<!--
+The web-resource-collection element is used to identify a subset
+of the resources and HTTP methods on those resources within a web
+application to which a security constraint applies. If no HTTP methods
+are specified, then the security constraint applies to all HTTP
+methods.
+-->
+
+<!ELEMENT web-resource-collection (web-resource-name, description?,
+url-pattern*, http-method*)>
+
+<!--
+The web-resource-name contains the name of this web resource
+collection
+-->
+
+<!ELEMENT web-resource-name (#PCDATA)>
+
+<!--
+The http-method contains an HTTP method (GET | POST |...)
+-->
+
+<!ELEMENT http-method (#PCDATA)>
+
+<!--
+The user-data-constraint element is used to indicate how data
+communicated between the client and container should be protected
+-->
+
+<!ELEMENT user-data-constraint (description?, transport-guarantee)>
+
+<!--
+The transport-guarantee element specifies that the communication
+between client and server should be NONE, INTEGRAL, or
+CONFIDENTIAL. NONE means that the application does not require any
+transport guarantees. A value of INTEGRAL means that the application
+requires that the data sent between the client and server be sent in
+such a way that it can't be changed in transit. CONFIDENTIAL means
+that the application requires that the data be transmitted in a
+fashion that prevents other entities from observing the contents of
+the transmission. In most cases, the presence of the INTEGRAL or
+CONFIDENTIAL flag will indicate that the use of SSL is required.
+-->
+
+<!ELEMENT transport-guarantee (#PCDATA)>
+
+<!--
+The auth-constraint element indicates the user roles that should
+be permitted access to this resource collection. The role used here
+must either in a security-role-ref element, or be the specially
+reserved role-name "*" that is a compact syntax for indicating all
+roles in the web application. If both "*" and rolenames appear, the
+container interprets this as all roles.
+-->
+
+<!ELEMENT auth-constraint (description?, role-name*)>
+
+<!--
+The role-name element contains the name of a security role.
+-->
+
+<!ELEMENT role-name (#PCDATA)>
+
+<!--
+The login-config element is used to configure the authentication
+method that should be used, the realm name that should be used for
+this application, and the attributes that are needed by the form login
+mechanism.
+-->
+
+<!ELEMENT login-config (auth-method?, realm-name?, form-login-config?)>
+
+<!--
+The realm name element specifies the realm name to use in HTTP
+Basic authorization
+-->
+
+<!ELEMENT realm-name (#PCDATA)>
+
+<!--
+The form-login-config element specifies the login and error pages
+that should be used in form based login. If form based authentication
+is not used, these elements are ignored.
+-->
+
+<!ELEMENT form-login-config (form-login-page, form-error-page)>
+
+<!--
+The form-login-page element defines the location in the web app
+where the page that can be used for login can be found
+-->
+
+<!ELEMENT form-login-page (#PCDATA)>
+
+<!--
+The form-error-page element defines the location in the web app
+where the error page that is displayed when login is not successful
+can be found
+-->
+
+<!ELEMENT form-error-page (#PCDATA)>
+
+<!--
+The auth-method element is used to configure the authentication
+mechanism for the web application. As a prerequisite to gaining access
+to any web resources which are protected by an authorization
+constraint, a user must have authenticated using the configured
+mechanism. Legal values for this element are "BASIC", "DIGEST",
+"FORM", or "CLIENT-CERT".
+-->
+
+<!ELEMENT auth-method (#PCDATA)>
+
+<!--
+The security-role element contains the declaration of a security
+role which is used in the security-constraints placed on the web
+application.
+-->
+
+<!ELEMENT security-role (description?, role-name)>
+
+<!--
+The security-role-ref element defines a mapping between the name of
+role called from a Servlet using
+isUserInRole(String name) and the name of a security role defined
+for the web application. For example,
+to map the security role reference "FOO" to the security role with
+role-name "manager" the sytax would
+be:
+<security-role-ref>
+<role-name>FOO</role-name>
+<role-link>manager</manager>
+</security-role-ref>
+In this case if the servlet called by a user belonging to the
+"manager" security role made the API call
+isUserInRole("FOO") the result would be true.
+Since the role-name "*" has a special meaning for authorization
+constraints, its value is not permitted here.
+-->
+
+<!ELEMENT security-role-ref (description?, role-name, role-link)>
+
+<!--
+The role-link element is used to link a security role reference
+to a defined security role. The role-link element must contain the
+name of one of the security roles defined in the security-role
+elements.
+-->
+
+<!ELEMENT role-link (#PCDATA)>
+
+<!--
+The env-entry element contains the declaration of an
+application's environment entry. This element is required to be
+honored on in J2EE compliant servlet containers.
+-->
+
+<!ELEMENT env-entry (description?, env-entry-name, env-entry-value?,
+env-entry-type)>
+
+<!--
+The env-entry-name contains the name of an application's
+environment entry
+-->
+
+<!ELEMENT env-entry-name (#PCDATA)>
+
+<!--
+The env-entry-value element contains the value of an
+application's environment entry
+-->
+
+<!ELEMENT env-entry-value (#PCDATA)>
+
+<!--
+The env-entry-type element contains the fully qualified Java type
+of the environment entry value that is expected by the application
+code. The following are the legal values of env-entry-type:
+java.lang.Boolean, java.lang.String, java.lang.Integer,
+java.lang.Double, java.lang.Float.
+-->
+
+<!ELEMENT env-entry-type (#PCDATA)>
+
+<!--
+The ejb-ref element is used to declare a reference to an
+enterprise bean. 
+-->
+
+<!ELEMENT ejb-ref (description?, ejb-ref-name, ejb-ref-type, home, remote,
+ejb-link?, run-as?)>
+
+<!--
+The ejb-ref-name element contains the name of an EJB
+reference. This is the JNDI name that the servlet code uses to get a
+reference to the enterprise bean.
+-->
+
+<!ELEMENT ejb-ref-name (#PCDATA)>
+
+<!--
+The ejb-ref-type element contains the expected java class type of
+the referenced EJB.
+-->
+
+<!ELEMENT ejb-ref-type (#PCDATA)>
+
+<!--
+The ejb-home element contains the fully qualified name of the
+EJB's home interface
+-->
+
+<!ELEMENT home (#PCDATA)>
+
+<!--
+The ejb-remote element contains the fully qualified name of the
+EJB's remote interface
+-->
+
+<!ELEMENT remote (#PCDATA)>
+
+<!--
+The ejb-link element is used in the ejb-ref element to specify
+that an EJB reference is linked to an EJB in an encompassing Java2
+Enterprise Edition (J2EE) application package. The value of the
+ejb-link element must be the ejb-name of and EJB in the J2EE
+application package.
+-->
+
+<!ELEMENT ejb-link (#PCDATA)>
+
+<!--
+The run-as element must contain the name of a security role defined
+for this web application.
+-->
+<!ELEMENT run-as (#PCDATA)>
+
+<!--
+The ID mechanism is to allow tools to easily make tool-specific
+references to the elements of the deployment descriptor. This allows
+tools that produce additional deployment information (i.e information
+beyond the standard deployment descriptor information) to store the
+non-standard information in a separate file, and easily refer from
+these tools-specific files to the information in the standard web-app
+deployment descriptor.
+-->
+
+<!ATTLIST web-app id ID #IMPLIED>
+<!ATTLIST filter id ID #IMPLIED>
+<!ATTLIST filter-name id ID #IMPLIED>
+<!ATTLIST filter-class id ID #IMPLIED>
+<!ATTLIST filter-mapping id ID #IMPLIED>
+<!ATTLIST icon id ID #IMPLIED>
+<!ATTLIST small-icon id ID #IMPLIED>
+<!ATTLIST large-icon id ID #IMPLIED>
+<!ATTLIST display-name id ID #IMPLIED>
+<!ATTLIST description id ID #IMPLIED>
+<!ATTLIST distributable id ID #IMPLIED>
+<!ATTLIST context-param id ID #IMPLIED>
+<!ATTLIST param-name id ID #IMPLIED>
+<!ATTLIST param-value id ID #IMPLIED>
+<!ATTLIST listener id ID #IMPLIED>
+<!ATTLIST listener-class id ID #IMPLIED>
+<!ATTLIST servlet id ID #IMPLIED>
+<!ATTLIST servlet-name id ID #IMPLIED>
+<!ATTLIST servlet-class id ID #IMPLIED>
+<!ATTLIST jsp-file id ID #IMPLIED>
+<!ATTLIST init-param id ID #IMPLIED>
+<!ATTLIST load-on-startup id ID #IMPLIED>
+<!ATTLIST servlet-mapping id ID #IMPLIED>
+<!ATTLIST url-pattern id ID #IMPLIED>
+<!ATTLIST session-config id ID #IMPLIED>
+<!ATTLIST session-timeout id ID #IMPLIED>
+<!ATTLIST mime-mapping id ID #IMPLIED>
+<!ATTLIST extension id ID #IMPLIED>
+<!ATTLIST mime-type id ID #IMPLIED>
+<!ATTLIST welcome-file-list id ID #IMPLIED>
+<!ATTLIST welcome-file id ID #IMPLIED>
+<!ATTLIST taglib id ID #IMPLIED>
+<!ATTLIST taglib-uri id ID #IMPLIED>
+<!ATTLIST taglib-location id ID #IMPLIED>
+<!ATTLIST error-page id ID #IMPLIED>
+<!ATTLIST error-code id ID #IMPLIED>
+<!ATTLIST exception-type id ID #IMPLIED>
+<!ATTLIST location id ID #IMPLIED>
+<!ATTLIST resource-env-ref id ID #IMPLIED>
+<!ATTLIST resource-env-ref-name id ID #IMPLIED>
+<!ATTLIST resource-env-ref-type id ID #IMPLIED>
+<!ATTLIST resource-ref id ID #IMPLIED>
+<!ATTLIST res-ref-name id ID #IMPLIED>
+<!ATTLIST res-type id ID #IMPLIED>
+<!ATTLIST res-auth id ID #IMPLIED>
+<!ATTLIST res-sharing-scope id ID #IMPLIED>
+<!ATTLIST security-constraint id ID #IMPLIED>
+<!ATTLIST web-resource-collection id ID #IMPLIED>
+<!ATTLIST web-resource-name id ID #IMPLIED>
+<!ATTLIST http-method id ID #IMPLIED>
+<!ATTLIST user-data-constraint id ID #IMPLIED>
+<!ATTLIST transport-guarantee id ID #IMPLIED>
+<!ATTLIST auth-constraint id ID #IMPLIED>
+<!ATTLIST role-name id ID #IMPLIED>
+<!ATTLIST login-config id ID #IMPLIED>
+<!ATTLIST realm-name id ID #IMPLIED>
+<!ATTLIST form-login-config id ID #IMPLIED>
+<!ATTLIST form-login-page id ID #IMPLIED>
+<!ATTLIST form-error-page id ID #IMPLIED>
+<!ATTLIST auth-method id ID #IMPLIED>
+<!ATTLIST security-role id ID #IMPLIED>
+<!ATTLIST security-role-ref id ID #IMPLIED>
+<!ATTLIST role-link id ID #IMPLIED>
+<!ATTLIST env-entry id ID #IMPLIED>
+<!ATTLIST env-entry-name id ID #IMPLIED>
+<!ATTLIST env-entry-value id ID #IMPLIED>
+<!ATTLIST env-entry-type id ID #IMPLIED>
+<!ATTLIST ejb-ref id ID #IMPLIED>
+<!ATTLIST ejb-ref-name id ID #IMPLIED>
+<!ATTLIST ejb-ref-type id ID #IMPLIED>
+<!ATTLIST home id ID #IMPLIED>
+<!ATTLIST remote id ID #IMPLIED>
+<!ATTLIST ejb-link id ID #IMPLIED>
+<!ATTLIST run-as id ID #IMPLIED>

gnpdev/sim/build/building/sim-classes/weblogic/servlet/internal/dd/weblogic-web-jar.dtd

@@ -0,0 +1,545 @@
+<!--
+Copyright (c) 1999-2002 by BEA Systems Inc. All Rights Reserved.
+
+This is the DTD for the Web application deployment parameters that are specific to the WebLogic server.
+
+-->
+
+
+<!-- 
+The weblogic-web-app is the root element of the weblogic component of the
+Web application deployment descriptor 
+-->
+<!ELEMENT weblogic-web-app (description?, weblogic-version?, 
+          security-role-assignment*, reference-descriptor?,
+          session-descriptor?, jsp-descriptor?, auth-filter?,
+	  container-descriptor?, charset-params?, 
+	  virtual-directory-mapping*, url-match-map?,
+	  preprocessor*, preprocessor-mapping*,
+          security-permission?, context-root?,
+          wl-dispatch-policy?)>
+
+<!-- 
+The description element is used to provide text describing the parent element.
+
+Used in: weblogic-web-app
+-->
+<!ELEMENT description (#PCDATA)>
+
+
+<!--
+The weblogic-version specifies the version of WebLogic to which 
+the weblogic-web-app applies.
+
+Used in: weblogic-web-app
+-->
+<!ELEMENT weblogic-version (#PCDATA)>
+
+
+<!--
+The security-role-assigment declares a mapping between an WebApp security role
+and one or more principals in the WebLogic server.
+
+Example:
+   <security-role-assignment>
+     <role-name>
+       PayrollAdmin
+     </role-name>
+     <principal-name>
+       Tanya
+     </principal-name>
+     <principal-name>
+       Fred
+     </principal-name>
+     <principal-name>
+       system
+     </principal-name>
+   </security-role-assignment>
+
+Used in: weblogic-web-app
+-->
+<!ELEMENT security-role-assignment (role-name, principal-name+)>
+
+<!--
+The role-name element contains the name of a security role.
+
+Used in: security-role-assignment
+-->
+<!ELEMENT role-name (#PCDATA)>
+
+
+<!--
+The principal-name element contains the name of a principal.
+
+Used in: security-role-assignment
+-->
+<!ELEMENT principal-name (#PCDATA)>
+
+
+<!--
+The reference-descriptor specifies a list of resource-descriptions and 
+the ejb-reference-description that describe the resources used in the application.
+
+ Used in: weblogic-web-app
+
+ Example:
+     <reference-descriptor>
+        <resource-description>
+	  <res-ref-name>
+	    jdbc/EmployeeAppDB
+	  </res-ref-name>
+	  <jndi-name>
+	    weblogic.jdbc.jts.ejbPool
+	  </jndi-name>
+        </resource-description>
+        <resource-description>
+	  <res-ref-name>
+	    jdbc/PersonDB
+	  </res-ref-name>
+	  <jndi-name>
+	    weblogic.jdbc.jts.personPool
+	  </jndi-name>
+        </resource-description>
+        <ejb-reference-description>
+	  <ejb-ref-name>
+	    AdminBean
+	  </ejb-ref-name>
+          <jndi-name>
+	    payroll.AdminBean
+          </jndi-name>
+        </ejb-reference-description>
+     </reference-descriptor>
+-->
+<!ELEMENT reference-descriptor (
+  resource-description*,
+  ejb-reference-description*
+)>
+
+
+<!--
+The ejb-reference-description is used to map the JNDI name in the WebLogic 
+server of an EJB that is referenced by the application in an ejb-reference.
+
+ Used in: reference-descriptor
+
+ Example:
+     <ejb-reference-description>
+	<ejb-ref-name>
+	  AdminBean
+	</ejb-ref-name>
+        <jndi-name>
+	  payroll.AdminBean
+        </jndi-name>
+     </ejb-reference-description>
+-->
+<!ELEMENT ejb-reference-description (ejb-ref-name, jndi-name)>
+
+
+<!--
+The ejb-ref-name element contains the name of an EJB reference. The
+EJB reference is an entry in the enterprise bean's environment.
+
+Used in: ejb-reference-description
+
+Example: 
+<ejb-ref-name>ejb/EmplRecords</ejb-ref-name>
+
+-->
+<!ELEMENT ejb-ref-name (#PCDATA)>
+
+
+<!-- 
+This specifies a jndi-name for a bean, resource or reference.
+
+Used in: weblogic-enterprise-bean, reference-descriptor
+-->
+<!ELEMENT jndi-name (#PCDATA)>
+
+
+<!--
+By specifying virtual directory mappings you can change the 
+default docroot for certain requests. virtual-directory-mapping 
+defines a mapping between url pattern and a new doc root
+-->
+<!ELEMENT virtual-directory-mapping (local-path, url-pattern+)>
+
+<!--
+The local-path element specifies a physical location on the disk.
+-->
+<!ELEMENT local-path (#PCDATA)>
+
+<!--
+The url-pattern element contains the url pattern of the mapping. Must follow the rules specified in Section 11.2 of the Servlet API Specification.
+-->
+<!ELEMENT url-pattern (#PCDATA)>
+
+<!--
+Example:
+
+  <virtual-directory-mapping>
+     <local-path>c:/usr/gifs</local-path>
+     <url-pattern>/images/*</url-pattern>
+     <url-pattern>*.jpg</url-pattern>
+  </virtual-directory-mapping>
+
+  <virtual-directory-mapping>
+     <local-path>c:/usr/jsps/common.jar</local-path>
+     <url-pattern>*.jsp</url-pattern>
+  </virtual-directory-mapping>
+-->
+
+
+
+<!--
+The resource-description is used to map the JNDI name in the WebLogic 
+server of a server resource that is used by a bean to an EJB resource 
+reference.
+
+ Used in: reference-descriptor
+
+ Example:
+     <resource-description>
+	<res-ref-name>
+	  jdbc/EmployeeAppDB
+	</res-ref-name>
+        <jndi-name>
+	  weblogic.jdbc.jts.ejbPool
+        </jndi-name>
+     </resource-description>
+-->
+<!ELEMENT resource-description (res-ref-name, jndi-name)>
+
+
+<!--
+The res-ref-name element specifies the name of a resource factory
+reference.
+
+Used in: reference-descriptor
+
+-->
+<!ELEMENT res-ref-name (#PCDATA)>
+
+<!--
+The sesson-descriptor specifies a list of session-params
+for servlet sessions.
+
+ Used in: weblogic-web-app
+
+ Example:
+     <session-descriptor>
+       <session-param>
+         <param-name>
+           FOO
+         </param-name>
+         <param-value>
+           BAR
+         </param-value>
+       </session-param>
+     </session-descriptor>
+
+  Valid Param Names:
+    CacheSize
+    ConsoleMainAttribute
+    CookieComment
+    CookieDomain
+    CookieMaxAgeSecs
+    CookieName
+    EncodeSessionIdInQueryParams
+    CookiePath
+    CookiesEnabled
+    CacheSessionCookie
+    CookieSecure
+    IDLength
+    InvalidationIntervalSecs
+    JDBCConnectionTimeoutSecs
+    JDBCColumnName_MaxInactiveInterval
+    PersistentStoreCookieName
+    PersistentStoreDir
+    PersistentStorePool
+    PersistentDataSourceJNDIName
+    PersistentSessionFlushInterval
+    PersistentSessionFlushThreshold
+    PersistentAsyncQueueTimeout
+    PersistentStoreShared
+    PersistentStoreTable
+    PersistentStoreType
+    SessionDebuggable
+    SwapIntervalSecs
+    TimeoutSecs
+    TrackingEnabled
+    URLRewritingEnabled
+
+-->
+<!ELEMENT session-descriptor (
+  session-param*
+)>
+
+<!--
+The session-param is to define parameters for servlet sessions.
+
+ Used in: session-descriptor
+
+ Example:
+      <session-param>
+        <param-name>
+          ConsoleMainAttribute
+        </param-name>
+        <param-value>
+          MyMainAttribute
+        </param-value>
+      </session-param>
+-->
+<!ELEMENT session-param (param-name,param-value)>
+
+<!--
+The jsp-descriptor specifies a list of jsp-params
+for servlet jsps.
+
+ Used in: weblogic-web-app
+
+ Example:
+     <jsp-descriptor>
+       <jsp-param>
+         <param-name>
+           verbose
+         </param-name>
+         <param-value>
+           false
+         </param-value>
+       </jsp-param>
+     </jsp-descriptor>
+
+  Valid Param Names:
+    compileCommand
+    compileFlags
+    compilerClass
+    compilerSupportsEncoding
+    defaultFilename
+    encoding
+    keepgenerated
+    noTryBlocks
+    packagePrefix
+    pageCheckSeconds
+    precompile
+    precompileContinue
+    verbose
+    workingDir
+
+-->
+<!ELEMENT jsp-descriptor (
+  jsp-param*
+)>
+
+<!--
+The jsp-param is to define parameters for servlet jsps.
+
+ Used in: jsp-descriptor
+
+ Example:
+      <jsp-param>
+        <param-name>
+          FOO
+        </param-name>
+        <param-value>
+          BAR
+        </param-value>
+      </jsp-param>
+-->
+<!ELEMENT jsp-param (param-name,param-value)>
+
+<!-- 
+This specifies a param-name
+
+Used in: session-param, jsp-param
+-->
+<!ELEMENT param-name (#PCDATA)>
+
+<!-- 
+This specifies a param-value
+
+Used in: session-param, jsp-param
+-->
+<!ELEMENT param-value (#PCDATA)>
+
+<!-- 
+This specifies an authentication filter HttpServlet class
+-->
+<!ELEMENT auth-filter (#PCDATA)>
+
+<!--
+The container-descriptor specifies a list of parameters
+that affect the behavior of the web application
+Used in: weblogic-web-app
+-->
+<!ELEMENT container-descriptor (
+  check-auth-on-forward?,
+  redirect-content-type?,
+  redirect-content?,
+  redirect-with-absolute-url?
+)>
+
+<!--
+The check-auth-on-forward element, by its presence in a weblogic
+deployment descriptor, indicates that the request dispatcher will
+check authorization when a request is forwarded
+-->
+<!ELEMENT check-auth-on-forward EMPTY>
+
+
+<!--
+If the redirect-content-type element is set, then
+the servlet container will set that type on the response
+for internal redirects (e.g., for welcome files).
+-->
+<!ELEMENT redirect-content-type (#PCDATA)>
+
+<!--
+If the redirect-content element is set, then
+the servlet container will use that as the
+value for the user readable data used in a 
+redirect.
+-->
+<!ELEMENT redirect-content (#PCDATA)>
+
+<!--
+If the redirect-with-absolute-url element is set to false, 
+then the servlet container will not convert 
+the relative url to the absolute url in the location 
+header in a redirect.
+-->
+<!ELEMENT redirect-with-absolute-url (#PCDATA)>
+
+<!--
+The charset-params element parameters related
+do what codeset will be used for non-unicode
+operations.
+Used in: weblogic-web-app
+-->
+<!ELEMENT charset-params (input-charset*,charset-mapping*)>
+
+<!--
+The input-charset element defines what charset will be
+used to process POST data for a particular resource
+-->
+<!ELEMENT input-charset (resource-path,java-charset-name)>
+
+<!--
+The charset-mapping element defines a mapping between
+IANA names and Java names for charsets
+-->
+<!ELEMENT charset-mapping (iana-charset-name,java-charset-name)>
+
+<!ELEMENT resource-path (#PCDATA)>
+<!ELEMENT java-charset-name (#PCDATA)>
+<!ELEMENT iana-charset-name (#PCDATA)>
+
+<!--
+Using url-match-map you can specify your own 
+class for url pattern matching. By default
+weblogic uses weblogic.servlet.utils.URLMatchMap, 
+which is based on J2EE standards. So using 
+url-match-map you could overide default behaviour or 
+write your own url pattern matcher. The new class 
+has to implement weblogic.servlet.utils.URLMapping
+interface.
+-->
+
+<!ELEMENT url-match-map (#PCDATA)>
+
+<!--
+The preprocessor element contains the declarative data of a preprocessor.
+ -->
+
+<!ELEMENT preprocessor (preprocessor-name, preprocessor-class)>
+
+<!--
+The preprocessor-name element contains the canonical name of the preprocessor.
+-->
+
+<!ELEMENT preprocessor-name (#PCDATA)>
+
+
+<!--
+The preprocessor-class element contains the fully qualified class name of the preprocessor.
+-->
+
+<!ELEMENT preprocessor-class (#PCDATA)>
+
+<!--
+The preprocessor-mapping element defines a mapping between a preprocessor and a url pattern
+-->
+
+<!ELEMENT preprocessor-mapping (preprocessor-name, url-pattern)>
+
+<!--
+The element security permission specifies a security permission that
+is associated with a J2EE Sandbox.
+
+Used in: weblogic-web-app
+-->
+<!ELEMENT security-permission (description?, security-permission-spec)>
+
+
+<!--
+The element permission-spec specifies a single security permission based
+on the Security policy file syntax. Refer to the following URL for
+Sun's implementation of the security permission specification:
+
+http://java.sun.com/j2se/1.3/docs/guide/security/PolicyFiles.html#FileSyntax
+
+ignore the "codebase" and "signedBy" clauses.
+
+e.g:
+ <security-permission-spec>
+    grant { permission java.net.SocketPermission "*", "resolve" };
+ </security-permission-spec>
+
+Used in: security-permission
+-->
+<!ELEMENT security-permission-spec (#PCDATA)>
+
+<!--
+The context root of this web application. This is useful for
+standalone web applications. Normally, you would specify the
+context-root in the META-INF/application.xml file of a J2EE
+EAR, however, if this is a standalone web application, you
+can specify the value here.
+
+If this value is set, it takes precedence over the setting
+in application.xml.
+-->
+<!ELEMENT context-root (#PCDATA)>
+
+<!--
+The wl-dispatch-policy can be used to assign the webapp to
+a configured execute queue by identifying the execute queue
+name. This webapp level param can be overridden at the
+individual servlet/jsp level. eg:
+  <servlet>
+    ...
+    <init-param>
+      <param-name>wl-dispatch-policy</param-name>
+      <param-value>CriticalAppQueue</param-value>
+    </init-param>
+  </servlet>
+-->
+<!ELEMENT wl-dispatch-policy (#PCDATA)>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+

gnpdev/sim/build/building/sim-classes/weblogic/servlet/internal/dd/weblogic700-web-jar.dtd

@@ -0,0 +1,733 @@
+<!--
+Copyright (c) 1999-2002 by BEA Systems Inc. All Rights Reserved.
+
+This is the DTD for the Web application deployment parameters that are
+specific to the WebLogic server in WebLogic 7.0.0.
+
+-->
+
+
+<!-- 
+The weblogic-web-app is the root element of the weblogic component of the
+Web application deployment descriptor 
+-->
+<!ELEMENT weblogic-web-app (description?, weblogic-version?, 
+          security-role-assignment*, run-as-role-assignment*, 
+          reference-descriptor?, session-descriptor?, jsp-descriptor?, 
+          auth-filter?, container-descriptor?, charset-params?, 
+	  virtual-directory-mapping*, url-match-map?,
+	  preprocessor*, preprocessor-mapping*,
+          security-permission?, context-root?, 
+          wl-dispatch-policy?, servlet-descriptor*,
+          init-as*, destroy-as*)>
+
+<!-- 
+The description element is used to provide text describing the parent element.
+
+Used in: weblogic-web-app
+-->
+<!ELEMENT description (#PCDATA)>
+
+
+<!--
+The weblogic-version specifies the version of WebLogic to which 
+the weblogic-web-app applies.
+
+Used in: weblogic-web-app
+-->
+<!ELEMENT weblogic-version (#PCDATA)>
+
+
+<!--
+The security-role-assigment declares a mapping between an WebApp security role
+and one or more principals in the WebLogic server.
+
+Example:
+   <security-role-assignment>
+     <role-name>PayrollAdmin</role-name>
+     <principal-name>Tanya</principal-name>
+     <principal-name>Fred</principal-name>
+     <principal-name>system</principal-name>
+   </security-role-assignment>
+
+Example to mark a given role as a externally defined role 
+(also known as global-role):
+   <security-role-assignment>
+     <role-name>roleadmin</role-name>
+     <externally-defined/>
+   </security-role-assignment>
+
+Note: The global-role tag has been replaced with the externally-defined tag.
+
+-->
+<!ELEMENT security-role-assignment (role-name, principal-name*, 
+externally-defined?, global-role?)>
+
+<!--
+run-as-role-assignment is used to map a given run-as role-name defined
+in web.xml to a valid username in the system. The value can be
+overridden for a given servlet by the run-as-principal-name element
+in the servlet-descriptor. Note that if the run-as-role-assignment is
+absent for a given rolename then the webapp container will choose
+the first principal-name defined in the security-role-assignment,
+if present, else will use the rolename as the run-as-role-assignment.
+
+Example to specify a given principal ("joe") to be used for run-as
+   <run-as-role-assignment>
+     <role-name>RunAsRoleName</role-name>
+     <run-as-principal-name>joe</run-as-principal-name>
+   </run-as-role-assignment>
+
+Used in: weblogic-web-app
+
+Since: 8.1
+-->
+<!ELEMENT run-as-role-assignment (role-name, run-as-principal-name)>
+
+<!--
+The role-name element contains the name of a security role.
+
+Used in: security-role-assignment
+-->
+<!ELEMENT role-name (#PCDATA)>
+
+<!--
+The principal-name element contains the name of a principal.
+
+Used in: security-role-assignment
+-->
+<!ELEMENT principal-name (#PCDATA)>
+
+<!--
+DEPRECATED: The global-role element is now deprecated and will 
+be removed in a future version of WebLogic. Please use the 
+externally-defined element instead.
+
+The global-role element indicates that a particular security role
+is defined 'globally' in a security realm.  Because the security role
+and it's principal-name mapping is defined elsewhere, principal-names
+are not to be specified in the deployment descriptor.  This tag
+is used as an indicative placeholder instead of a set of <principal-name> 
+elements.
+
+Used in: security-role-assignment
+
+Since:  7.0SP01
+
+-->
+<!ELEMENT global-role EMPTY>
+
+<!--
+The externally-defined element indicates that a particular security role
+is defined 'globally' in a security realm.  Because the security role
+and it's principal-name mapping is defined elsewhere, principal-names
+are not to be specified in the deployment descriptor.  This tag
+is used as an indicative placeholder instead of a set of <principal-name> 
+elements.
+
+Used in: security-role-assignment
+
+Since:  8.1
+-->
+<!ELEMENT externally-defined EMPTY>
+
+<!--
+The reference-descriptor specifies a list of resource-descriptions and 
+the ejb-reference-description that describe the resources used in the application.
+
+ Used in: weblogic-web-app
+
+ Example:
+     <reference-descriptor>
+        <resource-description>
+	  <res-ref-name>
+	    jdbc/EmployeeAppDB
+	  </res-ref-name>
+	  <jndi-name>
+	    weblogic.jdbc.jts.ejbPool
+	  </jndi-name>
+        </resource-description>
+        <resource-description>
+	  <res-ref-name>
+	    jdbc/PersonDB
+	  </res-ref-name>
+	  <jndi-name>
+	    weblogic.jdbc.jts.personPool
+	  </jndi-name>
+        </resource-description>
+        <ejb-reference-description>
+	  <ejb-ref-name>
+	    AdminBean
+	  </ejb-ref-name>
+          <jndi-name>
+	    payroll.AdminBean
+          </jndi-name>
+        </ejb-reference-description>
+     </reference-descriptor>
+-->
+<!ELEMENT reference-descriptor (
+  resource-description*,
+  resource-env-description*,
+  ejb-reference-description*
+)>
+
+
+<!--
+The ejb-reference-description is used to map the JNDI name in the WebLogic 
+server of an EJB that is referenced by the application in an ejb-reference.
+
+ Used in: reference-descriptor
+
+ Example:
+     <ejb-reference-description>
+	<ejb-ref-name>
+	  AdminBean
+	</ejb-ref-name>
+        <jndi-name>
+	  payroll.AdminBean
+        </jndi-name>
+     </ejb-reference-description>
+-->
+<!ELEMENT ejb-reference-description (ejb-ref-name, jndi-name)>
+
+
+<!--
+The ejb-ref-name element contains the name of an EJB reference. The
+EJB reference is an entry in the enterprise bean's environment.
+
+Used in: ejb-reference-description
+
+Example: 
+<ejb-ref-name>ejb/EmplRecords</ejb-ref-name>
+
+-->
+<!ELEMENT ejb-ref-name (#PCDATA)>
+
+
+<!-- 
+This specifies a jndi-name for a bean, resource or reference.
+
+Used in: weblogic-enterprise-bean, reference-descriptor
+-->
+<!ELEMENT jndi-name (#PCDATA)>
+
+
+<!--
+By specifying virtual directory mappings you can change the 
+default docroot for certain requests. virtual-directory-mapping 
+defines a mapping between url pattern and a new doc root
+-->
+<!ELEMENT virtual-directory-mapping (local-path, url-pattern+)>
+
+<!--
+The local-path element specifies a physical location on the disk.
+-->
+<!ELEMENT local-path (#PCDATA)>
+
+<!--
+The url-pattern element contains the url pattern of the mapping. Must follow the rules specified in Section 11.2 of the Servlet API Specification.
+-->
+<!ELEMENT url-pattern (#PCDATA)>
+
+<!--
+Example:
+
+  <virtual-directory-mapping>
+     <local-path>c:/usr/gifs</local-path>
+     <url-pattern>/images/*</url-pattern>
+     <url-pattern>*.jpg</url-pattern>
+  </virtual-directory-mapping>
+
+  <virtual-directory-mapping>
+     <local-path>c:/usr/jsps/common.jar</local-path>
+     <url-pattern>*.jsp</url-pattern>
+  </virtual-directory-mapping>
+-->
+
+
+
+<!--
+The resource-description is used to map the JNDI name in the WebLogic 
+server of a server resource that is used by a bean to an EJB resource 
+reference.
+
+ Used in: reference-descriptor
+
+ Example:
+     <resource-description>
+	<res-ref-name>
+	  jdbc/EmployeeAppDB
+	</res-ref-name>
+        <jndi-name>
+	  weblogic.jdbc.jts.ejbPool
+        </jndi-name>
+     </resource-description>
+-->
+<!ELEMENT resource-description (res-ref-name, jndi-name)>
+
+<!--
+The res-env-ref-name element specifies the name of a resource environment
+reference.
+
+Used in: resource-env-description
+
+-->
+<!ELEMENT res-env-ref-name (#PCDATA)>
+
+<!--
+The res-ref-name element specifies the name of a resource factory
+reference.
+
+Used in: reference-descriptor
+
+-->
+<!ELEMENT res-ref-name (#PCDATA)>
+
+<!--
+The resource-env-description element is used to map a resource-env-ref,
+declared in the ejb-jar.xml deployment descriptor, to the JNDI name of the 
+server resource it represents.
+
+ Used in: reference-descriptor
+
+ Example:
+     <resource-env-description>
+	<res-env-ref-name>
+	  jms/StockInfo
+	</res-env-ref-name>
+        <jndi-name>
+	  mystockapp.jms.queue.nasdaq
+        </jndi-name>
+     </resource-description>
+-->
+<!ELEMENT resource-env-description (res-env-ref-name, jndi-name)>
+
+<!--
+The sesson-descriptor specifies a list of session-params
+for servlet sessions.
+
+ Used in: weblogic-web-app
+
+ Example:
+     <session-descriptor>
+       <session-param>
+         <param-name>
+           FOO
+         </param-name>
+         <param-value>
+           BAR
+         </param-value>
+       </session-param>
+     </session-descriptor>
+
+  Valid Param Names:
+    CacheSize  // Used by jdbc/file based session persistence
+               // default's to 256. Set to 0 in order to turn off
+               // caching.
+    ConsoleMainAttribute
+    CookieComment
+    CookieDomain
+    CookieMaxAgeSecs
+    CookieName
+    CookiePath
+    CookiesEnabled
+    IDLength
+    InvalidationIntervalSecs
+    JDBCConnectionTimeoutSecs
+    PersistentStoreCookieName
+    PersistentStoreDir
+    PersistentStorePool
+    PersistentStoreType
+    SwapIntervalSecs
+    TimeoutSecs
+    TrackingEnabled
+    URLRewritingEnabled
+
+-->
+<!ELEMENT session-descriptor (
+  session-param*
+)>
+
+<!--
+The session-param is to define parameters for servlet sessions.
+
+ Used in: session-descriptor
+
+ Example:
+      <session-param>
+        <param-name>
+          ConsoleMainAttribute
+        </param-name>
+        <param-value>
+          MyMainAttribute
+        </param-value>
+      </session-param>
+-->
+<!ELEMENT session-param (param-name,param-value)>
+
+<!--
+The jsp-descriptor specifies a list of jsp-params
+for servlet jsps.
+
+ Used in: weblogic-web-app
+
+ Example:
+     <jsp-descriptor>
+       <jsp-param>
+         <param-name>
+           verbose
+         </param-name>
+         <param-value>
+           false
+         </param-value>
+       </jsp-param>
+     </jsp-descriptor>
+
+  Valid Param Names:
+    compileCommand
+    compileFlags
+    compilerClass
+    compilerSupportsEncoding
+    defaultFilename
+    encoding
+    keepgenerated
+    noTryBlocks
+    packagePrefix
+    pageCheckSeconds
+    precompile
+    verbose
+    workingDir
+    debug
+    printNulls
+
+-->
+<!ELEMENT jsp-descriptor (
+  jsp-param*
+)>
+
+<!--
+The jsp-param is to define parameters for servlet jsps.
+
+ Used in: jsp-descriptor
+
+ Example:
+      <jsp-param>
+        <param-name>
+          FOO
+        </param-name>
+        <param-value>
+          BAR
+        </param-value>
+      </jsp-param>
+-->
+<!ELEMENT jsp-param (param-name,param-value)>
+
+<!-- 
+This specifies a param-name
+
+Used in: session-param, jsp-param
+-->
+<!ELEMENT param-name (#PCDATA)>
+
+<!-- 
+This specifies a param-value
+
+Used in: session-param, jsp-param
+-->
+<!ELEMENT param-value (#PCDATA)>
+
+<!-- 
+This specifies an authentication filter HttpServlet class
+-->
+<!ELEMENT auth-filter (#PCDATA)>
+
+<!--
+The container-descriptor specifies a list of parameters
+that affect the behavior of the web application
+Used in: weblogic-web-app
+-->
+<!ELEMENT container-descriptor (
+  check-auth-on-forward?,
+  redirect-content-type?,
+  redirect-content?,
+  redirect-with-absolute-url?,
+  index-directory-enabled?, 
+  index-directory-sort-by?, 
+  servlet-reload-check-secs?,
+  single-threaded-servlet-pool-size?,
+  session-monitoring-enabled?,
+  prefer-web-inf-classes?
+)>
+
+<!--
+The check-auth-on-forward element, by its presence in a weblogic
+deployment descriptor, indicates that the request dispatcher will
+check authorization when a request is forwarded
+-->
+<!ELEMENT check-auth-on-forward EMPTY>
+
+
+<!--
+If the redirect-content-type element is set, then
+the servlet container will set that type on the response
+for internal redirects (e.g., for welcome files).
+-->
+<!ELEMENT redirect-content-type (#PCDATA)>
+
+<!--
+If the redirect-content element is set, then
+the servlet container will use that as the
+value for the user readable data used in a 
+redirect.
+-->
+<!ELEMENT redirect-content (#PCDATA)>
+
+<!--
+If the redirect-with-absolute-url element is set to false, 
+then the servlet container will not convert 
+the relative url to the absolute url in the location 
+header in a redirect.
+-->
+<!ELEMENT redirect-with-absolute-url (#PCDATA)>
+
+<!--
+Whether or not to automatically generate an HTML
+directory listing if no suitable index file is found.
+Defaults to "false". Value specified via console
+will be given precedence over this setting.
+-->
+<!ELEMENT index-directory-enabled (#PCDATA)>
+
+<!--
+This element defines the order of sorting for the directory 
+listing generated by weblogic.servlet.FileServlet. Valid values
+are "NAME" (default), "LAST_MODIFIED" and "SIZE".
+-->
+<!ELEMENT index-directory-sort-by (#PCDATA)>
+
+<!--
+How often WebLogic checks whether a servlet has been
+modified, and if so reloads it. -1 is never reload, 0 is 
+always reload. Default to 1 second. Value specified via 
+console will be given precedence over this setting.
+-->
+<!ELEMENT servlet-reload-check-secs (#PCDATA)>
+
+<!--
+Defines the size of the pool used for SingleThreadModle 
+instance pools. Defaults to 5. Value specified via 
+console will be given precedence over this setting.
+-->
+<!ELEMENT single-threaded-servlet-pool-size (#PCDATA)>
+
+<!--
+If true, then runtime mbeans will be created for sessions,
+otherwise, they will not. Defaults to false. Value specified 
+via console will be given precedence over this setting.
+-->
+<!ELEMENT session-monitoring-enabled (#PCDATA)>
+
+<!--
+If true, classes located in the WEB-INF directory of a 
+web-app will be loaded in preference to classes loaded 
+in the application or system classloader. Defaults to 
+false. Value specified via console will be given 
+precedence over this setting.
+-->
+<!ELEMENT prefer-web-inf-classes (#PCDATA)>
+
+<!--
+The charset-params element parameters related
+do what codeset will be used for non-unicode
+operations.
+Used in: weblogic-web-app
+-->
+<!ELEMENT charset-params (input-charset*,charset-mapping*)>
+
+<!--
+The input-charset element defines what charset will be
+used to process POST data for a particular resource
+-->
+<!ELEMENT input-charset (resource-path,java-charset-name)>
+
+<!--
+The charset-mapping element defines a mapping between
+IANA names and Java names for charsets
+-->
+<!ELEMENT charset-mapping (iana-charset-name,java-charset-name)>
+
+<!ELEMENT resource-path (#PCDATA)>
+<!ELEMENT java-charset-name (#PCDATA)>
+<!ELEMENT iana-charset-name (#PCDATA)>
+
+<!--
+Using url-match-map you can specify your own 
+class for url pattern matching. By default
+weblogic uses weblogic.servlet.utils.URLMatchMap, 
+which is based on J2EE standards. So using 
+url-match-map you could overide default behaviour or 
+write your own url pattern matcher. The new class 
+has to implement weblogic.servlet.utils.URLMapping
+interface.
+-->
+
+<!ELEMENT url-match-map (#PCDATA)>
+
+
+<!--
+The preprocessor element contains the declarative data of a preprocessor.
+ -->
+
+<!ELEMENT preprocessor (preprocessor-name, preprocessor-class)>
+
+<!--
+The preprocessor-name element contains the canonical name of the preprocessor.
+-->
+
+<!ELEMENT preprocessor-name (#PCDATA)>
+
+
+<!--
+The preprocessor-class element contains the fully qualified class name of the preprocessor.
+-->
+
+<!ELEMENT preprocessor-class (#PCDATA)>
+
+<!--
+The preprocessor-mapping element defines a mapping between a preprocessor and a url pattern
+-->
+
+<!ELEMENT preprocessor-mapping (preprocessor-name, url-pattern)>
+
+<!--
+The element security permission specifies a security permission that
+is associated with a J2EE Sandbox.
+
+Used in: weblogic-web-app
+-->
+<!ELEMENT security-permission (description?, security-permission-spec)>
+
+
+<!--
+The element permission-spec specifies a single security permission based
+on the Security policy file syntax. Refer to the following URL for
+Sun's implementation of the security permission specification:
+
+http://java.sun.com/j2se/1.3/docs/guide/security/PolicyFiles.html#FileSyntax
+
+ignore the "codebase" and "signedBy" clauses.
+
+e.g:
+ <security-permission-spec>
+    grant { permission java.net.SocketPermission "*", "resolve" };
+ </security-permission-spec>
+
+Used in: security-permission
+-->
+<!ELEMENT security-permission-spec (#PCDATA)>
+
+<!--
+The context root of this web application. This is useful for
+standalone web applications. Normally, you would specify the
+context-root in the META-INF/application.xml file of a J2EE
+EAR, however, if this is a standalone web application, you
+can specify the value here.
+
+If this value is set, it takes precedence over the setting
+in application.xml.
+-->
+<!ELEMENT context-root (#PCDATA)>
+
+<!--
+The wl-dispatch-policy can be used to assign the webapp to 
+a configured execute queue by identifying the execute queue 
+name. This webapp level param can be overridden at the 
+individual servlet/jsp level by per-servlet-dispatch-policy.
+-->
+<!ELEMENT wl-dispatch-policy (#PCDATA)>
+
+<!--
+The servlet-descriptor aggregates the servlet specific
+elements.
+
+Since: 8.1
+-->
+<!ELEMENT servlet-descriptor (servlet-name, run-as-principal-name?, 
+init-as-principal-name?, destroy-as-principal-name?, dispatch-policy?)>
+
+<!--
+servlet-name is the servlet-name as defined in web.xml's 
+servlet element.
+
+Used in: servlet-descriptor
+-->
+<!ELEMENT servlet-name (#PCDATA)>
+
+<!--
+The run-as-principal-name element contains the name of a principal
+against the run-as role-name defined in web.xml.
+
+Used in: run-as-role-assignment and servlet-descriptor
+-->
+<!ELEMENT run-as-principal-name (#PCDATA)>
+
+<!--
+init-as-principal-name is equivalent to run-as-principal-name 
+for the init method for servlets. The identity specified here 
+should be a valid username in the system. If init-as-principal-name
+is not specified the container will use the run-as-principal-name.
+
+Used in: servlet-descriptor
+-->
+<!ELEMENT init-as-principal-name (#PCDATA)>
+
+<!--
+destroy-as-principal-name is equivalent to run-as-principal-name 
+for the destroy method for servlets. The identity specified here 
+should be a valid username in the system. If destroy-as-principal-name
+is not specified the container will use the run-as-principal-name.
+
+Used in: servlet-descriptor
+-->
+<!ELEMENT destroy-as-principal-name (#PCDATA)>
+
+<!--
+The dispatch-policy element can be used to assign a given
+servlet to a configured execute-queue by identifying the
+execute queue name. This setting overrides the webapp
+level dispatch policy defined by wl-dispatch-policy.
+
+Used in: servlet-descriptor
+-->
+<!ELEMENT dispatch-policy (#PCDATA)>
+
+<!--
+DEPRECATED: The init-as element has been deprecated and has been
+replaced with the init-as-principal-name tag in the servlet-descriptor.
+
+This is equivalent to <run-as> for init method for servlets.
+example:
+  <init-as>
+    <servlet-name>FooServlet</servlet-name>
+    <principal-name>joe</principal-name>
+  </init-as>
+
+Since: 700sp1
+-->
+<!ELEMENT init-as (servlet-name, principal-name)>
+
+<!--
+DEPRECATED: The destroy-as element has been deprecated and has been
+replaced with the destroy-as-principal-name tag in the servlet-descriptor.
+
+This is equivalent to <run-as> for destroy method for servlets.
+example:
+  <destroy-as>
+    <servlet-name>BarServlet</servlet-name>
+    <principal-name>bob</principal-name>
+  </destroy-as>
+
+Since: 700sp1
+-->
+<!ELEMENT destroy-as (servlet-name, principal-name)>
+

gnpdev/sim/build/building/sim-classes/weblogic/servlet/internal/dd/weblogic810-web-jar.dtd

@@ -0,0 +1,762 @@
+<!--
+Copyright (c) 1999-2002 by BEA Systems Inc. All Rights Reserved.
+
+This is the DTD for the Web application deployment parameters that are
+specific to the WebLogic server in WebLogic 8.1.0.
+
+-->
+
+
+<!-- 
+The weblogic-web-app is the root element of the weblogic component of the
+Web application deployment descriptor 
+-->
+<!ELEMENT weblogic-web-app (description?, weblogic-version?, 
+          security-role-assignment*, run-as-role-assignment*, 
+          reference-descriptor?, session-descriptor?, jsp-descriptor?, 
+          auth-filter?, container-descriptor?, charset-params?, 
+	  virtual-directory-mapping*, url-match-map?,
+	  preprocessor*, preprocessor-mapping*,
+          security-permission?, context-root?, 
+          wl-dispatch-policy?, servlet-descriptor*,
+          init-as*, destroy-as*)>
+
+<!-- 
+The description element is used to provide text describing the parent element.
+
+Used in: weblogic-web-app
+-->
+<!ELEMENT description (#PCDATA)>
+
+
+<!--
+The weblogic-version specifies the version of WebLogic to which 
+the weblogic-web-app applies.
+
+Used in: weblogic-web-app
+-->
+<!ELEMENT weblogic-version (#PCDATA)>
+
+
+<!--
+The security-role-assigment declares a mapping between an WebApp security role
+and one or more principals in the WebLogic server.
+
+Example:
+   <security-role-assignment>
+     <role-name>PayrollAdmin</role-name>
+     <principal-name>Tanya</principal-name>
+     <principal-name>Fred</principal-name>
+     <principal-name>system</principal-name>
+   </security-role-assignment>
+
+Example to mark a given role as a externally defined role 
+(also known as global-role):
+   <security-role-assignment>
+     <role-name>roleadmin</role-name>
+     <externally-defined/>
+   </security-role-assignment>
+
+Note: The global-role tag has been replaced with the externally-defined tag.
+
+-->
+<!ELEMENT security-role-assignment (role-name, principal-name*, 
+externally-defined?, global-role?)>
+
+<!--
+run-as-role-assignment is used to map a given run-as role-name defined
+in web.xml to a valid username in the system. The value can be
+overridden for a given servlet by the run-as-principal-name element
+in the servlet-descriptor. Note that if the run-as-role-assignment is
+absent for a given rolename then the webapp container will choose
+the first principal-name defined in the security-role-assignment,
+if present, else will use the rolename as the run-as-role-assignment.
+
+Example to specify a given principal ("joe") to be used for run-as
+   <run-as-role-assignment>
+     <role-name>RunAsRoleName</role-name>
+     <run-as-principal-name>joe</run-as-principal-name>
+   </run-as-role-assignment>
+
+Used in: weblogic-web-app
+
+Since: 8.1
+-->
+<!ELEMENT run-as-role-assignment (role-name, run-as-principal-name)>
+
+<!--
+The role-name element contains the name of a security role.
+
+Used in: security-role-assignment
+-->
+<!ELEMENT role-name (#PCDATA)>
+
+<!--
+The principal-name element contains the name of a principal.
+
+Used in: security-role-assignment
+-->
+<!ELEMENT principal-name (#PCDATA)>
+
+<!--
+DEPRECATED: The global-role element is now deprecated and will 
+be removed in a future version of WebLogic. Please use the 
+externally-defined element instead.
+
+The global-role element indicates that a particular security role
+is defined 'globally' in a security realm.  Because the security role
+and it's principal-name mapping is defined elsewhere, principal-names
+are not to be specified in the deployment descriptor.  This tag
+is used as an indicative placeholder instead of a set of <principal-name> 
+elements.
+
+Used in: security-role-assignment
+
+Since:  7.0SP01
+
+-->
+<!ELEMENT global-role EMPTY>
+
+<!--
+The externally-defined element indicates that a particular security role
+is defined 'globally' in a security realm.  Because the security role
+and it's principal-name mapping is defined elsewhere, principal-names
+are not to be specified in the deployment descriptor.  This tag
+is used as an indicative placeholder instead of a set of <principal-name> 
+elements.
+
+Used in: security-role-assignment
+
+Since:  8.1
+-->
+<!ELEMENT externally-defined EMPTY>
+
+<!--
+The reference-descriptor specifies a list of resource-descriptions and 
+the ejb-reference-description that describe the resources used in the application.
+
+ Used in: weblogic-web-app
+
+ Example:
+     <reference-descriptor>
+        <resource-description>
+	  <res-ref-name>
+	    jdbc/EmployeeAppDB
+	  </res-ref-name>
+	  <jndi-name>
+	    weblogic.jdbc.jts.ejbPool
+	  </jndi-name>
+        </resource-description>
+        <resource-description>
+	  <res-ref-name>
+	    jdbc/PersonDB
+	  </res-ref-name>
+	  <jndi-name>
+	    weblogic.jdbc.jts.personPool
+	  </jndi-name>
+        </resource-description>
+        <ejb-reference-description>
+	  <ejb-ref-name>
+	    AdminBean
+	  </ejb-ref-name>
+          <jndi-name>
+	    payroll.AdminBean
+          </jndi-name>
+        </ejb-reference-description>
+     </reference-descriptor>
+-->
+<!ELEMENT reference-descriptor (
+  resource-description*,
+  resource-env-description*,
+  ejb-reference-description*
+)>
+
+
+<!--
+The ejb-reference-description is used to map the JNDI name in the WebLogic 
+server of an EJB that is referenced by the application in an ejb-reference.
+
+ Used in: reference-descriptor
+
+ Example:
+     <ejb-reference-description>
+	<ejb-ref-name>
+	  AdminBean
+	</ejb-ref-name>
+        <jndi-name>
+	  payroll.AdminBean
+        </jndi-name>
+     </ejb-reference-description>
+-->
+<!ELEMENT ejb-reference-description (ejb-ref-name, jndi-name)>
+
+
+<!--
+The ejb-ref-name element contains the name of an EJB reference. The
+EJB reference is an entry in the enterprise bean's environment.
+
+Used in: ejb-reference-description
+
+Example: 
+<ejb-ref-name>ejb/EmplRecords</ejb-ref-name>
+
+-->
+<!ELEMENT ejb-ref-name (#PCDATA)>
+
+
+<!-- 
+This specifies a jndi-name for a bean, resource or reference.
+
+Used in: weblogic-enterprise-bean, reference-descriptor
+-->
+<!ELEMENT jndi-name (#PCDATA)>
+
+
+<!--
+By specifying virtual directory mappings you can change the 
+default docroot for certain requests. virtual-directory-mapping 
+defines a mapping between url pattern and a new doc root
+-->
+<!ELEMENT virtual-directory-mapping (local-path, url-pattern+)>
+
+<!--
+The local-path element specifies a physical location on the disk.
+-->
+<!ELEMENT local-path (#PCDATA)>
+
+<!--
+The url-pattern element contains the url pattern of the mapping. Must follow the rules specified in Section 11.2 of the Servlet API Specification.
+-->
+<!ELEMENT url-pattern (#PCDATA)>
+
+<!--
+Example:
+
+  <virtual-directory-mapping>
+     <local-path>c:/usr/gifs</local-path>
+     <url-pattern>/images/*</url-pattern>
+     <url-pattern>*.jpg</url-pattern>
+  </virtual-directory-mapping>
+
+  <virtual-directory-mapping>
+     <local-path>c:/usr/jsps/common.jar</local-path>
+     <url-pattern>*.jsp</url-pattern>
+  </virtual-directory-mapping>
+-->
+
+
+
+<!--
+The resource-description is used to map the JNDI name in the WebLogic 
+server of a server resource that is used by a bean to an EJB resource 
+reference.
+
+ Used in: reference-descriptor
+
+ Example:
+     <resource-description>
+	<res-ref-name>
+	  jdbc/EmployeeAppDB
+	</res-ref-name>
+        <jndi-name>
+	  weblogic.jdbc.jts.ejbPool
+        </jndi-name>
+     </resource-description>
+-->
+<!ELEMENT resource-description (res-ref-name, jndi-name)>
+
+<!--
+The res-env-ref-name element specifies the name of a resource environment
+reference.
+
+Used in: resource-env-description
+
+-->
+<!ELEMENT res-env-ref-name (#PCDATA)>
+
+<!--
+The res-ref-name element specifies the name of a resource factory
+reference.
+
+Used in: reference-descriptor
+
+-->
+<!ELEMENT res-ref-name (#PCDATA)>
+
+<!--
+The resource-env-description element is used to map a resource-env-ref,
+declared in the ejb-jar.xml deployment descriptor, to the JNDI name of the 
+server resource it represents.
+
+ Used in: reference-descriptor
+
+ Example:
+     <resource-env-description>
+	<res-env-ref-name>
+	  jms/StockInfo
+	</res-env-ref-name>
+        <jndi-name>
+	  mystockapp.jms.queue.nasdaq
+        </jndi-name>
+     </resource-description>
+-->
+<!ELEMENT resource-env-description (res-env-ref-name, jndi-name)>
+
+<!--
+The sesson-descriptor specifies a list of session-params
+for servlet sessions.
+
+ Used in: weblogic-web-app
+
+ Example:
+     <session-descriptor>
+       <session-param>
+         <param-name>
+           FOO
+         </param-name>
+         <param-value>
+           BAR
+         </param-value>
+       </session-param>
+     </session-descriptor>
+
+  Valid Param Names:
+    CacheSize  // Used by jdbc/file based session persistence
+               // default's to 256. Set to 0 in order to turn off
+               // caching.
+    ConsoleMainAttribute
+    CookieComment
+    CookieDomain
+    CookieMaxAgeSecs
+    CookieName
+    CookiePath
+    CookiesEnabled
+    IDLength
+    InvalidationIntervalSecs
+    JDBCConnectionTimeoutSecs
+    PersistentStoreCookieName
+    PersistentStoreDir
+    PersistentStorePool
+    PersistentStoreType
+    SwapIntervalSecs
+    TimeoutSecs
+    TrackingEnabled
+    URLRewritingEnabled
+
+-->
+<!ELEMENT session-descriptor (
+  session-param*
+)>
+
+<!--
+The session-param is to define parameters for servlet sessions.
+
+ Used in: session-descriptor
+
+ Example:
+      <session-param>
+        <param-name>
+          ConsoleMainAttribute
+        </param-name>
+        <param-value>
+          MyMainAttribute
+        </param-value>
+      </session-param>
+-->
+<!ELEMENT session-param (param-name,param-value)>
+
+<!--
+The jsp-descriptor specifies a list of jsp-params
+for servlet jsps.
+
+ Used in: weblogic-web-app
+
+ Example:
+     <jsp-descriptor>
+       <jsp-param>
+         <param-name>
+           verbose
+         </param-name>
+         <param-value>
+           false
+         </param-value>
+       </jsp-param>
+     </jsp-descriptor>
+
+  Valid Param Names:
+    compileCommand
+    compileFlags
+    compilerClass
+    compilerSupportsEncoding
+    defaultFilename
+    encoding
+    keepgenerated
+    noTryBlocks
+    packagePrefix
+    pageCheckSeconds
+    precompile
+    verbose
+    workingDir
+    debug
+    printNulls
+
+-->
+<!ELEMENT jsp-descriptor (
+  jsp-param*
+)>
+
+<!--
+The jsp-param is to define parameters for servlet jsps.
+
+ Used in: jsp-descriptor
+
+ Example:
+      <jsp-param>
+        <param-name>
+          FOO
+        </param-name>
+        <param-value>
+          BAR
+        </param-value>
+      </jsp-param>
+-->
+<!ELEMENT jsp-param (param-name,param-value)>
+
+<!-- 
+This specifies a param-name
+
+Used in: session-param, jsp-param
+-->
+<!ELEMENT param-name (#PCDATA)>
+
+<!-- 
+This specifies a param-value
+
+Used in: session-param, jsp-param
+-->
+<!ELEMENT param-value (#PCDATA)>
+
+<!-- 
+This specifies an authentication filter HttpServlet class
+-->
+<!ELEMENT auth-filter (#PCDATA)>
+
+<!--
+The container-descriptor specifies a list of parameters
+that affect the behavior of the web application
+Used in: weblogic-web-app
+-->
+<!ELEMENT container-descriptor (
+  check-auth-on-forward?,
+  filter-dispatched-requests-enabled?, 
+  redirect-content-type?,
+  redirect-content?,
+  redirect-with-absolute-url?,
+  index-directory-enabled?, 
+  index-directory-sort-by?, 
+  servlet-reload-check-secs?,
+  single-threaded-servlet-pool-size?,
+  session-monitoring-enabled?,
+  save-sessions-enabled?,
+  prefer-web-inf-classes?,
+  default-mime-type?
+)>
+
+<!--
+The check-auth-on-forward element, by its presence in a weblogic
+deployment descriptor, indicates that the request dispatcher will
+check authorization when a request is forwarded
+-->
+<!ELEMENT check-auth-on-forward EMPTY>
+
+
+<!--
+DEPRECATED: The redirect-content-type element is deprecated since 8.1
+and will be removed in a future version of WebLogic.
+
+If the redirect-content-type element is set, then
+the servlet container will set that type on the response
+for internal redirects (e.g., for welcome files).
+-->
+<!ELEMENT redirect-content-type (#PCDATA)>
+
+<!--
+DEPRECATED: The redirect-content element is deprecated since 8.1
+and will be removed in a future version of WebLogic.
+
+If the redirect-content element is set, then
+the servlet container will use that as the
+value for the user readable data used in a 
+redirect.
+-->
+<!ELEMENT redirect-content (#PCDATA)>
+
+<!--
+If the redirect-with-absolute-url element is set to false, 
+then the servlet container will not convert 
+the relative url to the absolute url in the location 
+header in a redirect.
+-->
+<!ELEMENT redirect-with-absolute-url (#PCDATA)>
+
+<!--
+Whether or not apply filters to dispatched requests
+Defaults to "true". 
+-->
+<!ELEMENT filter-dispatched-requests-enabled (#PCDATA)>
+
+<!--
+Whether or not to automatically generate an HTML
+directory listing if no suitable index file is found.
+Defaults to "false". Value specified via console
+will be given precedence over this setting.
+-->
+<!ELEMENT index-directory-enabled (#PCDATA)>
+
+<!--
+This element defines the order of sorting for the directory 
+listing generated by weblogic.servlet.FileServlet. Valid values
+are "NAME" (default), "LAST_MODIFIED" and "SIZE".
+-->
+<!ELEMENT index-directory-sort-by (#PCDATA)>
+
+<!--
+How often WebLogic checks whether a servlet has been
+modified, and if so reloads it. -1 is never reload, 0 is 
+always reload. Default to 1 second. Value specified via 
+console will be given precedence over this setting.
+-->
+<!ELEMENT servlet-reload-check-secs (#PCDATA)>
+
+<!--
+Defines the size of the pool used for SingleThreadModle 
+instance pools. Defaults to 5. Value specified via 
+console will be given precedence over this setting.
+-->
+<!ELEMENT single-threaded-servlet-pool-size (#PCDATA)>
+
+<!--
+If true, then runtime mbeans will be created for sessions,
+otherwise, they will not. Defaults to false. Value specified 
+via console will be given precedence over this setting.
+-->
+<!ELEMENT session-monitoring-enabled (#PCDATA)>
+
+<!--
+If true, classes located in the WEB-INF directory of a 
+web-app will be loaded in preference to classes loaded 
+in the application or system classloader. Defaults to 
+false. Value specified via console will be given 
+precedence over this setting.
+-->
+<!ELEMENT prefer-web-inf-classes (#PCDATA)>
+
+<!--
+The charset-params element parameters related
+do what codeset will be used for non-unicode
+operations.
+Used in: weblogic-web-app
+-->
+<!ELEMENT charset-params (input-charset*,charset-mapping*)>
+
+<!--
+The input-charset element defines what charset will be
+used to process POST data for a particular resource
+-->
+<!ELEMENT input-charset (resource-path,java-charset-name)>
+
+<!--
+The charset-mapping element defines a mapping between
+IANA names and Java names for charsets
+-->
+<!ELEMENT charset-mapping (iana-charset-name,java-charset-name)>
+
+<!ELEMENT resource-path (#PCDATA)>
+<!ELEMENT java-charset-name (#PCDATA)>
+<!ELEMENT iana-charset-name (#PCDATA)>
+
+<!--
+Using url-match-map you can specify your own 
+class for url pattern matching. By default
+weblogic uses weblogic.servlet.utils.URLMatchMap, 
+which is based on J2EE standards. So using 
+url-match-map you could overide default behaviour or 
+write your own url pattern matcher. The new class 
+has to implement weblogic.servlet.utils.URLMapping
+interface.
+-->
+
+<!ELEMENT url-match-map (#PCDATA)>
+
+
+<!--
+The preprocessor element contains the declarative data of a preprocessor.
+ -->
+
+<!ELEMENT preprocessor (preprocessor-name, preprocessor-class)>
+
+<!--
+The preprocessor-name element contains the canonical name of the preprocessor.
+-->
+
+<!ELEMENT preprocessor-name (#PCDATA)>
+
+
+<!--
+The preprocessor-class element contains the fully qualified class name of the preprocessor.
+-->
+
+<!ELEMENT preprocessor-class (#PCDATA)>
+
+<!--
+The preprocessor-mapping element defines a mapping between a preprocessor and a url pattern
+-->
+
+<!ELEMENT preprocessor-mapping (preprocessor-name, url-pattern)>
+
+<!--
+The element security permission specifies a security permission that
+is associated with a J2EE Sandbox.
+
+Used in: weblogic-web-app
+-->
+<!ELEMENT security-permission (description?, security-permission-spec)>
+
+
+<!--
+The element permission-spec specifies a single security permission based
+on the Security policy file syntax. Refer to the following URL for
+Sun's implementation of the security permission specification:
+
+http://java.sun.com/j2se/1.3/docs/guide/security/PolicyFiles.html#FileSyntax
+
+ignore the "codebase" and "signedBy" clauses.
+
+e.g:
+ <security-permission-spec>
+    grant { permission java.net.SocketPermission "*", "resolve" };
+ </security-permission-spec>
+
+Used in: security-permission
+-->
+<!ELEMENT security-permission-spec (#PCDATA)>
+
+<!--
+The context root of this web application. This is useful for
+standalone web applications. Normally, you would specify the
+context-root in the META-INF/application.xml file of a J2EE
+EAR, however, if this is a standalone web application, you
+can specify the value here.
+
+If context-root has been specified in application.xml, it takes 
+precedence over the setting in weblogic.xml.
+-->
+<!ELEMENT context-root (#PCDATA)>
+
+<!--
+The wl-dispatch-policy can be used to assign the webapp to 
+a configured execute queue by identifying the execute queue 
+name. This webapp level param can be overridden at the 
+individual servlet/jsp level by per-servlet-dispatch-policy.
+-->
+<!ELEMENT wl-dispatch-policy (#PCDATA)>
+
+<!--
+The servlet-descriptor aggregates the servlet specific
+elements.
+
+Since: 8.1
+-->
+<!ELEMENT servlet-descriptor (servlet-name, run-as-principal-name?, 
+init-as-principal-name?, destroy-as-principal-name?, dispatch-policy?)>
+
+<!--
+servlet-name is the servlet-name as defined in web.xml's 
+servlet element.
+
+Used in: servlet-descriptor
+-->
+<!ELEMENT servlet-name (#PCDATA)>
+
+<!--
+The run-as-principal-name element contains the name of a principal
+against the run-as role-name defined in web.xml.
+
+Used in: run-as-role-assignment and servlet-descriptor
+-->
+<!ELEMENT run-as-principal-name (#PCDATA)>
+
+<!--
+init-as-principal-name is equivalent to run-as-principal-name 
+for the init method for servlets. The identity specified here 
+should be a valid username in the system. If init-as-principal-name
+is not specified the container will use the run-as-principal-name.
+
+Used in: servlet-descriptor
+-->
+<!ELEMENT init-as-principal-name (#PCDATA)>
+
+<!--
+destroy-as-principal-name is equivalent to run-as-principal-name 
+for the destroy method for servlets. The identity specified here 
+should be a valid username in the system. If destroy-as-principal-name
+is not specified the container will use the run-as-principal-name.
+
+Used in: servlet-descriptor
+-->
+<!ELEMENT destroy-as-principal-name (#PCDATA)>
+
+<!--
+The dispatch-policy element can be used to assign a given
+servlet to a configured execute-queue by identifying the
+execute queue name. This setting overrides the webapp
+level dispatch policy defined by wl-dispatch-policy.
+
+Used in: servlet-descriptor
+-->
+<!ELEMENT dispatch-policy (#PCDATA)>
+
+<!--
+DEPRECATED: The init-as element has been deprecated and has been
+replaced with the init-as-principal-name tag in the servlet-descriptor.
+
+This is equivalent to <run-as> for init method for servlets.
+example:
+  <init-as>
+    <servlet-name>FooServlet</servlet-name>
+    <principal-name>joe</principal-name>
+  </init-as>
+
+Since: 700sp1
+-->
+<!ELEMENT init-as (servlet-name, principal-name)>
+
+<!--
+DEPRECATED: The destroy-as element has been deprecated and has been
+replaced with the destroy-as-principal-name tag in the servlet-descriptor.
+
+This is equivalent to <run-as> for destroy method for servlets.
+example:
+  <destroy-as>
+    <servlet-name>BarServlet</servlet-name>
+    <principal-name>bob</principal-name>
+  </destroy-as>
+
+Since: 700sp1
+-->
+<!ELEMENT destroy-as (servlet-name, principal-name)>
+
+<!--
+The default mime type to be used for all extensions without 
+an explicit Mime map in web.xml
+-->
+<!ELEMENT default-mime-type (#PCDATA)>
+
+<!--
+This setting controls whether session data is cleaned up during 
+redeploy or undeploy. It affects memory and replicated sessions.
+Setting the value to true means session data is saved. Setting to
+false means session data will be destroyed when the web app is
+redeployed or undeployed. The default is false.
+-->
+<!ELEMENT save-sessions-enabled (#PCDATA)>