[jenkins-winstone] 02/14: Refreshed the patches
Emmanuel Bourg
ebourg-guest at moszumanska.debian.org
Fri Sep 5 15:23:22 UTC 2014
This is an automated email from the git hooks/post-receive script.
ebourg-guest pushed a commit to branch master
in repository jenkins-winstone.
commit e8e84a82928840a976df7d269ec249137ef29c7a
Author: Emmanuel Bourg <ebourg at apache.org>
Date: Fri Sep 5 14:41:24 2014 +0200
Refreshed the patches
---
debian/changelog | 5 +-
debian/patches/java8-compatibility.patch | 50 +-
debian/patches/series | 1 -
debian/patches/specification-resources.patch | 10425 -------------------------
4 files changed, 29 insertions(+), 10452 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 937e197..671e75a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,9 @@
-jenkins-winstone (0.9.10-jenkins-47+dfsg-3) UNRELEASED; urgency=medium
+jenkins-winstone (2.3-1) UNRELEASED; urgency=medium
* Team upload.
+ * New upstream release
+ - Removed specification-resources.patch (no longer needed)
+ - Refreshed java8-compatibility.patch
* Use XZ compression for the upstream tarball
-- Emmanuel Bourg <ebourg at apache.org> Fri, 05 Sep 2014 13:39:33 +0200
diff --git a/debian/patches/java8-compatibility.patch b/debian/patches/java8-compatibility.patch
index 0df9eec..c1a79e3 100644
--- a/debian/patches/java8-compatibility.patch
+++ b/debian/patches/java8-compatibility.patch
@@ -4,35 +4,35 @@ Description: Do not create a self signed certificate every time the HTTPS connec
sun.security.tools.keytool package.
Author: Emmanuel Bourg <ebourg at apache.org>
Forwarded: https://github.com/jenkinsci/winstone/pull/15
---- a/src/java/winstone/ssl/HttpsListener.java
-+++ b/src/java/winstone/ssl/HttpsListener.java
-@@ -29,7 +29,6 @@
-
+--- a/src/java/winstone/HttpsConnectorFactory.java
++++ b/src/java/winstone/HttpsConnectorFactory.java
+@@ -13,7 +13,6 @@
+ import org.eclipse.jetty.util.ssl.SslContextFactory;
import sun.security.util.DerInputStream;
import sun.security.util.DerValue;
-import sun.security.x509.CertAndKeyGen;
import sun.security.x509.X500Name;
- import winstone.HostGroup;
- import winstone.HttpListener;
-@@ -109,20 +108,7 @@
- keystore.load(null);
- keystore.setKeyEntry("hudson", key, password, new Certificate[]{cert});
- } else {
-- // use self-signed certificate
-- this.password = "changeit".toCharArray();
-- System.out.println("Using one-time self-signed certificate");
+ import winstone.cmdline.Option;
+
+@@ -94,20 +93,7 @@
+ keystore.load(null);
+ keystore.setKeyEntry("hudson", key, password, new Certificate[]{cert});
+ } else {
+- // use self-signed certificate
+- this.password = "changeit".toCharArray();
+- System.out.println("Using one-time self-signed certificate");
-
-- CertAndKeyGen ckg = new CertAndKeyGen("RSA", "SHA1WithRSA", null);
-- ckg.generate(1024);
-- PrivateKey privKey = ckg.getPrivateKey();
+- CertAndKeyGen ckg = new CertAndKeyGen("RSA", "SHA1WithRSA", null);
+- ckg.generate(1024);
+- PrivateKey privKey = ckg.getPrivateKey();
-
-- X500Name xn = new X500Name("Test site", "Unknown", "Unknown", "Unknown");
-- X509Certificate cert = ckg.getSelfCertificate(xn, 3650L * 24 * 60 * 60);
+- X500Name xn = new X500Name("Test site", "Unknown", "Unknown", "Unknown");
+- X509Certificate cert = ckg.getSelfCertificate(xn, 3650L * 24 * 60 * 60);
-
-- keystore = KeyStore.getInstance("JKS");
-- keystore.load(null);
-- keystore.setKeyEntry("hudson", privKey, password, new Certificate[]{cert});
-+ throw new WinstoneException("SSL certificate not found, please specify a keystore or an OpenSSL certificate");
- }
- } catch (GeneralSecurityException e) {
- throw (IOException)new IOException("Failed to handle keys").initCause(e);
+- keystore = KeyStore.getInstance("JKS");
+- keystore.load(null);
+- keystore.setKeyEntry("hudson", privKey, password, new Certificate[]{cert});
++ throw new WinstoneException("SSL certificate not found, please specify a keystore or an OpenSSL certificate");
+ }
+ } catch (GeneralSecurityException e) {
+ throw (IOException)new IOException("Failed to handle keys").initCause(e);
diff --git a/debian/patches/series b/debian/patches/series
index ab4d7f1..04ddc90 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1 @@
-specification-resources.patch
java8-compatibility.patch
diff --git a/debian/patches/specification-resources.patch b/debian/patches/specification-resources.patch
deleted file mode 100644
index ecc5869..0000000
--- a/debian/patches/specification-resources.patch
+++ /dev/null
@@ -1,10425 +0,0 @@
-Description: Winstone ships a number of non-DFSG compliant resources
- for specifications around JEE - Sun did release these under compatible
- licenses (this patch).
-Author: James Page <james.page at ubuntu.com>
-Forwarded: not-needed
-
-Index: jenkins-winstone/src/conf/javax/servlet/resources/XMLSchema.dtd
-===================================================================
---- /dev/null 1970-01-01 00:00:00.000000000 +0000
-+++ jenkins-winstone/src/conf/javax/servlet/resources/XMLSchema.dtd 2012-04-26 11:45:47.794315763 +0100
-@@ -0,0 +1,402 @@
-+<!-- DTD for XML Schemas: Part 1: Structures
-+ Public Identifier: "-//W3C//DTD XMLSCHEMA 200102//EN"
-+ Official Location: http://www.w3.org/2001/XMLSchema.dtd -->
-+<!-- $Id: XMLSchema.dtd,v 1.31 2001/10/24 15:50:16 ht Exp $ -->
-+<!-- Note this DTD is NOT normative, or even definitive. --> <!--d-->
-+<!-- prose copy in the structures REC is the definitive version --> <!--d-->
-+<!-- (which shouldn't differ from this one except for this --> <!--d-->
-+<!-- comment and entity expansions, but just in case) --> <!--d-->
-+<!-- With the exception of cases with multiple namespace
-+ prefixes for the XML Schema namespace, any XML document which is
-+ not valid per this DTD given redefinitions in its internal subset of the
-+ 'p' and 's' parameter entities below appropriate to its namespace
-+ declaration of the XML Schema namespace is almost certainly not
-+ a valid schema. -->
-+
-+<!-- The simpleType element and its constituent parts
-+ are defined in XML Schema: Part 2: Datatypes -->
-+<!ENTITY % xs-datatypes PUBLIC 'datatypes' 'datatypes.dtd' >
-+
-+<!ENTITY % p 'xs:'> <!-- can be overriden in the internal subset of a
-+ schema document to establish a different
-+ namespace prefix -->
-+<!ENTITY % s ':xs'> <!-- if %p is defined (e.g. as foo:) then you must
-+ also define %s as the suffix for the appropriate
-+ namespace declaration (e.g. :foo) -->
-+<!ENTITY % nds 'xmlns%s;'>
-+
-+<!-- Define all the element names, with optional prefix -->
-+<!ENTITY % schema "%p;schema">
-+<!ENTITY % complexType "%p;complexType">
-+<!ENTITY % complexContent "%p;complexContent">
-+<!ENTITY % simpleContent "%p;simpleContent">
-+<!ENTITY % extension "%p;extension">
-+<!ENTITY % element "%p;element">
-+<!ENTITY % unique "%p;unique">
-+<!ENTITY % key "%p;key">
-+<!ENTITY % keyref "%p;keyref">
-+<!ENTITY % selector "%p;selector">
-+<!ENTITY % field "%p;field">
-+<!ENTITY % group "%p;group">
-+<!ENTITY % all "%p;all">
-+<!ENTITY % choice "%p;choice">
-+<!ENTITY % sequence "%p;sequence">
-+<!ENTITY % any "%p;any">
-+<!ENTITY % anyAttribute "%p;anyAttribute">
-+<!ENTITY % attribute "%p;attribute">
-+<!ENTITY % attributeGroup "%p;attributeGroup">
-+<!ENTITY % include "%p;include">
-+<!ENTITY % import "%p;import">
-+<!ENTITY % redefine "%p;redefine">
-+<!ENTITY % notation "%p;notation">
-+
-+<!-- annotation elements -->
-+<!ENTITY % annotation "%p;annotation">
-+<!ENTITY % appinfo "%p;appinfo">
-+<!ENTITY % documentation "%p;documentation">
-+
-+<!-- Customisation entities for the ATTLIST of each element type.
-+ Define one of these if your schema takes advantage of the
-+ anyAttribute='##other' in the schema for schemas -->
-+
-+<!ENTITY % schemaAttrs ''>
-+<!ENTITY % complexTypeAttrs ''>
-+<!ENTITY % complexContentAttrs ''>
-+<!ENTITY % simpleContentAttrs ''>
-+<!ENTITY % extensionAttrs ''>
-+<!ENTITY % elementAttrs ''>
-+<!ENTITY % groupAttrs ''>
-+<!ENTITY % allAttrs ''>
-+<!ENTITY % choiceAttrs ''>
-+<!ENTITY % sequenceAttrs ''>
-+<!ENTITY % anyAttrs ''>
-+<!ENTITY % anyAttributeAttrs ''>
-+<!ENTITY % attributeAttrs ''>
-+<!ENTITY % attributeGroupAttrs ''>
-+<!ENTITY % uniqueAttrs ''>
-+<!ENTITY % keyAttrs ''>
-+<!ENTITY % keyrefAttrs ''>
-+<!ENTITY % selectorAttrs ''>
-+<!ENTITY % fieldAttrs ''>
-+<!ENTITY % includeAttrs ''>
-+<!ENTITY % importAttrs ''>
-+<!ENTITY % redefineAttrs ''>
-+<!ENTITY % notationAttrs ''>
-+<!ENTITY % annotationAttrs ''>
-+<!ENTITY % appinfoAttrs ''>
-+<!ENTITY % documentationAttrs ''>
-+
-+<!ENTITY % complexDerivationSet "CDATA">
-+ <!-- #all or space-separated list drawn from derivationChoice -->
-+<!ENTITY % blockSet "CDATA">
-+ <!-- #all or space-separated list drawn from
-+ derivationChoice + 'substitution' -->
-+
-+<!ENTITY % mgs '%all; | %choice; | %sequence;'>
-+<!ENTITY % cs '%choice; | %sequence;'>
-+<!ENTITY % formValues '(qualified|unqualified)'>
-+
-+
-+<!ENTITY % attrDecls '((%attribute;| %attributeGroup;)*,(%anyAttribute;)?)'>
-+
-+<!ENTITY % particleAndAttrs '((%mgs; | %group;)?, %attrDecls;)'>
-+
-+<!-- This is used in part2 -->
-+<!ENTITY % restriction1 '((%mgs; | %group;)?)'>
-+
-+%xs-datatypes;
-+
-+<!-- the duplication below is to produce an unambiguous content model
-+ which allows annotation everywhere -->
-+<!ELEMENT %schema; ((%include; | %import; | %redefine; | %annotation;)*,
-+ ((%simpleType; | %complexType;
-+ | %element; | %attribute;
-+ | %attributeGroup; | %group;
-+ | %notation; ),
-+ (%annotation;)*)* )>
-+<!ATTLIST %schema;
-+ targetNamespace %URIref; #IMPLIED
-+ version CDATA #IMPLIED
-+ %nds; %URIref; #FIXED 'http://www.w3.org/2001/XMLSchema'
-+ xmlns CDATA #IMPLIED
-+ finalDefault %complexDerivationSet; ''
-+ blockDefault %blockSet; ''
-+ id ID #IMPLIED
-+ elementFormDefault %formValues; 'unqualified'
-+ attributeFormDefault %formValues; 'unqualified'
-+ xml:lang CDATA #IMPLIED
-+ %schemaAttrs;>
-+<!-- Note the xmlns declaration is NOT in the Schema for Schemas,
-+ because at the Infoset level where schemas operate,
-+ xmlns(:prefix) is NOT an attribute! -->
-+<!-- The declaration of xmlns is a convenience for schema authors -->
-+
-+<!-- The id attribute here and below is for use in external references
-+ from non-schemas using simple fragment identifiers.
-+ It is NOT used for schema-to-schema reference, internal or
-+ external. -->
-+
-+<!-- a type is a named content type specification which allows attribute
-+ declarations-->
-+<!-- -->
-+
-+<!ELEMENT %complexType; ((%annotation;)?,
-+ (%simpleContent;|%complexContent;|
-+ %particleAndAttrs;))>
-+
-+<!ATTLIST %complexType;
-+ name %NCName; #IMPLIED
-+ id ID #IMPLIED
-+ abstract %boolean; #IMPLIED
-+ final %complexDerivationSet; #IMPLIED
-+ block %complexDerivationSet; #IMPLIED
-+ mixed (true|false) 'false'
-+ %complexTypeAttrs;>
-+
-+<!-- particleAndAttrs is shorthand for a root type -->
-+<!-- mixed is disallowed if simpleContent, overriden if complexContent
-+ has one too. -->
-+
-+<!-- If anyAttribute appears in one or more referenced attributeGroups
-+ and/or explicitly, the intersection of the permissions is used -->
-+
-+<!ELEMENT %complexContent; ((%annotation;)?, (%restriction;|%extension;))>
-+<!ATTLIST %complexContent;
-+ mixed (true|false) #IMPLIED
-+ id ID #IMPLIED
-+ %complexContentAttrs;>
-+
-+<!-- restriction should use the branch defined above, not the simple
-+ one from part2; extension should use the full model -->
-+
-+<!ELEMENT %simpleContent; ((%annotation;)?, (%restriction;|%extension;))>
-+<!ATTLIST %simpleContent;
-+ id ID #IMPLIED
-+ %simpleContentAttrs;>
-+
-+<!-- restriction should use the simple branch from part2, not the
-+ one defined above; extension should have no particle -->
-+
-+<!ELEMENT %extension; ((%annotation;)?, (%particleAndAttrs;))>
-+<!ATTLIST %extension;
-+ base %QName; #REQUIRED
-+ id ID #IMPLIED
-+ %extensionAttrs;>
-+
-+<!-- an element is declared by either:
-+ a name and a type (either nested or referenced via the type attribute)
-+ or a ref to an existing element declaration -->
-+
-+<!ELEMENT %element; ((%annotation;)?, (%complexType;| %simpleType;)?,
-+ (%unique; | %key; | %keyref;)*)>
-+<!-- simpleType or complexType only if no type|ref attribute -->
-+<!-- ref not allowed at top level -->
-+<!ATTLIST %element;
-+ name %NCName; #IMPLIED
-+ id ID #IMPLIED
-+ ref %QName; #IMPLIED
-+ type %QName; #IMPLIED
-+ minOccurs %nonNegativeInteger; #IMPLIED
-+ maxOccurs CDATA #IMPLIED
-+ nillable %boolean; #IMPLIED
-+ substitutionGroup %QName; #IMPLIED
-+ abstract %boolean; #IMPLIED
-+ final %complexDerivationSet; #IMPLIED
-+ block %blockSet; #IMPLIED
-+ default CDATA #IMPLIED
-+ fixed CDATA #IMPLIED
-+ form %formValues; #IMPLIED
-+ %elementAttrs;>
-+<!-- type and ref are mutually exclusive.
-+ name and ref are mutually exclusive, one is required -->
-+<!-- In the absence of type AND ref, type defaults to type of
-+ substitutionGroup, if any, else the ur-type, i.e. unconstrained -->
-+<!-- default and fixed are mutually exclusive -->
-+
-+<!ELEMENT %group; ((%annotation;)?,(%mgs;)?)>
-+<!ATTLIST %group;
-+ name %NCName; #IMPLIED
-+ ref %QName; #IMPLIED
-+ minOccurs %nonNegativeInteger; #IMPLIED
-+ maxOccurs CDATA #IMPLIED
-+ id ID #IMPLIED
-+ %groupAttrs;>
-+
-+<!ELEMENT %all; ((%annotation;)?, (%element;)*)>
-+<!ATTLIST %all;
-+ minOccurs (1) #IMPLIED
-+ maxOccurs (1) #IMPLIED
-+ id ID #IMPLIED
-+ %allAttrs;>
-+
-+<!ELEMENT %choice; ((%annotation;)?, (%element;| %group;| %cs; | %any;)*)>
-+<!ATTLIST %choice;
-+ minOccurs %nonNegativeInteger; #IMPLIED
-+ maxOccurs CDATA #IMPLIED
-+ id ID #IMPLIED
-+ %choiceAttrs;>
-+
-+<!ELEMENT %sequence; ((%annotation;)?, (%element;| %group;| %cs; | %any;)*)>
-+<!ATTLIST %sequence;
-+ minOccurs %nonNegativeInteger; #IMPLIED
-+ maxOccurs CDATA #IMPLIED
-+ id ID #IMPLIED
-+ %sequenceAttrs;>
-+
-+<!-- an anonymous grouping in a model, or
-+ a top-level named group definition, or a reference to same -->
-+
-+<!-- Note that if order is 'all', group is not allowed inside.
-+ If order is 'all' THIS group must be alone (or referenced alone) at
-+ the top level of a content model -->
-+<!-- If order is 'all', minOccurs==maxOccurs==1 on element/any inside -->
-+<!-- Should allow minOccurs=0 inside order='all' . . . -->
-+
-+<!ELEMENT %any; (%annotation;)?>
-+<!ATTLIST %any;
-+ namespace CDATA '##any'
-+ processContents (skip|lax|strict) 'strict'
-+ minOccurs %nonNegativeInteger; '1'
-+ maxOccurs CDATA '1'
-+ id ID #IMPLIED
-+ %anyAttrs;>
-+
-+<!-- namespace is interpreted as follows:
-+ ##any - - any non-conflicting WFXML at all
-+
-+ ##other - - any non-conflicting WFXML from namespace other
-+ than targetNamespace
-+
-+ ##local - - any unqualified non-conflicting WFXML/attribute
-+ one or - - any non-conflicting WFXML from
-+ more URI the listed namespaces
-+ references
-+
-+ ##targetNamespace ##local may appear in the above list,
-+ with the obvious meaning -->
-+
-+<!ELEMENT %anyAttribute; (%annotation;)?>
-+<!ATTLIST %anyAttribute;
-+ namespace CDATA '##any'
-+ processContents (skip|lax|strict) 'strict'
-+ id ID #IMPLIED
-+ %anyAttributeAttrs;>
-+<!-- namespace is interpreted as for 'any' above -->
-+
-+<!-- simpleType only if no type|ref attribute -->
-+<!-- ref not allowed at top level, name iff at top level -->
-+<!ELEMENT %attribute; ((%annotation;)?, (%simpleType;)?)>
-+<!ATTLIST %attribute;
-+ name %NCName; #IMPLIED
-+ id ID #IMPLIED
-+ ref %QName; #IMPLIED
-+ type %QName; #IMPLIED
-+ use (prohibited|optional|required) #IMPLIED
-+ default CDATA #IMPLIED
-+ fixed CDATA #IMPLIED
-+ form %formValues; #IMPLIED
-+ %attributeAttrs;>
-+<!-- type and ref are mutually exclusive.
-+ name and ref are mutually exclusive, one is required -->
-+<!-- default for use is optional when nested, none otherwise -->
-+<!-- default and fixed are mutually exclusive -->
-+<!-- type attr and simpleType content are mutually exclusive -->
-+
-+<!-- an attributeGroup is a named collection of attribute decls, or a
-+ reference thereto -->
-+<!ELEMENT %attributeGroup; ((%annotation;)?,
-+ (%attribute; | %attributeGroup;)*,
-+ (%anyAttribute;)?) >
-+<!ATTLIST %attributeGroup;
-+ name %NCName; #IMPLIED
-+ id ID #IMPLIED
-+ ref %QName; #IMPLIED
-+ %attributeGroupAttrs;>
-+
-+<!-- ref iff no content, no name. ref iff not top level -->
-+
-+<!-- better reference mechanisms -->
-+<!ELEMENT %unique; ((%annotation;)?, %selector;, (%field;)+)>
-+<!ATTLIST %unique;
-+ name %NCName; #REQUIRED
-+ id ID #IMPLIED
-+ %uniqueAttrs;>
-+
-+<!ELEMENT %key; ((%annotation;)?, %selector;, (%field;)+)>
-+<!ATTLIST %key;
-+ name %NCName; #REQUIRED
-+ id ID #IMPLIED
-+ %keyAttrs;>
-+
-+<!ELEMENT %keyref; ((%annotation;)?, %selector;, (%field;)+)>
-+<!ATTLIST %keyref;
-+ name %NCName; #REQUIRED
-+ refer %QName; #REQUIRED
-+ id ID #IMPLIED
-+ %keyrefAttrs;>
-+
-+<!ELEMENT %selector; ((%annotation;)?)>
-+<!ATTLIST %selector;
-+ xpath %XPathExpr; #REQUIRED
-+ id ID #IMPLIED
-+ %selectorAttrs;>
-+<!ELEMENT %field; ((%annotation;)?)>
-+<!ATTLIST %field;
-+ xpath %XPathExpr; #REQUIRED
-+ id ID #IMPLIED
-+ %fieldAttrs;>
-+
-+<!-- Schema combination mechanisms -->
-+<!ELEMENT %include; (%annotation;)?>
-+<!ATTLIST %include;
-+ schemaLocation %URIref; #REQUIRED
-+ id ID #IMPLIED
-+ %includeAttrs;>
-+
-+<!ELEMENT %import; (%annotation;)?>
-+<!ATTLIST %import;
-+ namespace %URIref; #IMPLIED
-+ schemaLocation %URIref; #IMPLIED
-+ id ID #IMPLIED
-+ %importAttrs;>
-+
-+<!ELEMENT %redefine; (%annotation; | %simpleType; | %complexType; |
-+ %attributeGroup; | %group;)*>
-+<!ATTLIST %redefine;
-+ schemaLocation %URIref; #REQUIRED
-+ id ID #IMPLIED
-+ %redefineAttrs;>
-+
-+<!ELEMENT %notation; (%annotation;)?>
-+<!ATTLIST %notation;
-+ name %NCName; #REQUIRED
-+ id ID #IMPLIED
-+ public CDATA #REQUIRED
-+ system %URIref; #IMPLIED
-+ %notationAttrs;>
-+
-+<!-- Annotation is either application information or documentation -->
-+<!-- By having these here they are available for datatypes as well
-+ as all the structures elements -->
-+
-+<!ELEMENT %annotation; (%appinfo; | %documentation;)*>
-+<!ATTLIST %annotation; %annotationAttrs;>
-+
-+<!-- User must define annotation elements in internal subset for this
-+ to work -->
-+<!ELEMENT %appinfo; ANY> <!-- too restrictive -->
-+<!ATTLIST %appinfo;
-+ source %URIref; #IMPLIED
-+ id ID #IMPLIED
-+ %appinfoAttrs;>
-+<!ELEMENT %documentation; ANY> <!-- too restrictive -->
-+<!ATTLIST %documentation;
-+ source %URIref; #IMPLIED
-+ id ID #IMPLIED
-+ xml:lang CDATA #IMPLIED
-+ %documentationAttrs;>
-+
-+<!NOTATION XMLSchemaStructures PUBLIC
-+ 'structures' 'http://www.w3.org/2001/XMLSchema.xsd' >
-+<!NOTATION XML PUBLIC
-+ 'REC-xml-1998-0210' 'http://www.w3.org/TR/1998/REC-xml-19980210' >
-Index: jenkins-winstone/src/conf/javax/servlet/resources/datatypes.dtd
-===================================================================
---- /dev/null 1970-01-01 00:00:00.000000000 +0000
-+++ jenkins-winstone/src/conf/javax/servlet/resources/datatypes.dtd 2012-04-26 11:45:47.794315763 +0100
-@@ -0,0 +1,203 @@
-+<!--
-+ DTD for XML Schemas: Part 2: Datatypes
-+ $Id: datatypes.dtd,v 1.23 2001/03/16 17:36:30 ht Exp $
-+ Note this DTD is NOT normative, or even definitive. - - the
-+ prose copy in the datatypes REC is the definitive version
-+ (which shouldn't differ from this one except for this comment
-+ and entity expansions, but just in case)
-+ -->
-+
-+<!--
-+ This DTD cannot be used on its own, it is intended
-+ only for incorporation in XMLSchema.dtd, q.v.
-+ -->
-+
-+<!-- Define all the element names, with optional prefix -->
-+<!ENTITY % simpleType "%p;simpleType">
-+<!ENTITY % restriction "%p;restriction">
-+<!ENTITY % list "%p;list">
-+<!ENTITY % union "%p;union">
-+<!ENTITY % maxExclusive "%p;maxExclusive">
-+<!ENTITY % minExclusive "%p;minExclusive">
-+<!ENTITY % maxInclusive "%p;maxInclusive">
-+<!ENTITY % minInclusive "%p;minInclusive">
-+<!ENTITY % totalDigits "%p;totalDigits">
-+<!ENTITY % fractionDigits "%p;fractionDigits">
-+<!ENTITY % length "%p;length">
-+<!ENTITY % minLength "%p;minLength">
-+<!ENTITY % maxLength "%p;maxLength">
-+<!ENTITY % enumeration "%p;enumeration">
-+<!ENTITY % whiteSpace "%p;whiteSpace">
-+<!ENTITY % pattern "%p;pattern">
-+
-+<!--
-+ Customisation entities for the ATTLIST of each element
-+ type. Define one of these if your schema takes advantage
-+ of the anyAttribute='##other' in the schema for schemas
-+ -->
-+
-+<!ENTITY % simpleTypeAttrs "">
-+<!ENTITY % restrictionAttrs "">
-+<!ENTITY % listAttrs "">
-+<!ENTITY % unionAttrs "">
-+<!ENTITY % maxExclusiveAttrs "">
-+<!ENTITY % minExclusiveAttrs "">
-+<!ENTITY % maxInclusiveAttrs "">
-+<!ENTITY % minInclusiveAttrs "">
-+<!ENTITY % totalDigitsAttrs "">
-+<!ENTITY % fractionDigitsAttrs "">
-+<!ENTITY % lengthAttrs "">
-+<!ENTITY % minLengthAttrs "">
-+<!ENTITY % maxLengthAttrs "">
-+<!ENTITY % enumerationAttrs "">
-+<!ENTITY % whiteSpaceAttrs "">
-+<!ENTITY % patternAttrs "">
-+
-+<!-- Define some entities for informative use as attribute
-+ types -->
-+<!ENTITY % URIref "CDATA">
-+<!ENTITY % XPathExpr "CDATA">
-+<!ENTITY % QName "NMTOKEN">
-+<!ENTITY % QNames "NMTOKENS">
-+<!ENTITY % NCName "NMTOKEN">
-+<!ENTITY % nonNegativeInteger "NMTOKEN">
-+<!ENTITY % boolean "(true|false)">
-+<!ENTITY % simpleDerivationSet "CDATA">
-+<!--
-+ #all or space-separated list drawn from derivationChoice
-+ -->
-+
-+<!--
-+ Note that the use of 'facet' below is less restrictive
-+ than is really intended: There should in fact be no
-+ more than one of each of minInclusive, minExclusive,
-+ maxInclusive, maxExclusive, totalDigits, fractionDigits,
-+ length, maxLength, minLength within datatype,
-+ and the min- and max- variants of Inclusive and Exclusive
-+ are mutually exclusive. On the other hand, pattern and
-+ enumeration may repeat.
-+ -->
-+<!ENTITY % minBound "(%minInclusive; | %minExclusive;)">
-+<!ENTITY % maxBound "(%maxInclusive; | %maxExclusive;)">
-+<!ENTITY % bounds "%minBound; | %maxBound;">
-+<!ENTITY % numeric "%totalDigits; | %fractionDigits;">
-+<!ENTITY % ordered "%bounds; | %numeric;">
-+<!ENTITY % unordered
-+ "%pattern; | %enumeration; | %whiteSpace; | %length; |
-+ %maxLength; | %minLength;">
-+<!ENTITY % facet "%ordered; | %unordered;">
-+<!ENTITY % facetAttr
-+ "value CDATA #REQUIRED
-+ id ID #IMPLIED">
-+<!ENTITY % fixedAttr "fixed %boolean; #IMPLIED">
-+<!ENTITY % facetModel "(%annotation;)?">
-+<!ELEMENT %simpleType;
-+ ((%annotation;)?, (%restriction; | %list; | %union;))>
-+<!ATTLIST %simpleType;
-+ name %NCName; #IMPLIED
-+ final %simpleDerivationSet; #IMPLIED
-+ id ID #IMPLIED
-+ %simpleTypeAttrs;>
-+<!-- name is required at top level -->
-+<!ELEMENT %restriction; ((%annotation;)?,
-+ (%restriction1; |
-+ ((%simpleType;)?,(%facet;)*)),
-+ (%attrDecls;))>
-+<!ATTLIST %restriction;
-+ base %QName; #IMPLIED
-+ id ID #IMPLIED
-+ %restrictionAttrs;>
-+<!--
-+ base and simpleType child are mutually exclusive,
-+ one is required.
-+
-+ restriction is shared between simpleType and
-+ simpleContent and complexContent (in XMLSchema.xsd).
-+ restriction1 is for the latter cases, when this
-+ is restricting a complex type, as is attrDecls.
-+ -->
-+<!ELEMENT %list; ((%annotation;)?,(%simpleType;)?)>
-+<!ATTLIST %list;
-+ itemType %QName; #IMPLIED
-+ id ID #IMPLIED
-+ %listAttrs;>
-+<!--
-+ itemType and simpleType child are mutually exclusive,
-+ one is required
-+ -->
-+<!ELEMENT %union; ((%annotation;)?,(%simpleType;)*)>
-+<!ATTLIST %union;
-+ id ID #IMPLIED
-+ memberTypes %QNames; #IMPLIED
-+ %unionAttrs;>
-+<!--
-+ At least one item in memberTypes or one simpleType
-+ child is required
-+ -->
-+
-+<!ELEMENT %maxExclusive; %facetModel;>
-+<!ATTLIST %maxExclusive;
-+ %facetAttr;
-+ %fixedAttr;
-+ %maxExclusiveAttrs;>
-+<!ELEMENT %minExclusive; %facetModel;>
-+<!ATTLIST %minExclusive;
-+ %facetAttr;
-+ %fixedAttr;
-+ %minExclusiveAttrs;>
-+
-+<!ELEMENT %maxInclusive; %facetModel;>
-+<!ATTLIST %maxInclusive;
-+ %facetAttr;
-+ %fixedAttr;
-+ %maxInclusiveAttrs;>
-+<!ELEMENT %minInclusive; %facetModel;>
-+<!ATTLIST %minInclusive;
-+ %facetAttr;
-+ %fixedAttr;
-+ %minInclusiveAttrs;>
-+
-+<!ELEMENT %totalDigits; %facetModel;>
-+<!ATTLIST %totalDigits;
-+ %facetAttr;
-+ %fixedAttr;
-+ %totalDigitsAttrs;>
-+<!ELEMENT %fractionDigits; %facetModel;>
-+<!ATTLIST %fractionDigits;
-+ %facetAttr;
-+ %fixedAttr;
-+ %fractionDigitsAttrs;>
-+
-+<!ELEMENT %length; %facetModel;>
-+<!ATTLIST %length;
-+ %facetAttr;
-+ %fixedAttr;
-+ %lengthAttrs;>
-+<!ELEMENT %minLength; %facetModel;>
-+<!ATTLIST %minLength;
-+ %facetAttr;
-+ %fixedAttr;
-+ %minLengthAttrs;>
-+<!ELEMENT %maxLength; %facetModel;>
-+<!ATTLIST %maxLength;
-+ %facetAttr;
-+ %fixedAttr;
-+ %maxLengthAttrs;>
-+
-+<!-- This one can be repeated -->
-+<!ELEMENT %enumeration; %facetModel;>
-+<!ATTLIST %enumeration;
-+ %facetAttr;
-+ %enumerationAttrs;>
-+
-+<!ELEMENT %whiteSpace; %facetModel;>
-+<!ATTLIST %whiteSpace;
-+ %facetAttr;
-+ %fixedAttr;
-+ %whiteSpaceAttrs;>
-+
-+<!-- This one can be repeated -->
-+<!ELEMENT %pattern; %facetModel;>
-+<!ATTLIST %pattern;
-+ %facetAttr;
-+ %patternAttrs;>
-Index: jenkins-winstone/src/conf/javax/servlet/resources/j2ee_1_4.xsd
-===================================================================
---- /dev/null 1970-01-01 00:00:00.000000000 +0000
-+++ jenkins-winstone/src/conf/javax/servlet/resources/j2ee_1_4.xsd 2012-04-26 11:45:47.798315613 +0100
-@@ -0,0 +1,1616 @@
-+<?xml version="1.0" encoding="UTF-8"?>
-+<xsd:schema
-+ targetNamespace="http://java.sun.com/xml/ns/j2ee"
-+ xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
-+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
-+ elementFormDefault="qualified"
-+ attributeFormDefault="unqualified"
-+ version="1.4">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ @(#)j2ee_1_4.xsds 1.43 03/09/16
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
-+
-+ Copyright 2003-2007 Sun Microsystems, Inc. All rights reserved.
-+
-+ The contents of this file are subject to the terms of either the
-+ GNU General Public License Version 2 only ("GPL") or the Common
-+ Development and Distribution License("CDDL") (collectively, the
-+ "License"). You may not use this file except in compliance with
-+ the License. You can obtain a copy of the License at
-+ https://glassfish.dev.java.net/public/CDDL+GPL.html or
-+ glassfish/bootstrap/legal/LICENSE.txt. See the License for the
-+ specific language governing permissions and limitations under the
-+ License.
-+
-+ When distributing the software, include this License Header
-+ Notice in each file and include the License file at
-+ glassfish/bootstrap/legal/LICENSE.txt. Sun designates this
-+ particular file as subject to the "Classpath" exception as
-+ provided by Sun in the GPL Version 2 section of the License file
-+ that accompanied this code. If applicable, add the following
-+ below the License Header, with the fields enclosed by brackets []
-+ replaced by your own identifying information:
-+ "Portions Copyrighted [year] [name of copyright owner]"
-+
-+ Contributor(s):
-+
-+ If you wish your version of this file to be governed by only the
-+ CDDL or only the GPL Version 2, indicate your decision by adding
-+ "[Contributor] elects to include this software in this
-+ distribution under the [CDDL or GPL Version 2] license." If you
-+ don't indicate a single choice of license, a recipient has the
-+ option to distribute your version of this file under either the
-+ CDDL, the GPL Version 2 or to extend the choice of license to its
-+ licensees as provided above. However, if you add GPL Version 2
-+ code and therefore, elected the GPL Version 2 license, then the
-+ option applies only if the new code is made subject to such
-+ option by the copyright holder.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+<xsd:annotation>
-+<xsd:documentation>
-+
-+The following definitions that appear in the common
-+shareable schema(s) of J2EE deployment descriptors should be
-+interpreted with respect to the context they are included:
-+
-+Deployment Component may indicate one of the following:
-+ j2ee application;
-+ application client;
-+ web application;
-+ enterprise bean;
-+ resource adapter;
-+
-+Deployment File may indicate one of the following:
-+ ear file;
-+ war file;
-+ jar file;
-+ rar file;
-+
-+</xsd:documentation>
-+</xsd:annotation>
-+
-+ <xsd:import namespace="http://www.w3.org/XML/1998/namespace"
-+ schemaLocation="http://www.w3.org/2001/xml.xsd"/>
-+
-+ <xsd:include schemaLocation=
-+ "http://www.ibm.com/webservices/xsd/j2ee_web_services_client_1_1.xsd"/>
-+
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:group name="descriptionGroup">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This group keeps the usage of the contained description related
-+ elements consistent across J2EE deployment descriptors.
-+
-+ All elements may occur multiple times with different languages,
-+ to support localization of the content.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="j2ee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="display-name"
-+ type="j2ee:display-nameType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="icon"
-+ type="j2ee:iconType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ </xsd:sequence>
-+ </xsd:group>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="descriptionType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The description type is used by a description element to
-+ provide text describing the parent element. The elements
-+ that use this type should include any information that the
-+ Deployment Component's Deployment File file producer wants
-+ to provide to the consumer of the Deployment Component's
-+ Deployment File (i.e., to the Deployer). Typically, the
-+ tools used by such a Deployment File consumer will display
-+ the description when processing the parent element that
-+ contains the description.
-+
-+ The lang attribute defines the language that the
-+ description is provided in. The default value is "en" (English).
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:extension base="j2ee:xsdStringType">
-+ <xsd:attribute ref="xml:lang"/>
-+ </xsd:extension>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:simpleType name="dewey-versionType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type defines a dewey decimal which is used
-+ to describe versions of documents.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:restriction base="xsd:decimal">
-+ <xsd:whiteSpace value="collapse"/>
-+ </xsd:restriction>
-+
-+ </xsd:simpleType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="display-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The display-name type contains a short name that is intended
-+ to be displayed by tools. It is used by display-name
-+ elements. The display name need not be unique.
-+
-+ Example:
-+
-+ ...
-+ <display-name xml:lang="en">Employee Self Service</display-name>
-+
-+ The value of the xml:lang attribute is "en" (English) by default.
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:extension base="j2ee:string">
-+ <xsd:attribute ref="xml:lang"/>
-+ </xsd:extension>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="ejb-linkType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The ejb-linkType is used by ejb-link
-+ elements in the ejb-ref or ejb-local-ref elements to specify
-+ that an EJB reference is linked to enterprise bean.
-+
-+ The value of the ejb-link element must be the ejb-name of an
-+ enterprise bean in the same ejb-jar file or in another ejb-jar
-+ file in the same J2EE application unit.
-+
-+ Alternatively, the name in the ejb-link element may be
-+ composed of a path name specifying the ejb-jar containing the
-+ referenced enterprise bean with the ejb-name of the target
-+ bean appended and separated from the path name by "#". The
-+ path name is relative to the Deployment File containing
-+ Deployment Component that is referencing the enterprise
-+ bean. This allows multiple enterprise beans with the same
-+ ejb-name to be uniquely identified.
-+
-+ Examples:
-+
-+ <ejb-link>EmployeeRecord</ejb-link>
-+
-+ <ejb-link>../products/product.jar#ProductEJB</ejb-link>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:string"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="ejb-local-refType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The ejb-local-refType is used by ejb-local-ref elements for
-+ the declaration of a reference to an enterprise bean's local
-+ home. The declaration consists of:
-+
-+ - an optional description
-+ - the EJB reference name used in the code of the Deployment
-+ Component that's referencing the enterprise bean
-+ - the expected type of the referenced enterprise bean
-+ - the expected local home and local interfaces of the
-+ referenced enterprise bean
-+ - optional ejb-link information, used to specify the
-+ referenced enterprise bean
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="j2ee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="ejb-ref-name"
-+ type="j2ee:ejb-ref-nameType"/>
-+ <xsd:element name="ejb-ref-type"
-+ type="j2ee:ejb-ref-typeType"/>
-+ <xsd:element name="local-home"
-+ type="j2ee:local-homeType"/>
-+ <xsd:element name="local"
-+ type="j2ee:localType"/>
-+ <xsd:element name="ejb-link"
-+ type="j2ee:ejb-linkType"
-+ minOccurs="0"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="ejb-ref-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The ejb-ref-name element contains the name of an EJB
-+ reference. The EJB reference is an entry in the
-+ Deployment Component's environment and is relative to the
-+ java:comp/env context. The name must be unique within the
-+ Deployment Component.
-+
-+ It is recommended that name is prefixed with "ejb/".
-+
-+ Example:
-+
-+ <ejb-ref-name>ejb/Payroll</ejb-ref-name>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:jndi-nameType"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="ejb-ref-typeType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The ejb-ref-typeType contains the expected type of the
-+ referenced enterprise bean.
-+
-+ The ejb-ref-type designates a value
-+ that must be one of the following:
-+
-+ Entity
-+ Session
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:string">
-+ <xsd:enumeration value="Entity"/>
-+ <xsd:enumeration value="Session"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="ejb-refType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The ejb-refType is used by ejb-ref elements for the
-+ declaration of a reference to an enterprise bean's home. The
-+ declaration consists of:
-+
-+ - an optional description
-+ - the EJB reference name used in the code of
-+ the Deployment Component that's referencing the enterprise
-+ bean
-+ - the expected type of the referenced enterprise bean
-+ - the expected home and remote interfaces of the referenced
-+ enterprise bean
-+ - optional ejb-link information, used to specify the
-+ referenced enterprise bean
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="j2ee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="ejb-ref-name"
-+ type="j2ee:ejb-ref-nameType"/>
-+ <xsd:element name="ejb-ref-type"
-+ type="j2ee:ejb-ref-typeType"/>
-+
-+ <xsd:element name="home"
-+ type="j2ee:homeType"/>
-+ <xsd:element name="remote"
-+ type="j2ee:remoteType"/>
-+ <xsd:element name="ejb-link"
-+ type="j2ee:ejb-linkType"
-+ minOccurs="0"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="emptyType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type is used to designate an empty
-+ element when used.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="env-entry-type-valuesType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ This type contains the fully-qualified Java type of the
-+ environment entry value that is expected by the
-+ application's code.
-+
-+ The following are the legal values of env-entry-type-valuesType:
-+
-+ java.lang.Boolean
-+ java.lang.Byte
-+ java.lang.Character
-+ java.lang.String
-+ java.lang.Short
-+ java.lang.Integer
-+ java.lang.Long
-+ java.lang.Float
-+ java.lang.Double
-+
-+ Example:
-+
-+ <env-entry-type>java.lang.Boolean</env-entry-type>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:string">
-+ <xsd:enumeration value="java.lang.Boolean"/>
-+ <xsd:enumeration value="java.lang.Byte"/>
-+ <xsd:enumeration value="java.lang.Character"/>
-+ <xsd:enumeration value="java.lang.String"/>
-+ <xsd:enumeration value="java.lang.Short"/>
-+ <xsd:enumeration value="java.lang.Integer"/>
-+ <xsd:enumeration value="java.lang.Long"/>
-+ <xsd:enumeration value="java.lang.Float"/>
-+ <xsd:enumeration value="java.lang.Double"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="env-entryType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The env-entryType is used to declare an application's
-+ environment entry. The declaration consists of an optional
-+ description, the name of the environment entry, and an
-+ optional value. If a value is not specified, one must be
-+ supplied during deployment.
-+
-+ It is used by env-entry elements.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="j2ee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="env-entry-name"
-+ type="j2ee:jndi-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The env-entry-name element contains the name of a
-+ Deployment Component's environment entry. The name
-+ is a JNDI name relative to the java:comp/env
-+ context. The name must be unique within a
-+ Deployment Component. The uniqueness
-+ constraints must be defined within the declared
-+ context.
-+
-+ Example:
-+
-+ <env-entry-name>minAmount</env-entry-name>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="env-entry-type"
-+ type="j2ee:env-entry-type-valuesType"/>
-+
-+ <xsd:element name="env-entry-value"
-+ type="j2ee:xsdStringType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The env-entry-value designates the value of a
-+ Deployment Component's environment entry. The value
-+ must be a String that is valid for the
-+ constructor of the specified type that takes a
-+ single String parameter, or for java.lang.Character,
-+ a single character.
-+
-+ Example:
-+
-+ <env-entry-value>100.00</env-entry-value>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="fully-qualified-classType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The elements that use this type designate the name of a
-+ Java class or interface. The name is in the form of a
-+ "binary name", as defined in the JLS. This is the form
-+ of name used in Class.forName(). Tools that need the
-+ canonical name (the name used in source code) will need
-+ to convert this binary name to the canonical name.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:string"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="generic-booleanType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type defines four different values which can designate
-+ boolean values. This includes values yes and no which are
-+ not designated by xsd:boolean
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:string">
-+ <xsd:enumeration value="true"/>
-+ <xsd:enumeration value="false"/>
-+ <xsd:enumeration value="yes"/>
-+ <xsd:enumeration value="no"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="homeType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The homeType defines the fully-qualified name of
-+ an enterprise bean's home interface.
-+
-+ Example:
-+
-+ <home>com.aardvark.payroll.PayrollHome</home>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:fully-qualified-classType"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="iconType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The icon type contains small-icon and large-icon elements
-+ that specify the file names for small and large GIF or
-+ JPEG icon images used to represent the parent element in a
-+ GUI tool.
-+
-+ The xml:lang attribute defines the language that the
-+ icon file names are provided in. Its value is "en" (English)
-+ by default.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="small-icon" type="j2ee:pathType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The small-icon element contains the name of a file
-+ containing a small (16 x 16) icon image. The file
-+ name is a relative path within the Deployment
-+ Component's Deployment File.
-+
-+ The image may be either in the JPEG or GIF format.
-+ The icon can be used by tools.
-+
-+ Example:
-+
-+ <small-icon>employee-service-icon16x16.jpg</small-icon>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="large-icon" type="j2ee:pathType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The large-icon element contains the name of a file
-+ containing a large
-+ (32 x 32) icon image. The file name is a relative
-+ path within the Deployment Component's Deployment
-+ File.
-+
-+ The image may be either in the JPEG or GIF format.
-+ The icon can be used by tools.
-+
-+ Example:
-+
-+ <large-icon>employee-service-icon32x32.jpg</large-icon>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ </xsd:sequence>
-+
-+ <xsd:attribute ref="xml:lang"/>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="java-identifierType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The java-identifierType defines a Java identifier.
-+ The users of this type should further verify that
-+ the content does not contain Java reserved keywords.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:string">
-+ <xsd:pattern value="($|_|\p{L})(\p{L}|\p{Nd}|_|$)*"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="java-typeType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This is a generic type that designates a Java primitive
-+ type or a fully qualified name of a Java interface/type,
-+ or an array of such types.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:string">
-+ <xsd:pattern value="[^\p{Z}]*"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="jndi-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The jndi-nameType type designates a JNDI name in the
-+ Deployment Component's environment and is relative to the
-+ java:comp/env context. A JNDI name must be unique within the
-+ Deployment Component.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:string"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:group name="jndiEnvironmentRefsGroup">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This group keeps the usage of the contained JNDI environment
-+ reference elements consistent across J2EE deployment descriptors.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:sequence>
-+ <xsd:element name="env-entry"
-+ type="j2ee:env-entryType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ <xsd:element name="ejb-ref"
-+ type="j2ee:ejb-refType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ <xsd:element name="ejb-local-ref"
-+ type="j2ee:ejb-local-refType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ <xsd:group ref="j2ee:service-refGroup"/>
-+ <xsd:element name="resource-ref"
-+ type="j2ee:resource-refType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ <xsd:element name="resource-env-ref"
-+ type="j2ee:resource-env-refType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ <xsd:element name="message-destination-ref"
-+ type="j2ee:message-destination-refType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ </xsd:sequence>
-+ </xsd:group>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="listenerType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The listenerType indicates the deployment properties for a web
-+ application listener bean.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:group ref="j2ee:descriptionGroup"/>
-+ <xsd:element name="listener-class"
-+ type="j2ee:fully-qualified-classType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The listener-class element declares a class in the
-+ application must be registered as a web
-+ application listener bean. The value is the fully
-+ qualified classname of the listener class.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="local-homeType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The local-homeType defines the fully-qualified
-+ name of an enterprise bean's local home interface.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:fully-qualified-classType"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="localType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The localType defines the fully-qualified name of an
-+ enterprise bean's local interface.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:fully-qualified-classType"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="message-destination-linkType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The message-destination-linkType is used to link a message
-+ destination reference or message-driven bean to a message
-+ destination.
-+
-+ The Assembler sets the value to reflect the flow of messages
-+ between producers and consumers in the application.
-+
-+ The value must be the message-destination-name of a message
-+ destination in the same Deployment File or in another
-+ Deployment File in the same J2EE application unit.
-+
-+ Alternatively, the value may be composed of a path name
-+ specifying a Deployment File containing the referenced
-+ message destination with the message-destination-name of the
-+ destination appended and separated from the path name by
-+ "#". The path name is relative to the Deployment File
-+ containing Deployment Component that is referencing the
-+ message destination. This allows multiple message
-+ destinations with the same name to be uniquely identified.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:string"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="message-destination-refType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The message-destination-ref element contains a declaration
-+ of Deployment Component's reference to a message destination
-+ associated with a resource in Deployment Component's
-+ environment. It consists of:
-+
-+ - an optional description
-+ - the message destination reference name
-+ - the message destination type
-+ - a specification as to whether the
-+ destination is used for
-+ consuming or producing messages, or both
-+ - a link to the message destination
-+
-+ Examples:
-+
-+ <message-destination-ref>
-+ <message-destination-ref-name>jms/StockQueue
-+ </message-destination-ref-name>
-+ <message-destination-type>javax.jms.Queue
-+ </message-destination-type>
-+ <message-destination-usage>Consumes
-+ </message-destination-usage>
-+ <message-destination-link>CorporateStocks
-+ </message-destination-link>
-+ </message-destination-ref>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="j2ee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="message-destination-ref-name"
-+ type="j2ee:jndi-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The message-destination-ref-name element specifies
-+ the name of a message destination reference; its
-+ value is the environment entry name used in
-+ Deployment Component code. The name is a JNDI name
-+ relative to the java:comp/env context and must be
-+ unique within an ejb-jar (for enterprise beans) or a
-+ Deployment File (for others).
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="message-destination-type"
-+ type="j2ee:message-destination-typeType"/>
-+ <xsd:element name="message-destination-usage"
-+ type="j2ee:message-destination-usageType"/>
-+ <xsd:element name="message-destination-link"
-+ type="j2ee:message-destination-linkType"
-+ minOccurs="0"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="message-destination-typeType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The message-destination-typeType specifies the type of
-+ the destination. The type is specified by the Java interface
-+ expected to be implemented by the destination.
-+
-+ Example:
-+
-+ <message-destination-type>javax.jms.Queue
-+ </message-destination-type>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:fully-qualified-classType"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="message-destination-usageType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The message-destination-usageType specifies the use of the
-+ message destination indicated by the reference. The value
-+ indicates whether messages are consumed from the message
-+ destination, produced for the destination, or both. The
-+ Assembler makes use of this information in linking producers
-+ of a destination with its consumers.
-+
-+ The value of the message-destination-usage element must be
-+ one of the following:
-+ Consumes
-+ Produces
-+ ConsumesProduces
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:string">
-+ <xsd:enumeration value="Consumes"/>
-+ <xsd:enumeration value="Produces"/>
-+ <xsd:enumeration value="ConsumesProduces"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="message-destinationType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The message-destinationType specifies a message
-+ destination. The logical destination described by this
-+ element is mapped to a physical destination by the Deployer.
-+
-+ The message destination element contains:
-+
-+ - an optional description
-+ - an optional display-name
-+ - an optional icon
-+ - a message destination name which must be unique
-+ among message destination names within the same
-+ Deployment File.
-+
-+ Example:
-+
-+ <message-destination>
-+ <message-destination-name>CorporateStocks
-+ </message-destination-name>
-+ </message-destination>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:sequence>
-+ <xsd:group ref="j2ee:descriptionGroup"/>
-+ <xsd:element name="message-destination-name"
-+ type="j2ee:string">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The message-destination-name element specifies a
-+ name for a message destination. This name must be
-+ unique among the names of message destinations
-+ within the Deployment File.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="param-valueType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type is a general type that can be used to declare
-+ parameter/value lists.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="j2ee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="param-name"
-+ type="j2ee:string">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The param-name element contains the name of a
-+ parameter.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="param-value"
-+ type="j2ee:xsdStringType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The param-value element contains the value of a
-+ parameter.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="pathType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The elements that use this type designate either a relative
-+ path or an absolute path starting with a "/".
-+
-+ In elements that specify a pathname to a file within the
-+ same Deployment File, relative filenames (i.e., those not
-+ starting with "/") are considered relative to the root of
-+ the Deployment File's namespace. Absolute filenames (i.e.,
-+ those starting with "/") also specify names in the root of
-+ the Deployment File's namespace. In general, relative names
-+ are preferred. The exception is .war files where absolute
-+ names are preferred for consistency with the Servlet API.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:string"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="remoteType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The remote element contains the fully-qualified name
-+ of the enterprise bean's remote interface.
-+
-+ Example:
-+
-+ <remote>com.wombat.empl.EmployeeService</remote>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:fully-qualified-classType"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="res-authType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The res-authType specifies whether the Deployment Component
-+ code signs on programmatically to the resource manager, or
-+ whether the Container will sign on to the resource manager
-+ on behalf of the Deployment Component. In the latter case,
-+ the Container uses information that is supplied by the
-+ Deployer.
-+
-+ The value must be one of the two following:
-+
-+ Application
-+ Container
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:string">
-+ <xsd:enumeration value="Application"/>
-+ <xsd:enumeration value="Container"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="res-sharing-scopeType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The res-sharing-scope type specifies whether connections
-+ obtained through the given resource manager connection
-+ factory reference can be shared. The value, if specified,
-+ must be one of the two following:
-+
-+ Shareable
-+ Unshareable
-+
-+ The default value is Shareable.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:string">
-+ <xsd:enumeration value="Shareable"/>
-+ <xsd:enumeration value="Unshareable"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="resource-env-refType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The resource-env-refType is used to define
-+ resource-env-type elements. It contains a declaration of a
-+ Deployment Component's reference to an administered object
-+ associated with a resource in the Deployment Component's
-+ environment. It consists of an optional description, the
-+ resource environment reference name, and an indication of
-+ the resource environment reference type expected by the
-+ Deployment Component code.
-+
-+ Example:
-+
-+ <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>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="j2ee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="resource-env-ref-name"
-+ type="j2ee:jndi-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The resource-env-ref-name element specifies the name
-+ of a resource environment reference; its value is
-+ the environment entry name used in
-+ the Deployment Component code. The name is a JNDI
-+ name relative to the java:comp/env context and must
-+ be unique within a Deployment Component.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="resource-env-ref-type"
-+ type="j2ee:fully-qualified-classType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The resource-env-ref-type element specifies the type
-+ of a resource environment reference. It is the
-+ fully qualified name of a Java language class or
-+ interface.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="resource-refType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The resource-refType contains a declaration of a
-+ Deployment Component's reference to an external resource. It
-+ consists of an optional description, the resource manager
-+ connection factory reference name, the indication of the
-+ resource manager connection factory type expected by the
-+ Deployment Component code, the type of authentication
-+ (Application or Container), and an optional specification of
-+ the shareability of connections obtained from the resource
-+ (Shareable or Unshareable).
-+
-+ Example:
-+
-+ <resource-ref>
-+ <res-ref-name>jdbc/EmployeeAppDB</res-ref-name>
-+ <res-type>javax.sql.DataSource</res-type>
-+ <res-auth>Container</res-auth>
-+ <res-sharing-scope>Shareable</res-sharing-scope>
-+ </resource-ref>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="j2ee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="res-ref-name"
-+ type="j2ee:jndi-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The res-ref-name element specifies the name of a
-+ resource manager connection factory reference.
-+ The name is a JNDI name relative to the
-+ java:comp/env context.
-+ The name must be unique within a Deployment File.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="res-type"
-+ type="j2ee:fully-qualified-classType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The res-type element specifies the type of the data
-+ source. The type is specified by the fully qualified
-+ Java language class or interface
-+ expected to be implemented by the data source.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="res-auth"
-+ type="j2ee:res-authType"/>
-+
-+ <xsd:element name="res-sharing-scope"
-+ type="j2ee:res-sharing-scopeType"
-+ minOccurs="0"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="role-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The role-nameType designates the name of a security role.
-+
-+ The name must conform to the lexical rules for a token.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:string"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="run-asType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The run-asType specifies the run-as identity to be
-+ used for the execution of a component. It contains an
-+ optional description, and the name of a security role.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="j2ee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="role-name"
-+ type="j2ee:role-nameType"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="security-role-refType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The security-role-refType contains the declaration of a
-+ security role reference in a component's or a
-+ Deployment Component's code. The declaration consists of an
-+ optional description, the security role name used in the
-+ code, and an optional link to a security role. If the
-+ security role is not specified, the Deployer must choose an
-+ appropriate security role.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="j2ee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="role-name"
-+ type="j2ee:role-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The value of the role-name element must be the String used
-+ as the parameter to the
-+ EJBContext.isCallerInRole(String roleName) method or the
-+ HttpServletRequest.isUserInRole(String role) method.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="role-link"
-+ type="j2ee:role-nameType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The role-link element is a 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.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="security-roleType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The security-roleType contains the definition of a security
-+ role. The definition consists of an optional description of the
-+ security role, and the security role name.
-+
-+ Example:
-+
-+ <security-role>
-+ <description>
-+ This role includes all employees who are authorized
-+ to access the employee service application.
-+ </description>
-+ <role-name>employee</role-name>
-+ </security-role>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="j2ee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="role-name"
-+ type="j2ee:role-nameType"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="string">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This is a special string datatype that is defined by J2EE as
-+ a base type for defining collapsed strings. When schemas
-+ require trailing/leading space elimination as well as
-+ collapsing the existing whitespace, this base type may be
-+ used.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:extension base="xsd:token">
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:extension>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="true-falseType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This simple type designates a boolean with only two
-+ permissible values
-+
-+ - true
-+ - false
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:xsdBooleanType">
-+ <xsd:pattern value="(true|false)"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="url-patternType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The url-patternType contains the url pattern of the mapping.
-+ It must follow the rules specified in Section 11.2 of the
-+ Servlet API Specification. This pattern is assumed to be in
-+ URL-decoded form and must not contain CR(#xD) or LF(#xA).
-+ If it contains those characters, the container must inform
-+ the developer with a descriptive error message.
-+ The container must preserve all characters including whitespaces.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:extension base="xsd:string"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="xsdAnyURIType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type adds an "id" attribute to xsd:anyURI.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:extension base="xsd:anyURI">
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:extension>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="xsdBooleanType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type adds an "id" attribute to xsd:boolean.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:extension base="xsd:boolean">
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:extension>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="xsdIntegerType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type adds an "id" attribute to xsd:integer.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:extension base="xsd:integer">
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:extension>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="xsdNMTOKENType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type adds an "id" attribute to xsd:NMTOKEN.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:extension base="xsd:NMTOKEN">
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:extension>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="xsdNonNegativeIntegerType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type adds an "id" attribute to xsd:nonNegativeInteger.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:extension base="xsd:nonNegativeInteger">
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:extension>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="xsdPositiveIntegerType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type adds an "id" attribute to xsd:positiveInteger.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:extension base="xsd:positiveInteger">
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:extension>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="xsdQNameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type adds an "id" attribute to xsd:QName.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:extension base="xsd:QName">
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:extension>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="xsdStringType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type adds an "id" attribute to xsd:string.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:extension base="xsd:string">
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:extension>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+</xsd:schema>
-+
-Index: jenkins-winstone/src/conf/javax/servlet/resources/j2ee_web_services_client_1_1.xsd
-===================================================================
---- /dev/null 1970-01-01 00:00:00.000000000 +0000
-+++ jenkins-winstone/src/conf/javax/servlet/resources/j2ee_web_services_client_1_1.xsd 2012-04-26 11:45:47.798315613 +0100
-@@ -0,0 +1,353 @@
-+<?xml version="1.0" encoding="UTF-8"?>
-+<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
-+ targetNamespace="http://java.sun.com/xml/ns/j2ee"
-+ xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
-+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
-+ elementFormDefault="qualified"
-+ attributeFormDefault="unqualified"
-+ version="1.1">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ @(#)j2ee_web_services_client_1_1.xsds 1.10 02/11/03
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
-+
-+ Copyright 2003-2007 Sun Microsystems, Inc. All rights reserved.
-+
-+ The contents of this file are subject to the terms of either the
-+ GNU General Public License Version 2 only ("GPL") or the Common
-+ Development and Distribution License("CDDL") (collectively, the
-+ "License"). You may not use this file except in compliance with
-+ the License. You can obtain a copy of the License at
-+ https://glassfish.dev.java.net/public/CDDL+GPL.html or
-+ glassfish/bootstrap/legal/LICENSE.txt. See the License for the
-+ specific language governing permissions and limitations under the
-+ License.
-+
-+ When distributing the software, include this License Header
-+ Notice in each file and include the License file at
-+ glassfish/bootstrap/legal/LICENSE.txt. Sun designates this
-+ particular file as subject to the "Classpath" exception as
-+ provided by Sun in the GPL Version 2 section of the License file
-+ that accompanied this code. If applicable, add the following
-+ below the License Header, with the fields enclosed by brackets []
-+ replaced by your own identifying information:
-+ "Portions Copyrighted [year] [name of copyright owner]"
-+
-+ Contributor(s):
-+
-+ If you wish your version of this file to be governed by only the
-+ CDDL or only the GPL Version 2, indicate your decision by adding
-+ "[Contributor] elects to include this software in this
-+ distribution under the [CDDL or GPL Version 2] license." If you
-+ don't indicate a single choice of license, a recipient has the
-+ option to distribute your version of this file under either the
-+ CDDL, the GPL Version 2 or to extend the choice of license to its
-+ licensees as provided above. However, if you add GPL Version 2
-+ code and therefore, elected the GPL Version 2 license, then the
-+ option applies only if the new code is made subject to such
-+ option by the copyright holder.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ (C) Copyright International Business Machines Corporation 2002
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="port-component-refType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The port-component-ref element declares a client dependency
-+ on the container for resolving a Service Endpoint Interface
-+ to a WSDL port. It optionally associates the Service Endpoint
-+ Interface with a particular port-component. This is only used
-+ by the container for a Service.getPort(Class) method call.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="service-endpoint-interface"
-+ type="j2ee:fully-qualified-classType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The service-endpoint-interface element defines a fully qualified
-+ Java class that represents the Service Endpoint Interface of a
-+ WSDL port.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="port-component-link"
-+ type="j2ee:string"
-+ minOccurs="0" maxOccurs="1">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The port-component-link element links a port-component-ref
-+ to a specific port-component required to be made available
-+ by a service reference.
-+
-+ The value of a port-component-link must be the
-+ port-component-name of a port-component in the same module
-+ or another module in the same application unit. The syntax
-+ for specification follows the syntax defined for ejb-link
-+ in the EJB 2.0 specification.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:group name="service-refGroup">
-+ <xsd:sequence>
-+ <xsd:element name="service-ref"
-+ type="j2ee:service-refType"
-+ minOccurs="0" maxOccurs="unbounded">
-+ <xsd:key name="service-ref_handler-name-key">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ Defines the name of the handler. The name must be unique
-+ within the module.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:selector xpath="j2ee:handler"/>
-+ <xsd:field xpath="j2ee:handler-name"/>
-+ </xsd:key>
-+ </xsd:element>
-+ </xsd:sequence>
-+ </xsd:group>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="service-refType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The service-ref element declares a reference to a Web
-+ service. It contains optional description, display name and
-+ icons, a declaration of the required Service interface,
-+ an optional WSDL document location, an optional set
-+ of JAX-RPC mappings, an optional QName for the service element,
-+ an optional set of Service Endpoint Interfaces to be resolved
-+ by the container to a WSDL port, and an optional set of handlers.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:group ref="j2ee:descriptionGroup"/>
-+ <xsd:element name="service-ref-name"
-+ type="j2ee:jndi-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The service-ref-name element declares logical name that the
-+ components in the module use to look up the Web service. It
-+ is recommended that all service reference names start with
-+ "service/".
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="service-interface"
-+ type="j2ee:fully-qualified-classType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The service-interface element declares the fully qualified class
-+ name of the JAX-RPC Service interface the client depends on.
-+ In most cases the value will be javax.xml.rpc.Service. A JAX-RPC
-+ generated Service Interface class may also be specified.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="wsdl-file"
-+ type="j2ee:xsdAnyURIType"
-+ minOccurs="0" maxOccurs="1">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The wsdl-file element contains the URI location of a WSDL
-+ file. The location is relative to the root of the module.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="jaxrpc-mapping-file"
-+ type="j2ee:pathType"
-+ minOccurs="0" maxOccurs="1">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The jaxrpc-mapping-file element contains the name of a file that
-+ describes the JAX-RPC mapping between the Java interaces used by
-+ the application and the WSDL description in the wsdl-file. The
-+ file name is a relative path within the module file.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="service-qname"
-+ type="j2ee:xsdQNameType"
-+ minOccurs="0" maxOccurs="1">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The service-qname element declares the specific WSDL service
-+ element that is being refered to. It is not specified if no
-+ wsdl-file is declared.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="port-component-ref"
-+ type="j2ee:port-component-refType"
-+ minOccurs="0" maxOccurs="unbounded">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The port-component-ref element declares a client dependency
-+ on the container for resolving a Service Endpoint Interface
-+ to a WSDL port. It optionally associates the Service Endpoint
-+ Interface with a particular port-component. This is only used
-+ by the container for a Service.getPort(Class) method call.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="handler"
-+ type="j2ee:service-ref_handlerType"
-+ minOccurs="0" maxOccurs="unbounded">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ Declares the handler for a port-component. Handlers can
-+ access the init-param name/value pairs using the
-+ HandlerInfo interface. If port-name is not specified, the
-+ handler is assumed to be associated with all ports of the
-+ service.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="service-ref_handlerType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ Declares the handler for a port-component. Handlers can access the
-+ init-param name/value pairs using the HandlerInfo interface. If
-+ port-name is not specified, the handler is assumed to be associated
-+ with all ports of the service.
-+
-+ Used in: service-ref
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:sequence>
-+ <xsd:group ref="j2ee:descriptionGroup"/>
-+ <xsd:element name="handler-name"
-+ type="j2ee:string">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ Defines the name of the handler. The name must be unique
-+ within the module.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="handler-class"
-+ type="j2ee:fully-qualified-classType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ Defines a fully qualified class name for the handler
-+ implementation.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="init-param"
-+ type="j2ee:param-valueType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+
-+ <xsd:element name="soap-header"
-+ type="j2ee:xsdQNameType"
-+ minOccurs="0" maxOccurs="unbounded">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ Defines the QName of a SOAP header that will be processed
-+ by the handler.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="soap-role"
-+ type="j2ee:string"
-+ minOccurs="0" maxOccurs="unbounded">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The soap-role element contains a SOAP actor definition that
-+ the Handler will play as a role.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="port-name"
-+ type="j2ee:string"
-+ minOccurs="0" maxOccurs="unbounded">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The port-name element defines the WSDL port-name that a
-+ handler should be associated with.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+</xsd:schema>
-+
-Index: jenkins-winstone/src/conf/javax/servlet/resources/javaee_5.xsd
-===================================================================
---- /dev/null 1970-01-01 00:00:00.000000000 +0000
-+++ jenkins-winstone/src/conf/javax/servlet/resources/javaee_5.xsd 2012-04-26 11:45:47.802315463 +0100
-@@ -0,0 +1,2102 @@
-+<?xml version="1.0" encoding="UTF-8"?>
-+<xsd:schema
-+ targetNamespace="http://java.sun.com/xml/ns/javaee"
-+ xmlns:javaee="http://java.sun.com/xml/ns/javaee"
-+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
-+ elementFormDefault="qualified"
-+ attributeFormDefault="unqualified"
-+ version="5">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ @(#)javaee_5.xsds 1.65 06/02/17
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
-+
-+ Copyright 2003-2007 Sun Microsystems, Inc. All rights reserved.
-+
-+ The contents of this file are subject to the terms of either the
-+ GNU General Public License Version 2 only ("GPL") or the Common
-+ Development and Distribution License("CDDL") (collectively, the
-+ "License"). You may not use this file except in compliance with
-+ the License. You can obtain a copy of the License at
-+ https://glassfish.dev.java.net/public/CDDL+GPL.html or
-+ glassfish/bootstrap/legal/LICENSE.txt. See the License for the
-+ specific language governing permissions and limitations under the
-+ License.
-+
-+ When distributing the software, include this License Header
-+ Notice in each file and include the License file at
-+ glassfish/bootstrap/legal/LICENSE.txt. Sun designates this
-+ particular file as subject to the "Classpath" exception as
-+ provided by Sun in the GPL Version 2 section of the License file
-+ that accompanied this code. If applicable, add the following
-+ below the License Header, with the fields enclosed by brackets []
-+ replaced by your own identifying information:
-+ "Portions Copyrighted [year] [name of copyright owner]"
-+
-+ Contributor(s):
-+
-+ If you wish your version of this file to be governed by only the
-+ CDDL or only the GPL Version 2, indicate your decision by adding
-+ "[Contributor] elects to include this software in this
-+ distribution under the [CDDL or GPL Version 2] license." If you
-+ don't indicate a single choice of license, a recipient has the
-+ option to distribute your version of this file under either the
-+ CDDL, the GPL Version 2 or to extend the choice of license to its
-+ licensees as provided above. However, if you add GPL Version 2
-+ code and therefore, elected the GPL Version 2 license, then the
-+ option applies only if the new code is made subject to such
-+ option by the copyright holder.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+<xsd:annotation>
-+<xsd:documentation>
-+
-+The following definitions that appear in the common
-+shareable schema(s) of J2EE deployment descriptors should be
-+interpreted with respect to the context they are included:
-+
-+Deployment Component may indicate one of the following:
-+ j2ee application;
-+ application client;
-+ web application;
-+ enterprise bean;
-+ resource adapter;
-+
-+Deployment File may indicate one of the following:
-+ ear file;
-+ war file;
-+ jar file;
-+ rar file;
-+
-+</xsd:documentation>
-+</xsd:annotation>
-+
-+ <xsd:import namespace="http://www.w3.org/XML/1998/namespace"
-+ schemaLocation="http://www.w3.org/2001/xml.xsd"/>
-+
-+ <xsd:include schemaLocation="javaee_web_services_client_1_2.xsd"/>
-+
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:group name="descriptionGroup">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This group keeps the usage of the contained description related
-+ elements consistent across Java EE deployment descriptors.
-+
-+ All elements may occur multiple times with different languages,
-+ to support localization of the content.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="javaee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="display-name"
-+ type="javaee:display-nameType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="icon"
-+ type="javaee:iconType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ </xsd:sequence>
-+ </xsd:group>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="descriptionType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The description type is used by a description element to
-+ provide text describing the parent element. The elements
-+ that use this type should include any information that the
-+ Deployment Component's Deployment File file producer wants
-+ to provide to the consumer of the Deployment Component's
-+ Deployment File (i.e., to the Deployer). Typically, the
-+ tools used by such a Deployment File consumer will display
-+ the description when processing the parent element that
-+ contains the description.
-+
-+ The lang attribute defines the language that the
-+ description is provided in. The default value is "en" (English).
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:extension base="javaee:xsdStringType">
-+ <xsd:attribute ref="xml:lang"/>
-+ </xsd:extension>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:simpleType name="dewey-versionType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type defines a dewey decimal that is used
-+ to describe versions of documents.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:restriction base="xsd:token">
-+ <xsd:pattern value="\.?[0-9]+(\.[0-9]+)*"/>
-+ </xsd:restriction>
-+ </xsd:simpleType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="display-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The display-name type contains a short name that is intended
-+ to be displayed by tools. It is used by display-name
-+ elements. The display name need not be unique.
-+
-+ Example:
-+
-+ ...
-+ <display-name xml:lang="en">
-+ Employee Self Service
-+ </display-name>
-+
-+ The value of the xml:lang attribute is "en" (English) by default.
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:extension base="javaee:string">
-+ <xsd:attribute ref="xml:lang"/>
-+ </xsd:extension>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="ejb-linkType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The ejb-linkType is used by ejb-link
-+ elements in the ejb-ref or ejb-local-ref elements to specify
-+ that an EJB reference is linked to enterprise bean.
-+
-+ The value of the ejb-link element must be the ejb-name of an
-+ enterprise bean in the same ejb-jar file or in another ejb-jar
-+ file in the same Java EE application unit.
-+
-+ Alternatively, the name in the ejb-link element may be
-+ composed of a path name specifying the ejb-jar containing the
-+ referenced enterprise bean with the ejb-name of the target
-+ bean appended and separated from the path name by "#". The
-+ path name is relative to the Deployment File containing
-+ Deployment Component that is referencing the enterprise
-+ bean. This allows multiple enterprise beans with the same
-+ ejb-name to be uniquely identified.
-+
-+ Examples:
-+
-+ <ejb-link>EmployeeRecord</ejb-link>
-+
-+ <ejb-link>../products/product.jar#ProductEJB</ejb-link>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:string"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="ejb-local-refType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The ejb-local-refType is used by ejb-local-ref elements for
-+ the declaration of a reference to an enterprise bean's local
-+ home or to the local business interface of a 3.0 bean.
-+ The declaration consists of:
-+
-+ - an optional description
-+ - the EJB reference name used in the code of the Deployment
-+ Component that's referencing the enterprise bean.
-+ - the optional expected type of the referenced enterprise bean
-+ - the optional expected local interface of the referenced
-+ enterprise bean or the local business interface of the
-+ referenced enterprise bean.
-+ - the optional expected local home interface of the referenced
-+ enterprise bean. Not applicable if this ejb-local-ref refers
-+ to the local business interface of a 3.0 bean.
-+ - optional ejb-link information, used to specify the
-+ referenced enterprise bean
-+ - optional elements to define injection of the named enterprise
-+ bean into a component field or property.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="javaee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="ejb-ref-name"
-+ type="javaee:ejb-ref-nameType"/>
-+ <xsd:element name="ejb-ref-type"
-+ type="javaee:ejb-ref-typeType"
-+ minOccurs="0"/>
-+ <xsd:element name="local-home"
-+ type="javaee:local-homeType"
-+ minOccurs="0"/>
-+ <xsd:element name="local"
-+ type="javaee:localType"
-+ minOccurs="0"/>
-+ <xsd:element name="ejb-link"
-+ type="javaee:ejb-linkType"
-+ minOccurs="0"/>
-+ <xsd:group ref="javaee:resourceGroup"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="ejb-ref-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The ejb-ref-name element contains the name of an EJB
-+ reference. The EJB reference is an entry in the
-+ Deployment Component's environment and is relative to the
-+ java:comp/env context. The name must be unique within the
-+ Deployment Component.
-+
-+ It is recommended that name is prefixed with "ejb/".
-+
-+ Example:
-+
-+ <ejb-ref-name>ejb/Payroll</ejb-ref-name>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:jndi-nameType"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="ejb-ref-typeType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The ejb-ref-typeType contains the expected type of the
-+ referenced enterprise bean.
-+
-+ The ejb-ref-type designates a value
-+ that must be one of the following:
-+
-+ Entity
-+ Session
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:string">
-+ <xsd:enumeration value="Entity"/>
-+ <xsd:enumeration value="Session"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="ejb-refType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The ejb-refType is used by ejb-ref elements for the
-+ declaration of a reference to an enterprise bean's home or
-+ to the remote business interface of a 3.0 bean.
-+ The declaration consists of:
-+
-+ - an optional description
-+ - the EJB reference name used in the code of
-+ the Deployment Component that's referencing the enterprise
-+ bean.
-+ - the optional expected type of the referenced enterprise bean
-+ - the optional remote interface of the referenced enterprise bean
-+ or the remote business interface of the referenced enterprise
-+ bean
-+ - the optional expected home interface of the referenced
-+ enterprise bean. Not applicable if this ejb-ref
-+ refers to the remote business interface of a 3.0 bean.
-+ - optional ejb-link information, used to specify the
-+ referenced enterprise bean
-+ - optional elements to define injection of the named enterprise
-+ bean into a component field or property
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="javaee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="ejb-ref-name"
-+ type="javaee:ejb-ref-nameType"/>
-+ <xsd:element name="ejb-ref-type"
-+ type="javaee:ejb-ref-typeType"
-+ minOccurs="0"/>
-+ <xsd:element name="home"
-+ type="javaee:homeType"
-+ minOccurs="0"/>
-+ <xsd:element name="remote"
-+ type="javaee:remoteType"
-+ minOccurs="0"/>
-+ <xsd:element name="ejb-link"
-+ type="javaee:ejb-linkType"
-+ minOccurs="0"/>
-+ <xsd:group ref="javaee:resourceGroup"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="emptyType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type is used to designate an empty
-+ element when used.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="env-entry-type-valuesType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ This type contains the fully-qualified Java type of the
-+ environment entry value that is expected by the
-+ application's code.
-+
-+ The following are the legal values of env-entry-type-valuesType:
-+
-+ java.lang.Boolean
-+ java.lang.Byte
-+ java.lang.Character
-+ java.lang.String
-+ java.lang.Short
-+ java.lang.Integer
-+ java.lang.Long
-+ java.lang.Float
-+ java.lang.Double
-+
-+ Example:
-+
-+ <env-entry-type>java.lang.Boolean</env-entry-type>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:string">
-+ <xsd:enumeration value="java.lang.Boolean"/>
-+ <xsd:enumeration value="java.lang.Byte"/>
-+ <xsd:enumeration value="java.lang.Character"/>
-+ <xsd:enumeration value="java.lang.String"/>
-+ <xsd:enumeration value="java.lang.Short"/>
-+ <xsd:enumeration value="java.lang.Integer"/>
-+ <xsd:enumeration value="java.lang.Long"/>
-+ <xsd:enumeration value="java.lang.Float"/>
-+ <xsd:enumeration value="java.lang.Double"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="env-entryType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The env-entryType is used to declare an application's
-+ environment entry. The declaration consists of an optional
-+ description, the name of the environment entry, a type
-+ (optional if the value is injected, otherwise required), and
-+ an optional value.
-+
-+ It also includes optional elements to define injection of
-+ the named resource into fields or JavaBeans properties.
-+
-+ If a value is not specified and injection is requested,
-+ no injection will occur and no entry of the specified name
-+ will be created. This allows an initial value to be
-+ specified in the source code without being incorrectly
-+ changed when no override has been specified.
-+
-+ If a value is not specified and no injection is requested,
-+ a value must be supplied during deployment.
-+
-+ This type is used by env-entry elements.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="javaee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="env-entry-name"
-+ type="javaee:jndi-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The env-entry-name element contains the name of a
-+ Deployment Component's environment entry. The name
-+ is a JNDI name relative to the java:comp/env
-+ context. The name must be unique within a
-+ Deployment Component. The uniqueness
-+ constraints must be defined within the declared
-+ context.
-+
-+ Example:
-+
-+ <env-entry-name>minAmount</env-entry-name>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="env-entry-type"
-+ type="javaee:env-entry-type-valuesType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The env-entry-type element contains the Java language
-+ type of the environment entry. If an injection target
-+ is specified for the environment entry, the type may
-+ be omitted, or must match the type of the injection
-+ target. If no injection target is specified, the type
-+ is required.
-+
-+ Example:
-+
-+ <env-entry-type>java.lang.Integer</env-entry-type>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="env-entry-value"
-+ type="javaee:xsdStringType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The env-entry-value designates the value of a
-+ Deployment Component's environment entry. The value
-+ must be a String that is valid for the
-+ constructor of the specified type that takes a
-+ single String parameter, or for java.lang.Character,
-+ a single character.
-+
-+ Example:
-+
-+ <env-entry-value>100.00</env-entry-value>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:group ref="javaee:resourceGroup"/>
-+
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="fully-qualified-classType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The elements that use this type designate the name of a
-+ Java class or interface. The name is in the form of a
-+ "binary name", as defined in the JLS. This is the form
-+ of name used in Class.forName(). Tools that need the
-+ canonical name (the name used in source code) will need
-+ to convert this binary name to the canonical name.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:string"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="generic-booleanType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type defines four different values which can designate
-+ boolean values. This includes values yes and no which are
-+ not designated by xsd:boolean
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:string">
-+ <xsd:enumeration value="true"/>
-+ <xsd:enumeration value="false"/>
-+ <xsd:enumeration value="yes"/>
-+ <xsd:enumeration value="no"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="homeType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The homeType defines the fully-qualified name of
-+ an enterprise bean's home interface.
-+
-+ Example:
-+
-+ <home>com.aardvark.payroll.PayrollHome</home>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:fully-qualified-classType"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="iconType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The icon type contains small-icon and large-icon elements
-+ that specify the file names for small and large GIF, JPEG,
-+ or PNG icon images used to represent the parent element in a
-+ GUI tool.
-+
-+ The xml:lang attribute defines the language that the
-+ icon file names are provided in. Its value is "en" (English)
-+ by default.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="small-icon" type="javaee:pathType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The small-icon element contains the name of a file
-+ containing a small (16 x 16) icon image. The file
-+ name is a relative path within the Deployment
-+ Component's Deployment File.
-+
-+ The image may be in the GIF, JPEG, or PNG format.
-+ The icon can be used by tools.
-+
-+ Example:
-+
-+ <small-icon>employee-service-icon16x16.jpg</small-icon>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="large-icon" type="javaee:pathType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The large-icon element contains the name of a file
-+ containing a large
-+ (32 x 32) icon image. The file name is a relative
-+ path within the Deployment Component's Deployment
-+ File.
-+
-+ The image may be in the GIF, JPEG, or PNG format.
-+ The icon can be used by tools.
-+
-+ Example:
-+
-+ <large-icon>employee-service-icon32x32.jpg</large-icon>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ </xsd:sequence>
-+
-+ <xsd:attribute ref="xml:lang"/>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="injection-targetType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ An injection target specifies a class and a name within
-+ that class into which a resource should be injected.
-+
-+ The injection target class specifies the fully qualified
-+ class name that is the target of the injection. The
-+ Java EE specifications describe which classes can be an
-+ injection target.
-+
-+ The injection target name specifies the target within
-+ the specified class. The target is first looked for as a
-+ JavaBeans property name. If not found, the target is
-+ looked for as a field name.
-+
-+ The specified resource will be injected into the target
-+ during initialization of the class by either calling the
-+ set method for the target property or by setting a value
-+ into the named field.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:sequence>
-+ <xsd:element name="injection-target-class"
-+ type="javaee:fully-qualified-classType"/>
-+ <xsd:element name="injection-target-name"
-+ type="javaee:java-identifierType"/>
-+ </xsd:sequence>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="java-identifierType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The java-identifierType defines a Java identifier.
-+ The users of this type should further verify that
-+ the content does not contain Java reserved keywords.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:string">
-+ <xsd:pattern value="($|_|\p{L})(\p{L}|\p{Nd}|_|$)*"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="java-typeType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This is a generic type that designates a Java primitive
-+ type or a fully qualified name of a Java interface/type,
-+ or an array of such types.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:string">
-+ <xsd:pattern value="[^\p{Z}]*"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="jndi-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The jndi-nameType type designates a JNDI name in the
-+ Deployment Component's environment and is relative to the
-+ java:comp/env context. A JNDI name must be unique within the
-+ Deployment Component.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:string"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:group name="jndiEnvironmentRefsGroup">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This group keeps the usage of the contained JNDI environment
-+ reference elements consistent across Java EE deployment descriptors.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:sequence>
-+ <xsd:element name="env-entry"
-+ type="javaee:env-entryType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ <xsd:element name="ejb-ref"
-+ type="javaee:ejb-refType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ <xsd:element name="ejb-local-ref"
-+ type="javaee:ejb-local-refType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ <xsd:group ref="javaee:service-refGroup"/>
-+ <xsd:element name="resource-ref"
-+ type="javaee:resource-refType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ <xsd:element name="resource-env-ref"
-+ type="javaee:resource-env-refType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ <xsd:element name="message-destination-ref"
-+ type="javaee:message-destination-refType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ <xsd:element name="persistence-context-ref"
-+ type="javaee:persistence-context-refType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ <xsd:element name="persistence-unit-ref"
-+ type="javaee:persistence-unit-refType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ <xsd:element name="post-construct"
-+ type="javaee:lifecycle-callbackType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ <xsd:element name="pre-destroy"
-+ type="javaee:lifecycle-callbackType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ </xsd:sequence>
-+ </xsd:group>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="lifecycle-callbackType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The lifecycle-callback type specifies a method on a
-+ class to be called when a lifecycle event occurs.
-+ Note that each class may have only one lifecycle callback
-+ method for any given event and that the method may not
-+ be overloaded.
-+
-+ If the lifefycle-callback-class element is missing then
-+ the class defining the callback is assumed to be the
-+ component class in scope at the place in the descriptor
-+ in which the callback definition appears.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:sequence>
-+ <xsd:element name="lifecycle-callback-class"
-+ type="javaee:fully-qualified-classType"
-+ minOccurs="0"/>
-+ <xsd:element name="lifecycle-callback-method"
-+ type="javaee:java-identifierType"/>
-+ </xsd:sequence>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="listenerType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The listenerType indicates the deployment properties for a web
-+ application listener bean.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:group ref="javaee:descriptionGroup"/>
-+ <xsd:element name="listener-class"
-+ type="javaee:fully-qualified-classType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The listener-class element declares a class in the
-+ application must be registered as a web
-+ application listener bean. The value is the fully
-+ qualified classname of the listener class.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="local-homeType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The local-homeType defines the fully-qualified
-+ name of an enterprise bean's local home interface.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:fully-qualified-classType"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="localType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The localType defines the fully-qualified name of an
-+ enterprise bean's local interface.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:fully-qualified-classType"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="message-destination-linkType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The message-destination-linkType is used to link a message
-+ destination reference or message-driven bean to a message
-+ destination.
-+
-+ The Assembler sets the value to reflect the flow of messages
-+ between producers and consumers in the application.
-+
-+ The value must be the message-destination-name of a message
-+ destination in the same Deployment File or in another
-+ Deployment File in the same Java EE application unit.
-+
-+ Alternatively, the value may be composed of a path name
-+ specifying a Deployment File containing the referenced
-+ message destination with the message-destination-name of the
-+ destination appended and separated from the path name by
-+ "#". The path name is relative to the Deployment File
-+ containing Deployment Component that is referencing the
-+ message destination. This allows multiple message
-+ destinations with the same name to be uniquely identified.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:string"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="message-destination-refType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The message-destination-ref element contains a declaration
-+ of Deployment Component's reference to a message destination
-+ associated with a resource in Deployment Component's
-+ environment. It consists of:
-+
-+ - an optional description
-+ - the message destination reference name
-+ - an optional message destination type
-+ - an optional specification as to whether
-+ the destination is used for
-+ consuming or producing messages, or both.
-+ if not specified, "both" is assumed.
-+ - an optional link to the message destination
-+ - optional injection targets
-+
-+ The message destination type must be supplied unless an
-+ injection target is specified, in which case the type
-+ of the target is used. If both are specified, the type
-+ must be assignment compatible with the type of the injection
-+ target.
-+
-+ Examples:
-+
-+ <message-destination-ref>
-+ <message-destination-ref-name>jms/StockQueue
-+ </message-destination-ref-name>
-+ <message-destination-type>javax.jms.Queue
-+ </message-destination-type>
-+ <message-destination-usage>Consumes
-+ </message-destination-usage>
-+ <message-destination-link>CorporateStocks
-+ </message-destination-link>
-+ </message-destination-ref>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="javaee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="message-destination-ref-name"
-+ type="javaee:jndi-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The message-destination-ref-name element specifies
-+ the name of a message destination reference; its
-+ value is the environment entry name used in
-+ Deployment Component code. The name is a JNDI name
-+ relative to the java:comp/env context and must be
-+ unique within an ejb-jar (for enterprise beans) or a
-+ Deployment File (for others).
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="message-destination-type"
-+ type="javaee:message-destination-typeType"
-+ minOccurs="0"/>
-+ <xsd:element name="message-destination-usage"
-+ type="javaee:message-destination-usageType"
-+ minOccurs="0"/>
-+ <xsd:element name="message-destination-link"
-+ type="javaee:message-destination-linkType"
-+ minOccurs="0"/>
-+
-+ <xsd:group ref="javaee:resourceGroup"/>
-+
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="message-destination-typeType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The message-destination-typeType specifies the type of
-+ the destination. The type is specified by the Java interface
-+ expected to be implemented by the destination.
-+
-+ Example:
-+
-+ <message-destination-type>javax.jms.Queue
-+ </message-destination-type>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:fully-qualified-classType"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="message-destination-usageType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The message-destination-usageType specifies the use of the
-+ message destination indicated by the reference. The value
-+ indicates whether messages are consumed from the message
-+ destination, produced for the destination, or both. The
-+ Assembler makes use of this information in linking producers
-+ of a destination with its consumers.
-+
-+ The value of the message-destination-usage element must be
-+ one of the following:
-+ Consumes
-+ Produces
-+ ConsumesProduces
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:string">
-+ <xsd:enumeration value="Consumes"/>
-+ <xsd:enumeration value="Produces"/>
-+ <xsd:enumeration value="ConsumesProduces"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="message-destinationType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The message-destinationType specifies a message
-+ destination. The logical destination described by this
-+ element is mapped to a physical destination by the Deployer.
-+
-+ The message destination element contains:
-+
-+ - an optional description
-+ - an optional display-name
-+ - an optional icon
-+ - a message destination name which must be unique
-+ among message destination names within the same
-+ Deployment File.
-+ - an optional mapped name
-+
-+ Example:
-+
-+ <message-destination>
-+ <message-destination-name>CorporateStocks
-+ </message-destination-name>
-+ </message-destination>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:sequence>
-+ <xsd:group ref="javaee:descriptionGroup"/>
-+ <xsd:element name="message-destination-name"
-+ type="javaee:string">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The message-destination-name element specifies a
-+ name for a message destination. This name must be
-+ unique among the names of message destinations
-+ within the Deployment File.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="mapped-name"
-+ type="javaee:xsdStringType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ A product specific name that this message destination
-+ should be mapped to. Each message-destination-ref
-+ element that references this message destination will
-+ define a name in the namespace of the referencing
-+ component. (It's a name in the JNDI java:comp/env
-+ namespace.) Many application servers provide a way to
-+ map these local names to names of resources known to the
-+ application server. This mapped name is often a global
-+ JNDI name, but may be a name of any form. Each of the
-+ local names should be mapped to this same global name.
-+
-+ Application servers are not required to support any
-+ particular form or type of mapped name, nor the ability
-+ to use mapped names. The mapped name is
-+ product-dependent and often installation-dependent. No
-+ use of a mapped name is portable.
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="param-valueType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type is a general type that can be used to declare
-+ parameter/value lists.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="javaee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="param-name"
-+ type="javaee:string">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The param-name element contains the name of a
-+ parameter.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="param-value"
-+ type="javaee:xsdStringType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The param-value element contains the value of a
-+ parameter.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="pathType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The elements that use this type designate either a relative
-+ path or an absolute path starting with a "/".
-+
-+ In elements that specify a pathname to a file within the
-+ same Deployment File, relative filenames (i.e., those not
-+ starting with "/") are considered relative to the root of
-+ the Deployment File's namespace. Absolute filenames (i.e.,
-+ those starting with "/") also specify names in the root of
-+ the Deployment File's namespace. In general, relative names
-+ are preferred. The exception is .war files where absolute
-+ names are preferred for consistency with the Servlet API.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:string"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="persistence-context-refType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The persistence-context-ref element contains a declaration
-+ of Deployment Component's reference to a persistence context
-+ associated within a Deployment Component's
-+ environment. It consists of:
-+
-+ - an optional description
-+ - the persistence context reference name
-+ - an optional persistence unit name. If not specified,
-+ the default persistence unit is assumed.
-+ - an optional specification as to whether
-+ the persistence context type is Transaction or
-+ Extended. If not specified, Transaction is assumed.
-+ - an optional list of persistence properties
-+ - optional injection targets
-+
-+ Examples:
-+
-+ <persistence-context-ref>
-+ <persistence-context-ref-name>myPersistenceContext
-+ </persistence-context-ref-name>
-+ </persistence-context-ref>
-+
-+ <persistence-context-ref>
-+ <persistence-context-ref-name>myPersistenceContext
-+ </persistence-context-ref-name>
-+ <persistence-unit-name>PersistenceUnit1
-+ </persistence-unit-name>
-+ <persistence-context-type>Extended</persistence-context-type>
-+ </persistence-context-ref>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="javaee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="persistence-context-ref-name"
-+ type="javaee:jndi-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The persistence-context-ref-name element specifies
-+ the name of a persistence context reference; its
-+ value is the environment entry name used in
-+ Deployment Component code. The name is a JNDI name
-+ relative to the java:comp/env context.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="persistence-unit-name"
-+ type="javaee:string"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The Application Assembler(or BeanProvider) may use the
-+ following syntax to avoid the need to rename persistence
-+ units to have unique names within a Java EE application.
-+
-+ The Application Assembler specifies the pathname of the
-+ root of the persistence.xml file for the referenced
-+ persistence unit and appends the name of the persistence
-+ unit separated from the pathname by #. The pathname is
-+ relative to the referencing application component jar file.
-+ In this manner, multiple persistence units with the same
-+ persistence unit name may be uniquely identified when the
-+ Application Assembler cannot change persistence unit names.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="persistence-context-type"
-+ type="javaee:persistence-context-typeType"
-+ minOccurs="0"/>
-+
-+ <xsd:element name="persistence-property"
-+ type="javaee:propertyType"
-+ minOccurs="0"
-+ maxOccurs="unbounded">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ Used to specify properties for the container or persistence
-+ provider. Vendor-specific properties may be included in
-+ the set of properties. Properties that are not recognized
-+ by a vendor must be ignored. Entries that make use of the
-+ namespace javax.persistence and its subnamespaces must not
-+ be used for vendor-specific properties. The namespace
-+ javax.persistence is reserved for use by the specification.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:group ref="javaee:resourceGroup"/>
-+
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="persistence-context-typeType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The persistence-context-typeType specifies the transactional
-+ nature of a persistence context reference.
-+
-+ The value of the persistence-context-type element must be
-+ one of the following:
-+ Transaction
-+ Extended
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:string">
-+ <xsd:enumeration value="Transaction"/>
-+ <xsd:enumeration value="Extended"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="persistence-unit-refType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The persistence-unit-ref element contains a declaration
-+ of Deployment Component's reference to a persistence unit
-+ associated within a Deployment Component's
-+ environment. It consists of:
-+
-+ - an optional description
-+ - the persistence unit reference name
-+ - an optional persistence unit name. If not specified,
-+ the default persistence unit is assumed.
-+ - optional injection targets
-+
-+ Examples:
-+
-+ <persistence-unit-ref>
-+ <persistence-unit-ref-name>myPersistenceUnit
-+ </persistence-unit-ref-name>
-+ </persistence-unit-ref>
-+
-+ <persistence-unit-ref>
-+ <persistence-unit-ref-name>myPersistenceUnit
-+ </persistence-unit-ref-name>
-+ <persistence-unit-name>PersistenceUnit1
-+ </persistence-unit-name>
-+ </persistence-unit-ref>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="javaee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="persistence-unit-ref-name"
-+ type="javaee:jndi-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The persistence-unit-ref-name element specifies
-+ the name of a persistence unit reference; its
-+ value is the environment entry name used in
-+ Deployment Component code. The name is a JNDI name
-+ relative to the java:comp/env context.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="persistence-unit-name"
-+ type="javaee:string"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The Application Assembler(or BeanProvider) may use the
-+ following syntax to avoid the need to rename persistence
-+ units to have unique names within a Java EE application.
-+
-+ The Application Assembler specifies the pathname of the
-+ root of the persistence.xml file for the referenced
-+ persistence unit and appends the name of the persistence
-+ unit separated from the pathname by #. The pathname is
-+ relative to the referencing application component jar file.
-+ In this manner, multiple persistence units with the same
-+ persistence unit name may be uniquely identified when the
-+ Application Assembler cannot change persistence unit names.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:group ref="javaee:resourceGroup"/>
-+
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="propertyType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ Specifies a name/value pair.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="name"
-+ type="javaee:xsdStringType">
-+ </xsd:element>
-+ <xsd:element name="value"
-+ type="javaee:xsdStringType">
-+ </xsd:element>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="remoteType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The remote element contains the fully-qualified name
-+ of the enterprise bean's remote interface.
-+
-+ Example:
-+
-+ <remote>com.wombat.empl.EmployeeService</remote>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:fully-qualified-classType"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="res-authType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The res-authType specifies whether the Deployment Component
-+ code signs on programmatically to the resource manager, or
-+ whether the Container will sign on to the resource manager
-+ on behalf of the Deployment Component. In the latter case,
-+ the Container uses information that is supplied by the
-+ Deployer.
-+
-+ The value must be one of the two following:
-+
-+ Application
-+ Container
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:string">
-+ <xsd:enumeration value="Application"/>
-+ <xsd:enumeration value="Container"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="res-sharing-scopeType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The res-sharing-scope type specifies whether connections
-+ obtained through the given resource manager connection
-+ factory reference can be shared. The value, if specified,
-+ must be one of the two following:
-+
-+ Shareable
-+ Unshareable
-+
-+ The default value is Shareable.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:string">
-+ <xsd:enumeration value="Shareable"/>
-+ <xsd:enumeration value="Unshareable"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="resource-env-refType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The resource-env-refType is used to define
-+ resource-env-type elements. It contains a declaration of a
-+ Deployment Component's reference to an administered object
-+ associated with a resource in the Deployment Component's
-+ environment. It consists of an optional description, the
-+ resource environment reference name, and an optional
-+ indication of the resource environment reference type
-+ expected by the Deployment Component code.
-+
-+ It also includes optional elements to define injection of
-+ the named resource into fields or JavaBeans properties.
-+
-+ The resource environment type must be supplied unless an
-+ injection target is specified, in which case the type
-+ of the target is used. If both are specified, the type
-+ must be assignment compatible with the type of the injection
-+ target.
-+
-+ Example:
-+
-+ <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>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="javaee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="resource-env-ref-name"
-+ type="javaee:jndi-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The resource-env-ref-name element specifies the name
-+ of a resource environment reference; its value is
-+ the environment entry name used in
-+ the Deployment Component code. The name is a JNDI
-+ name relative to the java:comp/env context and must
-+ be unique within a Deployment Component.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="resource-env-ref-type"
-+ type="javaee:fully-qualified-classType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The resource-env-ref-type element specifies the type
-+ of a resource environment reference. It is the
-+ fully qualified name of a Java language class or
-+ interface.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:group ref="javaee:resourceGroup"/>
-+
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="resource-refType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The resource-refType contains a declaration of a
-+ Deployment Component's reference to an external resource. It
-+ consists of an optional description, the resource manager
-+ connection factory reference name, an optional indication of
-+ the resource manager connection factory type expected by the
-+ Deployment Component code, an optional type of authentication
-+ (Application or Container), and an optional specification of
-+ the shareability of connections obtained from the resource
-+ (Shareable or Unshareable).
-+
-+ It also includes optional elements to define injection of
-+ the named resource into fields or JavaBeans properties.
-+
-+ The connection factory type must be supplied unless an
-+ injection target is specified, in which case the type
-+ of the target is used. If both are specified, the type
-+ must be assignment compatible with the type of the injection
-+ target.
-+
-+ Example:
-+
-+ <resource-ref>
-+ <res-ref-name>jdbc/EmployeeAppDB</res-ref-name>
-+ <res-type>javax.sql.DataSource</res-type>
-+ <res-auth>Container</res-auth>
-+ <res-sharing-scope>Shareable</res-sharing-scope>
-+ </resource-ref>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="javaee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="res-ref-name"
-+ type="javaee:jndi-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The res-ref-name element specifies the name of a
-+ resource manager connection factory reference.
-+ The name is a JNDI name relative to the
-+ java:comp/env context.
-+ The name must be unique within a Deployment File.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="res-type"
-+ type="javaee:fully-qualified-classType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The res-type element specifies the type of the data
-+ source. The type is specified by the fully qualified
-+ Java language class or interface
-+ expected to be implemented by the data source.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="res-auth"
-+ type="javaee:res-authType"
-+ minOccurs="0"/>
-+
-+ <xsd:element name="res-sharing-scope"
-+ type="javaee:res-sharing-scopeType"
-+ minOccurs="0"/>
-+
-+ <xsd:group ref="javaee:resourceGroup"/>
-+
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:group name="resourceGroup">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This group collects elements that are common to all the
-+ JNDI resource elements.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:sequence>
-+ <xsd:element name="mapped-name"
-+ type="javaee:xsdStringType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ A product specific name that this resource should be
-+ mapped to. The name of this resource, as defined by the
-+ resource's name element or defaulted, is a name that is
-+ local to the application component using the resource.
-+ (It's a name in the JNDI java:comp/env namespace.) Many
-+ application servers provide a way to map these local
-+ names to names of resources known to the application
-+ server. This mapped name is often a global JNDI name,
-+ but may be a name of any form.
-+
-+ Application servers are not required to support any
-+ particular form or type of mapped name, nor the ability
-+ to use mapped names. The mapped name is
-+ product-dependent and often installation-dependent. No
-+ use of a mapped name is portable.
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="injection-target"
-+ type="javaee:injection-targetType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ </xsd:sequence>
-+ </xsd:group>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="role-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The role-nameType designates the name of a security role.
-+
-+ The name must conform to the lexical rules for a token.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:string"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="run-asType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The run-asType specifies the run-as identity to be
-+ used for the execution of a component. It contains an
-+ optional description, and the name of a security role.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="javaee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="role-name"
-+ type="javaee:role-nameType"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="security-role-refType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The security-role-refType contains the declaration of a
-+ security role reference in a component's or a
-+ Deployment Component's code. The declaration consists of an
-+ optional description, the security role name used in the
-+ code, and an optional link to a security role. If the
-+ security role is not specified, the Deployer must choose an
-+ appropriate security role.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="javaee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="role-name"
-+ type="javaee:role-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The value of the role-name element must be the String used
-+ as the parameter to the
-+ EJBContext.isCallerInRole(String roleName) method or the
-+ HttpServletRequest.isUserInRole(String role) method.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="role-link"
-+ type="javaee:role-nameType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The role-link element is a 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.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="security-roleType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ The security-roleType contains the definition of a security
-+ role. The definition consists of an optional description of
-+ the security role, and the security role name.
-+
-+ Example:
-+
-+ <security-role>
-+ <description>
-+ This role includes all employees who are authorized
-+ to access the employee service application.
-+ </description>
-+ <role-name>employee</role-name>
-+ </security-role>
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="javaee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="role-name"
-+ type="javaee:role-nameType"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="string">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This is a special string datatype that is defined by Java EE as
-+ a base type for defining collapsed strings. When schemas
-+ require trailing/leading space elimination as well as
-+ collapsing the existing whitespace, this base type may be
-+ used.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:extension base="xsd:token">
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:extension>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="true-falseType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This simple type designates a boolean with only two
-+ permissible values
-+
-+ - true
-+ - false
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:xsdBooleanType">
-+ <xsd:pattern value="(true|false)"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="url-patternType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The url-patternType contains the url pattern of the mapping.
-+ It must follow the rules specified in Section 11.2 of the
-+ Servlet API Specification. This pattern is assumed to be in
-+ URL-decoded form and must not contain CR(#xD) or LF(#xA).
-+ If it contains those characters, the container must inform
-+ the developer with a descriptive error message.
-+ The container must preserve all characters including whitespaces.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:extension base="xsd:string"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="xsdAnyURIType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type adds an "id" attribute to xsd:anyURI.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:extension base="xsd:anyURI">
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:extension>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="xsdBooleanType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type adds an "id" attribute to xsd:boolean.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:extension base="xsd:boolean">
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:extension>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="xsdIntegerType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type adds an "id" attribute to xsd:integer.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:extension base="xsd:integer">
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:extension>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="xsdNMTOKENType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type adds an "id" attribute to xsd:NMTOKEN.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:extension base="xsd:NMTOKEN">
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:extension>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="xsdNonNegativeIntegerType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type adds an "id" attribute to xsd:nonNegativeInteger.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:extension base="xsd:nonNegativeInteger">
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:extension>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="xsdPositiveIntegerType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type adds an "id" attribute to xsd:positiveInteger.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:extension base="xsd:positiveInteger">
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:extension>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="xsdQNameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type adds an "id" attribute to xsd:QName.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:extension base="xsd:QName">
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:extension>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="xsdStringType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type adds an "id" attribute to xsd:string.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:extension base="xsd:string">
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:extension>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+</xsd:schema>
-+
-Index: jenkins-winstone/src/conf/javax/servlet/resources/javaee_web_services_client_1_2.xsd
-===================================================================
---- /dev/null 1970-01-01 00:00:00.000000000 +0000
-+++ jenkins-winstone/src/conf/javax/servlet/resources/javaee_web_services_client_1_2.xsd 2012-04-26 11:45:47.802315463 +0100
-@@ -0,0 +1,585 @@
-+<?xml version="1.0" encoding="UTF-8"?>
-+<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
-+ targetNamespace="http://java.sun.com/xml/ns/javaee"
-+ xmlns:javaee="http://java.sun.com/xml/ns/javaee"
-+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
-+ elementFormDefault="qualified"
-+ attributeFormDefault="unqualified"
-+ version="1.2">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ @(#)javaee_web_services_client_1_2.xsds 1.19 02/13/06
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
-+
-+ Copyright 2003-2007 Sun Microsystems, Inc. All rights reserved.
-+
-+ The contents of this file are subject to the terms of either the
-+ GNU General Public License Version 2 only ("GPL") or the Common
-+ Development and Distribution License("CDDL") (collectively, the
-+ "License"). You may not use this file except in compliance with
-+ the License. You can obtain a copy of the License at
-+ https://glassfish.dev.java.net/public/CDDL+GPL.html or
-+ glassfish/bootstrap/legal/LICENSE.txt. See the License for the
-+ specific language governing permissions and limitations under the
-+ License.
-+
-+ When distributing the software, include this License Header
-+ Notice in each file and include the License file at
-+ glassfish/bootstrap/legal/LICENSE.txt. Sun designates this
-+ particular file as subject to the "Classpath" exception as
-+ provided by Sun in the GPL Version 2 section of the License file
-+ that accompanied this code. If applicable, add the following
-+ below the License Header, with the fields enclosed by brackets []
-+ replaced by your own identifying information:
-+ "Portions Copyrighted [year] [name of copyright owner]"
-+
-+ Contributor(s):
-+
-+ If you wish your version of this file to be governed by only the
-+ CDDL or only the GPL Version 2, indicate your decision by adding
-+ "[Contributor] elects to include this software in this
-+ distribution under the [CDDL or GPL Version 2] license." If you
-+ don't indicate a single choice of license, a recipient has the
-+ option to distribute your version of this file under either the
-+ CDDL, the GPL Version 2 or to extend the choice of license to its
-+ licensees as provided above. However, if you add GPL Version 2
-+ code and therefore, elected the GPL Version 2 license, then the
-+ option applies only if the new code is made subject to such
-+ option by the copyright holder.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ (C) Copyright International Business Machines Corporation 2002
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="port-component-refType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The port-component-ref element declares a client dependency
-+ on the container for resolving a Service Endpoint Interface
-+ to a WSDL port. It optionally associates the Service Endpoint
-+ Interface with a particular port-component. This is only used
-+ by the container for a Service.getPort(Class) method call.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="service-endpoint-interface"
-+ type="javaee:fully-qualified-classType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The service-endpoint-interface element defines a fully qualified
-+ Java class that represents the Service Endpoint Interface of a
-+ WSDL port.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="enable-mtom"
-+ type="javaee:true-falseType"
-+ minOccurs="0" maxOccurs="1">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ Used to enable or disable SOAP MTOM/XOP mechanism on the client
-+ side for a port-component.
-+
-+ Not to be specified for JAX-RPC runtime
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="port-component-link"
-+ type="javaee:string"
-+ minOccurs="0" maxOccurs="1">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The port-component-link element links a port-component-ref
-+ to a specific port-component required to be made available
-+ by a service reference.
-+
-+ The value of a port-component-link must be the
-+ port-component-name of a port-component in the same module
-+ or another module in the same application unit. The syntax
-+ for specification follows the syntax defined for ejb-link
-+ in the EJB 2.0 specification.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:group name="service-refGroup">
-+ <xsd:sequence>
-+ <xsd:element name="service-ref"
-+ type="javaee:service-refType"
-+ minOccurs="0" maxOccurs="unbounded">
-+ <xsd:key name="service-ref_handler-name-key">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ Defines the name of the handler. The name must be unique
-+ within the module.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:selector xpath="javaee:handler"/>
-+ <xsd:field xpath="javaee:handler-name"/>
-+ </xsd:key>
-+ </xsd:element>
-+ </xsd:sequence>
-+ </xsd:group>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="service-refType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The service-ref element declares a reference to a Web
-+ service. It contains optional description, display name and
-+ icons, a declaration of the required Service interface,
-+ an optional WSDL document location, an optional set
-+ of JAX-RPC mappings, an optional QName for the service element,
-+ an optional set of Service Endpoint Interfaces to be resolved
-+ by the container to a WSDL port, and an optional set of handlers.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:group ref="javaee:descriptionGroup"/>
-+ <xsd:element name="service-ref-name"
-+ type="javaee:jndi-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The service-ref-name element declares logical name that the
-+ components in the module use to look up the Web service. It
-+ is recommended that all service reference names start with
-+ "service/".
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="service-interface"
-+ type="javaee:fully-qualified-classType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The service-interface element declares the fully qualified class
-+ name of the JAX-RPC Service interface the client depends on.
-+ In most cases the value will be javax.xml.rpc.Service. A JAX-RPC
-+ generated Service Interface class may also be specified.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="service-ref-type"
-+ type="javaee:fully-qualified-classType"
-+ minOccurs="0" maxOccurs="1">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The service-ref-type element declares the type of the service-ref
-+ element that is injected or returned when a JNDI lookup is done.
-+ This must be either a fully qualified name of Service class or
-+ the fully qualified name of service endpoint interface class.
-+ This is only used with JAX-WS runtime where the corresponding
-+ @WebServiceRef annotation can be used to denote both a Service
-+ or a Port.
-+
-+ If this is not specified, then the type of service-ref element
-+ that is injected or returned when a JNDI lookup is done is
-+ always a Service interface/class.
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="wsdl-file"
-+ type="javaee:xsdAnyURIType"
-+ minOccurs="0" maxOccurs="1">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The wsdl-file element contains the URI location of a WSDL
-+ file. The location is relative to the root of the module.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="jaxrpc-mapping-file"
-+ type="javaee:pathType"
-+ minOccurs="0" maxOccurs="1">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The jaxrpc-mapping-file element contains the name of a file that
-+ describes the JAX-RPC mapping between the Java interaces used by
-+ the application and the WSDL description in the wsdl-file. The
-+ file name is a relative path within the module file.
-+
-+ This is not required when JAX-WS based runtime is used.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="service-qname"
-+ type="javaee:xsdQNameType"
-+ minOccurs="0" maxOccurs="1">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The service-qname element declares the specific WSDL service
-+ element that is being refered to. It is not specified if no
-+ wsdl-file is declared.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="port-component-ref"
-+ type="javaee:port-component-refType"
-+ minOccurs="0" maxOccurs="unbounded">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The port-component-ref element declares a client dependency
-+ on the container for resolving a Service Endpoint Interface
-+ to a WSDL port. It optionally associates the Service Endpoint
-+ Interface with a particular port-component. This is only used
-+ by the container for a Service.getPort(Class) method call.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:choice>
-+ <xsd:element name="handler"
-+ type="javaee:service-ref_handlerType"
-+ minOccurs="0" maxOccurs="unbounded">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ Declares the handler for a port-component. Handlers can
-+ access the init-param name/value pairs using the
-+ HandlerInfo interface. If port-name is not specified, the
-+ handler is assumed to be associated with all ports of the
-+ service.
-+
-+ To be used with JAX-RPC based runtime only.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="handler-chains"
-+ type="javaee:service-ref_handler-chainsType"
-+ minOccurs="0" maxOccurs="1">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ To be used with JAX-WS based runtime only.
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:choice>
-+
-+ <xsd:group ref="javaee:resourceGroup"/>
-+
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="service-ref_handler-chainType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The handler-chain element defines the handlerchain.
-+ Handlerchain can be defined such that the handlers in the
-+ handlerchain operate,all ports of a service, on a specific
-+ port or on a list of protocol-bindings. The choice of elements
-+ service-name-pattern, port-name-pattern and protocol-bindings
-+ are used to specify whether the handlers in handler-chain are
-+ for a service, port or protocol binding. If none of these
-+ choices are specified with the handler-chain element then the
-+ handlers specified in the handler-chain will be applied on
-+ everything.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+
-+ <xsd:choice minOccurs="0" maxOccurs="1">
-+ <xsd:element name="service-name-pattern"
-+ type="javaee:service-ref_qname-pattern" />
-+ <xsd:element name="port-name-pattern"
-+ type="javaee:service-ref_qname-pattern" />
-+ <xsd:element name="protocol-bindings"
-+ type="javaee:service-ref_protocol-bindingListType"/>
-+ </xsd:choice>
-+
-+ <xsd:element name="handler"
-+ type="javaee:service-ref_handlerType"
-+ minOccurs="1" maxOccurs="unbounded"/>
-+ </xsd:sequence>
-+
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="service-ref_handler-chainsType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The handler-chains element defines the handlerchains associated with this
-+ service or service endpoint.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="handler-chain"
-+ type="javaee:service-ref_handler-chainType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ </xsd:sequence>
-+
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="service-ref_handlerType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ Declares the handler for a port-component. Handlers can access the
-+ init-param name/value pairs using the HandlerInfo interface. If
-+ port-name is not specified, the handler is assumed to be associated
-+ with all ports of the service.
-+
-+ Used in: service-ref
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:sequence>
-+ <xsd:group ref="javaee:descriptionGroup"/>
-+ <xsd:element name="handler-name"
-+ type="javaee:string">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ Defines the name of the handler. The name must be unique
-+ within the module.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="handler-class"
-+ type="javaee:fully-qualified-classType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ Defines a fully qualified class name for the handler
-+ implementation.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="init-param"
-+ type="javaee:param-valueType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+
-+ <xsd:element name="soap-header"
-+ type="javaee:xsdQNameType"
-+ minOccurs="0" maxOccurs="unbounded">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ Defines the QName of a SOAP header that will be processed
-+ by the handler.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="soap-role"
-+ type="javaee:string"
-+ minOccurs="0" maxOccurs="unbounded">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The soap-role element contains a SOAP actor definition that
-+ the Handler will play as a role.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="port-name"
-+ type="javaee:string"
-+ minOccurs="0" maxOccurs="unbounded">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The port-name element defines the WSDL port-name that a
-+ handler should be associated with.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:simpleType name="service-ref_protocol-URIAliasType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ Defines the type that is used for specifying tokens that
-+ start with ## which are used to alias existing standard
-+ protocol bindings and support aliases for new standard
-+ binding URIs that are introduced in future specifications.
-+
-+ The following tokens alias the standard protocol binding
-+ URIs:
-+
-+ ##SOAP11_HTTP = "http://schemas.xmlsoap.org/wsdl/soap/http"
-+ ##SOAP11_HTTP_MTOM =
-+ "http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true"
-+ ##SOAP12_HTTP = "http://www.w3.org/2003/05/soap/bindings/HTTP/"
-+ ##SOAP12_HTTP_MTOM =
-+ "http://www.w3.org/2003/05/soap/bindings/HTTP/?mtom=true"
-+ ##XML_HTTP = "http://www.w3.org/2004/08/wsdl/http"
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:restriction base="xsd:token">
-+ <xsd:pattern value="##.+"/>
-+ </xsd:restriction>
-+ </xsd:simpleType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:simpleType name="service-ref_protocol-bindingListType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ Defines the type used for specifying a list of
-+ protocol-bindingType(s). For e.g.
-+
-+ ##SOAP11_HTTP ##SOAP12_HTTP ##XML_HTTP
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:list itemType="javaee:service-ref_protocol-bindingType"/>
-+ </xsd:simpleType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:simpleType name="service-ref_protocol-bindingType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ Defines the type used for specifying the URI for the
-+ protocol binding used by the port-component. For
-+ portability one could use one of the following tokens that
-+ alias the standard binding types:
-+
-+ ##SOAP11_HTTP
-+ ##SOAP11_HTTP_MTOM
-+ ##SOAP12_HTTP
-+ ##SOAP12_HTTP_MTOM
-+ ##XML_HTTP
-+
-+ Other specifications could define tokens that start with ##
-+ to alias new standard binding URIs that are introduced.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:union memberTypes="xsd:anyURI javaee:service-ref_protocol-URIAliasType"/>
-+ </xsd:simpleType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:simpleType name="service-ref_qname-pattern">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ This is used to specify the QName pattern in the
-+ attribute service-name-pattern and port-name-pattern in
-+ the handler-chain element
-+
-+ For example, the various forms acceptable here for
-+ service-name-pattern attribute in handler-chain element
-+ are :
-+
-+ Exact Name: service-name-pattern="ns1:EchoService"
-+
-+ In this case, handlers specified in this
-+ handler-chain element will apply to all ports with
-+ this exact service name. The namespace prefix must
-+ have been declared in a namespace declaration
-+ attribute in either the start-tag of the element
-+ where the prefix is used or in an an ancestor
-+ element (i.e. an element in whose content the
-+ prefixed markup occurs)
-+
-+ Pattern : service-name-pattern="ns1:EchoService*"
-+
-+ In this case, handlers specified in this
-+ handler-chain element will apply to all ports whose
-+ Service names are like EchoService1, EchoServiceFoo
-+ etc. The namespace prefix must have been declared in
-+ a namespace declaration attribute in either the
-+ start-tag of the element where the prefix is used or
-+ in an an ancestor element (i.e. an element in whose
-+ content the prefixed markup occurs)
-+
-+ Wild Card : service-name-pattern="*"
-+
-+ In this case, handlers specified in this handler-chain
-+ element will apply to ports of all service names.
-+
-+ The same can be applied to port-name attribute in
-+ handler-chain element.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:restriction base="xsd:token">
-+ <xsd:pattern value="\*|([\i-[:]][\c-[:]]*:)?[\i-[:]][\c-[:]]*\*?"/>
-+ </xsd:restriction>
-+
-+ </xsd:simpleType>
-+
-+</xsd:schema>
-+
-Index: jenkins-winstone/src/conf/javax/servlet/resources/jsp_2_0.xsd
-===================================================================
---- /dev/null 1970-01-01 00:00:00.000000000 +0000
-+++ jenkins-winstone/src/conf/javax/servlet/resources/jsp_2_0.xsd 2012-04-26 11:45:47.802315463 +0100
-@@ -0,0 +1,316 @@
-+<?xml version="1.0" encoding="UTF-8"?>
-+<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
-+ targetNamespace="http://java.sun.com/xml/ns/j2ee"
-+ xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
-+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
-+ elementFormDefault="qualified"
-+ attributeFormDefault="unqualified"
-+ version="2.0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ @(#)jsp_2_0.xsds 1.17 03/18/03
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
-+
-+ Copyright 2003-2007 Sun Microsystems, Inc. All rights reserved.
-+
-+ The contents of this file are subject to the terms of either the
-+ GNU General Public License Version 2 only ("GPL") or the Common
-+ Development and Distribution License("CDDL") (collectively, the
-+ "License"). You may not use this file except in compliance with
-+ the License. You can obtain a copy of the License at
-+ https://glassfish.dev.java.net/public/CDDL+GPL.html or
-+ glassfish/bootstrap/legal/LICENSE.txt. See the License for the
-+ specific language governing permissions and limitations under the
-+ License.
-+
-+ When distributing the software, include this License Header
-+ Notice in each file and include the License file at
-+ glassfish/bootstrap/legal/LICENSE.txt. Sun designates this
-+ particular file as subject to the "Classpath" exception as
-+ provided by Sun in the GPL Version 2 section of the License file
-+ that accompanied this code. If applicable, add the following
-+ below the License Header, with the fields enclosed by brackets []
-+ replaced by your own identifying information:
-+ "Portions Copyrighted [year] [name of copyright owner]"
-+
-+ Contributor(s):
-+
-+ If you wish your version of this file to be governed by only the
-+ CDDL or only the GPL Version 2, indicate your decision by adding
-+ "[Contributor] elects to include this software in this
-+ distribution under the [CDDL or GPL Version 2] license." If you
-+ don't indicate a single choice of license, a recipient has the
-+ option to distribute your version of this file under either the
-+ CDDL, the GPL Version 2 or to extend the choice of license to its
-+ licensees as provided above. However, if you add GPL Version 2
-+ code and therefore, elected the GPL Version 2 license, then the
-+ option applies only if the new code is made subject to such
-+ option by the copyright holder.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This is the XML Schema for the JSP 2.0 deployment descriptor
-+ types. The JSP 2.0 schema contains all the special
-+ structures and datatypes that are necessary to use JSP files
-+ from a web application.
-+
-+ The contents of this schema is used by the web-app_2_4.xsd
-+ file to define JSP specific content.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The following conventions apply to all J2EE
-+ deployment descriptor elements unless indicated otherwise.
-+
-+ - In elements that specify a pathname to a file within the
-+ same JAR file, relative filenames (i.e., those not
-+ starting with "/") are considered relative to the root of
-+ the JAR file's namespace. Absolute filenames (i.e., those
-+ starting with "/") also specify names in the root of the
-+ JAR file's namespace. In general, relative names are
-+ preferred. The exception is .war files where absolute
-+ names are preferred for consistency with the Servlet API.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:include schemaLocation="j2ee_1_4.xsd"/>
-+
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="jsp-configType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The jsp-configType is used to provide global configuration
-+ information for the JSP files in a web application. It has
-+ two subelements, taglib and jsp-property-group.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="taglib"
-+ type="j2ee:taglibType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="jsp-property-group"
-+ type="j2ee:jsp-property-groupType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="jsp-fileType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The jsp-file element contains the full path to a JSP file
-+ within the web application beginning with a `/'.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:pathType"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="jsp-property-groupType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The jsp-property-groupType is used to group a number of
-+ files so they can be given global property information.
-+ All files so described are deemed to be JSP files. The
-+ following additional properties can be described:
-+
-+ - Control whether EL is ignored
-+ - Control whether scripting elements are invalid
-+ - Indicate pageEncoding information.
-+ - Indicate that a resource is a JSP document (XML)
-+ - Prelude and Coda automatic includes.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:group ref="j2ee:descriptionGroup"/>
-+ <xsd:element name="url-pattern"
-+ type="j2ee:url-patternType"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="el-ignored"
-+ type="j2ee:true-falseType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ Can be used to easily set the isELIgnored
-+ property of a group of JSP pages. By default, the
-+ EL evaluation is enabled for Web Applications using
-+ a Servlet 2.4 or greater web.xml, and disabled
-+ otherwise.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="page-encoding"
-+ type="j2ee:string"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The valid values of page-encoding are those of the
-+ pageEncoding page directive. It is a
-+ translation-time error to name different encodings
-+ in the pageEncoding attribute of the page directive
-+ of a JSP page and in a JSP configuration element
-+ matching the page. It is also a translation-time
-+ error to name different encodings in the prolog
-+ or text declaration of a document in XML syntax and
-+ in a JSP configuration element matching the document.
-+ It is legal to name the same encoding through
-+ mulitple mechanisms.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="scripting-invalid"
-+ type="j2ee:true-falseType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ Can be used to easily disable scripting in a
-+ group of JSP pages. By default, scripting is
-+ enabled.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="is-xml"
-+ type="j2ee:true-falseType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ If true, denotes that the group of resources
-+ that match the URL pattern are JSP documents,
-+ and thus must be interpreted as XML documents.
-+ If false, the resources are assumed to not
-+ be JSP documents, unless there is another
-+ property group that indicates otherwise.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="include-prelude"
-+ type="j2ee:pathType"
-+ minOccurs="0"
-+ maxOccurs="unbounded">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The include-prelude element is a context-relative
-+ path that must correspond to an element in the
-+ Web Application. When the element is present,
-+ the given path will be automatically included (as
-+ in an include directive) at the beginning of each
-+ JSP page in this jsp-property-group.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="include-coda"
-+ type="j2ee:pathType"
-+ minOccurs="0"
-+ maxOccurs="unbounded">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The include-coda element is a context-relative
-+ path that must correspond to an element in the
-+ Web Application. When the element is present,
-+ the given path will be automatically included (as
-+ in an include directive) at the end of each
-+ JSP page in this jsp-property-group.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="taglibType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The taglibType defines the syntax for declaring in
-+ the deployment descriptor that a tag library is
-+ available to the application. This can be done
-+ to override implicit map entries from TLD files and
-+ from the container.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="taglib-uri"
-+ type="j2ee:string">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ A taglib-uri element describes a URI identifying a
-+ tag library used in the web application. The body
-+ of the taglib-uri element may be either an
-+ absolute URI specification, or a relative URI.
-+ There should be no entries in web.xml with the
-+ same taglib-uri value.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="taglib-location"
-+ type="j2ee:pathType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ the taglib-location element contains the location
-+ (as a resource relative to the root of the web
-+ application) where to find the Tag Library
-+ Description file for the tag library.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+</xsd:schema>
-+
-Index: jenkins-winstone/src/conf/javax/servlet/resources/jsp_2_1.xsd
-===================================================================
---- /dev/null 1970-01-01 00:00:00.000000000 +0000
-+++ jenkins-winstone/src/conf/javax/servlet/resources/jsp_2_1.xsd 2012-04-26 11:45:47.806315312 +0100
-@@ -0,0 +1,349 @@
-+<?xml version="1.0" encoding="UTF-8"?>
-+<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
-+ targetNamespace="http://java.sun.com/xml/ns/javaee"
-+ xmlns:javaee="http://java.sun.com/xml/ns/javaee"
-+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
-+ elementFormDefault="qualified"
-+ attributeFormDefault="unqualified"
-+ version="2.1">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ @(#)jsp_2_1.xsds 1.5 08/11/05
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
-+
-+ Copyright 2003-2007 Sun Microsystems, Inc. All rights reserved.
-+
-+ The contents of this file are subject to the terms of either the
-+ GNU General Public License Version 2 only ("GPL") or the Common
-+ Development and Distribution License("CDDL") (collectively, the
-+ "License"). You may not use this file except in compliance with
-+ the License. You can obtain a copy of the License at
-+ https://glassfish.dev.java.net/public/CDDL+GPL.html or
-+ glassfish/bootstrap/legal/LICENSE.txt. See the License for the
-+ specific language governing permissions and limitations under the
-+ License.
-+
-+ When distributing the software, include this License Header
-+ Notice in each file and include the License file at
-+ glassfish/bootstrap/legal/LICENSE.txt. Sun designates this
-+ particular file as subject to the "Classpath" exception as
-+ provided by Sun in the GPL Version 2 section of the License file
-+ that accompanied this code. If applicable, add the following
-+ below the License Header, with the fields enclosed by brackets []
-+ replaced by your own identifying information:
-+ "Portions Copyrighted [year] [name of copyright owner]"
-+
-+ Contributor(s):
-+
-+ If you wish your version of this file to be governed by only the
-+ CDDL or only the GPL Version 2, indicate your decision by adding
-+ "[Contributor] elects to include this software in this
-+ distribution under the [CDDL or GPL Version 2] license." If you
-+ don't indicate a single choice of license, a recipient has the
-+ option to distribute your version of this file under either the
-+ CDDL, the GPL Version 2 or to extend the choice of license to its
-+ licensees as provided above. However, if you add GPL Version 2
-+ code and therefore, elected the GPL Version 2 license, then the
-+ option applies only if the new code is made subject to such
-+ option by the copyright holder.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This is the XML Schema for the JSP 2.1 deployment descriptor
-+ types. The JSP 2.1 schema contains all the special
-+ structures and datatypes that are necessary to use JSP files
-+ from a web application.
-+
-+ The contents of this schema is used by the web-app_2_5.xsd
-+ file to define JSP specific content.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The following conventions apply to all Java EE
-+ deployment descriptor elements unless indicated otherwise.
-+
-+ - In elements that specify a pathname to a file within the
-+ same JAR file, relative filenames (i.e., those not
-+ starting with "/") are considered relative to the root of
-+ the JAR file's namespace. Absolute filenames (i.e., those
-+ starting with "/") also specify names in the root of the
-+ JAR file's namespace. In general, relative names are
-+ preferred. The exception is .war files where absolute
-+ names are preferred for consistency with the Servlet API.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:include schemaLocation="javaee_5.xsd"/>
-+
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="jsp-configType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The jsp-configType is used to provide global configuration
-+ information for the JSP files in a web application. It has
-+ two subelements, taglib and jsp-property-group.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="taglib"
-+ type="javaee:taglibType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="jsp-property-group"
-+ type="javaee:jsp-property-groupType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="jsp-fileType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The jsp-file element contains the full path to a JSP file
-+ within the web application beginning with a `/'.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:pathType"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="jsp-property-groupType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The jsp-property-groupType is used to group a number of
-+ files so they can be given global property information.
-+ All files so described are deemed to be JSP files. The
-+ following additional properties can be described:
-+
-+ - Control whether EL is ignored.
-+ - Control whether scripting elements are invalid.
-+ - Indicate pageEncoding information.
-+ - Indicate that a resource is a JSP document (XML).
-+ - Prelude and Coda automatic includes.
-+ - Control whether the character sequence #{ is allowed
-+ when used as a String literal.
-+ - Control whether template text containing only
-+ whitespaces must be removed from the response output.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:group ref="javaee:descriptionGroup"/>
-+ <xsd:element name="url-pattern"
-+ type="javaee:url-patternType"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="el-ignored"
-+ type="javaee:true-falseType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ Can be used to easily set the isELIgnored
-+ property of a group of JSP pages. By default, the
-+ EL evaluation is enabled for Web Applications using
-+ a Servlet 2.4 or greater web.xml, and disabled
-+ otherwise.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="page-encoding"
-+ type="javaee:string"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The valid values of page-encoding are those of the
-+ pageEncoding page directive. It is a
-+ translation-time error to name different encodings
-+ in the pageEncoding attribute of the page directive
-+ of a JSP page and in a JSP configuration element
-+ matching the page. It is also a translation-time
-+ error to name different encodings in the prolog
-+ or text declaration of a document in XML syntax and
-+ in a JSP configuration element matching the document.
-+ It is legal to name the same encoding through
-+ mulitple mechanisms.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="scripting-invalid"
-+ type="javaee:true-falseType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ Can be used to easily disable scripting in a
-+ group of JSP pages. By default, scripting is
-+ enabled.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="is-xml"
-+ type="javaee:true-falseType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ If true, denotes that the group of resources
-+ that match the URL pattern are JSP documents,
-+ and thus must be interpreted as XML documents.
-+ If false, the resources are assumed to not
-+ be JSP documents, unless there is another
-+ property group that indicates otherwise.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="include-prelude"
-+ type="javaee:pathType"
-+ minOccurs="0"
-+ maxOccurs="unbounded">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The include-prelude element is a context-relative
-+ path that must correspond to an element in the
-+ Web Application. When the element is present,
-+ the given path will be automatically included (as
-+ in an include directive) at the beginning of each
-+ JSP page in this jsp-property-group.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="include-coda"
-+ type="javaee:pathType"
-+ minOccurs="0"
-+ maxOccurs="unbounded">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The include-coda element is a context-relative
-+ path that must correspond to an element in the
-+ Web Application. When the element is present,
-+ the given path will be automatically included (as
-+ in an include directive) at the end of each
-+ JSP page in this jsp-property-group.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="deferred-syntax-allowed-as-literal"
-+ type="javaee:true-falseType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The character sequence #{ is reserved for EL expressions.
-+ Consequently, a translation error occurs if the #{
-+ character sequence is used as a String literal, unless
-+ this element is enabled (true). Disabled (false) by
-+ default.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="trim-directive-whitespaces"
-+ type="javaee:true-falseType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ Indicates that template text containing only whitespaces
-+ must be removed from the response output. It has no
-+ effect on JSP documents (XML syntax). Disabled (false)
-+ by default.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="taglibType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The taglibType defines the syntax for declaring in
-+ the deployment descriptor that a tag library is
-+ available to the application. This can be done
-+ to override implicit map entries from TLD files and
-+ from the container.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="taglib-uri"
-+ type="javaee:string">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ A taglib-uri element describes a URI identifying a
-+ tag library used in the web application. The body
-+ of the taglib-uri element may be either an
-+ absolute URI specification, or a relative URI.
-+ There should be no entries in web.xml with the
-+ same taglib-uri value.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="taglib-location"
-+ type="javaee:pathType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ the taglib-location element contains the location
-+ (as a resource relative to the root of the web
-+ application) where to find the Tag Library
-+ Description file for the tag library.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+</xsd:schema>
-+
-Index: jenkins-winstone/src/conf/javax/servlet/resources/web-app_2_2.dtd
-===================================================================
---- /dev/null 1970-01-01 00:00:00.000000000 +0000
-+++ jenkins-winstone/src/conf/javax/servlet/resources/web-app_2_2.dtd 2012-04-26 11:45:47.806315312 +0100
-@@ -0,0 +1,602 @@
-+<!--
-+
-+DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
-+
-+Copyright 1999-2007 Sun Microsystems, Inc. All rights reserved.
-+
-+The contents of this file are subject to the terms of either the GNU
-+General Public License Version 2 only ("GPL") or the Common Development
-+and Distribution License("CDDL") (collectively, the "License"). You
-+may not use this file except in compliance with the License. You can obtain
-+a copy of the License at https://glassfish.dev.java.net/public/CDDL+GPL.html
-+or glassfish/bootstrap/legal/LICENSE.txt. See the License for the specific
-+language governing permissions and limitations under the License.
-+
-+When distributing the software, include this License Header Notice in each
-+file and include the License file at glassfish/bootstrap/legal/LICENSE.txt.
-+Sun designates this particular file as subject to the "Classpath" exception
-+as provided by Sun in the GPL Version 2 section of the License file that
-+accompanied this code. If applicable, add the following below the License
-+Header, with the fields enclosed by brackets [] replaced by your own
-+identifying information: "Portions Copyrighted [year]
-+[name of copyright owner]"
-+
-+Contributor(s):
-+
-+If you wish your version of this file to be governed by only the CDDL or
-+only the GPL Version 2, indicate your decision by adding "[Contributor]
-+elects to include this software in this distribution under the [CDDL or GPL
-+Version 2] license." If you don't indicate a single choice of license, a
-+recipient has the option to distribute your version of this file under
-+either the CDDL, the GPL Version 2 or to extend the choice of license to
-+its licensees as provided above. However, if you add GPL Version 2 code
-+and therefore, elected the GPL Version 2 license, then the option applies
-+only if the new code is made subject to such option by the copyright
-+holder.
-+
-+-->
-+
-+<!--
-+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*, servlet*, servlet-mapping*, session-config?,
-+mime-mapping*, welcome-file-list?, error-page*, taglib*,
-+resource-ref*, security-constraint*, login-config?, security-role*,
-+env-entry*, ejb-ref*)>
-+
-+<!--
-+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 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 10 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-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)>
-+
-+<!--
-+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. Must be CONTAINER or SERVLET
-+-->
-+
-+<!ELEMENT res-auth (#PCDATA)>
-+
-+<!--
-+The security-constraint element is used to associate security
-+constraints with one or more web resource collections
-+-->
-+
-+<!ELEMENT security-constraint (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 appear in a security-role-ref element.
-+-->
-+
-+<!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 role-name element contains the name of a role. This element
-+must contain a non-empty string.
-+-->
-+
-+<!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?)>
-+
-+<!--
-+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 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 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 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-ref id ID #IMPLIED>
-+<!ATTLIST res-ref-name id ID #IMPLIED>
-+<!ATTLIST res-type id ID #IMPLIED>
-+<!ATTLIST res-auth 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>
-Index: jenkins-winstone/src/conf/javax/servlet/resources/web-app_2_3.dtd
-===================================================================
---- /dev/null 1970-01-01 00:00:00.000000000 +0000
-+++ jenkins-winstone/src/conf/javax/servlet/resources/web-app_2_3.dtd 2012-04-26 11:45:47.806315312 +0100
-@@ -0,0 +1,1022 @@
-+<!--
-+DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
-+
-+Copyright 2000-2007 Sun Microsystems, Inc. All rights reserved.
-+
-+The contents of this file are subject to the terms of either the GNU
-+General Public License Version 2 only ("GPL") or the Common Development
-+and Distribution License("CDDL") (collectively, the "License"). You
-+may not use this file except in compliance with the License. You can obtain
-+a copy of the License at https://glassfish.dev.java.net/public/CDDL+GPL.html
-+or glassfish/bootstrap/legal/LICENSE.txt. See the License for the specific
-+language governing permissions and limitations under the License.
-+
-+When distributing the software, include this License Header Notice in each
-+file and include the License file at glassfish/bootstrap/legal/LICENSE.txt.
-+Sun designates this particular file as subject to the "Classpath" exception
-+as provided by Sun in the GPL Version 2 section of the License file that
-+accompanied this code. If applicable, add the following below the License
-+Header, with the fields enclosed by brackets [] replaced by your own
-+identifying information: "Portions Copyrighted [year]
-+[name of copyright owner]"
-+
-+Contributor(s):
-+
-+If you wish your version of this file to be governed by only the CDDL or
-+only the GPL Version 2, indicate your decision by adding "[Contributor]
-+elects to include this software in this distribution under the [CDDL or GPL
-+Version 2] license." If you don't indicate a single choice of license, a
-+recipient has the option to distribute your version of this file under
-+either the CDDL, the GPL Version 2 or to extend the choice of license to
-+its licensees as provided above. However, if you add GPL Version 2 code
-+and therefore, elected the GPL Version 2 license, then the option applies
-+only if the new code is made subject to such option by the copyright
-+holder.
-+-->
-+
-+<!--
-+This is the XML DTD for the Servlet 2.3 deployment descriptor.
-+All Servlet 2.3 deployment descriptors must include a DOCTYPE
-+of the following form:
-+
-+ <!DOCTYPE web-app PUBLIC
-+ "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
-+ "http://java.sun.com/dtd/web-app_2_3.dtd">
-+
-+-->
-+
-+<!--
-+The following conventions apply to all J2EE deployment descriptor
-+elements unless indicated otherwise.
-+
-+- In elements that contain PCDATA, leading and trailing whitespace
-+ in the data may be ignored.
-+
-+- In elements whose value is an "enumerated type", the value is
-+ case sensitive.
-+
-+- In elements that specify a pathname to a file within the same
-+ JAR file, relative filenames (i.e., those not starting with "/")
-+ are considered relative to the root of the JAR file's namespace.
-+ Absolute filenames (i.e., those starting with "/") also specify
-+ names in the root of the JAR file's namespace. In general, relative
-+ names are preferred. The exception is .war files where absolute
-+ names are preferred for consistency with the servlet API.
-+-->
-+
-+
-+<!--
-+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*, ejb-local-ref*)>
-+
-+<!--
-+The auth-constraint element indicates the user roles that should
-+be permitted access to this resource collection. The role-name
-+used here must either correspond to the role-name of one of the
-+security-role elements defined for this web application, 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.
-+If no roles are defined, no user is allowed access to the portion of
-+the web application described by the containing security-constraint.
-+The container matches role names case sensitively when determining
-+access.
-+
-+
-+Used in: security-constraint
-+-->
-+<!ELEMENT auth-constraint (description?, role-name*)>
-+
-+<!--
-+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".
-+
-+Used in: login-config
-+-->
-+<!ELEMENT auth-method (#PCDATA)>
-+
-+<!--
-+The context-param element contains the declaration of a web
-+application's servlet context initialization parameters.
-+
-+Used in: web-app
-+-->
-+<!ELEMENT context-param (param-name, param-value, description?)>
-+
-+<!--
-+The description element is used to provide text describing the parent
-+element. The description element should include any information that
-+the web application war file producer wants to provide to the consumer of
-+the web application war file (i.e., to the Deployer). Typically, the tools
-+used by the web application war file consumer will display the description
-+when processing the parent element that contains the description.
-+
-+Used in: auth-constraint, context-param, ejb-local-ref, ejb-ref,
-+env-entry, filter, init-param, resource-env-ref, resource-ref, run-as,
-+security-role, security-role-ref, servlet, user-data-constraint,
-+web-app, web-resource-collection
-+-->
-+<!ELEMENT description (#PCDATA)>
-+
-+<!--
-+The display-name element contains a short name that is intended to be
-+displayed by tools. The display name need not be unique.
-+
-+Used in: filter, security-constraint, servlet, web-app
-+
-+Example:
-+
-+<display-name>Employee Self Service</display-name>
-+-->
-+<!ELEMENT display-name (#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
-+
-+Used in: web-app
-+-->
-+<!ELEMENT distributable EMPTY>
-+
-+<!--
-+The ejb-link element is used in the ejb-ref or ejb-local-ref
-+elements to specify that an EJB reference is linked to an
-+enterprise bean.
-+
-+The name in the ejb-link element is composed of a
-+path name specifying the ejb-jar containing the referenced enterprise
-+bean with the ejb-name of the target bean appended and separated from
-+the path name by "#". The path name is relative to the war file
-+containing the web application that is referencing the enterprise bean.
-+This allows multiple enterprise beans with the same ejb-name to be
-+uniquely identified.
-+
-+Used in: ejb-local-ref, ejb-ref
-+
-+Examples:
-+
-+ <ejb-link>EmployeeRecord</ejb-link>
-+
-+ <ejb-link>../products/product.jar#ProductEJB</ejb-link>
-+
-+-->
-+<!ELEMENT ejb-link (#PCDATA)>
-+
-+<!--
-+The ejb-local-ref element is used for the declaration of a reference to
-+an enterprise bean's local home. The declaration consists of:
-+
-+ - an optional description
-+ - the EJB reference name used in the code of the web application
-+ that's referencing the enterprise bean
-+ - the expected type of the referenced enterprise bean
-+ - the expected local home and local interfaces of the referenced
-+ enterprise bean
-+ - optional ejb-link information, used to specify the referenced
-+ enterprise bean
-+
-+Used in: web-app
-+-->
-+<!ELEMENT ejb-local-ref (description?, ejb-ref-name, ejb-ref-type,
-+ local-home, local, ejb-link?)>
-+
-+<!--
-+The ejb-ref element is used for the declaration of a reference to
-+an enterprise bean's home. The declaration consists of:
-+
-+ - an optional description
-+ - the EJB reference name used in the code of
-+ the web application that's referencing the enterprise bean
-+ - the expected type of the referenced enterprise bean
-+ - the expected home and remote interfaces of the referenced
-+ enterprise bean
-+ - optional ejb-link information, used to specify the referenced
-+ enterprise bean
-+
-+Used in: web-app
-+-->
-+<!ELEMENT ejb-ref (description?, ejb-ref-name, ejb-ref-type,
-+ home, remote, ejb-link?)>
-+
-+<!--
-+The ejb-ref-name element contains the name of an EJB reference. The
-+EJB reference is an entry in the web application's environment and is
-+relative to the java:comp/env context. The name must be unique
-+within the web application.
-+
-+It is recommended that name is prefixed with "ejb/".
-+
-+Used in: ejb-local-ref, ejb-ref
-+
-+Example:
-+
-+<ejb-ref-name>ejb/Payroll</ejb-ref-name>
-+-->
-+<!ELEMENT ejb-ref-name (#PCDATA)>
-+
-+<!--
-+The ejb-ref-type element contains the expected type of the
-+referenced enterprise bean.
-+
-+The ejb-ref-type element must be one of the following:
-+
-+ <ejb-ref-type>Entity</ejb-ref-type>
-+ <ejb-ref-type>Session</ejb-ref-type>
-+
-+Used in: ejb-local-ref, ejb-ref
-+-->
-+<!ELEMENT ejb-ref-type (#PCDATA)>
-+
-+<!--
-+The env-entry element contains the declaration of a web application's
-+environment entry. The declaration consists of an optional
-+description, the name of the environment entry, and an optional
-+value. If a value is not specified, one must be supplied
-+during deployment.
-+-->
-+<!ELEMENT env-entry (description?, env-entry-name, env-entry-value?,
-+env-entry-type)>
-+
-+<!--
-+The env-entry-name element contains the name of a web applications's
-+environment entry. The name is a JNDI name relative to the
-+java:comp/env context. The name must be unique within a web application.
-+
-+Example:
-+
-+<env-entry-name>minAmount</env-entry-name>
-+
-+Used in: env-entry
-+-->
-+<!ELEMENT env-entry-name (#PCDATA)>
-+
-+<!--
-+The env-entry-type element contains the fully-qualified Java type of
-+the environment entry value that is expected by the web application's
-+code.
-+
-+The following are the legal values of env-entry-type:
-+
-+ java.lang.Boolean
-+ java.lang.Byte
-+ java.lang.Character
-+ java.lang.String
-+ java.lang.Short
-+ java.lang.Integer
-+ java.lang.Long
-+ java.lang.Float
-+ java.lang.Double
-+
-+Used in: env-entry
-+-->
-+<!ELEMENT env-entry-type (#PCDATA)>
-+
-+<!--
-+The env-entry-value element contains the value of a web application's
-+environment entry. The value must be a String that is valid for the
-+constructor of the specified type that takes a single String
-+parameter, or for java.lang.Character, a single character.
-+
-+Example:
-+
-+<env-entry-value>100.00</env-entry-value>
-+
-+Used in: env-entry
-+-->
-+<!ELEMENT env-entry-value (#PCDATA)>
-+
-+<!--
-+The error-code contains an HTTP error code, ex: 404
-+
-+Used in: error-page
-+-->
-+<!ELEMENT error-code (#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
-+
-+Used in: web-app
-+-->
-+<!ELEMENT error-page ((error-code | exception-type), location)>
-+
-+<!--
-+The exception type contains a fully qualified class name of a
-+Java exception type.
-+
-+Used in: error-page
-+-->
-+<!ELEMENT exception-type (#PCDATA)>
-+
-+<!--
-+The extension element contains a string describing an
-+extension. example: "txt"
-+
-+Used in: mime-mapping
-+-->
-+<!ELEMENT extension (#PCDATA)>
-+
-+<!--
-+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.
-+
-+Used in: web-app
-+-->
-+<!ELEMENT filter (icon?, filter-name, display-name?, description?,
-+filter-class, init-param*)>
-+
-+<!--
-+The fully qualified classname of the filter.
-+
-+Used in: 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.
-+
-+Used in: web-app
-+-->
-+<!ELEMENT filter-mapping (filter-name, (url-pattern | servlet-name))>
-+
-+<!--
-+The logical name of the filter. This name is used to map the filter.
-+Each filter name is unique within the web application.
-+
-+Used in: filter, filter-mapping
-+-->
-+<!ELEMENT filter-name (#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. The path begins with a leading / and is interpreted
-+relative to the root of the WAR.
-+
-+Used in: form-login-config
-+-->
-+<!ELEMENT form-error-page (#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.
-+
-+Used in: login-config
-+-->
-+<!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. The path
-+begins with a leading / and is interpreted relative to the root of the WAR.
-+
-+Used in: form-login-config
-+-->
-+<!ELEMENT form-login-page (#PCDATA)>
-+
-+<!--
-+The home element contains the fully-qualified name of the enterprise
-+bean's home interface.
-+
-+Used in: ejb-ref
-+
-+Example:
-+
-+<home>com.aardvark.payroll.PayrollHome</home>
-+-->
-+<!ELEMENT home (#PCDATA)>
-+
-+<!--
-+The http-method contains an HTTP method (GET | POST |...).
-+
-+Used in: web-resource-collection
-+-->
-+<!ELEMENT http-method (#PCDATA)>
-+
-+<!--
-+The icon element contains small-icon and large-icon elements that
-+specify the file names for small and a large GIF or JPEG icon images
-+used to represent the parent element in a GUI tool.
-+
-+Used in: filter, servlet, web-app
-+-->
-+<!ELEMENT icon (small-icon?, large-icon?)>
-+
-+<!--
-+The init-param element contains a name/value pair as an
-+initialization param of the servlet
-+
-+Used in: filter, servlet
-+-->
-+<!ELEMENT init-param (param-name, param-value, description?)>
-+
-+<!--
-+The jsp-file element contains the full path to a JSP file within
-+the web application beginning with a `/'.
-+
-+Used in: servlet
-+-->
-+<!ELEMENT jsp-file (#PCDATA)>
-+
-+<!--
-+The large-icon element contains the name of a file
-+containing a large (32 x 32) icon image. The file
-+name is a relative path within the web application's
-+war file.
-+
-+The image may be either in the JPEG or GIF format.
-+The icon can be used by tools.
-+
-+Used in: icon
-+
-+Example:
-+
-+<large-icon>employee-service-icon32x32.jpg</large-icon>
-+-->
-+<!ELEMENT large-icon (#PCDATA)>
-+
-+<!--
-+The listener element indicates the deployment properties for a web
-+application listener bean.
-+
-+Used in: web-app
-+-->
-+<!ELEMENT listener (listener-class)>
-+
-+<!--
-+The listener-class element declares a class in the application must be
-+registered as a web application listener bean. The value is the fully qualified classname of the listener class.
-+
-+
-+Used in: listener
-+-->
-+<!ELEMENT listener-class (#PCDATA)>
-+
-+<!--
-+The load-on-startup element indicates that this servlet should be
-+loaded (instantiated and have its init() called) on the startup
-+of the web application. The optional contents of
-+these element must be an integer indicating the order in which
-+the servlet should be loaded. If the value is a negative integer,
-+or the element is not present, the container is free to load the
-+servlet whenever it chooses. If the value is a positive integer
-+or 0, the container must load and initialize the servlet as the
-+application is deployed. The container must guarantee that
-+servlets marked with lower integers are loaded before servlets
-+marked with higher integers. The container may choose the order
-+of loading of servlets with the same load-on-start-up value.
-+
-+Used in: servlet
-+-->
-+<!ELEMENT load-on-startup (#PCDATA)>
-+
-+<!--
-+
-+The local element contains the fully-qualified name of the
-+enterprise bean's local interface.
-+
-+Used in: ejb-local-ref
-+
-+-->
-+<!ELEMENT local (#PCDATA)>
-+
-+<!--
-+
-+The local-home element contains the fully-qualified name of the
-+enterprise bean's local home interface.
-+
-+Used in: ejb-local-ref
-+-->
-+<!ELEMENT local-home (#PCDATA)>
-+
-+<!--
-+The location element contains the location of the resource in the web
-+application relative to the root of the web application. The value of
-+the location must have a leading `/'.
-+
-+Used in: error-page
-+-->
-+<!ELEMENT location (#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.
-+
-+Used in: web-app
-+-->
-+<!ELEMENT login-config (auth-method?, realm-name?, form-login-config?)>
-+
-+<!--
-+The mime-mapping element defines a mapping between an extension
-+and a mime type.
-+
-+Used in: web-app
-+-->
-+<!ELEMENT mime-mapping (extension, mime-type)>
-+
-+<!--
-+The mime-type element contains a defined mime type. example:
-+"text/plain"
-+
-+Used in: mime-mapping
-+-->
-+<!ELEMENT mime-type (#PCDATA)>
-+
-+<!--
-+The param-name element contains the name of a parameter. Each parameter
-+name must be unique in the web application.
-+
-+
-+Used in: context-param, init-param
-+-->
-+<!ELEMENT param-name (#PCDATA)>
-+
-+<!--
-+The param-value element contains the value of a parameter.
-+
-+Used in: context-param, init-param
-+-->
-+<!ELEMENT param-value (#PCDATA)>
-+
-+<!--
-+The realm name element specifies the realm name to use in HTTP
-+Basic authorization.
-+
-+Used in: login-config
-+-->
-+<!ELEMENT realm-name (#PCDATA)>
-+
-+<!--
-+The remote element contains the fully-qualified name of the enterprise
-+bean's remote interface.
-+
-+Used in: ejb-ref
-+
-+Example:
-+
-+<remote>com.wombat.empl.EmployeeService</remote>
-+-->
-+<!ELEMENT remote (#PCDATA)>
-+
-+<!--
-+The res-auth element specifies whether the web application code signs
-+on programmatically to the resource manager, or whether the Container
-+will sign on to the resource manager on behalf of the web application. In the
-+latter case, the Container uses information that is supplied by the
-+Deployer.
-+
-+The value of this element must be one of the two following:
-+
-+ <res-auth>Application</res-auth>
-+ <res-auth>Container</res-auth>
-+
-+Used in: resource-ref
-+-->
-+<!ELEMENT res-auth (#PCDATA)>
-+
-+<!--
-+The res-ref-name element specifies the name of a resource manager
-+connection factory reference. The name is a JNDI name relative to the
-+java:comp/env context. The name must be unique within a web application.
-+
-+Used in: resource-ref
-+-->
-+<!ELEMENT res-ref-name (#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.
-+
-+Used in: resource-ref
-+-->
-+<!ELEMENT res-sharing-scope (#PCDATA)>
-+
-+<!--
-+The res-type element specifies the type of the data source. The type
-+is specified by the fully qualified Java language class or interface
-+expected to be implemented by the data source.
-+
-+Used in: resource-ref
-+-->
-+<!ELEMENT res-type (#PCDATA)>
-+
-+<!--
-+The resource-env-ref element contains a declaration of a web application's
-+reference to an administered object associated with a resource
-+in the web application's environment. It consists of an optional
-+description, the resource environment reference name, and an
-+indication of the resource environment reference type expected by
-+the web application code.
-+
-+Used in: web-app
-+
-+Example:
-+
-+<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
-+the web application code. The name is a JNDI name relative to the
-+java:comp/env context and must be unique within a web application.
-+
-+Used in: resource-env-ref
-+-->
-+<!ELEMENT resource-env-ref-name (#PCDATA)>
-+
-+<!--
-+The resource-env-ref-type element specifies the type of a resource
-+environment reference. It is the fully qualified name of a Java
-+language class or interface.
-+
-+Used in: resource-env-ref
-+-->
-+<!ELEMENT resource-env-ref-type (#PCDATA)>
-+
-+<!--
-+The resource-ref element contains a declaration of a web application's
-+reference to an external resource. It consists of an optional
-+description, the resource manager connection factory reference name,
-+the indication of the resource manager connection factory type
-+expected by the web application code, the type of authentication
-+(Application or Container), and an optional specification of the
-+shareability of connections obtained from the resource (Shareable or
-+Unshareable).
-+
-+Used in: web-app
-+
-+Example:
-+
-+ <resource-ref>
-+ <res-ref-name>jdbc/EmployeeAppDB</res-ref-name>
-+ <res-type>javax.sql.DataSource</res-type>
-+ <res-auth>Container</res-auth>
-+ <res-sharing-scope>Shareable</res-sharing-scope>
-+ </resource-ref>
-+-->
-+<!ELEMENT resource-ref (description?, res-ref-name, res-type, res-auth,
-+ res-sharing-scope?)>
-+
-+<!--
-+The role-link element is a 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.
-+
-+Used in: security-role-ref
-+-->
-+<!ELEMENT role-link (#PCDATA)>
-+
-+<!--
-+The role-name element contains the name of a security role.
-+
-+The name must conform to the lexical rules for an NMTOKEN.
-+
-+Used in: auth-constraint, run-as, security-role, security-role-ref
-+-->
-+<!ELEMENT role-name (#PCDATA)>
-+
-+<!--
-+The run-as element specifies the run-as identity to be used for the
-+execution of the web application. It contains an optional description, and
-+the name of a security role.
-+
-+Used in: servlet
-+-->
-+<!ELEMENT run-as (description?, role-name)>
-+
-+<!--
-+The security-constraint element is used to associate security
-+constraints with one or more web resource collections
-+
-+Used in: web-app
-+-->
-+<!ELEMENT security-constraint (display-name?, web-resource-collection+,
-+auth-constraint?, user-data-constraint?)>
-+
-+<!--
-+The security-role element contains the definition of a security
-+role. The definition consists of an optional description of the
-+security role, and the security role name.
-+
-+Used in: web-app
-+
-+Example:
-+
-+ <security-role>
-+ <description>
-+ This role includes all employees who are authorized
-+ to access the employee service application.
-+ </description>
-+ <role-name>employee</role-name>
-+ </security-role>
-+-->
-+<!ELEMENT security-role (description?, role-name)>
-+
-+<!--
-+The security-role-ref element contains the declaration of a security
-+role reference in the web application's code. The declaration consists
-+of an optional description, the security role name used in the code,
-+and an optional link to a security role. If the security role is not
-+specified, the Deployer must choose an appropriate security role.
-+
-+The value of the role-name element must be the String used as the
-+parameter to the EJBContext.isCallerInRole(String roleName) method
-+or the HttpServletRequest.isUserInRole(String role) method.
-+
-+Used in: servlet
-+
-+-->
-+<!ELEMENT security-role-ref (description?, role-name, role-link?)>
-+
-+<!--
-+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.
-+
-+Used in: web-app
-+-->
-+<!ELEMENT servlet (icon?, servlet-name, display-name?, description?,
-+(servlet-class|jsp-file), init-param*, load-on-startup?, run-as?, security-role-ref*)>
-+
-+<!--
-+The servlet-class element contains the fully qualified class name
-+of the servlet.
-+
-+Used in: servlet
-+-->
-+<!ELEMENT servlet-class (#PCDATA)>
-+
-+<!--
-+The servlet-mapping element defines a mapping between a servlet
-+and a url pattern
-+
-+Used in: web-app
-+-->
-+<!ELEMENT servlet-mapping (servlet-name, url-pattern)>
-+
-+<!--
-+The servlet-name element contains the canonical name of the
-+servlet. Each servlet name is unique within the web application.
-+
-+Used in: filter-mapping, servlet, servlet-mapping
-+-->
-+<!ELEMENT servlet-name (#PCDATA)>
-+
-+<!--
-+The session-config element defines the session parameters for
-+this web application.
-+
-+Used in: web-app
-+-->
-+<!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.
-+If the timeout is 0 or less, the container ensures the default
-+behaviour of sessions is never to time out.
-+
-+Used in: session-config
-+-->
-+<!ELEMENT session-timeout (#PCDATA)>
-+
-+<!--
-+The small-icon element contains the name of a file
-+containing a small (16 x 16) icon image. The file
-+name is a relative path within the web application's
-+war file.
-+
-+The image may be either in the JPEG or GIF format.
-+The icon can be used by tools.
-+
-+Used in: icon
-+
-+Example:
-+
-+<small-icon>employee-service-icon16x16.jpg</small-icon>
-+-->
-+<!ELEMENT small-icon (#PCDATA)>
-+
-+<!--
-+The taglib element is used to describe a JSP tag library.
-+
-+Used in: web-app
-+-->
-+<!ELEMENT taglib (taglib-uri, taglib-location)>
-+
-+<!--
-+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.
-+
-+Used in: taglib
-+-->
-+<!ELEMENT taglib-location (#PCDATA)>
-+
-+<!--
-+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.
-+
-+Used in: taglib
-+-->
-+<!ELEMENT taglib-uri (#PCDATA)>
-+
-+<!--
-+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.
-+
-+Used in: user-data-constraint
-+-->
-+<!ELEMENT transport-guarantee (#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.
-+
-+Used in: filter-mapping, servlet-mapping, web-resource-collection
-+-->
-+<!ELEMENT url-pattern (#PCDATA)>
-+
-+<!--
-+The user-data-constraint element is used to indicate how data
-+communicated between the client and container should be protected.
-+
-+Used in: security-constraint
-+-->
-+<!ELEMENT user-data-constraint (description?, transport-guarantee)>
-+
-+<!--
-+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.
-+
-+Used in: security-constraint
-+-->
-+<!ELEMENT web-resource-collection (web-resource-name, description?,
-+url-pattern*, http-method*)>
-+
-+<!--
-+The web-resource-name contains the name of this web resource
-+collection.
-+
-+Used in: web-resource-collection
-+-->
-+<!ELEMENT web-resource-name (#PCDATA)>
-+
-+<!--
-+The welcome-file element contains file name to use as a default
-+welcome file, such as index.html
-+
-+Used in: welcome-file-list
-+-->
-+<!ELEMENT welcome-file (#PCDATA)>
-+
-+<!--
-+The welcome-file-list contains an ordered list of welcome files
-+elements.
-+
-+Used in: web-app
-+-->
-+<!ELEMENT welcome-file-list (welcome-file+)>
-+
-+<!--
-+The ID mechanism is to allow 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 tool-specific files to the
-+information in the standard deployment descriptor.
-+
-+Tools are not allowed to add the non-standard information into the
-+standard deployment descriptor.
-+-->
-+
-+<!ATTLIST auth-constraint id ID #IMPLIED>
-+<!ATTLIST auth-method id ID #IMPLIED>
-+<!ATTLIST context-param id ID #IMPLIED>
-+<!ATTLIST description id ID #IMPLIED>
-+<!ATTLIST display-name id ID #IMPLIED>
-+<!ATTLIST distributable id ID #IMPLIED>
-+<!ATTLIST ejb-link id ID #IMPLIED>
-+<!ATTLIST ejb-local-ref id ID #IMPLIED>
-+<!ATTLIST ejb-ref id ID #IMPLIED>
-+<!ATTLIST ejb-ref-name id ID #IMPLIED>
-+<!ATTLIST ejb-ref-type id ID #IMPLIED>
-+<!ATTLIST env-entry id ID #IMPLIED>
-+<!ATTLIST env-entry-name id ID #IMPLIED>
-+<!ATTLIST env-entry-type id ID #IMPLIED>
-+<!ATTLIST env-entry-value id ID #IMPLIED>
-+<!ATTLIST error-code id ID #IMPLIED>
-+<!ATTLIST error-page id ID #IMPLIED>
-+<!ATTLIST exception-type id ID #IMPLIED>
-+<!ATTLIST extension id ID #IMPLIED>
-+<!ATTLIST filter id ID #IMPLIED>
-+<!ATTLIST filter-class id ID #IMPLIED>
-+<!ATTLIST filter-mapping id ID #IMPLIED>
-+<!ATTLIST filter-name id ID #IMPLIED>
-+<!ATTLIST form-error-page id ID #IMPLIED>
-+<!ATTLIST form-login-config id ID #IMPLIED>
-+<!ATTLIST form-login-page id ID #IMPLIED>
-+<!ATTLIST home id ID #IMPLIED>
-+<!ATTLIST http-method id ID #IMPLIED>
-+<!ATTLIST icon id ID #IMPLIED>
-+<!ATTLIST init-param id ID #IMPLIED>
-+<!ATTLIST jsp-file id ID #IMPLIED>
-+<!ATTLIST large-icon id ID #IMPLIED>
-+<!ATTLIST listener id ID #IMPLIED>
-+<!ATTLIST listener-class id ID #IMPLIED>
-+<!ATTLIST load-on-startup id ID #IMPLIED>
-+<!ATTLIST local id ID #IMPLIED>
-+<!ATTLIST local-home id ID #IMPLIED>
-+<!ATTLIST location id ID #IMPLIED>
-+<!ATTLIST login-config id ID #IMPLIED>
-+<!ATTLIST mime-mapping id ID #IMPLIED>
-+<!ATTLIST mime-type id ID #IMPLIED>
-+<!ATTLIST param-name id ID #IMPLIED>
-+<!ATTLIST param-value id ID #IMPLIED>
-+<!ATTLIST realm-name id ID #IMPLIED>
-+<!ATTLIST remote id ID #IMPLIED>
-+<!ATTLIST res-auth id ID #IMPLIED>
-+<!ATTLIST res-ref-name id ID #IMPLIED>
-+<!ATTLIST res-sharing-scope id ID #IMPLIED>
-+<!ATTLIST res-type 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 role-link id ID #IMPLIED>
-+<!ATTLIST role-name id ID #IMPLIED>
-+<!ATTLIST run-as id ID #IMPLIED>
-+<!ATTLIST security-constraint id ID #IMPLIED>
-+<!ATTLIST security-role id ID #IMPLIED>
-+<!ATTLIST security-role-ref id ID #IMPLIED>
-+<!ATTLIST servlet id ID #IMPLIED>
-+<!ATTLIST servlet-class id ID #IMPLIED>
-+<!ATTLIST servlet-mapping id ID #IMPLIED>
-+<!ATTLIST servlet-name id ID #IMPLIED>
-+<!ATTLIST session-config id ID #IMPLIED>
-+<!ATTLIST session-timeout id ID #IMPLIED>
-+<!ATTLIST small-icon id ID #IMPLIED>
-+<!ATTLIST taglib id ID #IMPLIED>
-+<!ATTLIST taglib-location id ID #IMPLIED>
-+<!ATTLIST taglib-uri id ID #IMPLIED>
-+<!ATTLIST transport-guarantee id ID #IMPLIED>
-+<!ATTLIST url-pattern id ID #IMPLIED>
-+<!ATTLIST user-data-constraint id ID #IMPLIED>
-+<!ATTLIST web-app id ID #IMPLIED>
-+<!ATTLIST web-resource-collection id ID #IMPLIED>
-+<!ATTLIST web-resource-name id ID #IMPLIED>
-+<!ATTLIST welcome-file id ID #IMPLIED>
-+<!ATTLIST welcome-file-list id ID #IMPLIED>
-Index: jenkins-winstone/src/conf/javax/servlet/resources/web-app_2_4.xsd
-===================================================================
---- /dev/null 1970-01-01 00:00:00.000000000 +0000
-+++ jenkins-winstone/src/conf/javax/servlet/resources/web-app_2_4.xsd 2012-04-26 11:45:47.806315312 +0100
-@@ -0,0 +1,1242 @@
-+<?xml version="1.0" encoding="UTF-8"?>
-+<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
-+ targetNamespace="http://java.sun.com/xml/ns/j2ee"
-+ xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
-+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
-+ elementFormDefault="qualified"
-+ attributeFormDefault="unqualified"
-+ version="2.4">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ @(#)web-app_2_4.xsds 1.61 04/04/16
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
-+
-+ Copyright 2003-2007 Sun Microsystems, Inc. All rights reserved.
-+
-+ The contents of this file are subject to the terms of either the
-+ GNU General Public License Version 2 only ("GPL") or the Common
-+ Development and Distribution License("CDDL") (collectively, the
-+ "License"). You may not use this file except in compliance with
-+ the License. You can obtain a copy of the License at
-+ https://glassfish.dev.java.net/public/CDDL+GPL.html or
-+ glassfish/bootstrap/legal/LICENSE.txt. See the License for the
-+ specific language governing permissions and limitations under the
-+ License.
-+
-+ When distributing the software, include this License Header
-+ Notice in each file and include the License file at
-+ glassfish/bootstrap/legal/LICENSE.txt. Sun designates this
-+ particular file as subject to the "Classpath" exception as
-+ provided by Sun in the GPL Version 2 section of the License file
-+ that accompanied this code. If applicable, add the following
-+ below the License Header, with the fields enclosed by brackets []
-+ replaced by your own identifying information:
-+ "Portions Copyrighted [year] [name of copyright owner]"
-+
-+ Contributor(s):
-+
-+ If you wish your version of this file to be governed by only the
-+ CDDL or only the GPL Version 2, indicate your decision by adding
-+ "[Contributor] elects to include this software in this
-+ distribution under the [CDDL or GPL Version 2] license." If you
-+ don't indicate a single choice of license, a recipient has the
-+ option to distribute your version of this file under either the
-+ CDDL, the GPL Version 2 or to extend the choice of license to its
-+ licensees as provided above. However, if you add GPL Version 2
-+ code and therefore, elected the GPL Version 2 license, then the
-+ option applies only if the new code is made subject to such
-+ option by the copyright holder.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ This is the XML Schema for the Servlet 2.4 deployment descriptor.
-+ The deployment descriptor must be named "WEB-INF/web.xml" in the
-+ web application's war file. All Servlet deployment descriptors
-+ must indicate the web application schema by using the J2EE
-+ namespace:
-+
-+ http://java.sun.com/xml/ns/j2ee
-+
-+ and by indicating the version of the schema by
-+ using the version element as shown below:
-+
-+ <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
-+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-+ xsi:schemaLocation="..."
-+ version="2.4">
-+ ...
-+ </web-app>
-+
-+ The instance documents may indicate the published version of
-+ the schema using the xsi:schemaLocation attribute for J2EE
-+ namespace with the following location:
-+
-+ http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The following conventions apply to all J2EE
-+ deployment descriptor elements unless indicated otherwise.
-+
-+ - In elements that specify a pathname to a file within the
-+ same JAR file, relative filenames (i.e., those not
-+ starting with "/") are considered relative to the root of
-+ the JAR file's namespace. Absolute filenames (i.e., those
-+ starting with "/") also specify names in the root of the
-+ JAR file's namespace. In general, relative names are
-+ preferred. The exception is .war files where absolute
-+ names are preferred for consistency with the Servlet API.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:include schemaLocation="j2ee_1_4.xsd"/>
-+ <xsd:include schemaLocation="jsp_2_0.xsd"/>
-+
-+
-+<!-- **************************************************** -->
-+
-+
-+ <xsd:element name="web-app" type="j2ee:web-appType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The web-app element is the root of the deployment
-+ descriptor for a web application. Note that the sub-elements
-+ of this element can be in the arbitrary order. Because of
-+ that, the multiplicity of the elements of distributable,
-+ session-config, welcome-file-list, jsp-config, login-config,
-+ and locale-encoding-mapping-list was changed from "?" to "*"
-+ in this schema. However, the deployment descriptor instance
-+ file must not contain multiple elements of session-config,
-+ jsp-config, and login-config. When there are multiple elements of
-+ welcome-file-list or locale-encoding-mapping-list, the container
-+ must concatinate the element contents. The multiple occurance
-+ of the element distributable is redundant and the container
-+ treats that case exactly in the same way when there is only
-+ one distributable.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:unique name="web-app-servlet-name-uniqueness">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The servlet element contains the name of a servlet.
-+ The name must be unique within the web application.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:selector xpath="j2ee:servlet"/>
-+ <xsd:field xpath="j2ee:servlet-name"/>
-+ </xsd:unique>
-+
-+ <xsd:unique name="web-app-filter-name-uniqueness">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The filter element contains the name of a filter.
-+ The name must be unique within the web application.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:selector xpath="j2ee:filter"/>
-+ <xsd:field xpath="j2ee:filter-name"/>
-+ </xsd:unique>
-+
-+ <xsd:unique name="web-app-ejb-local-ref-name-uniqueness">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The ejb-local-ref-name element contains the name of an EJB
-+ reference. The EJB reference is an entry in the web
-+ application's environment and is relative to the
-+ java:comp/env context. The name must be unique within
-+ the web application.
-+
-+ It is recommended that name is prefixed with "ejb/".
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:selector xpath="j2ee:ejb-local-ref"/>
-+ <xsd:field xpath="j2ee:ejb-ref-name"/>
-+ </xsd:unique>
-+
-+ <xsd:unique name="web-app-ejb-ref-name-uniqueness">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The ejb-ref-name element contains the name of an EJB
-+ reference. The EJB reference is an entry in the web
-+ application's environment and is relative to the
-+ java:comp/env context. The name must be unique within
-+ the web application.
-+
-+ It is recommended that name is prefixed with "ejb/".
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:selector xpath="j2ee:ejb-ref"/>
-+ <xsd:field xpath="j2ee:ejb-ref-name"/>
-+ </xsd:unique>
-+
-+ <xsd:unique name="web-app-resource-env-ref-uniqueness">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The resource-env-ref-name element specifies the name of
-+ a resource environment reference; its value is the
-+ environment entry name used in the web application code.
-+ The name is a JNDI name relative to the java:comp/env
-+ context and must be unique within a web application.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:selector xpath="j2ee:resource-env-ref"/>
-+ <xsd:field xpath="j2ee:resource-env-ref-name"/>
-+ </xsd:unique>
-+
-+ <xsd:unique name="web-app-message-destination-ref-uniqueness">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The message-destination-ref-name element specifies the name of
-+ a message destination reference; its value is the
-+ environment entry name used in the web application code.
-+ The name is a JNDI name relative to the java:comp/env
-+ context and must be unique within a web application.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:selector xpath="j2ee:message-destination-ref"/>
-+ <xsd:field xpath="j2ee:message-destination-ref-name"/>
-+ </xsd:unique>
-+
-+ <xsd:unique name="web-app-res-ref-name-uniqueness">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The res-ref-name element specifies the name of a
-+ resource manager connection factory reference. The name
-+ is a JNDI name relative to the java:comp/env context.
-+ The name must be unique within a web application.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:selector xpath="j2ee:resource-ref"/>
-+ <xsd:field xpath="j2ee:res-ref-name"/>
-+ </xsd:unique>
-+
-+ <xsd:unique name="web-app-env-entry-name-uniqueness">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The env-entry-name element contains the name of a web
-+ application's environment entry. The name is a JNDI
-+ name relative to the java:comp/env context. The name
-+ must be unique within a web application.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:selector xpath="j2ee:env-entry"/>
-+ <xsd:field xpath="j2ee:env-entry-name"/>
-+ </xsd:unique>
-+
-+ <xsd:key name="web-app-role-name-key">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ A role-name-key is specified to allow the references
-+ from the security-role-refs.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:selector xpath="j2ee:security-role"/>
-+ <xsd:field xpath="j2ee:role-name"/>
-+ </xsd:key>
-+
-+ <xsd:keyref name="web-app-role-name-references"
-+ refer="j2ee:web-app-role-name-key">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The keyref indicates the references from
-+ security-role-ref to a specified role-name.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:selector xpath="j2ee:servlet/j2ee:security-role-ref"/>
-+ <xsd:field xpath="j2ee:role-link"/>
-+ </xsd:keyref>
-+ </xsd:element>
-+
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="auth-constraintType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The auth-constraintType indicates the user roles that
-+ should be permitted access to this resource
-+ collection. The role-name used here must either correspond
-+ to the role-name of one of the security-role elements
-+ defined for this web application, 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. If no roles are defined, no user is allowed access
-+ to the portion of the web application described by the
-+ containing security-constraint. The container matches
-+ role names case sensitively when determining access.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="j2ee:descriptionType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ <xsd:element name="role-name"
-+ type="j2ee:role-nameType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="auth-methodType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The auth-methodType 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 are "BASIC",
-+ "DIGEST", "FORM", "CLIENT-CERT", or a vendor-specific
-+ authentication scheme.
-+
-+ Used in: login-config
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:string"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="dispatcherType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The dispatcher has four legal values: FORWARD, REQUEST, INCLUDE,
-+ and ERROR. A value of FORWARD means the Filter will be applied
-+ under RequestDispatcher.forward() calls. A value of REQUEST
-+ means the Filter will be applied under ordinary client calls to
-+ the path or servlet. A value of INCLUDE means the Filter will be
-+ applied under RequestDispatcher.include() calls. A value of
-+ ERROR means the Filter will be applied under the error page
-+ mechanism. The absence of any dispatcher elements in a
-+ filter-mapping indicates a default of applying filters only under
-+ ordinary client calls to the path or servlet.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:string">
-+ <xsd:enumeration value="FORWARD"/>
-+ <xsd:enumeration value="INCLUDE"/>
-+ <xsd:enumeration value="REQUEST"/>
-+ <xsd:enumeration value="ERROR"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:simpleType name="encodingType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The encodingType defines IANA character sets.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:restriction base="xsd:string">
-+ <xsd:pattern value="[^\s]+"/>
-+ </xsd:restriction>
-+ </xsd:simpleType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="error-codeType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The error-code contains an HTTP error code, ex: 404
-+
-+ Used in: error-page
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:xsdPositiveIntegerType">
-+ <xsd:pattern value="\d{3}"/>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="error-pageType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The error-pageType contains a mapping between an error code
-+ or exception type to the path of a resource in the web
-+ application.
-+
-+ Used in: web-app
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:choice>
-+ <xsd:element name="error-code"
-+ type="j2ee:error-codeType"/>
-+
-+ <xsd:element name="exception-type"
-+ type="j2ee:fully-qualified-classType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The exception-type contains a fully qualified class
-+ name of a Java exception type.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:choice>
-+
-+ <xsd:element name="location"
-+ type="j2ee:war-pathType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The location element contains the location of the
-+ resource in the web application relative to the root of
-+ the web application. The value of the location must have
-+ a leading `/'.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="filter-mappingType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ Declaration of the filter mappings in this web
-+ application is done by using filter-mappingType.
-+ 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.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="filter-name"
-+ type="j2ee:filter-nameType"/>
-+ <xsd:choice>
-+ <xsd:element name="url-pattern"
-+ type="j2ee:url-patternType"/>
-+ <xsd:element name="servlet-name"
-+ type="j2ee:servlet-nameType"/>
-+ </xsd:choice>
-+ <xsd:element name="dispatcher"
-+ type="j2ee:dispatcherType"
-+ minOccurs="0" maxOccurs="4"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="filter-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The logical name of the filter is declare
-+ by using filter-nameType. This name is used to map the
-+ filter. Each filter name is unique within the web
-+ application.
-+
-+ Used in: filter, filter-mapping
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:simpleContent>
-+ <xsd:extension base="j2ee:nonEmptyStringType"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="filterType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The filterType is used to declare 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.
-+
-+ Used in: web-app
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:group ref="j2ee:descriptionGroup"/>
-+ <xsd:element name="filter-name"
-+ type="j2ee:filter-nameType"/>
-+ <xsd:element name="filter-class"
-+ type="j2ee:fully-qualified-classType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The fully qualified classname of the filter.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="init-param"
-+ type="j2ee:param-valueType"
-+ minOccurs="0" maxOccurs="unbounded">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The init-param element contains a name/value pair as
-+ an initialization param of a servlet filter
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="form-login-configType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The form-login-configType 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.
-+
-+ Used in: login-config
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+
-+ <xsd:element name="form-login-page"
-+ type="j2ee:war-pathType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The form-login-page element defines the location in the web
-+ app where the page that can be used for login can be
-+ found. The path begins with a leading / and is interpreted
-+ relative to the root of the WAR.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="form-error-page"
-+ type="j2ee:war-pathType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ 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.
-+ The path begins with a leading / and is interpreted
-+ relative to the root of the WAR.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="http-methodType">
-+ <xsd:annotation>
-+
-+ <xsd:documentation>
-+
-+ The http-method contains an HTTP method recognized by the
-+ web-app, for example GET, POST, ...
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:string">
-+ <xsd:enumeration value="GET"/>
-+ <xsd:enumeration value="POST"/>
-+ <xsd:enumeration value="PUT"/>
-+ <xsd:enumeration value="DELETE"/>
-+ <xsd:enumeration value="HEAD"/>
-+ <xsd:enumeration value="OPTIONS"/>
-+ <xsd:enumeration value="TRACE"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="locale-encoding-mapping-listType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The locale-encoding-mapping-list contains one or more
-+ locale-encoding-mapping(s).
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="locale-encoding-mapping"
-+ type="j2ee:locale-encoding-mappingType"
-+ maxOccurs="unbounded"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="locale-encoding-mappingType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The locale-encoding-mapping contains locale name and
-+ encoding name. The locale name must be either "Language-code",
-+ such as "ja", defined by ISO-639 or "Language-code_Country-code",
-+ such as "ja_JP". "Country code" is defined by ISO-3166.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="locale"
-+ type="j2ee:localeType"/>
-+ <xsd:element name="encoding"
-+ type="j2ee:encodingType"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:simpleType name="localeType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The localeType defines valid locale defined by ISO-639-1
-+ and ISO-3166.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:restriction base="xsd:string">
-+ <xsd:pattern value="[a-z]{2}(_|-)?([\p{L}\-\p{Nd}]{2})?"/>
-+ </xsd:restriction>
-+ </xsd:simpleType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="login-configType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The login-configType 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.
-+
-+ Used in: web-app
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="auth-method"
-+ type="j2ee:auth-methodType"
-+ minOccurs="0"/>
-+ <xsd:element name="realm-name"
-+ type="j2ee:string" minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The realm name element specifies the realm name to
-+ use in HTTP Basic authorization.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="form-login-config"
-+ type="j2ee:form-login-configType"
-+ minOccurs="0"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="mime-mappingType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The mime-mappingType defines a mapping between an extension
-+ and a mime type.
-+
-+ Used in: web-app
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The extension element contains a string describing an
-+ extension. example: "txt"
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:element name="extension"
-+ type="j2ee:string"/>
-+ <xsd:element name="mime-type"
-+ type="j2ee:mime-typeType"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="mime-typeType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The mime-typeType is used to indicate a defined mime type.
-+
-+ Example:
-+ "text/plain"
-+
-+ Used in: mime-mapping
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:string">
-+ <xsd:pattern value="[^\p{Cc}^\s]+/[^\p{Cc}^\s]+"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="nonEmptyStringType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ This type defines a string which contains at least one
-+ character.
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:string">
-+ <xsd:minLength value="1"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="security-constraintType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The security-constraintType is used to associate
-+ security constraints with one or more web resource
-+ collections
-+
-+ Used in: web-app
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="display-name"
-+ type="j2ee:display-nameType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="web-resource-collection"
-+ type="j2ee:web-resource-collectionType"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="auth-constraint"
-+ type="j2ee:auth-constraintType"
-+ minOccurs="0"/>
-+ <xsd:element name="user-data-constraint"
-+ type="j2ee:user-data-constraintType"
-+ minOccurs="0"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="servlet-mappingType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The servlet-mappingType defines a mapping between a
-+ servlet and a url pattern.
-+
-+ Used in: web-app
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="servlet-name"
-+ type="j2ee:servlet-nameType"/>
-+ <xsd:element name="url-pattern"
-+ type="j2ee:url-patternType"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="servlet-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The servlet-name element contains the canonical name of the
-+ servlet. Each servlet name is unique within the web
-+ application.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:simpleContent>
-+ <xsd:extension base="j2ee:nonEmptyStringType"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="servletType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The servletType is used to declare a servlet.
-+ It 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.
-+
-+ Used in: web-app
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:group ref="j2ee:descriptionGroup"/>
-+ <xsd:element name="servlet-name"
-+ type="j2ee:servlet-nameType"/>
-+ <xsd:choice>
-+ <xsd:element name="servlet-class"
-+ type="j2ee:fully-qualified-classType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The servlet-class element contains the fully
-+ qualified class name of the servlet.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="jsp-file"
-+ type="j2ee:jsp-fileType"/>
-+
-+ </xsd:choice>
-+
-+ <xsd:element name="init-param"
-+ type="j2ee:param-valueType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ <xsd:element name="load-on-startup"
-+ type="j2ee:xsdIntegerType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The load-on-startup element indicates that this
-+ servlet should be loaded (instantiated and have
-+ its init() called) on the startup of the web
-+ application. The optional contents of these
-+ element must be an integer indicating the order in
-+ which the servlet should be loaded. If the value
-+ is a negative integer, or the element is not
-+ present, the container is free to load the servlet
-+ whenever it chooses. If the value is a positive
-+ integer or 0, the container must load and
-+ initialize the servlet as the application is
-+ deployed. The container must guarantee that
-+ servlets marked with lower integers are loaded
-+ before servlets marked with higher integers. The
-+ container may choose the order of loading of
-+ servlets with the same load-on-start-up value.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="run-as"
-+ type="j2ee:run-asType"
-+ minOccurs="0"/>
-+ <xsd:element name="security-role-ref"
-+ type="j2ee:security-role-refType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="session-configType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The session-configType defines the session parameters
-+ for this web application.
-+
-+ Used in: web-app
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="session-timeout"
-+ type="j2ee:xsdIntegerType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ 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.
-+ If the timeout is 0 or less, the container ensures
-+ the default behaviour of sessions is never to time
-+ out. If this element is not specified, the container
-+ must set its default timeout period.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="transport-guaranteeType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The transport-guaranteeType 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.
-+
-+ Used in: user-data-constraint
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:string">
-+ <xsd:enumeration value="NONE"/>
-+ <xsd:enumeration value="INTEGRAL"/>
-+ <xsd:enumeration value="CONFIDENTIAL"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="user-data-constraintType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The user-data-constraintType is used to indicate how
-+ data communicated between the client and container should be
-+ protected.
-+
-+ Used in: security-constraint
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="j2ee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="transport-guarantee"
-+ type="j2ee:transport-guaranteeType"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="war-pathType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The elements that use this type designate a path starting
-+ with a "/" and interpreted relative to the root of a WAR
-+ file.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="j2ee:string">
-+ <xsd:pattern value="/.*"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:simpleType name="web-app-versionType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type contains the recognized versions of
-+ web-application supported. It is used to designate the
-+ version of the web application.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:restriction base="xsd:token">
-+ <xsd:enumeration value="2.4"/>
-+ </xsd:restriction>
-+ </xsd:simpleType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="web-appType">
-+
-+ <xsd:choice minOccurs="0" maxOccurs="unbounded">
-+ <xsd:group ref="j2ee:descriptionGroup"/>
-+ <xsd:element name="distributable"
-+ type="j2ee:emptyType"/>
-+ <xsd:element name="context-param"
-+ type="j2ee:param-valueType">
-+
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The context-param element contains the declaration
-+ of a web application's servlet context
-+ initialization parameters.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="filter"
-+ type="j2ee:filterType"/>
-+ <xsd:element name="filter-mapping"
-+ type="j2ee:filter-mappingType"/>
-+ <xsd:element name="listener"
-+ type="j2ee:listenerType"/>
-+ <xsd:element name="servlet"
-+ type="j2ee:servletType"/>
-+ <xsd:element name="servlet-mapping"
-+ type="j2ee:servlet-mappingType"/>
-+ <xsd:element name="session-config"
-+ type="j2ee:session-configType"/>
-+ <xsd:element name="mime-mapping"
-+ type="j2ee:mime-mappingType"/>
-+ <xsd:element name="welcome-file-list"
-+ type="j2ee:welcome-file-listType"/>
-+ <xsd:element name="error-page"
-+ type="j2ee:error-pageType"/>
-+ <xsd:element name="jsp-config"
-+ type="j2ee:jsp-configType"/>
-+ <xsd:element name="security-constraint"
-+ type="j2ee:security-constraintType"/>
-+ <xsd:element name="login-config"
-+ type="j2ee:login-configType"/>
-+ <xsd:element name="security-role"
-+ type="j2ee:security-roleType"/>
-+ <xsd:group ref="j2ee:jndiEnvironmentRefsGroup"/>
-+ <xsd:element name="message-destination"
-+ type="j2ee:message-destinationType"/>
-+ <xsd:element name="locale-encoding-mapping-list"
-+ type="j2ee:locale-encoding-mapping-listType"/>
-+ </xsd:choice>
-+
-+ <xsd:attribute name="version"
-+ type="j2ee:web-app-versionType"
-+ use="required"/>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="web-resource-collectionType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The web-resource-collectionType 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.
-+
-+ Used in: security-constraint
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="web-resource-name"
-+ type="j2ee:string">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The web-resource-name contains the name of this web
-+ resource collection.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="description"
-+ type="j2ee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="url-pattern"
-+ type="j2ee:url-patternType"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="http-method"
-+ type="j2ee:http-methodType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="welcome-file-listType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The welcome-file-list contains an ordered list of welcome
-+ files elements.
-+
-+ Used in: web-app
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="welcome-file"
-+ type="xsd:string"
-+ maxOccurs="unbounded">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The welcome-file element contains file name to use
-+ as a default welcome file, such as index.html
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+</xsd:schema>
-+
-Index: jenkins-winstone/src/conf/javax/servlet/resources/web-app_2_5.xsd
-===================================================================
---- /dev/null 1970-01-01 00:00:00.000000000 +0000
-+++ jenkins-winstone/src/conf/javax/servlet/resources/web-app_2_5.xsd 2012-04-26 11:45:47.806315312 +0100
-@@ -0,0 +1,1275 @@
-+<?xml version="1.0" encoding="UTF-8"?>
-+<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
-+ targetNamespace="http://java.sun.com/xml/ns/javaee"
-+ xmlns:javaee="http://java.sun.com/xml/ns/javaee"
-+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
-+ elementFormDefault="qualified"
-+ attributeFormDefault="unqualified"
-+ version="2.5">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ @(#)web-app_2_5.xsds 1.68 07/03/09
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
-+
-+ Copyright 2003-2007 Sun Microsystems, Inc. All rights reserved.
-+
-+ The contents of this file are subject to the terms of either the
-+ GNU General Public License Version 2 only ("GPL") or the Common
-+ Development and Distribution License("CDDL") (collectively, the
-+ "License"). You may not use this file except in compliance with
-+ the License. You can obtain a copy of the License at
-+ https://glassfish.dev.java.net/public/CDDL+GPL.html or
-+ glassfish/bootstrap/legal/LICENSE.txt. See the License for the
-+ specific language governing permissions and limitations under the
-+ License.
-+
-+ When distributing the software, include this License Header
-+ Notice in each file and include the License file at
-+ glassfish/bootstrap/legal/LICENSE.txt. Sun designates this
-+ particular file as subject to the "Classpath" exception as
-+ provided by Sun in the GPL Version 2 section of the License file
-+ that accompanied this code. If applicable, add the following
-+ below the License Header, with the fields enclosed by brackets []
-+ replaced by your own identifying information:
-+ "Portions Copyrighted [year] [name of copyright owner]"
-+
-+ Contributor(s):
-+
-+ If you wish your version of this file to be governed by only the
-+ CDDL or only the GPL Version 2, indicate your decision by adding
-+ "[Contributor] elects to include this software in this
-+ distribution under the [CDDL or GPL Version 2] license." If you
-+ don't indicate a single choice of license, a recipient has the
-+ option to distribute your version of this file under either the
-+ CDDL, the GPL Version 2 or to extend the choice of license to its
-+ licensees as provided above. However, if you add GPL Version 2
-+ code and therefore, elected the GPL Version 2 license, then the
-+ option applies only if the new code is made subject to such
-+ option by the copyright holder.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ <![CDATA[
-+
-+ This is the XML Schema for the Servlet 2.5 deployment descriptor.
-+ The deployment descriptor must be named "WEB-INF/web.xml" in the
-+ web application's war file. All Servlet deployment descriptors
-+ must indicate the web application schema by using the Java EE
-+ namespace:
-+
-+ http://java.sun.com/xml/ns/javaee
-+
-+ and by indicating the version of the schema by
-+ using the version element as shown below:
-+
-+ <web-app xmlns="http://java.sun.com/xml/ns/javaee"
-+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-+ xsi:schemaLocation="..."
-+ version="2.5">
-+ ...
-+ </web-app>
-+
-+ The instance documents may indicate the published version of
-+ the schema using the xsi:schemaLocation attribute for Java EE
-+ namespace with the following location:
-+
-+ http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd
-+
-+ ]]>
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The following conventions apply to all Java EE
-+ deployment descriptor elements unless indicated otherwise.
-+
-+ - In elements that specify a pathname to a file within the
-+ same JAR file, relative filenames (i.e., those not
-+ starting with "/") are considered relative to the root of
-+ the JAR file's namespace. Absolute filenames (i.e., those
-+ starting with "/") also specify names in the root of the
-+ JAR file's namespace. In general, relative names are
-+ preferred. The exception is .war files where absolute
-+ names are preferred for consistency with the Servlet API.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:include schemaLocation="javaee_5.xsd"/>
-+ <xsd:include schemaLocation="jsp_2_1.xsd"/>
-+
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:element name="web-app" type="javaee:web-appType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The web-app element is the root of the deployment
-+ descriptor for a web application. Note that the sub-elements
-+ of this element can be in the arbitrary order. Because of
-+ that, the multiplicity of the elements of distributable,
-+ session-config, welcome-file-list, jsp-config, login-config,
-+ and locale-encoding-mapping-list was changed from "?" to "*"
-+ in this schema. However, the deployment descriptor instance
-+ file must not contain multiple elements of session-config,
-+ jsp-config, and login-config. When there are multiple elements of
-+ welcome-file-list or locale-encoding-mapping-list, the container
-+ must concatenate the element contents. The multiple occurence
-+ of the element distributable is redundant and the container
-+ treats that case exactly in the same way when there is only
-+ one distributable.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:unique name="web-app-servlet-name-uniqueness">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The servlet element contains the name of a servlet.
-+ The name must be unique within the web application.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:selector xpath="javaee:servlet"/>
-+ <xsd:field xpath="javaee:servlet-name"/>
-+ </xsd:unique>
-+
-+ <xsd:unique name="web-app-filter-name-uniqueness">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The filter element contains the name of a filter.
-+ The name must be unique within the web application.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:selector xpath="javaee:filter"/>
-+ <xsd:field xpath="javaee:filter-name"/>
-+ </xsd:unique>
-+
-+ <xsd:unique name="web-app-ejb-local-ref-name-uniqueness">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The ejb-local-ref-name element contains the name of an EJB
-+ reference. The EJB reference is an entry in the web
-+ application's environment and is relative to the
-+ java:comp/env context. The name must be unique within
-+ the web application.
-+
-+ It is recommended that name is prefixed with "ejb/".
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:selector xpath="javaee:ejb-local-ref"/>
-+ <xsd:field xpath="javaee:ejb-ref-name"/>
-+ </xsd:unique>
-+
-+ <xsd:unique name="web-app-ejb-ref-name-uniqueness">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The ejb-ref-name element contains the name of an EJB
-+ reference. The EJB reference is an entry in the web
-+ application's environment and is relative to the
-+ java:comp/env context. The name must be unique within
-+ the web application.
-+
-+ It is recommended that name is prefixed with "ejb/".
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:selector xpath="javaee:ejb-ref"/>
-+ <xsd:field xpath="javaee:ejb-ref-name"/>
-+ </xsd:unique>
-+
-+ <xsd:unique name="web-app-resource-env-ref-uniqueness">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The resource-env-ref-name element specifies the name of
-+ a resource environment reference; its value is the
-+ environment entry name used in the web application code.
-+ The name is a JNDI name relative to the java:comp/env
-+ context and must be unique within a web application.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:selector xpath="javaee:resource-env-ref"/>
-+ <xsd:field xpath="javaee:resource-env-ref-name"/>
-+ </xsd:unique>
-+
-+ <xsd:unique name="web-app-message-destination-ref-uniqueness">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The message-destination-ref-name element specifies the name of
-+ a message destination reference; its value is the
-+ environment entry name used in the web application code.
-+ The name is a JNDI name relative to the java:comp/env
-+ context and must be unique within a web application.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:selector xpath="javaee:message-destination-ref"/>
-+ <xsd:field xpath="javaee:message-destination-ref-name"/>
-+ </xsd:unique>
-+
-+ <xsd:unique name="web-app-res-ref-name-uniqueness">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The res-ref-name element specifies the name of a
-+ resource manager connection factory reference. The name
-+ is a JNDI name relative to the java:comp/env context.
-+ The name must be unique within a web application.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:selector xpath="javaee:resource-ref"/>
-+ <xsd:field xpath="javaee:res-ref-name"/>
-+ </xsd:unique>
-+
-+ <xsd:unique name="web-app-env-entry-name-uniqueness">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The env-entry-name element contains the name of a web
-+ application's environment entry. The name is a JNDI
-+ name relative to the java:comp/env context. The name
-+ must be unique within a web application.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:selector xpath="javaee:env-entry"/>
-+ <xsd:field xpath="javaee:env-entry-name"/>
-+ </xsd:unique>
-+
-+ <xsd:key name="web-app-role-name-key">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ A role-name-key is specified to allow the references
-+ from the security-role-refs.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:selector xpath="javaee:security-role"/>
-+ <xsd:field xpath="javaee:role-name"/>
-+ </xsd:key>
-+
-+ <xsd:keyref name="web-app-role-name-references"
-+ refer="javaee:web-app-role-name-key">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The keyref indicates the references from
-+ security-role-ref to a specified role-name.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:selector xpath="javaee:servlet/javaee:security-role-ref"/>
-+ <xsd:field xpath="javaee:role-link"/>
-+ </xsd:keyref>
-+ </xsd:element>
-+
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="auth-constraintType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The auth-constraintType indicates the user roles that
-+ should be permitted access to this resource
-+ collection. The role-name used here must either correspond
-+ to the role-name of one of the security-role elements
-+ defined for this web application, 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. If no roles are defined, no user is allowed access
-+ to the portion of the web application described by the
-+ containing security-constraint. The container matches
-+ role names case sensitively when determining access.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="javaee:descriptionType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ <xsd:element name="role-name"
-+ type="javaee:role-nameType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="auth-methodType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The auth-methodType 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 are "BASIC",
-+ "DIGEST", "FORM", "CLIENT-CERT", or a vendor-specific
-+ authentication scheme.
-+
-+ Used in: login-config
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:string"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="dispatcherType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The dispatcher has four legal values: FORWARD, REQUEST, INCLUDE,
-+ and ERROR. A value of FORWARD means the Filter will be applied
-+ under RequestDispatcher.forward() calls. A value of REQUEST
-+ means the Filter will be applied under ordinary client calls to
-+ the path or servlet. A value of INCLUDE means the Filter will be
-+ applied under RequestDispatcher.include() calls. A value of
-+ ERROR means the Filter will be applied under the error page
-+ mechanism. The absence of any dispatcher elements in a
-+ filter-mapping indicates a default of applying filters only under
-+ ordinary client calls to the path or servlet.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:string">
-+ <xsd:enumeration value="FORWARD"/>
-+ <xsd:enumeration value="INCLUDE"/>
-+ <xsd:enumeration value="REQUEST"/>
-+ <xsd:enumeration value="ERROR"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:simpleType name="encodingType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The encodingType defines IANA character sets.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:restriction base="xsd:string">
-+ <xsd:pattern value="[^\s]+"/>
-+ </xsd:restriction>
-+ </xsd:simpleType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="error-codeType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The error-code contains an HTTP error code, ex: 404
-+
-+ Used in: error-page
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:xsdPositiveIntegerType">
-+ <xsd:pattern value="\d{3}"/>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="error-pageType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The error-pageType contains a mapping between an error code
-+ or exception type to the path of a resource in the web
-+ application.
-+
-+ Used in: web-app
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:choice>
-+ <xsd:element name="error-code"
-+ type="javaee:error-codeType"/>
-+
-+ <xsd:element name="exception-type"
-+ type="javaee:fully-qualified-classType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The exception-type contains a fully qualified class
-+ name of a Java exception type.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:choice>
-+
-+ <xsd:element name="location"
-+ type="javaee:war-pathType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The location element contains the location of the
-+ resource in the web application relative to the root of
-+ the web application. The value of the location must have
-+ a leading `/'.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="filter-mappingType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ Declaration of the filter mappings in this web
-+ application is done by using filter-mappingType.
-+ 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.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="filter-name"
-+ type="javaee:filter-nameType"/>
-+ <xsd:choice minOccurs="1" maxOccurs="unbounded">
-+ <xsd:element name="url-pattern"
-+ type="javaee:url-patternType"/>
-+ <xsd:element name="servlet-name"
-+ type="javaee:servlet-nameType"/>
-+ </xsd:choice>
-+ <xsd:element name="dispatcher"
-+ type="javaee:dispatcherType"
-+ minOccurs="0" maxOccurs="4"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="filter-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The logical name of the filter is declare
-+ by using filter-nameType. This name is used to map the
-+ filter. Each filter name is unique within the web
-+ application.
-+
-+ Used in: filter, filter-mapping
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:simpleContent>
-+ <xsd:extension base="javaee:nonEmptyStringType"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="filterType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The filterType is used to declare 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.
-+
-+ Used in: web-app
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:group ref="javaee:descriptionGroup"/>
-+ <xsd:element name="filter-name"
-+ type="javaee:filter-nameType"/>
-+ <xsd:element name="filter-class"
-+ type="javaee:fully-qualified-classType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The fully qualified classname of the filter.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="init-param"
-+ type="javaee:param-valueType"
-+ minOccurs="0" maxOccurs="unbounded">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The init-param element contains a name/value pair as
-+ an initialization param of a servlet filter
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="form-login-configType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The form-login-configType 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.
-+
-+ Used in: login-config
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+
-+ <xsd:element name="form-login-page"
-+ type="javaee:war-pathType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The form-login-page element defines the location in the web
-+ app where the page that can be used for login can be
-+ found. The path begins with a leading / and is interpreted
-+ relative to the root of the WAR.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="form-error-page"
-+ type="javaee:war-pathType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ 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.
-+ The path begins with a leading / and is interpreted
-+ relative to the root of the WAR.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:simpleType name="http-methodType">
-+ <xsd:annotation>
-+
-+ <xsd:documentation>
-+
-+ A HTTP method type as defined in HTTP 1.1 section 2.2.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:restriction base="xsd:token">
-+ <xsd:pattern value="[!-~-[\(\)<>@,;:"/\[\]?=\{\}\\\p{Z}]]+"/>
-+ </xsd:restriction>
-+
-+ </xsd:simpleType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:simpleType name="load-on-startupType">
-+ <xsd:union memberTypes="javaee:null-charType xsd:integer"/>
-+ </xsd:simpleType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="locale-encoding-mapping-listType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The locale-encoding-mapping-list contains one or more
-+ locale-encoding-mapping(s).
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="locale-encoding-mapping"
-+ type="javaee:locale-encoding-mappingType"
-+ maxOccurs="unbounded"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="locale-encoding-mappingType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The locale-encoding-mapping contains locale name and
-+ encoding name. The locale name must be either "Language-code",
-+ such as "ja", defined by ISO-639 or "Language-code_Country-code",
-+ such as "ja_JP". "Country code" is defined by ISO-3166.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="locale"
-+ type="javaee:localeType"/>
-+ <xsd:element name="encoding"
-+ type="javaee:encodingType"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:simpleType name="localeType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The localeType defines valid locale defined by ISO-639-1
-+ and ISO-3166.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:restriction base="xsd:string">
-+ <xsd:pattern value="[a-z]{2}(_|-)?([\p{L}\-\p{Nd}]{2})?"/>
-+ </xsd:restriction>
-+ </xsd:simpleType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="login-configType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The login-configType 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.
-+
-+ Used in: web-app
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="auth-method"
-+ type="javaee:auth-methodType"
-+ minOccurs="0"/>
-+ <xsd:element name="realm-name"
-+ type="javaee:string" minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The realm name element specifies the realm name to
-+ use in HTTP Basic authorization.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="form-login-config"
-+ type="javaee:form-login-configType"
-+ minOccurs="0"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="mime-mappingType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The mime-mappingType defines a mapping between an extension
-+ and a mime type.
-+
-+ Used in: web-app
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The extension element contains a string describing an
-+ extension. example: "txt"
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:element name="extension"
-+ type="javaee:string"/>
-+ <xsd:element name="mime-type"
-+ type="javaee:mime-typeType"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="mime-typeType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The mime-typeType is used to indicate a defined mime type.
-+
-+ Example:
-+ "text/plain"
-+
-+ Used in: mime-mapping
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:string">
-+ <xsd:pattern value="[^\p{Cc}^\s]+/[^\p{Cc}^\s]+"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="nonEmptyStringType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+ This type defines a string which contains at least one
-+ character.
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:string">
-+ <xsd:minLength value="1"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:simpleType name="null-charType">
-+ <xsd:restriction base="xsd:string">
-+ <xsd:enumeration value=""/>
-+ </xsd:restriction>
-+ </xsd:simpleType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="security-constraintType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The security-constraintType is used to associate
-+ security constraints with one or more web resource
-+ collections
-+
-+ Used in: web-app
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="display-name"
-+ type="javaee:display-nameType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="web-resource-collection"
-+ type="javaee:web-resource-collectionType"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="auth-constraint"
-+ type="javaee:auth-constraintType"
-+ minOccurs="0"/>
-+ <xsd:element name="user-data-constraint"
-+ type="javaee:user-data-constraintType"
-+ minOccurs="0"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="servlet-mappingType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The servlet-mappingType defines a mapping between a
-+ servlet and a url pattern.
-+
-+ Used in: web-app
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="servlet-name"
-+ type="javaee:servlet-nameType"/>
-+ <xsd:element name="url-pattern"
-+ type="javaee:url-patternType"
-+ minOccurs="1" maxOccurs="unbounded"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="servlet-nameType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The servlet-name element contains the canonical name of the
-+ servlet. Each servlet name is unique within the web
-+ application.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:simpleContent>
-+ <xsd:extension base="javaee:nonEmptyStringType"/>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="servletType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The servletType is used to declare a servlet.
-+ It 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.
-+
-+ Used in: web-app
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:group ref="javaee:descriptionGroup"/>
-+ <xsd:element name="servlet-name"
-+ type="javaee:servlet-nameType"/>
-+ <xsd:choice>
-+ <xsd:element name="servlet-class"
-+ type="javaee:fully-qualified-classType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The servlet-class element contains the fully
-+ qualified class name of the servlet.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="jsp-file"
-+ type="javaee:jsp-fileType"/>
-+
-+ </xsd:choice>
-+
-+ <xsd:element name="init-param"
-+ type="javaee:param-valueType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ <xsd:element name="load-on-startup"
-+ type="javaee:load-on-startupType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The load-on-startup element indicates that this
-+ servlet should be loaded (instantiated and have
-+ its init() called) on the startup of the web
-+ application. The optional contents of these
-+ element must be an integer indicating the order in
-+ which the servlet should be loaded. If the value
-+ is a negative integer, or the element is not
-+ present, the container is free to load the servlet
-+ whenever it chooses. If the value is a positive
-+ integer or 0, the container must load and
-+ initialize the servlet as the application is
-+ deployed. The container must guarantee that
-+ servlets marked with lower integers are loaded
-+ before servlets marked with higher integers. The
-+ container may choose the order of loading of
-+ servlets with the same load-on-start-up value.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="run-as"
-+ type="javaee:run-asType"
-+ minOccurs="0"/>
-+ <xsd:element name="security-role-ref"
-+ type="javaee:security-role-refType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="session-configType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The session-configType defines the session parameters
-+ for this web application.
-+
-+ Used in: web-app
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="session-timeout"
-+ type="javaee:xsdIntegerType"
-+ minOccurs="0">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ 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.
-+ If the timeout is 0 or less, the container ensures
-+ the default behaviour of sessions is never to time
-+ out. If this element is not specified, the container
-+ must set its default timeout period.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="transport-guaranteeType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The transport-guaranteeType 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.
-+
-+ Used in: user-data-constraint
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:string">
-+ <xsd:enumeration value="NONE"/>
-+ <xsd:enumeration value="INTEGRAL"/>
-+ <xsd:enumeration value="CONFIDENTIAL"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="user-data-constraintType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The user-data-constraintType is used to indicate how
-+ data communicated between the client and container should be
-+ protected.
-+
-+ Used in: security-constraint
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="description"
-+ type="javaee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="transport-guarantee"
-+ type="javaee:transport-guaranteeType"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="war-pathType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The elements that use this type designate a path starting
-+ with a "/" and interpreted relative to the root of a WAR
-+ file.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:simpleContent>
-+ <xsd:restriction base="javaee:string">
-+ <xsd:pattern value="/.*"/>
-+ </xsd:restriction>
-+ </xsd:simpleContent>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:simpleType name="web-app-versionType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ This type contains the recognized versions of
-+ web-application supported. It is used to designate the
-+ version of the web application.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ <xsd:restriction base="xsd:token">
-+ <xsd:enumeration value="2.5"/>
-+ </xsd:restriction>
-+ </xsd:simpleType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="web-appType">
-+
-+ <xsd:choice minOccurs="0" maxOccurs="unbounded">
-+ <xsd:group ref="javaee:descriptionGroup"/>
-+ <xsd:element name="distributable"
-+ type="javaee:emptyType"/>
-+ <xsd:element name="context-param"
-+ type="javaee:param-valueType">
-+
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The context-param element contains the declaration
-+ of a web application's servlet context
-+ initialization parameters.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+
-+ <xsd:element name="filter"
-+ type="javaee:filterType"/>
-+ <xsd:element name="filter-mapping"
-+ type="javaee:filter-mappingType"/>
-+ <xsd:element name="listener"
-+ type="javaee:listenerType"/>
-+ <xsd:element name="servlet"
-+ type="javaee:servletType"/>
-+ <xsd:element name="servlet-mapping"
-+ type="javaee:servlet-mappingType"/>
-+ <xsd:element name="session-config"
-+ type="javaee:session-configType"/>
-+ <xsd:element name="mime-mapping"
-+ type="javaee:mime-mappingType"/>
-+ <xsd:element name="welcome-file-list"
-+ type="javaee:welcome-file-listType"/>
-+ <xsd:element name="error-page"
-+ type="javaee:error-pageType"/>
-+ <xsd:element name="jsp-config"
-+ type="javaee:jsp-configType"/>
-+ <xsd:element name="security-constraint"
-+ type="javaee:security-constraintType"/>
-+ <xsd:element name="login-config"
-+ type="javaee:login-configType"/>
-+ <xsd:element name="security-role"
-+ type="javaee:security-roleType"/>
-+ <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/>
-+ <xsd:element name="message-destination"
-+ type="javaee:message-destinationType"/>
-+ <xsd:element name="locale-encoding-mapping-list"
-+ type="javaee:locale-encoding-mapping-listType"/>
-+ </xsd:choice>
-+
-+ <xsd:attribute name="version"
-+ type="javaee:web-app-versionType"
-+ use="required"/>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+
-+ <xsd:attribute name="metadata-complete" type="xsd:boolean">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The metadata-complete attribute defines whether this
-+ deployment descriptor and other related deployment
-+ descriptors for this module (e.g., web service
-+ descriptors) are complete, or whether the class
-+ files available to this module and packaged with
-+ this application should be examined for annotations
-+ that specify deployment information.
-+
-+ If metadata-complete is set to "true", the deployment
-+ tool must ignore any annotations that specify deployment
-+ information, which might be present in the class files
-+ of the application.
-+
-+ If metadata-complete is not specified or is set to
-+ "false", the deployment tool must examine the class
-+ files of the application for annotations, as
-+ specified by the specifications.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:attribute>
-+
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="web-resource-collectionType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The web-resource-collectionType 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.
-+
-+ Used in: security-constraint
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="web-resource-name"
-+ type="javaee:string">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The web-resource-name contains the name of this web
-+ resource collection.
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ <xsd:element name="description"
-+ type="javaee:descriptionType"
-+ minOccurs="0"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="url-pattern"
-+ type="javaee:url-patternType"
-+ maxOccurs="unbounded"/>
-+ <xsd:element name="http-method"
-+ type="javaee:http-methodType"
-+ minOccurs="0" maxOccurs="unbounded"/>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+<!-- **************************************************** -->
-+
-+ <xsd:complexType name="welcome-file-listType">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The welcome-file-list contains an ordered list of welcome
-+ files elements.
-+
-+ Used in: web-app
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+
-+ <xsd:sequence>
-+ <xsd:element name="welcome-file"
-+ type="xsd:string"
-+ maxOccurs="unbounded">
-+ <xsd:annotation>
-+ <xsd:documentation>
-+
-+ The welcome-file element contains file name to use
-+ as a default welcome file, such as index.html
-+
-+ </xsd:documentation>
-+ </xsd:annotation>
-+ </xsd:element>
-+ </xsd:sequence>
-+ <xsd:attribute name="id" type="xsd:ID"/>
-+ </xsd:complexType>
-+
-+</xsd:schema>
-+
-Index: jenkins-winstone/src/conf/javax/servlet/resources/xml.xsd
-===================================================================
---- /dev/null 1970-01-01 00:00:00.000000000 +0000
-+++ jenkins-winstone/src/conf/javax/servlet/resources/xml.xsd 2012-04-26 11:45:47.806315312 +0100
-@@ -0,0 +1,287 @@
-+<?xml version='1.0'?>
-+<?xml-stylesheet href="../2008/09/xsd.xsl" type="text/xsl"?>
-+<xs:schema targetNamespace="http://www.w3.org/XML/1998/namespace"
-+ xmlns:xs="http://www.w3.org/2001/XMLSchema"
-+ xmlns ="http://www.w3.org/1999/xhtml"
-+ xml:lang="en">
-+
-+ <xs:annotation>
-+ <xs:documentation>
-+ <div>
-+ <h1>About the XML namespace</h1>
-+
-+ <div class="bodytext">
-+ <p>
-+ This schema document describes the XML namespace, in a form
-+ suitable for import by other schema documents.
-+ </p>
-+ <p>
-+ See <a href="http://www.w3.org/XML/1998/namespace.html">
-+ http://www.w3.org/XML/1998/namespace.html</a> and
-+ <a href="http://www.w3.org/TR/REC-xml">
-+ http://www.w3.org/TR/REC-xml</a> for information
-+ about this namespace.
-+ </p>
-+ <p>
-+ Note that local names in this namespace are intended to be
-+ defined only by the World Wide Web Consortium or its subgroups.
-+ The names currently defined in this namespace are listed below.
-+ They should not be used with conflicting semantics by any Working
-+ Group, specification, or document instance.
-+ </p>
-+ <p>
-+ See further below in this document for more information about <a
-+ href="#usage">how to refer to this schema document from your own
-+ XSD schema documents</a> and about <a href="#nsversioning">the
-+ namespace-versioning policy governing this schema document</a>.
-+ </p>
-+ </div>
-+ </div>
-+ </xs:documentation>
-+ </xs:annotation>
-+
-+ <xs:attribute name="lang">
-+ <xs:annotation>
-+ <xs:documentation>
-+ <div>
-+
-+ <h3>lang (as an attribute name)</h3>
-+ <p>
-+ denotes an attribute whose value
-+ is a language code for the natural language of the content of
-+ any element; its value is inherited. This name is reserved
-+ by virtue of its definition in the XML specification.</p>
-+
-+ </div>
-+ <div>
-+ <h4>Notes</h4>
-+ <p>
-+ Attempting to install the relevant ISO 2- and 3-letter
-+ codes as the enumerated possible values is probably never
-+ going to be a realistic possibility.
-+ </p>
-+ <p>
-+ See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">
-+ http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>
-+ and the IANA language subtag registry at
-+ <a href="http://www.iana.org/assignments/language-subtag-registry">
-+ http://www.iana.org/assignments/language-subtag-registry</a>
-+ for further information.
-+ </p>
-+ <p>
-+ The union allows for the 'un-declaration' of xml:lang with
-+ the empty string.
-+ </p>
-+ </div>
-+ </xs:documentation>
-+ </xs:annotation>
-+ <xs:simpleType>
-+ <xs:union memberTypes="xs:language">
-+ <xs:simpleType>
-+ <xs:restriction base="xs:string">
-+ <xs:enumeration value=""/>
-+ </xs:restriction>
-+ </xs:simpleType>
-+ </xs:union>
-+ </xs:simpleType>
-+ </xs:attribute>
-+
-+ <xs:attribute name="space">
-+ <xs:annotation>
-+ <xs:documentation>
-+ <div>
-+
-+ <h3>space (as an attribute name)</h3>
-+ <p>
-+ denotes an attribute whose
-+ value is a keyword indicating what whitespace processing
-+ discipline is intended for the content of the element; its
-+ value is inherited. This name is reserved by virtue of its
-+ definition in the XML specification.</p>
-+
-+ </div>
-+ </xs:documentation>
-+ </xs:annotation>
-+ <xs:simpleType>
-+ <xs:restriction base="xs:NCName">
-+ <xs:enumeration value="default"/>
-+ <xs:enumeration value="preserve"/>
-+ </xs:restriction>
-+ </xs:simpleType>
-+ </xs:attribute>
-+
-+ <xs:attribute name="base" type="xs:anyURI"> <xs:annotation>
-+ <xs:documentation>
-+ <div>
-+
-+ <h3>base (as an attribute name)</h3>
-+ <p>
-+ denotes an attribute whose value
-+ provides a URI to be used as the base for interpreting any
-+ relative URIs in the scope of the element on which it
-+ appears; its value is inherited. This name is reserved
-+ by virtue of its definition in the XML Base specification.</p>
-+
-+ <p>
-+ See <a
-+ href="http://www.w3.org/TR/xmlbase/">http://www.w3.org/TR/xmlbase/</a>
-+ for information about this attribute.
-+ </p>
-+ </div>
-+ </xs:documentation>
-+ </xs:annotation>
-+ </xs:attribute>
-+
-+ <xs:attribute name="id" type="xs:ID">
-+ <xs:annotation>
-+ <xs:documentation>
-+ <div>
-+
-+ <h3>id (as an attribute name)</h3>
-+ <p>
-+ denotes an attribute whose value
-+ should be interpreted as if declared to be of type ID.
-+ This name is reserved by virtue of its definition in the
-+ xml:id specification.</p>
-+
-+ <p>
-+ See <a
-+ href="http://www.w3.org/TR/xml-id/">http://www.w3.org/TR/xml-id/</a>
-+ for information about this attribute.
-+ </p>
-+ </div>
-+ </xs:documentation>
-+ </xs:annotation>
-+ </xs:attribute>
-+
-+ <xs:attributeGroup name="specialAttrs">
-+ <xs:attribute ref="xml:base"/>
-+ <xs:attribute ref="xml:lang"/>
-+ <xs:attribute ref="xml:space"/>
-+ <xs:attribute ref="xml:id"/>
-+ </xs:attributeGroup>
-+
-+ <xs:annotation>
-+ <xs:documentation>
-+ <div>
-+
-+ <h3>Father (in any context at all)</h3>
-+
-+ <div class="bodytext">
-+ <p>
-+ denotes Jon Bosak, the chair of
-+ the original XML Working Group. This name is reserved by
-+ the following decision of the W3C XML Plenary and
-+ XML Coordination groups:
-+ </p>
-+ <blockquote>
-+ <p>
-+ In appreciation for his vision, leadership and
-+ dedication the W3C XML Plenary on this 10th day of
-+ February, 2000, reserves for Jon Bosak in perpetuity
-+ the XML name "xml:Father".
-+ </p>
-+ </blockquote>
-+ </div>
-+ </div>
-+ </xs:documentation>
-+ </xs:annotation>
-+
-+ <xs:annotation>
-+ <xs:documentation>
-+ <div xml:id="usage" id="usage">
-+ <h2><a name="usage">About this schema document</a></h2>
-+
-+ <div class="bodytext">
-+ <p>
-+ This schema defines attributes and an attribute group suitable
-+ for use by schemas wishing to allow <code>xml:base</code>,
-+ <code>xml:lang</code>, <code>xml:space</code> or
-+ <code>xml:id</code> attributes on elements they define.
-+ </p>
-+ <p>
-+ To enable this, such a schema must import this schema for
-+ the XML namespace, e.g. as follows:
-+ </p>
-+ <pre>
-+ <schema . . .>
-+ . . .
-+ <import namespace="http://www.w3.org/XML/1998/namespace"
-+ schemaLocation="http://www.w3.org/2001/xml.xsd"/>
-+ </pre>
-+ <p>
-+ or
-+ </p>
-+ <pre>
-+ <import namespace="http://www.w3.org/XML/1998/namespace"
-+ schemaLocation="http://www.w3.org/2009/01/xml.xsd"/>
-+ </pre>
-+ <p>
-+ Subsequently, qualified reference to any of the attributes or the
-+ group defined below will have the desired effect, e.g.
-+ </p>
-+ <pre>
-+ <type . . .>
-+ . . .
-+ <attributeGroup ref="xml:specialAttrs"/>
-+ </pre>
-+ <p>
-+ will define a type which will schema-validate an instance element
-+ with any of those attributes.
-+ </p>
-+ </div>
-+ </div>
-+ </xs:documentation>
-+ </xs:annotation>
-+
-+ <xs:annotation>
-+ <xs:documentation>
-+ <div id="nsversioning" xml:id="nsversioning">
-+ <h2><a name="nsversioning">Versioning policy for this schema document</a></h2>
-+ <div class="bodytext">
-+ <p>
-+ In keeping with the XML Schema WG's standard versioning
-+ policy, this schema document will persist at
-+ <a href="http://www.w3.org/2009/01/xml.xsd">
-+ http://www.w3.org/2009/01/xml.xsd</a>.
-+ </p>
-+ <p>
-+ At the date of issue it can also be found at
-+ <a href="http://www.w3.org/2001/xml.xsd">
-+ http://www.w3.org/2001/xml.xsd</a>.
-+ </p>
-+ <p>
-+ The schema document at that URI may however change in the future,
-+ in order to remain compatible with the latest version of XML
-+ Schema itself, or with the XML namespace itself. In other words,
-+ if the XML Schema or XML namespaces change, the version of this
-+ document at <a href="http://www.w3.org/2001/xml.xsd">
-+ http://www.w3.org/2001/xml.xsd
-+ </a>
-+ will change accordingly; the version at
-+ <a href="http://www.w3.org/2009/01/xml.xsd">
-+ http://www.w3.org/2009/01/xml.xsd
-+ </a>
-+ will not change.
-+ </p>
-+ <p>
-+ Previous dated (and unchanging) versions of this schema
-+ document are at:
-+ </p>
-+ <ul>
-+ <li><a href="http://www.w3.org/2009/01/xml.xsd">
-+ http://www.w3.org/2009/01/xml.xsd</a></li>
-+ <li><a href="http://www.w3.org/2007/08/xml.xsd">
-+ http://www.w3.org/2007/08/xml.xsd</a></li>
-+ <li><a href="http://www.w3.org/2004/10/xml.xsd">
-+ http://www.w3.org/2004/10/xml.xsd</a></li>
-+ <li><a href="http://www.w3.org/2001/03/xml.xsd">
-+ http://www.w3.org/2001/03/xml.xsd</a></li>
-+ </ul>
-+ </div>
-+ </div>
-+ </xs:documentation>
-+ </xs:annotation>
-+
-+</xs:schema>
-+
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-java/jenkins-winstone.git
More information about the pkg-java-commits
mailing list