Ubuntu
jenkins-winstone package

Merge lp:~james-page/ubuntu/oneiric/jenkins-winstone/827651 into lp:ubuntu/oneiric/jenkins-winstone

  1. Oneiric (11.10)
  2. 827651
  3. Merge into oneiric
Proposed by James Page
Status: Merged
Merge reported by: James Page
Merged at revision: not available
Proposed branch: lp:~james-page/ubuntu/oneiric/jenkins-winstone/827651
Merge into: lp:ubuntu/oneiric/jenkins-winstone
Diff against target: 21177 lines (+20803/-202)
24 files modified
.pc/applied-patches (+1/-1)
.pc/use_system_servletapi.patch/pom.xml (+0/-151)
debian/README.source (+3/-3)
debian/changelog (+16/-0)
debian/control (+0/-2)
debian/copyright (+9/-0)
debian/libjenkins-winstone-java.classpath (+0/-1)
debian/patches/series (+1/-1)
debian/patches/specification-resources.patch (+10419/-0)
debian/patches/use_system_servletapi.patch (+0/-30)
pom.xml (+0/-13)
src/conf/javax/servlet/resources/XMLSchema.dtd (+402/-0)
src/conf/javax/servlet/resources/datatypes.dtd (+203/-0)
src/conf/javax/servlet/resources/j2ee_1_4.xsd (+1616/-0)
src/conf/javax/servlet/resources/j2ee_web_services_client_1_1.xsd (+353/-0)
src/conf/javax/servlet/resources/javaee_5.xsd (+2102/-0)
src/conf/javax/servlet/resources/javaee_web_services_client_1_2.xsd (+585/-0)
src/conf/javax/servlet/resources/jsp_2_0.xsd (+316/-0)
src/conf/javax/servlet/resources/jsp_2_1.xsd (+349/-0)
src/conf/javax/servlet/resources/web-app_2_2.dtd (+602/-0)
src/conf/javax/servlet/resources/web-app_2_3.dtd (+1022/-0)
src/conf/javax/servlet/resources/web-app_2_4.xsd (+1242/-0)
src/conf/javax/servlet/resources/web-app_2_5.xsd (+1275/-0)
src/conf/javax/servlet/resources/xml.xsd (+287/-0)
To merge this branch: bzr merge lp:~james-page/ubuntu/oneiric/jenkins-winstone/827651
Reviewer Review Type Date Requested Status
Ubuntu Development Team Pending
Review via email: mp+72024@code.launchpad.net

Description of the change

Patch in required Java EE specifications under CDDL/GPL-2 license to provide full offline functionality and remove dependencies on libservlet-2.5-java which does not have the full set of specifications required.

To post a comment you must log in.

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
=== modified file '.pc/applied-patches'
--- .pc/applied-patches 2011-06-29 12:16:17 +0000
+++ .pc/applied-patches 2011-08-18 11:23:23 +0000
@@ -1,2 +1,2 @@
1java-1.6.patch1java-1.6.patch
2use_system_servletapi.patch2specification-resources.patch
33
=== added directory '.pc/specification-resources.patch'
=== added directory '.pc/specification-resources.patch/src'
=== added directory '.pc/specification-resources.patch/src/conf'
=== added directory '.pc/specification-resources.patch/src/conf/javax'
=== added directory '.pc/specification-resources.patch/src/conf/javax/servlet'
=== added directory '.pc/specification-resources.patch/src/conf/javax/servlet/resources'
=== added file '.pc/specification-resources.patch/src/conf/javax/servlet/resources/XMLSchema.dtd'
=== added file '.pc/specification-resources.patch/src/conf/javax/servlet/resources/datatypes.dtd'
=== added file '.pc/specification-resources.patch/src/conf/javax/servlet/resources/j2ee_1_4.xsd'
=== added file '.pc/specification-resources.patch/src/conf/javax/servlet/resources/j2ee_web_services_client_1_1.xsd'
=== added file '.pc/specification-resources.patch/src/conf/javax/servlet/resources/javaee_5.xsd'
=== added file '.pc/specification-resources.patch/src/conf/javax/servlet/resources/javaee_web_services_client_1_2.xsd'
=== added file '.pc/specification-resources.patch/src/conf/javax/servlet/resources/jsp_2_0.xsd'
=== added file '.pc/specification-resources.patch/src/conf/javax/servlet/resources/jsp_2_1.xsd'
=== added file '.pc/specification-resources.patch/src/conf/javax/servlet/resources/web-app_2_2.dtd'
=== added file '.pc/specification-resources.patch/src/conf/javax/servlet/resources/web-app_2_3.dtd'
=== added file '.pc/specification-resources.patch/src/conf/javax/servlet/resources/web-app_2_4.xsd'
=== added file '.pc/specification-resources.patch/src/conf/javax/servlet/resources/web-app_2_5.xsd'
=== added file '.pc/specification-resources.patch/src/conf/javax/servlet/resources/xml.xsd'
=== removed directory '.pc/use_system_servletapi.patch'
=== removed file '.pc/use_system_servletapi.patch/pom.xml'
--- .pc/use_system_servletapi.patch/pom.xml 2011-06-29 12:16:17 +0000
+++ .pc/use_system_servletapi.patch/pom.xml 1970-01-01 00:00:00 +0000
@@ -1,151 +0,0 @@
1<project>
2 <modelVersion>4.0.0</modelVersion>
3 <groupId>org.jenkins-ci</groupId>
4 <artifactId>winstone</artifactId>
5 <version>0.9.10-jenkins-25</version>
6 <packaging>jar</packaging>
7
8 <name>Winstone</name>
9 <url>http://winstone.sourceforge.net/</url>
10 <description>Winstone is a servlet container that was written out of a desire to provide servlet functionality without the bloat that full J2EE compliance introduces.</description>
11
12 <licenses>
13 <license>
14 <name>GNU Lesser General Public License version 2.1</name>
15 <url>http://www.gnu.org/licenses/lgpl.html</url>
16 </license>
17 <license>
18 <name>COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 1.0</name>
19 <url>http://www.sun.com/cddl/cddl.html</url>
20 </license>
21 </licenses>
22
23 <scm>
24 <connection>scm:cvs:pserver:anonymous@winstone.cvs.sourceforge.net:/cvsroot/winstone</connection>
25 <url>http://winstone.cvs.sourceforge.net/winstone/winstone</url>
26 </scm>
27
28 <build>
29 <sourceDirectory>src/java</sourceDirectory>
30
31 <resources>
32 <resource>
33 <directory>src/conf</directory>
34 <filtering>true</filtering>
35 <includes>
36 <include>**/*.*</include>
37 </includes>
38 </resource>
39
40 <resource>
41 <directory>src/java</directory>
42 <includes>
43 <include>**/*.properties</include>
44 </includes>
45 </resource>
46 </resources>
47
48 <testSourceDirectory>src/test</testSourceDirectory>
49
50 <testResources>
51 <testResource>
52 <directory>src/test</directory>
53 <excludes>
54 <exclude>**/*.java</exclude>
55 </excludes>
56 </testResource>
57 </testResources>
58
59 <plugins>
60 <plugin>
61 <artifactId>maven-compiler-plugin</artifactId>
62 <configuration>
63 <source>1.5</source>
64 <target>1.5</target>
65 </configuration>
66 </plugin>
67
68 <plugin>
69 <artifactId>maven-antrun-plugin</artifactId>
70 <executions>
71 <execution>
72 <id>prepare-testwebapp</id>
73 <phase>process-test-classes</phase>
74 <goals>
75 <goal>run</goal>
76 </goals>
77 <configuration>
78 <tasks>
79 <copy overwrite="true" todir="${project.build.directory}">
80 <fileset dir="${basedir}/src" includes="testwebapp/**"/>
81 </copy>
82 <copy overwrite="true" todir="${project.build.directory}/testwebapp/WEB-INF/classes">
83 <fileset dir="${project.build.testOutputDirectory}" includes="**"/>
84 </copy>
85 </tasks>
86 </configuration>
87 </execution>
88 </executions>
89 </plugin>
90
91 <plugin>
92 <artifactId>maven-surefire-plugin</artifactId>
93 <configuration>
94 <includes>
95 <include>**/*Test.java</include>
96 </includes>
97 <excludes>
98 <exclude>**/*NaughtyTest.java</exclude>
99 <exclude>winstone/testCase/load/LoadTest.java</exclude>
100 </excludes>
101 </configuration>
102 </plugin>
103
104 <plugin>
105 <artifactId>maven-jar-plugin</artifactId>
106 <configuration>
107 <archive>
108 <manifest>
109 <addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>
110 <addDefaultImplementationEntries>true</addDefaultImplementationEntries>
111 <mainClass>winstone.Launcher</mainClass>
112 </manifest>
113 </archive>
114 </configuration>
115 </plugin>
116 </plugins>
117 </build>
118
119 <distributionManagement>
120 <repository>
121 <id>maven.jenkins-ci.org</id>
122 <url>http://maven.jenkins-ci.org:8081/content/repositories/releases</url>
123 </repository>
124 </distributionManagement>
125
126 <repositories>
127 <repository>
128 <id>maven2-repository.dev.java.net</id>
129 <name>Java.net Repository for Maven</name>
130 <url>http://download.java.net/maven/2/</url>
131 </repository>
132 </repositories>
133
134 <dependencies>
135 <dependency>
136 <groupId>junit</groupId>
137 <artifactId>junit</artifactId>
138 <version>3.8.1</version>
139 <scope>test</scope>
140 </dependency>
141
142 <dependency>
143 <groupId>httpunit</groupId>
144 <artifactId>httpunit</artifactId>
145 <version>1.6</version>
146 <scope>test</scope>
147 </dependency>
148 </dependencies>
149
150</project>
151
1520
=== modified file 'debian/README.source'
--- debian/README.source 2011-06-29 12:16:17 +0000
+++ debian/README.source 2011-08-18 11:23:23 +0000
@@ -21,6 +21,6 @@
21license appears to have been granted to the winstone project 21license appears to have been granted to the winstone project
22for these files.22for these files.
2323
24Sun Microsystems did release these files under CDDL or GPL-2;24Sun Microsystems did released these files under CDDL or GPL-2;
25libservlet2.5-java provides the same files under CDDL/Apache-2.025these versions are patched into the source tree during package build.
26so this library is used instead.26(see debian/patches/specification-resources.patch)
2727
=== modified file 'debian/changelog'
--- debian/changelog 2011-06-29 12:16:17 +0000
+++ debian/changelog 2011-08-18 11:23:23 +0000
@@ -1,3 +1,19 @@
1jenkins-winstone (0.9.10-jenkins-25+dfsg-0ubuntu2) oneiric; urgency=low
2
3 * Support offline validation of XML configuration files (LP: #827651):
4 - debian/patches/specification-resources.patch: CDDL/GPL-2 licensed
5 xsd+DTD resources for all servlet, jsp and j2ee specifications.
6 - debian/copyright: documented copyright + license for
7 specification-resources.patch.
8 - debian/control: Removed dependency on libservlet2.5-java, no longer
9 required.
10 - debian/patches/series,debian/patches/use_system_servletapi.patch:
11 Dropped patch as no longer required.
12 - debian/libjenkins-winstone-java.classpath: Dropped as all required
13 resources are now included in winstone.
14
15 -- James Page <james.page@ubuntu.com> Thu, 18 Aug 2011 09:55:33 +0100
16
1jenkins-winstone (0.9.10-jenkins-25+dfsg-0ubuntu1) oneiric; urgency=low17jenkins-winstone (0.9.10-jenkins-25+dfsg-0ubuntu1) oneiric; urgency=low
218
3 * Initial release 19 * Initial release
420
=== modified file 'debian/control'
--- debian/control 2011-06-29 12:16:17 +0000
+++ debian/control 2011-08-18 11:23:23 +0000
@@ -16,8 +16,6 @@
16 libhttpunit-java,16 libhttpunit-java,
17 libmaven-antrun-plugin-java,17 libmaven-antrun-plugin-java,
18 libmaven-javadoc-plugin-java,18 libmaven-javadoc-plugin-java,
19 libservlet2.5-java,
20 libservlet2.5-java-doc
21Standards-Version: 3.9.219Standards-Version: 3.9.2
22Homepage: http://github.com/jenkinsci/winstone20Homepage: http://github.com/jenkinsci/winstone
2321
2422
=== modified file 'debian/copyright'
--- debian/copyright 2011-06-29 12:16:17 +0000
+++ debian/copyright 2011-08-18 11:23:23 +0000
@@ -10,6 +10,10 @@
10Copyright: 2011, Canonical Ltd (http://www.canonical.com/)10Copyright: 2011, Canonical Ltd (http://www.canonical.com/)
11License: CDDL11License: CDDL
1212
13Files: debian/patches/specification-resources.patch
14Copyright: 1999-2007, Sun Microsystems, Inc
15License: CDDL or GPL-2 with Classpath exception
16
13License: CDDL17License: CDDL
14 COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 1.018 COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 1.0
15 .19 .
@@ -395,3 +399,8 @@
395License: LGPL-2.1399License: LGPL-2.1
396 On Debian GNU/Linux system you can find the complete text of the400 On Debian GNU/Linux system you can find the complete text of the
397 LGPL-2.1 license in '/usr/share/common-licenses/LGPL-2.1'401 LGPL-2.1 license in '/usr/share/common-licenses/LGPL-2.1'
402
403License: GPL-2
404 On Debian GNU/Linux system you can find the complete text of the
405 GPL-2 license in '/usr/share/common-licenses/GPL-2'
406
398407
=== removed file 'debian/libjenkins-winstone-java.classpath'
--- debian/libjenkins-winstone-java.classpath 2011-06-29 12:16:17 +0000
+++ debian/libjenkins-winstone-java.classpath 1970-01-01 00:00:00 +0000
@@ -1,1 +0,0 @@
1usr/share/java/jenkins-winstone.jar /usr/share/java/servlet-api-2.5.jar
20
=== modified file 'debian/patches/series'
--- debian/patches/series 2011-06-29 12:16:17 +0000
+++ debian/patches/series 2011-08-18 11:23:23 +0000
@@ -1,2 +1,2 @@
1java-1.6.patch1java-1.6.patch
2use_system_servletapi.patch2specification-resources.patch
33
=== added file 'debian/patches/specification-resources.patch'
--- debian/patches/specification-resources.patch 1970-01-01 00:00:00 +0000
+++ debian/patches/specification-resources.patch 2011-08-18 11:23:23 +0000
@@ -0,0 +1,10419 @@
1Index: jenkins-winstone/src/conf/javax/servlet/resources/XMLSchema.dtd
2===================================================================
3--- /dev/null 1970-01-01 00:00:00.000000000 +0000
4+++ jenkins-winstone/src/conf/javax/servlet/resources/XMLSchema.dtd 2011-08-18 09:37:53.671397840 +0100
5@@ -0,0 +1,402 @@
6+<!-- DTD for XML Schemas: Part 1: Structures
7+ Public Identifier: "-//W3C//DTD XMLSCHEMA 200102//EN"
8+ Official Location: http://www.w3.org/2001/XMLSchema.dtd -->
9+<!-- $Id: XMLSchema.dtd,v 1.31 2001/10/24 15:50:16 ht Exp $ -->
10+<!-- Note this DTD is NOT normative, or even definitive. --> <!--d-->
11+<!-- prose copy in the structures REC is the definitive version --> <!--d-->
12+<!-- (which shouldn't differ from this one except for this --> <!--d-->
13+<!-- comment and entity expansions, but just in case) --> <!--d-->
14+<!-- With the exception of cases with multiple namespace
15+ prefixes for the XML Schema namespace, any XML document which is
16+ not valid per this DTD given redefinitions in its internal subset of the
17+ 'p' and 's' parameter entities below appropriate to its namespace
18+ declaration of the XML Schema namespace is almost certainly not
19+ a valid schema. -->
20+
21+<!-- The simpleType element and its constituent parts
22+ are defined in XML Schema: Part 2: Datatypes -->
23+<!ENTITY % xs-datatypes PUBLIC 'datatypes' 'datatypes.dtd' >
24+
25+<!ENTITY % p 'xs:'> <!-- can be overriden in the internal subset of a
26+ schema document to establish a different
27+ namespace prefix -->
28+<!ENTITY % s ':xs'> <!-- if %p is defined (e.g. as foo:) then you must
29+ also define %s as the suffix for the appropriate
30+ namespace declaration (e.g. :foo) -->
31+<!ENTITY % nds 'xmlns%s;'>
32+
33+<!-- Define all the element names, with optional prefix -->
34+<!ENTITY % schema "%p;schema">
35+<!ENTITY % complexType "%p;complexType">
36+<!ENTITY % complexContent "%p;complexContent">
37+<!ENTITY % simpleContent "%p;simpleContent">
38+<!ENTITY % extension "%p;extension">
39+<!ENTITY % element "%p;element">
40+<!ENTITY % unique "%p;unique">
41+<!ENTITY % key "%p;key">
42+<!ENTITY % keyref "%p;keyref">
43+<!ENTITY % selector "%p;selector">
44+<!ENTITY % field "%p;field">
45+<!ENTITY % group "%p;group">
46+<!ENTITY % all "%p;all">
47+<!ENTITY % choice "%p;choice">
48+<!ENTITY % sequence "%p;sequence">
49+<!ENTITY % any "%p;any">
50+<!ENTITY % anyAttribute "%p;anyAttribute">
51+<!ENTITY % attribute "%p;attribute">
52+<!ENTITY % attributeGroup "%p;attributeGroup">
53+<!ENTITY % include "%p;include">
54+<!ENTITY % import "%p;import">
55+<!ENTITY % redefine "%p;redefine">
56+<!ENTITY % notation "%p;notation">
57+
58+<!-- annotation elements -->
59+<!ENTITY % annotation "%p;annotation">
60+<!ENTITY % appinfo "%p;appinfo">
61+<!ENTITY % documentation "%p;documentation">
62+
63+<!-- Customisation entities for the ATTLIST of each element type.
64+ Define one of these if your schema takes advantage of the
65+ anyAttribute='##other' in the schema for schemas -->
66+
67+<!ENTITY % schemaAttrs ''>
68+<!ENTITY % complexTypeAttrs ''>
69+<!ENTITY % complexContentAttrs ''>
70+<!ENTITY % simpleContentAttrs ''>
71+<!ENTITY % extensionAttrs ''>
72+<!ENTITY % elementAttrs ''>
73+<!ENTITY % groupAttrs ''>
74+<!ENTITY % allAttrs ''>
75+<!ENTITY % choiceAttrs ''>
76+<!ENTITY % sequenceAttrs ''>
77+<!ENTITY % anyAttrs ''>
78+<!ENTITY % anyAttributeAttrs ''>
79+<!ENTITY % attributeAttrs ''>
80+<!ENTITY % attributeGroupAttrs ''>
81+<!ENTITY % uniqueAttrs ''>
82+<!ENTITY % keyAttrs ''>
83+<!ENTITY % keyrefAttrs ''>
84+<!ENTITY % selectorAttrs ''>
85+<!ENTITY % fieldAttrs ''>
86+<!ENTITY % includeAttrs ''>
87+<!ENTITY % importAttrs ''>
88+<!ENTITY % redefineAttrs ''>
89+<!ENTITY % notationAttrs ''>
90+<!ENTITY % annotationAttrs ''>
91+<!ENTITY % appinfoAttrs ''>
92+<!ENTITY % documentationAttrs ''>
93+
94+<!ENTITY % complexDerivationSet "CDATA">
95+ <!-- #all or space-separated list drawn from derivationChoice -->
96+<!ENTITY % blockSet "CDATA">
97+ <!-- #all or space-separated list drawn from
98+ derivationChoice + 'substitution' -->
99+
100+<!ENTITY % mgs '%all; | %choice; | %sequence;'>
101+<!ENTITY % cs '%choice; | %sequence;'>
102+<!ENTITY % formValues '(qualified|unqualified)'>
103+
104+
105+<!ENTITY % attrDecls '((%attribute;| %attributeGroup;)*,(%anyAttribute;)?)'>
106+
107+<!ENTITY % particleAndAttrs '((%mgs; | %group;)?, %attrDecls;)'>
108+
109+<!-- This is used in part2 -->
110+<!ENTITY % restriction1 '((%mgs; | %group;)?)'>
111+
112+%xs-datatypes;
113+
114+<!-- the duplication below is to produce an unambiguous content model
115+ which allows annotation everywhere -->
116+<!ELEMENT %schema; ((%include; | %import; | %redefine; | %annotation;)*,
117+ ((%simpleType; | %complexType;
118+ | %element; | %attribute;
119+ | %attributeGroup; | %group;
120+ | %notation; ),
121+ (%annotation;)*)* )>
122+<!ATTLIST %schema;
123+ targetNamespace %URIref; #IMPLIED
124+ version CDATA #IMPLIED
125+ %nds; %URIref; #FIXED 'http://www.w3.org/2001/XMLSchema'
126+ xmlns CDATA #IMPLIED
127+ finalDefault %complexDerivationSet; ''
128+ blockDefault %blockSet; ''
129+ id ID #IMPLIED
130+ elementFormDefault %formValues; 'unqualified'
131+ attributeFormDefault %formValues; 'unqualified'
132+ xml:lang CDATA #IMPLIED
133+ %schemaAttrs;>
134+<!-- Note the xmlns declaration is NOT in the Schema for Schemas,
135+ because at the Infoset level where schemas operate,
136+ xmlns(:prefix) is NOT an attribute! -->
137+<!-- The declaration of xmlns is a convenience for schema authors -->
138+
139+<!-- The id attribute here and below is for use in external references
140+ from non-schemas using simple fragment identifiers.
141+ It is NOT used for schema-to-schema reference, internal or
142+ external. -->
143+
144+<!-- a type is a named content type specification which allows attribute
145+ declarations-->
146+<!-- -->
147+
148+<!ELEMENT %complexType; ((%annotation;)?,
149+ (%simpleContent;|%complexContent;|
150+ %particleAndAttrs;))>
151+
152+<!ATTLIST %complexType;
153+ name %NCName; #IMPLIED
154+ id ID #IMPLIED
155+ abstract %boolean; #IMPLIED
156+ final %complexDerivationSet; #IMPLIED
157+ block %complexDerivationSet; #IMPLIED
158+ mixed (true|false) 'false'
159+ %complexTypeAttrs;>
160+
161+<!-- particleAndAttrs is shorthand for a root type -->
162+<!-- mixed is disallowed if simpleContent, overriden if complexContent
163+ has one too. -->
164+
165+<!-- If anyAttribute appears in one or more referenced attributeGroups
166+ and/or explicitly, the intersection of the permissions is used -->
167+
168+<!ELEMENT %complexContent; ((%annotation;)?, (%restriction;|%extension;))>
169+<!ATTLIST %complexContent;
170+ mixed (true|false) #IMPLIED
171+ id ID #IMPLIED
172+ %complexContentAttrs;>
173+
174+<!-- restriction should use the branch defined above, not the simple
175+ one from part2; extension should use the full model -->
176+
177+<!ELEMENT %simpleContent; ((%annotation;)?, (%restriction;|%extension;))>
178+<!ATTLIST %simpleContent;
179+ id ID #IMPLIED
180+ %simpleContentAttrs;>
181+
182+<!-- restriction should use the simple branch from part2, not the
183+ one defined above; extension should have no particle -->
184+
185+<!ELEMENT %extension; ((%annotation;)?, (%particleAndAttrs;))>
186+<!ATTLIST %extension;
187+ base %QName; #REQUIRED
188+ id ID #IMPLIED
189+ %extensionAttrs;>
190+
191+<!-- an element is declared by either:
192+ a name and a type (either nested or referenced via the type attribute)
193+ or a ref to an existing element declaration -->
194+
195+<!ELEMENT %element; ((%annotation;)?, (%complexType;| %simpleType;)?,
196+ (%unique; | %key; | %keyref;)*)>
197+<!-- simpleType or complexType only if no type|ref attribute -->
198+<!-- ref not allowed at top level -->
199+<!ATTLIST %element;
200+ name %NCName; #IMPLIED
201+ id ID #IMPLIED
202+ ref %QName; #IMPLIED
203+ type %QName; #IMPLIED
204+ minOccurs %nonNegativeInteger; #IMPLIED
205+ maxOccurs CDATA #IMPLIED
206+ nillable %boolean; #IMPLIED
207+ substitutionGroup %QName; #IMPLIED
208+ abstract %boolean; #IMPLIED
209+ final %complexDerivationSet; #IMPLIED
210+ block %blockSet; #IMPLIED
211+ default CDATA #IMPLIED
212+ fixed CDATA #IMPLIED
213+ form %formValues; #IMPLIED
214+ %elementAttrs;>
215+<!-- type and ref are mutually exclusive.
216+ name and ref are mutually exclusive, one is required -->
217+<!-- In the absence of type AND ref, type defaults to type of
218+ substitutionGroup, if any, else the ur-type, i.e. unconstrained -->
219+<!-- default and fixed are mutually exclusive -->
220+
221+<!ELEMENT %group; ((%annotation;)?,(%mgs;)?)>
222+<!ATTLIST %group;
223+ name %NCName; #IMPLIED
224+ ref %QName; #IMPLIED
225+ minOccurs %nonNegativeInteger; #IMPLIED
226+ maxOccurs CDATA #IMPLIED
227+ id ID #IMPLIED
228+ %groupAttrs;>
229+
230+<!ELEMENT %all; ((%annotation;)?, (%element;)*)>
231+<!ATTLIST %all;
232+ minOccurs (1) #IMPLIED
233+ maxOccurs (1) #IMPLIED
234+ id ID #IMPLIED
235+ %allAttrs;>
236+
237+<!ELEMENT %choice; ((%annotation;)?, (%element;| %group;| %cs; | %any;)*)>
238+<!ATTLIST %choice;
239+ minOccurs %nonNegativeInteger; #IMPLIED
240+ maxOccurs CDATA #IMPLIED
241+ id ID #IMPLIED
242+ %choiceAttrs;>
243+
244+<!ELEMENT %sequence; ((%annotation;)?, (%element;| %group;| %cs; | %any;)*)>
245+<!ATTLIST %sequence;
246+ minOccurs %nonNegativeInteger; #IMPLIED
247+ maxOccurs CDATA #IMPLIED
248+ id ID #IMPLIED
249+ %sequenceAttrs;>
250+
251+<!-- an anonymous grouping in a model, or
252+ a top-level named group definition, or a reference to same -->
253+
254+<!-- Note that if order is 'all', group is not allowed inside.
255+ If order is 'all' THIS group must be alone (or referenced alone) at
256+ the top level of a content model -->
257+<!-- If order is 'all', minOccurs==maxOccurs==1 on element/any inside -->
258+<!-- Should allow minOccurs=0 inside order='all' . . . -->
259+
260+<!ELEMENT %any; (%annotation;)?>
261+<!ATTLIST %any;
262+ namespace CDATA '##any'
263+ processContents (skip|lax|strict) 'strict'
264+ minOccurs %nonNegativeInteger; '1'
265+ maxOccurs CDATA '1'
266+ id ID #IMPLIED
267+ %anyAttrs;>
268+
269+<!-- namespace is interpreted as follows:
270+ ##any - - any non-conflicting WFXML at all
271+
272+ ##other - - any non-conflicting WFXML from namespace other
273+ than targetNamespace
274+
275+ ##local - - any unqualified non-conflicting WFXML/attribute
276+ one or - - any non-conflicting WFXML from
277+ more URI the listed namespaces
278+ references
279+
280+ ##targetNamespace ##local may appear in the above list,
281+ with the obvious meaning -->
282+
283+<!ELEMENT %anyAttribute; (%annotation;)?>
284+<!ATTLIST %anyAttribute;
285+ namespace CDATA '##any'
286+ processContents (skip|lax|strict) 'strict'
287+ id ID #IMPLIED
288+ %anyAttributeAttrs;>
289+<!-- namespace is interpreted as for 'any' above -->
290+
291+<!-- simpleType only if no type|ref attribute -->
292+<!-- ref not allowed at top level, name iff at top level -->
293+<!ELEMENT %attribute; ((%annotation;)?, (%simpleType;)?)>
294+<!ATTLIST %attribute;
295+ name %NCName; #IMPLIED
296+ id ID #IMPLIED
297+ ref %QName; #IMPLIED
298+ type %QName; #IMPLIED
299+ use (prohibited|optional|required) #IMPLIED
300+ default CDATA #IMPLIED
301+ fixed CDATA #IMPLIED
302+ form %formValues; #IMPLIED
303+ %attributeAttrs;>
304+<!-- type and ref are mutually exclusive.
305+ name and ref are mutually exclusive, one is required -->
306+<!-- default for use is optional when nested, none otherwise -->
307+<!-- default and fixed are mutually exclusive -->
308+<!-- type attr and simpleType content are mutually exclusive -->
309+
310+<!-- an attributeGroup is a named collection of attribute decls, or a
311+ reference thereto -->
312+<!ELEMENT %attributeGroup; ((%annotation;)?,
313+ (%attribute; | %attributeGroup;)*,
314+ (%anyAttribute;)?) >
315+<!ATTLIST %attributeGroup;
316+ name %NCName; #IMPLIED
317+ id ID #IMPLIED
318+ ref %QName; #IMPLIED
319+ %attributeGroupAttrs;>
320+
321+<!-- ref iff no content, no name. ref iff not top level -->
322+
323+<!-- better reference mechanisms -->
324+<!ELEMENT %unique; ((%annotation;)?, %selector;, (%field;)+)>
325+<!ATTLIST %unique;
326+ name %NCName; #REQUIRED
327+ id ID #IMPLIED
328+ %uniqueAttrs;>
329+
330+<!ELEMENT %key; ((%annotation;)?, %selector;, (%field;)+)>
331+<!ATTLIST %key;
332+ name %NCName; #REQUIRED
333+ id ID #IMPLIED
334+ %keyAttrs;>
335+
336+<!ELEMENT %keyref; ((%annotation;)?, %selector;, (%field;)+)>
337+<!ATTLIST %keyref;
338+ name %NCName; #REQUIRED
339+ refer %QName; #REQUIRED
340+ id ID #IMPLIED
341+ %keyrefAttrs;>
342+
343+<!ELEMENT %selector; ((%annotation;)?)>
344+<!ATTLIST %selector;
345+ xpath %XPathExpr; #REQUIRED
346+ id ID #IMPLIED
347+ %selectorAttrs;>
348+<!ELEMENT %field; ((%annotation;)?)>
349+<!ATTLIST %field;
350+ xpath %XPathExpr; #REQUIRED
351+ id ID #IMPLIED
352+ %fieldAttrs;>
353+
354+<!-- Schema combination mechanisms -->
355+<!ELEMENT %include; (%annotation;)?>
356+<!ATTLIST %include;
357+ schemaLocation %URIref; #REQUIRED
358+ id ID #IMPLIED
359+ %includeAttrs;>
360+
361+<!ELEMENT %import; (%annotation;)?>
362+<!ATTLIST %import;
363+ namespace %URIref; #IMPLIED
364+ schemaLocation %URIref; #IMPLIED
365+ id ID #IMPLIED
366+ %importAttrs;>
367+
368+<!ELEMENT %redefine; (%annotation; | %simpleType; | %complexType; |
369+ %attributeGroup; | %group;)*>
370+<!ATTLIST %redefine;
371+ schemaLocation %URIref; #REQUIRED
372+ id ID #IMPLIED
373+ %redefineAttrs;>
374+
375+<!ELEMENT %notation; (%annotation;)?>
376+<!ATTLIST %notation;
377+ name %NCName; #REQUIRED
378+ id ID #IMPLIED
379+ public CDATA #REQUIRED
380+ system %URIref; #IMPLIED
381+ %notationAttrs;>
382+
383+<!-- Annotation is either application information or documentation -->
384+<!-- By having these here they are available for datatypes as well
385+ as all the structures elements -->
386+
387+<!ELEMENT %annotation; (%appinfo; | %documentation;)*>
388+<!ATTLIST %annotation; %annotationAttrs;>
389+
390+<!-- User must define annotation elements in internal subset for this
391+ to work -->
392+<!ELEMENT %appinfo; ANY> <!-- too restrictive -->
393+<!ATTLIST %appinfo;
394+ source %URIref; #IMPLIED
395+ id ID #IMPLIED
396+ %appinfoAttrs;>
397+<!ELEMENT %documentation; ANY> <!-- too restrictive -->
398+<!ATTLIST %documentation;
399+ source %URIref; #IMPLIED
400+ id ID #IMPLIED
401+ xml:lang CDATA #IMPLIED
402+ %documentationAttrs;>
403+
404+<!NOTATION XMLSchemaStructures PUBLIC
405+ 'structures' 'http://www.w3.org/2001/XMLSchema.xsd' >
406+<!NOTATION XML PUBLIC
407+ 'REC-xml-1998-0210' 'http://www.w3.org/TR/1998/REC-xml-19980210' >
408Index: jenkins-winstone/src/conf/javax/servlet/resources/datatypes.dtd
409===================================================================
410--- /dev/null 1970-01-01 00:00:00.000000000 +0000
411+++ jenkins-winstone/src/conf/javax/servlet/resources/datatypes.dtd 2011-08-18 09:38:09.181383207 +0100
412@@ -0,0 +1,203 @@
413+<!--
414+ DTD for XML Schemas: Part 2: Datatypes
415+ $Id: datatypes.dtd,v 1.23 2001/03/16 17:36:30 ht Exp $
416+ Note this DTD is NOT normative, or even definitive. - - the
417+ prose copy in the datatypes REC is the definitive version
418+ (which shouldn't differ from this one except for this comment
419+ and entity expansions, but just in case)
420+ -->
421+
422+<!--
423+ This DTD cannot be used on its own, it is intended
424+ only for incorporation in XMLSchema.dtd, q.v.
425+ -->
426+
427+<!-- Define all the element names, with optional prefix -->
428+<!ENTITY % simpleType "%p;simpleType">
429+<!ENTITY % restriction "%p;restriction">
430+<!ENTITY % list "%p;list">
431+<!ENTITY % union "%p;union">
432+<!ENTITY % maxExclusive "%p;maxExclusive">
433+<!ENTITY % minExclusive "%p;minExclusive">
434+<!ENTITY % maxInclusive "%p;maxInclusive">
435+<!ENTITY % minInclusive "%p;minInclusive">
436+<!ENTITY % totalDigits "%p;totalDigits">
437+<!ENTITY % fractionDigits "%p;fractionDigits">
438+<!ENTITY % length "%p;length">
439+<!ENTITY % minLength "%p;minLength">
440+<!ENTITY % maxLength "%p;maxLength">
441+<!ENTITY % enumeration "%p;enumeration">
442+<!ENTITY % whiteSpace "%p;whiteSpace">
443+<!ENTITY % pattern "%p;pattern">
444+
445+<!--
446+ Customisation entities for the ATTLIST of each element
447+ type. Define one of these if your schema takes advantage
448+ of the anyAttribute='##other' in the schema for schemas
449+ -->
450+
451+<!ENTITY % simpleTypeAttrs "">
452+<!ENTITY % restrictionAttrs "">
453+<!ENTITY % listAttrs "">
454+<!ENTITY % unionAttrs "">
455+<!ENTITY % maxExclusiveAttrs "">
456+<!ENTITY % minExclusiveAttrs "">
457+<!ENTITY % maxInclusiveAttrs "">
458+<!ENTITY % minInclusiveAttrs "">
459+<!ENTITY % totalDigitsAttrs "">
460+<!ENTITY % fractionDigitsAttrs "">
461+<!ENTITY % lengthAttrs "">
462+<!ENTITY % minLengthAttrs "">
463+<!ENTITY % maxLengthAttrs "">
464+<!ENTITY % enumerationAttrs "">
465+<!ENTITY % whiteSpaceAttrs "">
466+<!ENTITY % patternAttrs "">
467+
468+<!-- Define some entities for informative use as attribute
469+ types -->
470+<!ENTITY % URIref "CDATA">
471+<!ENTITY % XPathExpr "CDATA">
472+<!ENTITY % QName "NMTOKEN">
473+<!ENTITY % QNames "NMTOKENS">
474+<!ENTITY % NCName "NMTOKEN">
475+<!ENTITY % nonNegativeInteger "NMTOKEN">
476+<!ENTITY % boolean "(true|false)">
477+<!ENTITY % simpleDerivationSet "CDATA">
478+<!--
479+ #all or space-separated list drawn from derivationChoice
480+ -->
481+
482+<!--
483+ Note that the use of 'facet' below is less restrictive
484+ than is really intended: There should in fact be no
485+ more than one of each of minInclusive, minExclusive,
486+ maxInclusive, maxExclusive, totalDigits, fractionDigits,
487+ length, maxLength, minLength within datatype,
488+ and the min- and max- variants of Inclusive and Exclusive
489+ are mutually exclusive. On the other hand, pattern and
490+ enumeration may repeat.
491+ -->
492+<!ENTITY % minBound "(%minInclusive; | %minExclusive;)">
493+<!ENTITY % maxBound "(%maxInclusive; | %maxExclusive;)">
494+<!ENTITY % bounds "%minBound; | %maxBound;">
495+<!ENTITY % numeric "%totalDigits; | %fractionDigits;">
496+<!ENTITY % ordered "%bounds; | %numeric;">
497+<!ENTITY % unordered
498+ "%pattern; | %enumeration; | %whiteSpace; | %length; |
499+ %maxLength; | %minLength;">
500+<!ENTITY % facet "%ordered; | %unordered;">
501+<!ENTITY % facetAttr
502+ "value CDATA #REQUIRED
503+ id ID #IMPLIED">
504+<!ENTITY % fixedAttr "fixed %boolean; #IMPLIED">
505+<!ENTITY % facetModel "(%annotation;)?">
506+<!ELEMENT %simpleType;
507+ ((%annotation;)?, (%restriction; | %list; | %union;))>
508+<!ATTLIST %simpleType;
509+ name %NCName; #IMPLIED
510+ final %simpleDerivationSet; #IMPLIED
511+ id ID #IMPLIED
512+ %simpleTypeAttrs;>
513+<!-- name is required at top level -->
514+<!ELEMENT %restriction; ((%annotation;)?,
515+ (%restriction1; |
516+ ((%simpleType;)?,(%facet;)*)),
517+ (%attrDecls;))>
518+<!ATTLIST %restriction;
519+ base %QName; #IMPLIED
520+ id ID #IMPLIED
521+ %restrictionAttrs;>
522+<!--
523+ base and simpleType child are mutually exclusive,
524+ one is required.
525+
526+ restriction is shared between simpleType and
527+ simpleContent and complexContent (in XMLSchema.xsd).
528+ restriction1 is for the latter cases, when this
529+ is restricting a complex type, as is attrDecls.
530+ -->
531+<!ELEMENT %list; ((%annotation;)?,(%simpleType;)?)>
532+<!ATTLIST %list;
533+ itemType %QName; #IMPLIED
534+ id ID #IMPLIED
535+ %listAttrs;>
536+<!--
537+ itemType and simpleType child are mutually exclusive,
538+ one is required
539+ -->
540+<!ELEMENT %union; ((%annotation;)?,(%simpleType;)*)>
541+<!ATTLIST %union;
542+ id ID #IMPLIED
543+ memberTypes %QNames; #IMPLIED
544+ %unionAttrs;>
545+<!--
546+ At least one item in memberTypes or one simpleType
547+ child is required
548+ -->
549+
550+<!ELEMENT %maxExclusive; %facetModel;>
551+<!ATTLIST %maxExclusive;
552+ %facetAttr;
553+ %fixedAttr;
554+ %maxExclusiveAttrs;>
555+<!ELEMENT %minExclusive; %facetModel;>
556+<!ATTLIST %minExclusive;
557+ %facetAttr;
558+ %fixedAttr;
559+ %minExclusiveAttrs;>
560+
561+<!ELEMENT %maxInclusive; %facetModel;>
562+<!ATTLIST %maxInclusive;
563+ %facetAttr;
564+ %fixedAttr;
565+ %maxInclusiveAttrs;>
566+<!ELEMENT %minInclusive; %facetModel;>
567+<!ATTLIST %minInclusive;
568+ %facetAttr;
569+ %fixedAttr;
570+ %minInclusiveAttrs;>
571+
572+<!ELEMENT %totalDigits; %facetModel;>
573+<!ATTLIST %totalDigits;
574+ %facetAttr;
575+ %fixedAttr;
576+ %totalDigitsAttrs;>
577+<!ELEMENT %fractionDigits; %facetModel;>
578+<!ATTLIST %fractionDigits;
579+ %facetAttr;
580+ %fixedAttr;
581+ %fractionDigitsAttrs;>
582+
583+<!ELEMENT %length; %facetModel;>
584+<!ATTLIST %length;
585+ %facetAttr;
586+ %fixedAttr;
587+ %lengthAttrs;>
588+<!ELEMENT %minLength; %facetModel;>
589+<!ATTLIST %minLength;
590+ %facetAttr;
591+ %fixedAttr;
592+ %minLengthAttrs;>
593+<!ELEMENT %maxLength; %facetModel;>
594+<!ATTLIST %maxLength;
595+ %facetAttr;
596+ %fixedAttr;
597+ %maxLengthAttrs;>
598+
599+<!-- This one can be repeated -->
600+<!ELEMENT %enumeration; %facetModel;>
601+<!ATTLIST %enumeration;
602+ %facetAttr;
603+ %enumerationAttrs;>
604+
605+<!ELEMENT %whiteSpace; %facetModel;>
606+<!ATTLIST %whiteSpace;
607+ %facetAttr;
608+ %fixedAttr;
609+ %whiteSpaceAttrs;>
610+
611+<!-- This one can be repeated -->
612+<!ELEMENT %pattern; %facetModel;>
613+<!ATTLIST %pattern;
614+ %facetAttr;
615+ %patternAttrs;>
616Index: jenkins-winstone/src/conf/javax/servlet/resources/j2ee_1_4.xsd
617===================================================================
618--- /dev/null 1970-01-01 00:00:00.000000000 +0000
619+++ jenkins-winstone/src/conf/javax/servlet/resources/j2ee_1_4.xsd 2011-08-18 09:34:02.141615523 +0100
620@@ -0,0 +1,1616 @@
621+<?xml version="1.0" encoding="UTF-8"?>
622+<xsd:schema
623+ targetNamespace="http://java.sun.com/xml/ns/j2ee"
624+ xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
625+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
626+ elementFormDefault="qualified"
627+ attributeFormDefault="unqualified"
628+ version="1.4">
629+ <xsd:annotation>
630+ <xsd:documentation>
631+ @(#)j2ee_1_4.xsds 1.43 03/09/16
632+ </xsd:documentation>
633+ </xsd:annotation>
634+
635+ <xsd:annotation>
636+ <xsd:documentation>
637+
638+ DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
639+
640+ Copyright 2003-2007 Sun Microsystems, Inc. All rights reserved.
641+
642+ The contents of this file are subject to the terms of either the
643+ GNU General Public License Version 2 only ("GPL") or the Common
644+ Development and Distribution License("CDDL") (collectively, the
645+ "License"). You may not use this file except in compliance with
646+ the License. You can obtain a copy of the License at
647+ https://glassfish.dev.java.net/public/CDDL+GPL.html or
648+ glassfish/bootstrap/legal/LICENSE.txt. See the License for the
649+ specific language governing permissions and limitations under the
650+ License.
651+
652+ When distributing the software, include this License Header
653+ Notice in each file and include the License file at
654+ glassfish/bootstrap/legal/LICENSE.txt. Sun designates this
655+ particular file as subject to the "Classpath" exception as
656+ provided by Sun in the GPL Version 2 section of the License file
657+ that accompanied this code. If applicable, add the following
658+ below the License Header, with the fields enclosed by brackets []
659+ replaced by your own identifying information:
660+ "Portions Copyrighted [year] [name of copyright owner]"
661+
662+ Contributor(s):
663+
664+ If you wish your version of this file to be governed by only the
665+ CDDL or only the GPL Version 2, indicate your decision by adding
666+ "[Contributor] elects to include this software in this
667+ distribution under the [CDDL or GPL Version 2] license." If you
668+ don't indicate a single choice of license, a recipient has the
669+ option to distribute your version of this file under either the
670+ CDDL, the GPL Version 2 or to extend the choice of license to its
671+ licensees as provided above. However, if you add GPL Version 2
672+ code and therefore, elected the GPL Version 2 license, then the
673+ option applies only if the new code is made subject to such
674+ option by the copyright holder.
675+
676+ </xsd:documentation>
677+ </xsd:annotation>
678+
679+<xsd:annotation>
680+<xsd:documentation>
681+
682+The following definitions that appear in the common
683+shareable schema(s) of J2EE deployment descriptors should be
684+interpreted with respect to the context they are included:
685+
686+Deployment Component may indicate one of the following:
687+ j2ee application;
688+ application client;
689+ web application;
690+ enterprise bean;
691+ resource adapter;
692+
693+Deployment File may indicate one of the following:
694+ ear file;
695+ war file;
696+ jar file;
697+ rar file;
698+
699+</xsd:documentation>
700+</xsd:annotation>
701+
702+ <xsd:import namespace="http://www.w3.org/XML/1998/namespace"
703+ schemaLocation="http://www.w3.org/2001/xml.xsd"/>
704+
705+ <xsd:include schemaLocation=
706+ "http://www.ibm.com/webservices/xsd/j2ee_web_services_client_1_1.xsd"/>
707+
708+
709+<!-- **************************************************** -->
710+
711+ <xsd:group name="descriptionGroup">
712+ <xsd:annotation>
713+ <xsd:documentation>
714+
715+ This group keeps the usage of the contained description related
716+ elements consistent across J2EE deployment descriptors.
717+
718+ All elements may occur multiple times with different languages,
719+ to support localization of the content.
720+
721+ </xsd:documentation>
722+ </xsd:annotation>
723+ <xsd:sequence>
724+ <xsd:element name="description"
725+ type="j2ee:descriptionType"
726+ minOccurs="0"
727+ maxOccurs="unbounded"/>
728+ <xsd:element name="display-name"
729+ type="j2ee:display-nameType"
730+ minOccurs="0"
731+ maxOccurs="unbounded"/>
732+ <xsd:element name="icon"
733+ type="j2ee:iconType"
734+ minOccurs="0"
735+ maxOccurs="unbounded"/>
736+ </xsd:sequence>
737+ </xsd:group>
738+
739+<!-- **************************************************** -->
740+
741+ <xsd:complexType name="descriptionType">
742+ <xsd:annotation>
743+ <xsd:documentation>
744+
745+ The description type is used by a description element to
746+ provide text describing the parent element. The elements
747+ that use this type should include any information that the
748+ Deployment Component's Deployment File file producer wants
749+ to provide to the consumer of the Deployment Component's
750+ Deployment File (i.e., to the Deployer). Typically, the
751+ tools used by such a Deployment File consumer will display
752+ the description when processing the parent element that
753+ contains the description.
754+
755+ The lang attribute defines the language that the
756+ description is provided in. The default value is "en" (English).
757+
758+ </xsd:documentation>
759+ </xsd:annotation>
760+ <xsd:simpleContent>
761+ <xsd:extension base="j2ee:xsdStringType">
762+ <xsd:attribute ref="xml:lang"/>
763+ </xsd:extension>
764+ </xsd:simpleContent>
765+ </xsd:complexType>
766+
767+<!-- **************************************************** -->
768+
769+ <xsd:simpleType name="dewey-versionType">
770+ <xsd:annotation>
771+ <xsd:documentation>
772+
773+ This type defines a dewey decimal which is used
774+ to describe versions of documents.
775+
776+ </xsd:documentation>
777+ </xsd:annotation>
778+
779+ <xsd:restriction base="xsd:decimal">
780+ <xsd:whiteSpace value="collapse"/>
781+ </xsd:restriction>
782+
783+ </xsd:simpleType>
784+
785+<!-- **************************************************** -->
786+
787+ <xsd:complexType name="display-nameType">
788+ <xsd:annotation>
789+ <xsd:documentation>
790+ <![CDATA[
791+
792+ The display-name type contains a short name that is intended
793+ to be displayed by tools. It is used by display-name
794+ elements. The display name need not be unique.
795+
796+ Example:
797+
798+ ...
799+ <display-name xml:lang="en">Employee Self Service</display-name>
800+
801+ The value of the xml:lang attribute is "en" (English) by default.
802+
803+ ]]>
804+ </xsd:documentation>
805+ </xsd:annotation>
806+ <xsd:simpleContent>
807+ <xsd:extension base="j2ee:string">
808+ <xsd:attribute ref="xml:lang"/>
809+ </xsd:extension>
810+ </xsd:simpleContent>
811+ </xsd:complexType>
812+
813+<!-- **************************************************** -->
814+
815+ <xsd:complexType name="ejb-linkType">
816+ <xsd:annotation>
817+ <xsd:documentation>
818+ <![CDATA[
819+
820+ The ejb-linkType is used by ejb-link
821+ elements in the ejb-ref or ejb-local-ref elements to specify
822+ that an EJB reference is linked to enterprise bean.
823+
824+ The value of the ejb-link element must be the ejb-name of an
825+ enterprise bean in the same ejb-jar file or in another ejb-jar
826+ file in the same J2EE application unit.
827+
828+ Alternatively, the name in the ejb-link element may be
829+ composed of a path name specifying the ejb-jar containing the
830+ referenced enterprise bean with the ejb-name of the target
831+ bean appended and separated from the path name by "#". The
832+ path name is relative to the Deployment File containing
833+ Deployment Component that is referencing the enterprise
834+ bean. This allows multiple enterprise beans with the same
835+ ejb-name to be uniquely identified.
836+
837+ Examples:
838+
839+ <ejb-link>EmployeeRecord</ejb-link>
840+
841+ <ejb-link>../products/product.jar#ProductEJB</ejb-link>
842+
843+ ]]>
844+ </xsd:documentation>
845+ </xsd:annotation>
846+ <xsd:simpleContent>
847+ <xsd:restriction base="j2ee:string"/>
848+ </xsd:simpleContent>
849+ </xsd:complexType>
850+
851+<!-- **************************************************** -->
852+
853+ <xsd:complexType name="ejb-local-refType">
854+ <xsd:annotation>
855+ <xsd:documentation>
856+
857+ The ejb-local-refType is used by ejb-local-ref elements for
858+ the declaration of a reference to an enterprise bean's local
859+ home. The declaration consists of:
860+
861+ - an optional description
862+ - the EJB reference name used in the code of the Deployment
863+ Component that's referencing the enterprise bean
864+ - the expected type of the referenced enterprise bean
865+ - the expected local home and local interfaces of the
866+ referenced enterprise bean
867+ - optional ejb-link information, used to specify the
868+ referenced enterprise bean
869+
870+ </xsd:documentation>
871+ </xsd:annotation>
872+
873+ <xsd:sequence>
874+ <xsd:element name="description"
875+ type="j2ee:descriptionType"
876+ minOccurs="0"
877+ maxOccurs="unbounded"/>
878+ <xsd:element name="ejb-ref-name"
879+ type="j2ee:ejb-ref-nameType"/>
880+ <xsd:element name="ejb-ref-type"
881+ type="j2ee:ejb-ref-typeType"/>
882+ <xsd:element name="local-home"
883+ type="j2ee:local-homeType"/>
884+ <xsd:element name="local"
885+ type="j2ee:localType"/>
886+ <xsd:element name="ejb-link"
887+ type="j2ee:ejb-linkType"
888+ minOccurs="0"/>
889+ </xsd:sequence>
890+ <xsd:attribute name="id" type="xsd:ID"/>
891+ </xsd:complexType>
892+
893+<!-- **************************************************** -->
894+
895+ <xsd:complexType name="ejb-ref-nameType">
896+ <xsd:annotation>
897+ <xsd:documentation>
898+ <![CDATA[
899+
900+ The ejb-ref-name element contains the name of an EJB
901+ reference. The EJB reference is an entry in the
902+ Deployment Component's environment and is relative to the
903+ java:comp/env context. The name must be unique within the
904+ Deployment Component.
905+
906+ It is recommended that name is prefixed with "ejb/".
907+
908+ Example:
909+
910+ <ejb-ref-name>ejb/Payroll</ejb-ref-name>
911+
912+ ]]>
913+ </xsd:documentation>
914+ </xsd:annotation>
915+ <xsd:simpleContent>
916+ <xsd:restriction base="j2ee:jndi-nameType"/>
917+ </xsd:simpleContent>
918+ </xsd:complexType>
919+
920+<!-- **************************************************** -->
921+
922+ <xsd:complexType name="ejb-ref-typeType">
923+ <xsd:annotation>
924+ <xsd:documentation>
925+
926+ The ejb-ref-typeType contains the expected type of the
927+ referenced enterprise bean.
928+
929+ The ejb-ref-type designates a value
930+ that must be one of the following:
931+
932+ Entity
933+ Session
934+
935+ </xsd:documentation>
936+ </xsd:annotation>
937+ <xsd:simpleContent>
938+ <xsd:restriction base="j2ee:string">
939+ <xsd:enumeration value="Entity"/>
940+ <xsd:enumeration value="Session"/>
941+ </xsd:restriction>
942+ </xsd:simpleContent>
943+ </xsd:complexType>
944+
945+<!-- **************************************************** -->
946+
947+ <xsd:complexType name="ejb-refType">
948+ <xsd:annotation>
949+ <xsd:documentation>
950+
951+ The ejb-refType is used by ejb-ref elements for the
952+ declaration of a reference to an enterprise bean's home. The
953+ declaration consists of:
954+
955+ - an optional description
956+ - the EJB reference name used in the code of
957+ the Deployment Component that's referencing the enterprise
958+ bean
959+ - the expected type of the referenced enterprise bean
960+ - the expected home and remote interfaces of the referenced
961+ enterprise bean
962+ - optional ejb-link information, used to specify the
963+ referenced enterprise bean
964+
965+ </xsd:documentation>
966+ </xsd:annotation>
967+
968+ <xsd:sequence>
969+ <xsd:element name="description"
970+ type="j2ee:descriptionType"
971+ minOccurs="0"
972+ maxOccurs="unbounded"/>
973+ <xsd:element name="ejb-ref-name"
974+ type="j2ee:ejb-ref-nameType"/>
975+ <xsd:element name="ejb-ref-type"
976+ type="j2ee:ejb-ref-typeType"/>
977+
978+ <xsd:element name="home"
979+ type="j2ee:homeType"/>
980+ <xsd:element name="remote"
981+ type="j2ee:remoteType"/>
982+ <xsd:element name="ejb-link"
983+ type="j2ee:ejb-linkType"
984+ minOccurs="0"/>
985+ </xsd:sequence>
986+ <xsd:attribute name="id" type="xsd:ID"/>
987+ </xsd:complexType>
988+
989+<!-- **************************************************** -->
990+
991+ <xsd:complexType name="emptyType">
992+ <xsd:annotation>
993+ <xsd:documentation>
994+
995+ This type is used to designate an empty
996+ element when used.
997+
998+ </xsd:documentation>
999+ </xsd:annotation>
1000+ <xsd:attribute name="id" type="xsd:ID"/>
1001+ </xsd:complexType>
1002+
1003+<!-- **************************************************** -->
1004+
1005+ <xsd:complexType name="env-entry-type-valuesType">
1006+ <xsd:annotation>
1007+ <xsd:documentation>
1008+ <![CDATA[
1009+
1010+ This type contains the fully-qualified Java type of the
1011+ environment entry value that is expected by the
1012+ application's code.
1013+
1014+ The following are the legal values of env-entry-type-valuesType:
1015+
1016+ java.lang.Boolean
1017+ java.lang.Byte
1018+ java.lang.Character
1019+ java.lang.String
1020+ java.lang.Short
1021+ java.lang.Integer
1022+ java.lang.Long
1023+ java.lang.Float
1024+ java.lang.Double
1025+
1026+ Example:
1027+
1028+ <env-entry-type>java.lang.Boolean</env-entry-type>
1029+
1030+ ]]>
1031+ </xsd:documentation>
1032+ </xsd:annotation>
1033+ <xsd:simpleContent>
1034+ <xsd:restriction base="j2ee:string">
1035+ <xsd:enumeration value="java.lang.Boolean"/>
1036+ <xsd:enumeration value="java.lang.Byte"/>
1037+ <xsd:enumeration value="java.lang.Character"/>
1038+ <xsd:enumeration value="java.lang.String"/>
1039+ <xsd:enumeration value="java.lang.Short"/>
1040+ <xsd:enumeration value="java.lang.Integer"/>
1041+ <xsd:enumeration value="java.lang.Long"/>
1042+ <xsd:enumeration value="java.lang.Float"/>
1043+ <xsd:enumeration value="java.lang.Double"/>
1044+ </xsd:restriction>
1045+ </xsd:simpleContent>
1046+ </xsd:complexType>
1047+
1048+<!-- **************************************************** -->
1049+
1050+ <xsd:complexType name="env-entryType">
1051+ <xsd:annotation>
1052+ <xsd:documentation>
1053+
1054+ The env-entryType is used to declare an application's
1055+ environment entry. The declaration consists of an optional
1056+ description, the name of the environment entry, and an
1057+ optional value. If a value is not specified, one must be
1058+ supplied during deployment.
1059+
1060+ It is used by env-entry elements.
1061+
1062+ </xsd:documentation>
1063+ </xsd:annotation>
1064+
1065+ <xsd:sequence>
1066+ <xsd:element name="description"
1067+ type="j2ee:descriptionType"
1068+ minOccurs="0"
1069+ maxOccurs="unbounded"/>
1070+ <xsd:element name="env-entry-name"
1071+ type="j2ee:jndi-nameType">
1072+ <xsd:annotation>
1073+ <xsd:documentation>
1074+ <![CDATA[
1075+
1076+ The env-entry-name element contains the name of a
1077+ Deployment Component's environment entry. The name
1078+ is a JNDI name relative to the java:comp/env
1079+ context. The name must be unique within a
1080+ Deployment Component. The uniqueness
1081+ constraints must be defined within the declared
1082+ context.
1083+
1084+ Example:
1085+
1086+ <env-entry-name>minAmount</env-entry-name>
1087+
1088+ ]]>
1089+ </xsd:documentation>
1090+ </xsd:annotation>
1091+ </xsd:element>
1092+
1093+ <xsd:element name="env-entry-type"
1094+ type="j2ee:env-entry-type-valuesType"/>
1095+
1096+ <xsd:element name="env-entry-value"
1097+ type="j2ee:xsdStringType"
1098+ minOccurs="0">
1099+ <xsd:annotation>
1100+ <xsd:documentation>
1101+ <![CDATA[
1102+
1103+ The env-entry-value designates the value of a
1104+ Deployment Component's environment entry. The value
1105+ must be a String that is valid for the
1106+ constructor of the specified type that takes a
1107+ single String parameter, or for java.lang.Character,
1108+ a single character.
1109+
1110+ Example:
1111+
1112+ <env-entry-value>100.00</env-entry-value>
1113+
1114+ ]]>
1115+ </xsd:documentation>
1116+ </xsd:annotation>
1117+ </xsd:element>
1118+
1119+ </xsd:sequence>
1120+ <xsd:attribute name="id" type="xsd:ID"/>
1121+ </xsd:complexType>
1122+
1123+<!-- **************************************************** -->
1124+
1125+ <xsd:complexType name="fully-qualified-classType">
1126+ <xsd:annotation>
1127+ <xsd:documentation>
1128+
1129+ The elements that use this type designate the name of a
1130+ Java class or interface. The name is in the form of a
1131+ "binary name", as defined in the JLS. This is the form
1132+ of name used in Class.forName(). Tools that need the
1133+ canonical name (the name used in source code) will need
1134+ to convert this binary name to the canonical name.
1135+
1136+ </xsd:documentation>
1137+ </xsd:annotation>
1138+ <xsd:simpleContent>
1139+ <xsd:restriction base="j2ee:string"/>
1140+ </xsd:simpleContent>
1141+ </xsd:complexType>
1142+
1143+<!-- **************************************************** -->
1144+
1145+ <xsd:complexType name="generic-booleanType">
1146+ <xsd:annotation>
1147+ <xsd:documentation>
1148+
1149+ This type defines four different values which can designate
1150+ boolean values. This includes values yes and no which are
1151+ not designated by xsd:boolean
1152+
1153+ </xsd:documentation>
1154+ </xsd:annotation>
1155+ <xsd:simpleContent>
1156+ <xsd:restriction base="j2ee:string">
1157+ <xsd:enumeration value="true"/>
1158+ <xsd:enumeration value="false"/>
1159+ <xsd:enumeration value="yes"/>
1160+ <xsd:enumeration value="no"/>
1161+ </xsd:restriction>
1162+ </xsd:simpleContent>
1163+ </xsd:complexType>
1164+
1165+<!-- **************************************************** -->
1166+
1167+ <xsd:complexType name="homeType">
1168+ <xsd:annotation>
1169+ <xsd:documentation>
1170+ <![CDATA[
1171+
1172+ The homeType defines the fully-qualified name of
1173+ an enterprise bean's home interface.
1174+
1175+ Example:
1176+
1177+ <home>com.aardvark.payroll.PayrollHome</home>
1178+
1179+ ]]>
1180+ </xsd:documentation>
1181+ </xsd:annotation>
1182+ <xsd:simpleContent>
1183+ <xsd:restriction base="j2ee:fully-qualified-classType"/>
1184+ </xsd:simpleContent>
1185+ </xsd:complexType>
1186+
1187+<!-- **************************************************** -->
1188+
1189+ <xsd:complexType name="iconType">
1190+ <xsd:annotation>
1191+ <xsd:documentation>
1192+
1193+ The icon type contains small-icon and large-icon elements
1194+ that specify the file names for small and large GIF or
1195+ JPEG icon images used to represent the parent element in a
1196+ GUI tool.
1197+
1198+ The xml:lang attribute defines the language that the
1199+ icon file names are provided in. Its value is "en" (English)
1200+ by default.
1201+
1202+ </xsd:documentation>
1203+ </xsd:annotation>
1204+
1205+ <xsd:sequence>
1206+ <xsd:element name="small-icon" type="j2ee:pathType"
1207+ minOccurs="0">
1208+ <xsd:annotation>
1209+ <xsd:documentation>
1210+ <![CDATA[
1211+
1212+ The small-icon element contains the name of a file
1213+ containing a small (16 x 16) icon image. The file
1214+ name is a relative path within the Deployment
1215+ Component's Deployment File.
1216+
1217+ The image may be either in the JPEG or GIF format.
1218+ The icon can be used by tools.
1219+
1220+ Example:
1221+
1222+ <small-icon>employee-service-icon16x16.jpg</small-icon>
1223+
1224+ ]]>
1225+ </xsd:documentation>
1226+ </xsd:annotation>
1227+ </xsd:element>
1228+ <xsd:element name="large-icon" type="j2ee:pathType"
1229+ minOccurs="0">
1230+ <xsd:annotation>
1231+ <xsd:documentation>
1232+ <![CDATA[
1233+
1234+ The large-icon element contains the name of a file
1235+ containing a large
1236+ (32 x 32) icon image. The file name is a relative
1237+ path within the Deployment Component's Deployment
1238+ File.
1239+
1240+ The image may be either in the JPEG or GIF format.
1241+ The icon can be used by tools.
1242+
1243+ Example:
1244+
1245+ <large-icon>employee-service-icon32x32.jpg</large-icon>
1246+
1247+ ]]>
1248+ </xsd:documentation>
1249+ </xsd:annotation>
1250+ </xsd:element>
1251+
1252+ </xsd:sequence>
1253+
1254+ <xsd:attribute ref="xml:lang"/>
1255+ <xsd:attribute name="id" type="xsd:ID"/>
1256+
1257+ </xsd:complexType>
1258+
1259+<!-- **************************************************** -->
1260+
1261+ <xsd:complexType name="java-identifierType">
1262+ <xsd:annotation>
1263+ <xsd:documentation>
1264+
1265+ The java-identifierType defines a Java identifier.
1266+ The users of this type should further verify that
1267+ the content does not contain Java reserved keywords.
1268+
1269+ </xsd:documentation>
1270+ </xsd:annotation>
1271+ <xsd:simpleContent>
1272+ <xsd:restriction base="j2ee:string">
1273+ <xsd:pattern value="($|_|\p{L})(\p{L}|\p{Nd}|_|$)*"/>
1274+ </xsd:restriction>
1275+ </xsd:simpleContent>
1276+ </xsd:complexType>
1277+
1278+<!-- **************************************************** -->
1279+
1280+ <xsd:complexType name="java-typeType">
1281+ <xsd:annotation>
1282+ <xsd:documentation>
1283+
1284+ This is a generic type that designates a Java primitive
1285+ type or a fully qualified name of a Java interface/type,
1286+ or an array of such types.
1287+
1288+ </xsd:documentation>
1289+ </xsd:annotation>
1290+ <xsd:simpleContent>
1291+ <xsd:restriction base="j2ee:string">
1292+ <xsd:pattern value="[^\p{Z}]*"/>
1293+ </xsd:restriction>
1294+ </xsd:simpleContent>
1295+ </xsd:complexType>
1296+
1297+<!-- **************************************************** -->
1298+
1299+ <xsd:complexType name="jndi-nameType">
1300+ <xsd:annotation>
1301+ <xsd:documentation>
1302+
1303+ The jndi-nameType type designates a JNDI name in the
1304+ Deployment Component's environment and is relative to the
1305+ java:comp/env context. A JNDI name must be unique within the
1306+ Deployment Component.
1307+
1308+ </xsd:documentation>
1309+ </xsd:annotation>
1310+ <xsd:simpleContent>
1311+ <xsd:restriction base="j2ee:string"/>
1312+ </xsd:simpleContent>
1313+ </xsd:complexType>
1314+
1315+<!-- **************************************************** -->
1316+
1317+ <xsd:group name="jndiEnvironmentRefsGroup">
1318+ <xsd:annotation>
1319+ <xsd:documentation>
1320+
1321+ This group keeps the usage of the contained JNDI environment
1322+ reference elements consistent across J2EE deployment descriptors.
1323+
1324+ </xsd:documentation>
1325+ </xsd:annotation>
1326+ <xsd:sequence>
1327+ <xsd:element name="env-entry"
1328+ type="j2ee:env-entryType"
1329+ minOccurs="0" maxOccurs="unbounded"/>
1330+ <xsd:element name="ejb-ref"
1331+ type="j2ee:ejb-refType"
1332+ minOccurs="0" maxOccurs="unbounded"/>
1333+ <xsd:element name="ejb-local-ref"
1334+ type="j2ee:ejb-local-refType"
1335+ minOccurs="0" maxOccurs="unbounded"/>
1336+ <xsd:group ref="j2ee:service-refGroup"/>
1337+ <xsd:element name="resource-ref"
1338+ type="j2ee:resource-refType"
1339+ minOccurs="0" maxOccurs="unbounded"/>
1340+ <xsd:element name="resource-env-ref"
1341+ type="j2ee:resource-env-refType"
1342+ minOccurs="0" maxOccurs="unbounded"/>
1343+ <xsd:element name="message-destination-ref"
1344+ type="j2ee:message-destination-refType"
1345+ minOccurs="0" maxOccurs="unbounded"/>
1346+ </xsd:sequence>
1347+ </xsd:group>
1348+
1349+<!-- **************************************************** -->
1350+
1351+ <xsd:complexType name="listenerType">
1352+ <xsd:annotation>
1353+ <xsd:documentation>
1354+
1355+ The listenerType indicates the deployment properties for a web
1356+ application listener bean.
1357+
1358+ </xsd:documentation>
1359+ </xsd:annotation>
1360+
1361+ <xsd:sequence>
1362+ <xsd:group ref="j2ee:descriptionGroup"/>
1363+ <xsd:element name="listener-class"
1364+ type="j2ee:fully-qualified-classType">
1365+ <xsd:annotation>
1366+ <xsd:documentation>
1367+
1368+ The listener-class element declares a class in the
1369+ application must be registered as a web
1370+ application listener bean. The value is the fully
1371+ qualified classname of the listener class.
1372+
1373+ </xsd:documentation>
1374+ </xsd:annotation>
1375+ </xsd:element>
1376+ </xsd:sequence>
1377+ <xsd:attribute name="id" type="xsd:ID"/>
1378+ </xsd:complexType>
1379+
1380+<!-- **************************************************** -->
1381+
1382+ <xsd:complexType name="local-homeType">
1383+ <xsd:annotation>
1384+ <xsd:documentation>
1385+
1386+ The local-homeType defines the fully-qualified
1387+ name of an enterprise bean's local home interface.
1388+
1389+ </xsd:documentation>
1390+ </xsd:annotation>
1391+ <xsd:simpleContent>
1392+ <xsd:restriction base="j2ee:fully-qualified-classType"/>
1393+ </xsd:simpleContent>
1394+ </xsd:complexType>
1395+
1396+<!-- **************************************************** -->
1397+
1398+ <xsd:complexType name="localType">
1399+ <xsd:annotation>
1400+ <xsd:documentation>
1401+
1402+ The localType defines the fully-qualified name of an
1403+ enterprise bean's local interface.
1404+
1405+ </xsd:documentation>
1406+ </xsd:annotation>
1407+ <xsd:simpleContent>
1408+ <xsd:restriction base="j2ee:fully-qualified-classType"/>
1409+ </xsd:simpleContent>
1410+ </xsd:complexType>
1411+
1412+<!-- **************************************************** -->
1413+
1414+ <xsd:complexType name="message-destination-linkType">
1415+ <xsd:annotation>
1416+ <xsd:documentation>
1417+
1418+ The message-destination-linkType is used to link a message
1419+ destination reference or message-driven bean to a message
1420+ destination.
1421+
1422+ The Assembler sets the value to reflect the flow of messages
1423+ between producers and consumers in the application.
1424+
1425+ The value must be the message-destination-name of a message
1426+ destination in the same Deployment File or in another
1427+ Deployment File in the same J2EE application unit.
1428+
1429+ Alternatively, the value may be composed of a path name
1430+ specifying a Deployment File containing the referenced
1431+ message destination with the message-destination-name of the
1432+ destination appended and separated from the path name by
1433+ "#". The path name is relative to the Deployment File
1434+ containing Deployment Component that is referencing the
1435+ message destination. This allows multiple message
1436+ destinations with the same name to be uniquely identified.
1437+
1438+ </xsd:documentation>
1439+ </xsd:annotation>
1440+ <xsd:simpleContent>
1441+ <xsd:restriction base="j2ee:string"/>
1442+ </xsd:simpleContent>
1443+ </xsd:complexType>
1444+
1445+<!-- **************************************************** -->
1446+
1447+ <xsd:complexType name="message-destination-refType">
1448+ <xsd:annotation>
1449+ <xsd:documentation>
1450+ <![CDATA[
1451+
1452+ The message-destination-ref element contains a declaration
1453+ of Deployment Component's reference to a message destination
1454+ associated with a resource in Deployment Component's
1455+ environment. It consists of:
1456+
1457+ - an optional description
1458+ - the message destination reference name
1459+ - the message destination type
1460+ - a specification as to whether the
1461+ destination is used for
1462+ consuming or producing messages, or both
1463+ - a link to the message destination
1464+
1465+ Examples:
1466+
1467+ <message-destination-ref>
1468+ <message-destination-ref-name>jms/StockQueue
1469+ </message-destination-ref-name>
1470+ <message-destination-type>javax.jms.Queue
1471+ </message-destination-type>
1472+ <message-destination-usage>Consumes
1473+ </message-destination-usage>
1474+ <message-destination-link>CorporateStocks
1475+ </message-destination-link>
1476+ </message-destination-ref>
1477+
1478+ ]]>
1479+ </xsd:documentation>
1480+ </xsd:annotation>
1481+ <xsd:sequence>
1482+ <xsd:element name="description"
1483+ type="j2ee:descriptionType"
1484+ minOccurs="0"
1485+ maxOccurs="unbounded"/>
1486+ <xsd:element name="message-destination-ref-name"
1487+ type="j2ee:jndi-nameType">
1488+ <xsd:annotation>
1489+ <xsd:documentation>
1490+
1491+ The message-destination-ref-name element specifies
1492+ the name of a message destination reference; its
1493+ value is the environment entry name used in
1494+ Deployment Component code. The name is a JNDI name
1495+ relative to the java:comp/env context and must be
1496+ unique within an ejb-jar (for enterprise beans) or a
1497+ Deployment File (for others).
1498+
1499+ </xsd:documentation>
1500+ </xsd:annotation>
1501+ </xsd:element>
1502+ <xsd:element name="message-destination-type"
1503+ type="j2ee:message-destination-typeType"/>
1504+ <xsd:element name="message-destination-usage"
1505+ type="j2ee:message-destination-usageType"/>
1506+ <xsd:element name="message-destination-link"
1507+ type="j2ee:message-destination-linkType"
1508+ minOccurs="0"/>
1509+ </xsd:sequence>
1510+ <xsd:attribute name="id" type="xsd:ID"/>
1511+
1512+ </xsd:complexType>
1513+
1514+<!-- **************************************************** -->
1515+
1516+ <xsd:complexType name="message-destination-typeType">
1517+ <xsd:annotation>
1518+ <xsd:documentation>
1519+ <![CDATA[
1520+
1521+ The message-destination-typeType specifies the type of
1522+ the destination. The type is specified by the Java interface
1523+ expected to be implemented by the destination.
1524+
1525+ Example:
1526+
1527+ <message-destination-type>javax.jms.Queue
1528+ </message-destination-type>
1529+
1530+ ]]>
1531+ </xsd:documentation>
1532+ </xsd:annotation>
1533+ <xsd:simpleContent>
1534+ <xsd:restriction base="j2ee:fully-qualified-classType"/>
1535+ </xsd:simpleContent>
1536+ </xsd:complexType>
1537+
1538+<!-- **************************************************** -->
1539+
1540+ <xsd:complexType name="message-destination-usageType">
1541+ <xsd:annotation>
1542+ <xsd:documentation>
1543+
1544+ The message-destination-usageType specifies the use of the
1545+ message destination indicated by the reference. The value
1546+ indicates whether messages are consumed from the message
1547+ destination, produced for the destination, or both. The
1548+ Assembler makes use of this information in linking producers
1549+ of a destination with its consumers.
1550+
1551+ The value of the message-destination-usage element must be
1552+ one of the following:
1553+ Consumes
1554+ Produces
1555+ ConsumesProduces
1556+
1557+ </xsd:documentation>
1558+ </xsd:annotation>
1559+ <xsd:simpleContent>
1560+ <xsd:restriction base="j2ee:string">
1561+ <xsd:enumeration value="Consumes"/>
1562+ <xsd:enumeration value="Produces"/>
1563+ <xsd:enumeration value="ConsumesProduces"/>
1564+ </xsd:restriction>
1565+ </xsd:simpleContent>
1566+ </xsd:complexType>
1567+
1568+<!-- **************************************************** -->
1569+
1570+ <xsd:complexType name="message-destinationType">
1571+ <xsd:annotation>
1572+ <xsd:documentation>
1573+ <![CDATA[
1574+
1575+ The message-destinationType specifies a message
1576+ destination. The logical destination described by this
1577+ element is mapped to a physical destination by the Deployer.
1578+
1579+ The message destination element contains:
1580+
1581+ - an optional description
1582+ - an optional display-name
1583+ - an optional icon
1584+ - a message destination name which must be unique
1585+ among message destination names within the same
1586+ Deployment File.
1587+
1588+ Example:
1589+
1590+ <message-destination>
1591+ <message-destination-name>CorporateStocks
1592+ </message-destination-name>
1593+ </message-destination>
1594+
1595+ ]]>
1596+ </xsd:documentation>
1597+ </xsd:annotation>
1598+ <xsd:sequence>
1599+ <xsd:group ref="j2ee:descriptionGroup"/>
1600+ <xsd:element name="message-destination-name"
1601+ type="j2ee:string">
1602+ <xsd:annotation>
1603+ <xsd:documentation>
1604+
1605+ The message-destination-name element specifies a
1606+ name for a message destination. This name must be
1607+ unique among the names of message destinations
1608+ within the Deployment File.
1609+
1610+ </xsd:documentation>
1611+ </xsd:annotation>
1612+ </xsd:element>
1613+ </xsd:sequence>
1614+ <xsd:attribute name="id" type="xsd:ID"/>
1615+ </xsd:complexType>
1616+
1617+<!-- **************************************************** -->
1618+
1619+ <xsd:complexType name="param-valueType">
1620+ <xsd:annotation>
1621+ <xsd:documentation>
1622+
1623+ This type is a general type that can be used to declare
1624+ parameter/value lists.
1625+
1626+ </xsd:documentation>
1627+ </xsd:annotation>
1628+
1629+ <xsd:sequence>
1630+ <xsd:element name="description"
1631+ type="j2ee:descriptionType"
1632+ minOccurs="0"
1633+ maxOccurs="unbounded"/>
1634+ <xsd:element name="param-name"
1635+ type="j2ee:string">
1636+ <xsd:annotation>
1637+ <xsd:documentation>
1638+
1639+ The param-name element contains the name of a
1640+ parameter.
1641+
1642+ </xsd:documentation>
1643+ </xsd:annotation>
1644+ </xsd:element>
1645+
1646+ <xsd:element name="param-value"
1647+ type="j2ee:xsdStringType">
1648+ <xsd:annotation>
1649+ <xsd:documentation>
1650+
1651+ The param-value element contains the value of a
1652+ parameter.
1653+
1654+ </xsd:documentation>
1655+ </xsd:annotation>
1656+ </xsd:element>
1657+ </xsd:sequence>
1658+ <xsd:attribute name="id" type="xsd:ID"/>
1659+ </xsd:complexType>
1660+
1661+<!-- **************************************************** -->
1662+
1663+ <xsd:complexType name="pathType">
1664+ <xsd:annotation>
1665+ <xsd:documentation>
1666+
1667+ The elements that use this type designate either a relative
1668+ path or an absolute path starting with a "/".
1669+
1670+ In elements that specify a pathname to a file within the
1671+ same Deployment File, relative filenames (i.e., those not
1672+ starting with "/") are considered relative to the root of
1673+ the Deployment File's namespace. Absolute filenames (i.e.,
1674+ those starting with "/") also specify names in the root of
1675+ the Deployment File's namespace. In general, relative names
1676+ are preferred. The exception is .war files where absolute
1677+ names are preferred for consistency with the Servlet API.
1678+
1679+ </xsd:documentation>
1680+ </xsd:annotation>
1681+ <xsd:simpleContent>
1682+ <xsd:restriction base="j2ee:string"/>
1683+ </xsd:simpleContent>
1684+ </xsd:complexType>
1685+
1686+<!-- **************************************************** -->
1687+
1688+ <xsd:complexType name="remoteType">
1689+ <xsd:annotation>
1690+ <xsd:documentation>
1691+ <![CDATA[
1692+
1693+ The remote element contains the fully-qualified name
1694+ of the enterprise bean's remote interface.
1695+
1696+ Example:
1697+
1698+ <remote>com.wombat.empl.EmployeeService</remote>
1699+
1700+ ]]>
1701+ </xsd:documentation>
1702+ </xsd:annotation>
1703+ <xsd:simpleContent>
1704+ <xsd:restriction base="j2ee:fully-qualified-classType"/>
1705+ </xsd:simpleContent>
1706+ </xsd:complexType>
1707+
1708+<!-- **************************************************** -->
1709+
1710+ <xsd:complexType name="res-authType">
1711+ <xsd:annotation>
1712+ <xsd:documentation>
1713+
1714+ The res-authType specifies whether the Deployment Component
1715+ code signs on programmatically to the resource manager, or
1716+ whether the Container will sign on to the resource manager
1717+ on behalf of the Deployment Component. In the latter case,
1718+ the Container uses information that is supplied by the
1719+ Deployer.
1720+
1721+ The value must be one of the two following:
1722+
1723+ Application
1724+ Container
1725+
1726+ </xsd:documentation>
1727+ </xsd:annotation>
1728+ <xsd:simpleContent>
1729+ <xsd:restriction base="j2ee:string">
1730+ <xsd:enumeration value="Application"/>
1731+ <xsd:enumeration value="Container"/>
1732+ </xsd:restriction>
1733+ </xsd:simpleContent>
1734+ </xsd:complexType>
1735+
1736+<!-- **************************************************** -->
1737+
1738+ <xsd:complexType name="res-sharing-scopeType">
1739+ <xsd:annotation>
1740+ <xsd:documentation>
1741+
1742+ The res-sharing-scope type specifies whether connections
1743+ obtained through the given resource manager connection
1744+ factory reference can be shared. The value, if specified,
1745+ must be one of the two following:
1746+
1747+ Shareable
1748+ Unshareable
1749+
1750+ The default value is Shareable.
1751+
1752+ </xsd:documentation>
1753+ </xsd:annotation>
1754+ <xsd:simpleContent>
1755+ <xsd:restriction base="j2ee:string">
1756+ <xsd:enumeration value="Shareable"/>
1757+ <xsd:enumeration value="Unshareable"/>
1758+ </xsd:restriction>
1759+ </xsd:simpleContent>
1760+ </xsd:complexType>
1761+
1762+<!-- **************************************************** -->
1763+
1764+ <xsd:complexType name="resource-env-refType">
1765+ <xsd:annotation>
1766+ <xsd:documentation>
1767+ <![CDATA[
1768+
1769+ The resource-env-refType is used to define
1770+ resource-env-type elements. It contains a declaration of a
1771+ Deployment Component's reference to an administered object
1772+ associated with a resource in the Deployment Component's
1773+ environment. It consists of an optional description, the
1774+ resource environment reference name, and an indication of
1775+ the resource environment reference type expected by the
1776+ Deployment Component code.
1777+
1778+ Example:
1779+
1780+ <resource-env-ref>
1781+ <resource-env-ref-name>jms/StockQueue
1782+ </resource-env-ref-name>
1783+ <resource-env-ref-type>javax.jms.Queue
1784+ </resource-env-ref-type>
1785+ </resource-env-ref>
1786+
1787+ ]]>
1788+ </xsd:documentation>
1789+ </xsd:annotation>
1790+
1791+ <xsd:sequence>
1792+ <xsd:element name="description"
1793+ type="j2ee:descriptionType"
1794+ minOccurs="0"
1795+ maxOccurs="unbounded"/>
1796+ <xsd:element name="resource-env-ref-name"
1797+ type="j2ee:jndi-nameType">
1798+ <xsd:annotation>
1799+ <xsd:documentation>
1800+
1801+ The resource-env-ref-name element specifies the name
1802+ of a resource environment reference; its value is
1803+ the environment entry name used in
1804+ the Deployment Component code. The name is a JNDI
1805+ name relative to the java:comp/env context and must
1806+ be unique within a Deployment Component.
1807+
1808+ </xsd:documentation>
1809+ </xsd:annotation>
1810+ </xsd:element>
1811+
1812+ <xsd:element name="resource-env-ref-type"
1813+ type="j2ee:fully-qualified-classType">
1814+ <xsd:annotation>
1815+ <xsd:documentation>
1816+
1817+ The resource-env-ref-type element specifies the type
1818+ of a resource environment reference. It is the
1819+ fully qualified name of a Java language class or
1820+ interface.
1821+
1822+ </xsd:documentation>
1823+ </xsd:annotation>
1824+ </xsd:element>
1825+
1826+ </xsd:sequence>
1827+ <xsd:attribute name="id" type="xsd:ID"/>
1828+ </xsd:complexType>
1829+
1830+<!-- **************************************************** -->
1831+
1832+ <xsd:complexType name="resource-refType">
1833+ <xsd:annotation>
1834+ <xsd:documentation>
1835+ <![CDATA[
1836+
1837+ The resource-refType contains a declaration of a
1838+ Deployment Component's reference to an external resource. It
1839+ consists of an optional description, the resource manager
1840+ connection factory reference name, the indication of the
1841+ resource manager connection factory type expected by the
1842+ Deployment Component code, the type of authentication
1843+ (Application or Container), and an optional specification of
1844+ the shareability of connections obtained from the resource
1845+ (Shareable or Unshareable).
1846+
1847+ Example:
1848+
1849+ <resource-ref>
1850+ <res-ref-name>jdbc/EmployeeAppDB</res-ref-name>
1851+ <res-type>javax.sql.DataSource</res-type>
1852+ <res-auth>Container</res-auth>
1853+ <res-sharing-scope>Shareable</res-sharing-scope>
1854+ </resource-ref>
1855+
1856+ ]]>
1857+ </xsd:documentation>
1858+ </xsd:annotation>
1859+
1860+ <xsd:sequence>
1861+ <xsd:element name="description"
1862+ type="j2ee:descriptionType"
1863+ minOccurs="0"
1864+ maxOccurs="unbounded"/>
1865+ <xsd:element name="res-ref-name"
1866+ type="j2ee:jndi-nameType">
1867+ <xsd:annotation>
1868+ <xsd:documentation>
1869+
1870+ The res-ref-name element specifies the name of a
1871+ resource manager connection factory reference.
1872+ The name is a JNDI name relative to the
1873+ java:comp/env context.
1874+ The name must be unique within a Deployment File.
1875+
1876+ </xsd:documentation>
1877+ </xsd:annotation>
1878+ </xsd:element>
1879+
1880+ <xsd:element name="res-type"
1881+ type="j2ee:fully-qualified-classType">
1882+ <xsd:annotation>
1883+ <xsd:documentation>
1884+
1885+ The res-type element specifies the type of the data
1886+ source. The type is specified by the fully qualified
1887+ Java language class or interface
1888+ expected to be implemented by the data source.
1889+
1890+ </xsd:documentation>
1891+ </xsd:annotation>
1892+ </xsd:element>
1893+
1894+ <xsd:element name="res-auth"
1895+ type="j2ee:res-authType"/>
1896+
1897+ <xsd:element name="res-sharing-scope"
1898+ type="j2ee:res-sharing-scopeType"
1899+ minOccurs="0"/>
1900+ </xsd:sequence>
1901+ <xsd:attribute name="id" type="xsd:ID"/>
1902+ </xsd:complexType>
1903+
1904+<!-- **************************************************** -->
1905+
1906+ <xsd:complexType name="role-nameType">
1907+ <xsd:annotation>
1908+ <xsd:documentation>
1909+
1910+ The role-nameType designates the name of a security role.
1911+
1912+ The name must conform to the lexical rules for a token.
1913+
1914+ </xsd:documentation>
1915+ </xsd:annotation>
1916+
1917+ <xsd:simpleContent>
1918+ <xsd:restriction base="j2ee:string"/>
1919+ </xsd:simpleContent>
1920+ </xsd:complexType>
1921+
1922+<!-- **************************************************** -->
1923+
1924+ <xsd:complexType name="run-asType">
1925+ <xsd:annotation>
1926+ <xsd:documentation>
1927+
1928+ The run-asType specifies the run-as identity to be
1929+ used for the execution of a component. It contains an
1930+ optional description, and the name of a security role.
1931+
1932+ </xsd:documentation>
1933+ </xsd:annotation>
1934+
1935+ <xsd:sequence>
1936+ <xsd:element name="description"
1937+ type="j2ee:descriptionType"
1938+ minOccurs="0"
1939+ maxOccurs="unbounded"/>
1940+ <xsd:element name="role-name"
1941+ type="j2ee:role-nameType"/>
1942+ </xsd:sequence>
1943+ <xsd:attribute name="id" type="xsd:ID"/>
1944+ </xsd:complexType>
1945+
1946+<!-- **************************************************** -->
1947+
1948+ <xsd:complexType name="security-role-refType">
1949+ <xsd:annotation>
1950+ <xsd:documentation>
1951+
1952+ The security-role-refType contains the declaration of a
1953+ security role reference in a component's or a
1954+ Deployment Component's code. The declaration consists of an
1955+ optional description, the security role name used in the
1956+ code, and an optional link to a security role. If the
1957+ security role is not specified, the Deployer must choose an
1958+ appropriate security role.
1959+
1960+ </xsd:documentation>
1961+ </xsd:annotation>
1962+
1963+ <xsd:sequence>
1964+ <xsd:element name="description"
1965+ type="j2ee:descriptionType"
1966+ minOccurs="0"
1967+ maxOccurs="unbounded"/>
1968+ <xsd:element name="role-name"
1969+ type="j2ee:role-nameType">
1970+ <xsd:annotation>
1971+ <xsd:documentation>
1972+
1973+ The value of the role-name element must be the String used
1974+ as the parameter to the
1975+ EJBContext.isCallerInRole(String roleName) method or the
1976+ HttpServletRequest.isUserInRole(String role) method.
1977+
1978+ </xsd:documentation>
1979+ </xsd:annotation>
1980+ </xsd:element>
1981+
1982+ <xsd:element name="role-link"
1983+ type="j2ee:role-nameType"
1984+ minOccurs="0">
1985+ <xsd:annotation>
1986+ <xsd:documentation>
1987+
1988+ The role-link element is a reference to a defined
1989+ security role. The role-link element must contain
1990+ the name of one of the security roles defined in the
1991+ security-role elements.
1992+
1993+ </xsd:documentation>
1994+ </xsd:annotation>
1995+ </xsd:element>
1996+ </xsd:sequence>
1997+ <xsd:attribute name="id" type="xsd:ID"/>
1998+ </xsd:complexType>
1999+
2000+<!-- **************************************************** -->
2001+
2002+ <xsd:complexType name="security-roleType">
2003+ <xsd:annotation>
2004+ <xsd:documentation>
2005+ <![CDATA[
2006+
2007+ The security-roleType contains the definition of a security
2008+ role. The definition consists of an optional description of the
2009+ security role, and the security role name.
2010+
2011+ Example:
2012+
2013+ <security-role>
2014+ <description>
2015+ This role includes all employees who are authorized
2016+ to access the employee service application.
2017+ </description>
2018+ <role-name>employee</role-name>
2019+ </security-role>
2020+
2021+ ]]>
2022+ </xsd:documentation>
2023+ </xsd:annotation>
2024+
2025+ <xsd:sequence>
2026+ <xsd:element name="description"
2027+ type="j2ee:descriptionType"
2028+ minOccurs="0"
2029+ maxOccurs="unbounded"/>
2030+ <xsd:element name="role-name"
2031+ type="j2ee:role-nameType"/>
2032+ </xsd:sequence>
2033+ <xsd:attribute name="id" type="xsd:ID"/>
2034+ </xsd:complexType>
2035+
2036+<!-- **************************************************** -->
2037+
2038+ <xsd:complexType name="string">
2039+ <xsd:annotation>
2040+ <xsd:documentation>
2041+
2042+ This is a special string datatype that is defined by J2EE as
2043+ a base type for defining collapsed strings. When schemas
2044+ require trailing/leading space elimination as well as
2045+ collapsing the existing whitespace, this base type may be
2046+ used.
2047+
2048+ </xsd:documentation>
2049+ </xsd:annotation>
2050+ <xsd:simpleContent>
2051+ <xsd:extension base="xsd:token">
2052+ <xsd:attribute name="id" type="xsd:ID"/>
2053+ </xsd:extension>
2054+ </xsd:simpleContent>
2055+ </xsd:complexType>
2056+
2057+<!-- **************************************************** -->
2058+
2059+ <xsd:complexType name="true-falseType">
2060+ <xsd:annotation>
2061+ <xsd:documentation>
2062+
2063+ This simple type designates a boolean with only two
2064+ permissible values
2065+
2066+ - true
2067+ - false
2068+
2069+ </xsd:documentation>
2070+ </xsd:annotation>
2071+ <xsd:simpleContent>
2072+ <xsd:restriction base="j2ee:xsdBooleanType">
2073+ <xsd:pattern value="(true|false)"/>
2074+ </xsd:restriction>
2075+ </xsd:simpleContent>
2076+ </xsd:complexType>
2077+
2078+<!-- **************************************************** -->
2079+
2080+ <xsd:complexType name="url-patternType">
2081+ <xsd:annotation>
2082+ <xsd:documentation>
2083+
2084+ The url-patternType contains the url pattern of the mapping.
2085+ It must follow the rules specified in Section 11.2 of the
2086+ Servlet API Specification. This pattern is assumed to be in
2087+ URL-decoded form and must not contain CR(#xD) or LF(#xA).
2088+ If it contains those characters, the container must inform
2089+ the developer with a descriptive error message.
2090+ The container must preserve all characters including whitespaces.
2091+
2092+ </xsd:documentation>
2093+ </xsd:annotation>
2094+ <xsd:simpleContent>
2095+ <xsd:extension base="xsd:string"/>
2096+ </xsd:simpleContent>
2097+ </xsd:complexType>
2098+
2099+<!-- **************************************************** -->
2100+
2101+ <xsd:complexType name="xsdAnyURIType">
2102+ <xsd:annotation>
2103+ <xsd:documentation>
2104+
2105+ This type adds an "id" attribute to xsd:anyURI.
2106+
2107+ </xsd:documentation>
2108+ </xsd:annotation>
2109+ <xsd:simpleContent>
2110+ <xsd:extension base="xsd:anyURI">
2111+ <xsd:attribute name="id" type="xsd:ID"/>
2112+ </xsd:extension>
2113+ </xsd:simpleContent>
2114+ </xsd:complexType>
2115+
2116+<!-- **************************************************** -->
2117+
2118+ <xsd:complexType name="xsdBooleanType">
2119+ <xsd:annotation>
2120+ <xsd:documentation>
2121+
2122+ This type adds an "id" attribute to xsd:boolean.
2123+
2124+ </xsd:documentation>
2125+ </xsd:annotation>
2126+ <xsd:simpleContent>
2127+ <xsd:extension base="xsd:boolean">
2128+ <xsd:attribute name="id" type="xsd:ID"/>
2129+ </xsd:extension>
2130+ </xsd:simpleContent>
2131+ </xsd:complexType>
2132+
2133+<!-- **************************************************** -->
2134+
2135+ <xsd:complexType name="xsdIntegerType">
2136+ <xsd:annotation>
2137+ <xsd:documentation>
2138+
2139+ This type adds an "id" attribute to xsd:integer.
2140+
2141+ </xsd:documentation>
2142+ </xsd:annotation>
2143+ <xsd:simpleContent>
2144+ <xsd:extension base="xsd:integer">
2145+ <xsd:attribute name="id" type="xsd:ID"/>
2146+ </xsd:extension>
2147+ </xsd:simpleContent>
2148+ </xsd:complexType>
2149+
2150+<!-- **************************************************** -->
2151+
2152+ <xsd:complexType name="xsdNMTOKENType">
2153+ <xsd:annotation>
2154+ <xsd:documentation>
2155+
2156+ This type adds an "id" attribute to xsd:NMTOKEN.
2157+
2158+ </xsd:documentation>
2159+ </xsd:annotation>
2160+ <xsd:simpleContent>
2161+ <xsd:extension base="xsd:NMTOKEN">
2162+ <xsd:attribute name="id" type="xsd:ID"/>
2163+ </xsd:extension>
2164+ </xsd:simpleContent>
2165+ </xsd:complexType>
2166+
2167+<!-- **************************************************** -->
2168+
2169+ <xsd:complexType name="xsdNonNegativeIntegerType">
2170+ <xsd:annotation>
2171+ <xsd:documentation>
2172+
2173+ This type adds an "id" attribute to xsd:nonNegativeInteger.
2174+
2175+ </xsd:documentation>
2176+ </xsd:annotation>
2177+ <xsd:simpleContent>
2178+ <xsd:extension base="xsd:nonNegativeInteger">
2179+ <xsd:attribute name="id" type="xsd:ID"/>
2180+ </xsd:extension>
2181+ </xsd:simpleContent>
2182+ </xsd:complexType>
2183+
2184+<!-- **************************************************** -->
2185+
2186+ <xsd:complexType name="xsdPositiveIntegerType">
2187+ <xsd:annotation>
2188+ <xsd:documentation>
2189+
2190+ This type adds an "id" attribute to xsd:positiveInteger.
2191+
2192+ </xsd:documentation>
2193+ </xsd:annotation>
2194+ <xsd:simpleContent>
2195+ <xsd:extension base="xsd:positiveInteger">
2196+ <xsd:attribute name="id" type="xsd:ID"/>
2197+ </xsd:extension>
2198+ </xsd:simpleContent>
2199+ </xsd:complexType>
2200+
2201+<!-- **************************************************** -->
2202+
2203+ <xsd:complexType name="xsdQNameType">
2204+ <xsd:annotation>
2205+ <xsd:documentation>
2206+
2207+ This type adds an "id" attribute to xsd:QName.
2208+
2209+ </xsd:documentation>
2210+ </xsd:annotation>
2211+ <xsd:simpleContent>
2212+ <xsd:extension base="xsd:QName">
2213+ <xsd:attribute name="id" type="xsd:ID"/>
2214+ </xsd:extension>
2215+ </xsd:simpleContent>
2216+ </xsd:complexType>
2217+
2218+<!-- **************************************************** -->
2219+
2220+ <xsd:complexType name="xsdStringType">
2221+ <xsd:annotation>
2222+ <xsd:documentation>
2223+
2224+ This type adds an "id" attribute to xsd:string.
2225+
2226+ </xsd:documentation>
2227+ </xsd:annotation>
2228+ <xsd:simpleContent>
2229+ <xsd:extension base="xsd:string">
2230+ <xsd:attribute name="id" type="xsd:ID"/>
2231+ </xsd:extension>
2232+ </xsd:simpleContent>
2233+ </xsd:complexType>
2234+
2235+</xsd:schema>
2236+
2237Index: jenkins-winstone/src/conf/javax/servlet/resources/j2ee_web_services_client_1_1.xsd
2238===================================================================
2239--- /dev/null 1970-01-01 00:00:00.000000000 +0000
2240+++ jenkins-winstone/src/conf/javax/servlet/resources/j2ee_web_services_client_1_1.xsd 2011-08-18 09:34:14.231604192 +0100
2241@@ -0,0 +1,353 @@
2242+<?xml version="1.0" encoding="UTF-8"?>
2243+<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
2244+ targetNamespace="http://java.sun.com/xml/ns/j2ee"
2245+ xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
2246+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
2247+ elementFormDefault="qualified"
2248+ attributeFormDefault="unqualified"
2249+ version="1.1">
2250+ <xsd:annotation>
2251+ <xsd:documentation>
2252+ @(#)j2ee_web_services_client_1_1.xsds 1.10 02/11/03
2253+ </xsd:documentation>
2254+ </xsd:annotation>
2255+
2256+ <xsd:annotation>
2257+ <xsd:documentation>
2258+
2259+ DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
2260+
2261+ Copyright 2003-2007 Sun Microsystems, Inc. All rights reserved.
2262+
2263+ The contents of this file are subject to the terms of either the
2264+ GNU General Public License Version 2 only ("GPL") or the Common
2265+ Development and Distribution License("CDDL") (collectively, the
2266+ "License"). You may not use this file except in compliance with
2267+ the License. You can obtain a copy of the License at
2268+ https://glassfish.dev.java.net/public/CDDL+GPL.html or
2269+ glassfish/bootstrap/legal/LICENSE.txt. See the License for the
2270+ specific language governing permissions and limitations under the
2271+ License.
2272+
2273+ When distributing the software, include this License Header
2274+ Notice in each file and include the License file at
2275+ glassfish/bootstrap/legal/LICENSE.txt. Sun designates this
2276+ particular file as subject to the "Classpath" exception as
2277+ provided by Sun in the GPL Version 2 section of the License file
2278+ that accompanied this code. If applicable, add the following
2279+ below the License Header, with the fields enclosed by brackets []
2280+ replaced by your own identifying information:
2281+ "Portions Copyrighted [year] [name of copyright owner]"
2282+
2283+ Contributor(s):
2284+
2285+ If you wish your version of this file to be governed by only the
2286+ CDDL or only the GPL Version 2, indicate your decision by adding
2287+ "[Contributor] elects to include this software in this
2288+ distribution under the [CDDL or GPL Version 2] license." If you
2289+ don't indicate a single choice of license, a recipient has the
2290+ option to distribute your version of this file under either the
2291+ CDDL, the GPL Version 2 or to extend the choice of license to its
2292+ licensees as provided above. However, if you add GPL Version 2
2293+ code and therefore, elected the GPL Version 2 license, then the
2294+ option applies only if the new code is made subject to such
2295+ option by the copyright holder.
2296+
2297+ </xsd:documentation>
2298+ </xsd:annotation>
2299+
2300+ <xsd:annotation>
2301+ <xsd:documentation>
2302+
2303+ (C) Copyright International Business Machines Corporation 2002
2304+
2305+ </xsd:documentation>
2306+ </xsd:annotation>
2307+
2308+
2309+<!-- **************************************************** -->
2310+
2311+ <xsd:complexType name="port-component-refType">
2312+ <xsd:annotation>
2313+ <xsd:documentation>
2314+
2315+ The port-component-ref element declares a client dependency
2316+ on the container for resolving a Service Endpoint Interface
2317+ to a WSDL port. It optionally associates the Service Endpoint
2318+ Interface with a particular port-component. This is only used
2319+ by the container for a Service.getPort(Class) method call.
2320+
2321+ </xsd:documentation>
2322+ </xsd:annotation>
2323+
2324+ <xsd:sequence>
2325+ <xsd:element name="service-endpoint-interface"
2326+ type="j2ee:fully-qualified-classType">
2327+ <xsd:annotation>
2328+ <xsd:documentation>
2329+
2330+ The service-endpoint-interface element defines a fully qualified
2331+ Java class that represents the Service Endpoint Interface of a
2332+ WSDL port.
2333+
2334+ </xsd:documentation>
2335+ </xsd:annotation>
2336+ </xsd:element>
2337+
2338+ <xsd:element name="port-component-link"
2339+ type="j2ee:string"
2340+ minOccurs="0" maxOccurs="1">
2341+ <xsd:annotation>
2342+ <xsd:documentation>
2343+
2344+ The port-component-link element links a port-component-ref
2345+ to a specific port-component required to be made available
2346+ by a service reference.
2347+
2348+ The value of a port-component-link must be the
2349+ port-component-name of a port-component in the same module
2350+ or another module in the same application unit. The syntax
2351+ for specification follows the syntax defined for ejb-link
2352+ in the EJB 2.0 specification.
2353+
2354+ </xsd:documentation>
2355+ </xsd:annotation>
2356+ </xsd:element>
2357+ </xsd:sequence>
2358+ <xsd:attribute name="id" type="xsd:ID"/>
2359+ </xsd:complexType>
2360+
2361+<!-- **************************************************** -->
2362+
2363+ <xsd:group name="service-refGroup">
2364+ <xsd:sequence>
2365+ <xsd:element name="service-ref"
2366+ type="j2ee:service-refType"
2367+ minOccurs="0" maxOccurs="unbounded">
2368+ <xsd:key name="service-ref_handler-name-key">
2369+ <xsd:annotation>
2370+ <xsd:documentation>
2371+
2372+ Defines the name of the handler. The name must be unique
2373+ within the module.
2374+
2375+ </xsd:documentation>
2376+ </xsd:annotation>
2377+ <xsd:selector xpath="j2ee:handler"/>
2378+ <xsd:field xpath="j2ee:handler-name"/>
2379+ </xsd:key>
2380+ </xsd:element>
2381+ </xsd:sequence>
2382+ </xsd:group>
2383+
2384+<!-- **************************************************** -->
2385+
2386+ <xsd:complexType name="service-refType">
2387+ <xsd:annotation>
2388+ <xsd:documentation>
2389+
2390+ The service-ref element declares a reference to a Web
2391+ service. It contains optional description, display name and
2392+ icons, a declaration of the required Service interface,
2393+ an optional WSDL document location, an optional set
2394+ of JAX-RPC mappings, an optional QName for the service element,
2395+ an optional set of Service Endpoint Interfaces to be resolved
2396+ by the container to a WSDL port, and an optional set of handlers.
2397+
2398+ </xsd:documentation>
2399+ </xsd:annotation>
2400+
2401+ <xsd:sequence>
2402+ <xsd:group ref="j2ee:descriptionGroup"/>
2403+ <xsd:element name="service-ref-name"
2404+ type="j2ee:jndi-nameType">
2405+ <xsd:annotation>
2406+ <xsd:documentation>
2407+
2408+ The service-ref-name element declares logical name that the
2409+ components in the module use to look up the Web service. It
2410+ is recommended that all service reference names start with
2411+ "service/".
2412+
2413+ </xsd:documentation>
2414+ </xsd:annotation>
2415+ </xsd:element>
2416+
2417+ <xsd:element name="service-interface"
2418+ type="j2ee:fully-qualified-classType">
2419+ <xsd:annotation>
2420+ <xsd:documentation>
2421+
2422+ The service-interface element declares the fully qualified class
2423+ name of the JAX-RPC Service interface the client depends on.
2424+ In most cases the value will be javax.xml.rpc.Service. A JAX-RPC
2425+ generated Service Interface class may also be specified.
2426+
2427+ </xsd:documentation>
2428+ </xsd:annotation>
2429+ </xsd:element>
2430+
2431+ <xsd:element name="wsdl-file"
2432+ type="j2ee:xsdAnyURIType"
2433+ minOccurs="0" maxOccurs="1">
2434+ <xsd:annotation>
2435+ <xsd:documentation>
2436+
2437+ The wsdl-file element contains the URI location of a WSDL
2438+ file. The location is relative to the root of the module.
2439+
2440+ </xsd:documentation>
2441+ </xsd:annotation>
2442+ </xsd:element>
2443+
2444+ <xsd:element name="jaxrpc-mapping-file"
2445+ type="j2ee:pathType"
2446+ minOccurs="0" maxOccurs="1">
2447+ <xsd:annotation>
2448+ <xsd:documentation>
2449+
2450+ The jaxrpc-mapping-file element contains the name of a file that
2451+ describes the JAX-RPC mapping between the Java interaces used by
2452+ the application and the WSDL description in the wsdl-file. The
2453+ file name is a relative path within the module file.
2454+
2455+ </xsd:documentation>
2456+ </xsd:annotation>
2457+ </xsd:element>
2458+
2459+ <xsd:element name="service-qname"
2460+ type="j2ee:xsdQNameType"
2461+ minOccurs="0" maxOccurs="1">
2462+ <xsd:annotation>
2463+ <xsd:documentation>
2464+
2465+ The service-qname element declares the specific WSDL service
2466+ element that is being refered to. It is not specified if no
2467+ wsdl-file is declared.
2468+
2469+ </xsd:documentation>
2470+ </xsd:annotation>
2471+ </xsd:element>
2472+
2473+ <xsd:element name="port-component-ref"
2474+ type="j2ee:port-component-refType"
2475+ minOccurs="0" maxOccurs="unbounded">
2476+ <xsd:annotation>
2477+ <xsd:documentation>
2478+
2479+ The port-component-ref element declares a client dependency
2480+ on the container for resolving a Service Endpoint Interface
2481+ to a WSDL port. It optionally associates the Service Endpoint
2482+ Interface with a particular port-component. This is only used
2483+ by the container for a Service.getPort(Class) method call.
2484+
2485+ </xsd:documentation>
2486+ </xsd:annotation>
2487+ </xsd:element>
2488+
2489+ <xsd:element name="handler"
2490+ type="j2ee:service-ref_handlerType"
2491+ minOccurs="0" maxOccurs="unbounded">
2492+ <xsd:annotation>
2493+ <xsd:documentation>
2494+
2495+ Declares the handler for a port-component. Handlers can
2496+ access the init-param name/value pairs using the
2497+ HandlerInfo interface. If port-name is not specified, the
2498+ handler is assumed to be associated with all ports of the
2499+ service.
2500+
2501+ </xsd:documentation>
2502+ </xsd:annotation>
2503+ </xsd:element>
2504+ </xsd:sequence>
2505+ <xsd:attribute name="id" type="xsd:ID"/>
2506+ </xsd:complexType>
2507+
2508+<!-- **************************************************** -->
2509+
2510+ <xsd:complexType name="service-ref_handlerType">
2511+ <xsd:annotation>
2512+ <xsd:documentation>
2513+
2514+ Declares the handler for a port-component. Handlers can access the
2515+ init-param name/value pairs using the HandlerInfo interface. If
2516+ port-name is not specified, the handler is assumed to be associated
2517+ with all ports of the service.
2518+
2519+ Used in: service-ref
2520+
2521+ </xsd:documentation>
2522+ </xsd:annotation>
2523+ <xsd:sequence>
2524+ <xsd:group ref="j2ee:descriptionGroup"/>
2525+ <xsd:element name="handler-name"
2526+ type="j2ee:string">
2527+ <xsd:annotation>
2528+ <xsd:documentation>
2529+
2530+ Defines the name of the handler. The name must be unique
2531+ within the module.
2532+
2533+ </xsd:documentation>
2534+ </xsd:annotation>
2535+ </xsd:element>
2536+ <xsd:element name="handler-class"
2537+ type="j2ee:fully-qualified-classType">
2538+ <xsd:annotation>
2539+ <xsd:documentation>
2540+
2541+ Defines a fully qualified class name for the handler
2542+ implementation.
2543+
2544+ </xsd:documentation>
2545+ </xsd:annotation>
2546+ </xsd:element>
2547+ <xsd:element name="init-param"
2548+ type="j2ee:param-valueType"
2549+ minOccurs="0" maxOccurs="unbounded"/>
2550+
2551+ <xsd:element name="soap-header"
2552+ type="j2ee:xsdQNameType"
2553+ minOccurs="0" maxOccurs="unbounded">
2554+ <xsd:annotation>
2555+ <xsd:documentation>
2556+
2557+ Defines the QName of a SOAP header that will be processed
2558+ by the handler.
2559+
2560+ </xsd:documentation>
2561+ </xsd:annotation>
2562+ </xsd:element>
2563+
2564+ <xsd:element name="soap-role"
2565+ type="j2ee:string"
2566+ minOccurs="0" maxOccurs="unbounded">
2567+ <xsd:annotation>
2568+ <xsd:documentation>
2569+
2570+ The soap-role element contains a SOAP actor definition that
2571+ the Handler will play as a role.
2572+
2573+ </xsd:documentation>
2574+ </xsd:annotation>
2575+ </xsd:element>
2576+
2577+ <xsd:element name="port-name"
2578+ type="j2ee:string"
2579+ minOccurs="0" maxOccurs="unbounded">
2580+ <xsd:annotation>
2581+ <xsd:documentation>
2582+
2583+ The port-name element defines the WSDL port-name that a
2584+ handler should be associated with.
2585+
2586+ </xsd:documentation>
2587+ </xsd:annotation>
2588+ </xsd:element>
2589+ </xsd:sequence>
2590+ <xsd:attribute name="id" type="xsd:ID"/>
2591+ </xsd:complexType>
2592+
2593+</xsd:schema>
2594+
2595Index: jenkins-winstone/src/conf/javax/servlet/resources/javaee_5.xsd
2596===================================================================
2597--- /dev/null 1970-01-01 00:00:00.000000000 +0000
2598+++ jenkins-winstone/src/conf/javax/servlet/resources/javaee_5.xsd 2011-08-18 09:36:03.641501467 +0100
2599@@ -0,0 +1,2102 @@
2600+<?xml version="1.0" encoding="UTF-8"?>
2601+<xsd:schema
2602+ targetNamespace="http://java.sun.com/xml/ns/javaee"
2603+ xmlns:javaee="http://java.sun.com/xml/ns/javaee"
2604+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
2605+ elementFormDefault="qualified"
2606+ attributeFormDefault="unqualified"
2607+ version="5">
2608+ <xsd:annotation>
2609+ <xsd:documentation>
2610+ @(#)javaee_5.xsds 1.65 06/02/17
2611+ </xsd:documentation>
2612+ </xsd:annotation>
2613+
2614+ <xsd:annotation>
2615+ <xsd:documentation>
2616+
2617+ DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
2618+
2619+ Copyright 2003-2007 Sun Microsystems, Inc. All rights reserved.
2620+
2621+ The contents of this file are subject to the terms of either the
2622+ GNU General Public License Version 2 only ("GPL") or the Common
2623+ Development and Distribution License("CDDL") (collectively, the
2624+ "License"). You may not use this file except in compliance with
2625+ the License. You can obtain a copy of the License at
2626+ https://glassfish.dev.java.net/public/CDDL+GPL.html or
2627+ glassfish/bootstrap/legal/LICENSE.txt. See the License for the
2628+ specific language governing permissions and limitations under the
2629+ License.
2630+
2631+ When distributing the software, include this License Header
2632+ Notice in each file and include the License file at
2633+ glassfish/bootstrap/legal/LICENSE.txt. Sun designates this
2634+ particular file as subject to the "Classpath" exception as
2635+ provided by Sun in the GPL Version 2 section of the License file
2636+ that accompanied this code. If applicable, add the following
2637+ below the License Header, with the fields enclosed by brackets []
2638+ replaced by your own identifying information:
2639+ "Portions Copyrighted [year] [name of copyright owner]"
2640+
2641+ Contributor(s):
2642+
2643+ If you wish your version of this file to be governed by only the
2644+ CDDL or only the GPL Version 2, indicate your decision by adding
2645+ "[Contributor] elects to include this software in this
2646+ distribution under the [CDDL or GPL Version 2] license." If you
2647+ don't indicate a single choice of license, a recipient has the
2648+ option to distribute your version of this file under either the
2649+ CDDL, the GPL Version 2 or to extend the choice of license to its
2650+ licensees as provided above. However, if you add GPL Version 2
2651+ code and therefore, elected the GPL Version 2 license, then the
2652+ option applies only if the new code is made subject to such
2653+ option by the copyright holder.
2654+
2655+ </xsd:documentation>
2656+ </xsd:annotation>
2657+
2658+<xsd:annotation>
2659+<xsd:documentation>
2660+
2661+The following definitions that appear in the common
2662+shareable schema(s) of J2EE deployment descriptors should be
2663+interpreted with respect to the context they are included:
2664+
2665+Deployment Component may indicate one of the following:
2666+ j2ee application;
2667+ application client;
2668+ web application;
2669+ enterprise bean;
2670+ resource adapter;
2671+
2672+Deployment File may indicate one of the following:
2673+ ear file;
2674+ war file;
2675+ jar file;
2676+ rar file;
2677+
2678+</xsd:documentation>
2679+</xsd:annotation>
2680+
2681+ <xsd:import namespace="http://www.w3.org/XML/1998/namespace"
2682+ schemaLocation="http://www.w3.org/2001/xml.xsd"/>
2683+
2684+ <xsd:include schemaLocation="javaee_web_services_client_1_2.xsd"/>
2685+
2686+
2687+<!-- **************************************************** -->
2688+
2689+ <xsd:group name="descriptionGroup">
2690+ <xsd:annotation>
2691+ <xsd:documentation>
2692+
2693+ This group keeps the usage of the contained description related
2694+ elements consistent across Java EE deployment descriptors.
2695+
2696+ All elements may occur multiple times with different languages,
2697+ to support localization of the content.
2698+
2699+ </xsd:documentation>
2700+ </xsd:annotation>
2701+ <xsd:sequence>
2702+ <xsd:element name="description"
2703+ type="javaee:descriptionType"
2704+ minOccurs="0"
2705+ maxOccurs="unbounded"/>
2706+ <xsd:element name="display-name"
2707+ type="javaee:display-nameType"
2708+ minOccurs="0"
2709+ maxOccurs="unbounded"/>
2710+ <xsd:element name="icon"
2711+ type="javaee:iconType"
2712+ minOccurs="0"
2713+ maxOccurs="unbounded"/>
2714+ </xsd:sequence>
2715+ </xsd:group>
2716+
2717+<!-- **************************************************** -->
2718+
2719+ <xsd:complexType name="descriptionType">
2720+ <xsd:annotation>
2721+ <xsd:documentation>
2722+
2723+ The description type is used by a description element to
2724+ provide text describing the parent element. The elements
2725+ that use this type should include any information that the
2726+ Deployment Component's Deployment File file producer wants
2727+ to provide to the consumer of the Deployment Component's
2728+ Deployment File (i.e., to the Deployer). Typically, the
2729+ tools used by such a Deployment File consumer will display
2730+ the description when processing the parent element that
2731+ contains the description.
2732+
2733+ The lang attribute defines the language that the
2734+ description is provided in. The default value is "en" (English).
2735+
2736+ </xsd:documentation>
2737+ </xsd:annotation>
2738+ <xsd:simpleContent>
2739+ <xsd:extension base="javaee:xsdStringType">
2740+ <xsd:attribute ref="xml:lang"/>
2741+ </xsd:extension>
2742+ </xsd:simpleContent>
2743+ </xsd:complexType>
2744+
2745+<!-- **************************************************** -->
2746+
2747+ <xsd:simpleType name="dewey-versionType">
2748+ <xsd:annotation>
2749+ <xsd:documentation>
2750+
2751+ This type defines a dewey decimal that is used
2752+ to describe versions of documents.
2753+
2754+ </xsd:documentation>
2755+ </xsd:annotation>
2756+
2757+ <xsd:restriction base="xsd:token">
2758+ <xsd:pattern value="\.?[0-9]+(\.[0-9]+)*"/>
2759+ </xsd:restriction>
2760+ </xsd:simpleType>
2761+
2762+<!-- **************************************************** -->
2763+
2764+ <xsd:complexType name="display-nameType">
2765+ <xsd:annotation>
2766+ <xsd:documentation>
2767+ <![CDATA[
2768+
2769+ The display-name type contains a short name that is intended
2770+ to be displayed by tools. It is used by display-name
2771+ elements. The display name need not be unique.
2772+
2773+ Example:
2774+
2775+ ...
2776+ <display-name xml:lang="en">
2777+ Employee Self Service
2778+ </display-name>
2779+
2780+ The value of the xml:lang attribute is "en" (English) by default.
2781+
2782+ ]]>
2783+ </xsd:documentation>
2784+ </xsd:annotation>
2785+ <xsd:simpleContent>
2786+ <xsd:extension base="javaee:string">
2787+ <xsd:attribute ref="xml:lang"/>
2788+ </xsd:extension>
2789+ </xsd:simpleContent>
2790+ </xsd:complexType>
2791+
2792+<!-- **************************************************** -->
2793+
2794+ <xsd:complexType name="ejb-linkType">
2795+ <xsd:annotation>
2796+ <xsd:documentation>
2797+ <![CDATA[
2798+
2799+ The ejb-linkType is used by ejb-link
2800+ elements in the ejb-ref or ejb-local-ref elements to specify
2801+ that an EJB reference is linked to enterprise bean.
2802+
2803+ The value of the ejb-link element must be the ejb-name of an
2804+ enterprise bean in the same ejb-jar file or in another ejb-jar
2805+ file in the same Java EE application unit.
2806+
2807+ Alternatively, the name in the ejb-link element may be
2808+ composed of a path name specifying the ejb-jar containing the
2809+ referenced enterprise bean with the ejb-name of the target
2810+ bean appended and separated from the path name by "#". The
2811+ path name is relative to the Deployment File containing
2812+ Deployment Component that is referencing the enterprise
2813+ bean. This allows multiple enterprise beans with the same
2814+ ejb-name to be uniquely identified.
2815+
2816+ Examples:
2817+
2818+ <ejb-link>EmployeeRecord</ejb-link>
2819+
2820+ <ejb-link>../products/product.jar#ProductEJB</ejb-link>
2821+
2822+ ]]>
2823+ </xsd:documentation>
2824+ </xsd:annotation>
2825+ <xsd:simpleContent>
2826+ <xsd:restriction base="javaee:string"/>
2827+ </xsd:simpleContent>
2828+ </xsd:complexType>
2829+
2830+<!-- **************************************************** -->
2831+
2832+ <xsd:complexType name="ejb-local-refType">
2833+ <xsd:annotation>
2834+ <xsd:documentation>
2835+
2836+ The ejb-local-refType is used by ejb-local-ref elements for
2837+ the declaration of a reference to an enterprise bean's local
2838+ home or to the local business interface of a 3.0 bean.
2839+ The declaration consists of:
2840+
2841+ - an optional description
2842+ - the EJB reference name used in the code of the Deployment
2843+ Component that's referencing the enterprise bean.
2844+ - the optional expected type of the referenced enterprise bean
2845+ - the optional expected local interface of the referenced
2846+ enterprise bean or the local business interface of the
2847+ referenced enterprise bean.
2848+ - the optional expected local home interface of the referenced
2849+ enterprise bean. Not applicable if this ejb-local-ref refers
2850+ to the local business interface of a 3.0 bean.
2851+ - optional ejb-link information, used to specify the
2852+ referenced enterprise bean
2853+ - optional elements to define injection of the named enterprise
2854+ bean into a component field or property.
2855+
2856+ </xsd:documentation>
2857+ </xsd:annotation>
2858+
2859+ <xsd:sequence>
2860+ <xsd:element name="description"
2861+ type="javaee:descriptionType"
2862+ minOccurs="0"
2863+ maxOccurs="unbounded"/>
2864+ <xsd:element name="ejb-ref-name"
2865+ type="javaee:ejb-ref-nameType"/>
2866+ <xsd:element name="ejb-ref-type"
2867+ type="javaee:ejb-ref-typeType"
2868+ minOccurs="0"/>
2869+ <xsd:element name="local-home"
2870+ type="javaee:local-homeType"
2871+ minOccurs="0"/>
2872+ <xsd:element name="local"
2873+ type="javaee:localType"
2874+ minOccurs="0"/>
2875+ <xsd:element name="ejb-link"
2876+ type="javaee:ejb-linkType"
2877+ minOccurs="0"/>
2878+ <xsd:group ref="javaee:resourceGroup"/>
2879+ </xsd:sequence>
2880+ <xsd:attribute name="id" type="xsd:ID"/>
2881+ </xsd:complexType>
2882+
2883+<!-- **************************************************** -->
2884+
2885+ <xsd:complexType name="ejb-ref-nameType">
2886+ <xsd:annotation>
2887+ <xsd:documentation>
2888+ <![CDATA[
2889+
2890+ The ejb-ref-name element contains the name of an EJB
2891+ reference. The EJB reference is an entry in the
2892+ Deployment Component's environment and is relative to the
2893+ java:comp/env context. The name must be unique within the
2894+ Deployment Component.
2895+
2896+ It is recommended that name is prefixed with "ejb/".
2897+
2898+ Example:
2899+
2900+ <ejb-ref-name>ejb/Payroll</ejb-ref-name>
2901+
2902+ ]]>
2903+ </xsd:documentation>
2904+ </xsd:annotation>
2905+ <xsd:simpleContent>
2906+ <xsd:restriction base="javaee:jndi-nameType"/>
2907+ </xsd:simpleContent>
2908+ </xsd:complexType>
2909+
2910+<!-- **************************************************** -->
2911+
2912+ <xsd:complexType name="ejb-ref-typeType">
2913+ <xsd:annotation>
2914+ <xsd:documentation>
2915+
2916+ The ejb-ref-typeType contains the expected type of the
2917+ referenced enterprise bean.
2918+
2919+ The ejb-ref-type designates a value
2920+ that must be one of the following:
2921+
2922+ Entity
2923+ Session
2924+
2925+ </xsd:documentation>
2926+ </xsd:annotation>
2927+ <xsd:simpleContent>
2928+ <xsd:restriction base="javaee:string">
2929+ <xsd:enumeration value="Entity"/>
2930+ <xsd:enumeration value="Session"/>
2931+ </xsd:restriction>
2932+ </xsd:simpleContent>
2933+ </xsd:complexType>
2934+
2935+<!-- **************************************************** -->
2936+
2937+ <xsd:complexType name="ejb-refType">
2938+ <xsd:annotation>
2939+ <xsd:documentation>
2940+
2941+ The ejb-refType is used by ejb-ref elements for the
2942+ declaration of a reference to an enterprise bean's home or
2943+ to the remote business interface of a 3.0 bean.
2944+ The declaration consists of:
2945+
2946+ - an optional description
2947+ - the EJB reference name used in the code of
2948+ the Deployment Component that's referencing the enterprise
2949+ bean.
2950+ - the optional expected type of the referenced enterprise bean
2951+ - the optional remote interface of the referenced enterprise bean
2952+ or the remote business interface of the referenced enterprise
2953+ bean
2954+ - the optional expected home interface of the referenced
2955+ enterprise bean. Not applicable if this ejb-ref
2956+ refers to the remote business interface of a 3.0 bean.
2957+ - optional ejb-link information, used to specify the
2958+ referenced enterprise bean
2959+ - optional elements to define injection of the named enterprise
2960+ bean into a component field or property
2961+
2962+ </xsd:documentation>
2963+ </xsd:annotation>
2964+
2965+ <xsd:sequence>
2966+ <xsd:element name="description"
2967+ type="javaee:descriptionType"
2968+ minOccurs="0"
2969+ maxOccurs="unbounded"/>
2970+ <xsd:element name="ejb-ref-name"
2971+ type="javaee:ejb-ref-nameType"/>
2972+ <xsd:element name="ejb-ref-type"
2973+ type="javaee:ejb-ref-typeType"
2974+ minOccurs="0"/>
2975+ <xsd:element name="home"
2976+ type="javaee:homeType"
2977+ minOccurs="0"/>
2978+ <xsd:element name="remote"
2979+ type="javaee:remoteType"
2980+ minOccurs="0"/>
2981+ <xsd:element name="ejb-link"
2982+ type="javaee:ejb-linkType"
2983+ minOccurs="0"/>
2984+ <xsd:group ref="javaee:resourceGroup"/>
2985+ </xsd:sequence>
2986+ <xsd:attribute name="id" type="xsd:ID"/>
2987+ </xsd:complexType>
2988+
2989+<!-- **************************************************** -->
2990+
2991+ <xsd:complexType name="emptyType">
2992+ <xsd:annotation>
2993+ <xsd:documentation>
2994+
2995+ This type is used to designate an empty
2996+ element when used.
2997+
2998+ </xsd:documentation>
2999+ </xsd:annotation>
3000+ <xsd:attribute name="id" type="xsd:ID"/>
3001+ </xsd:complexType>
3002+
3003+<!-- **************************************************** -->
3004+
3005+ <xsd:complexType name="env-entry-type-valuesType">
3006+ <xsd:annotation>
3007+ <xsd:documentation>
3008+ <![CDATA[
3009+
3010+ This type contains the fully-qualified Java type of the
3011+ environment entry value that is expected by the
3012+ application's code.
3013+
3014+ The following are the legal values of env-entry-type-valuesType:
3015+
3016+ java.lang.Boolean
3017+ java.lang.Byte
3018+ java.lang.Character
3019+ java.lang.String
3020+ java.lang.Short
3021+ java.lang.Integer
3022+ java.lang.Long
3023+ java.lang.Float
3024+ java.lang.Double
3025+
3026+ Example:
3027+
3028+ <env-entry-type>java.lang.Boolean</env-entry-type>
3029+
3030+ ]]>
3031+ </xsd:documentation>
3032+ </xsd:annotation>
3033+ <xsd:simpleContent>
3034+ <xsd:restriction base="javaee:string">
3035+ <xsd:enumeration value="java.lang.Boolean"/>
3036+ <xsd:enumeration value="java.lang.Byte"/>
3037+ <xsd:enumeration value="java.lang.Character"/>
3038+ <xsd:enumeration value="java.lang.String"/>
3039+ <xsd:enumeration value="java.lang.Short"/>
3040+ <xsd:enumeration value="java.lang.Integer"/>
3041+ <xsd:enumeration value="java.lang.Long"/>
3042+ <xsd:enumeration value="java.lang.Float"/>
3043+ <xsd:enumeration value="java.lang.Double"/>
3044+ </xsd:restriction>
3045+ </xsd:simpleContent>
3046+ </xsd:complexType>
3047+
3048+<!-- **************************************************** -->
3049+
3050+ <xsd:complexType name="env-entryType">
3051+ <xsd:annotation>
3052+ <xsd:documentation>
3053+
3054+ The env-entryType is used to declare an application's
3055+ environment entry. The declaration consists of an optional
3056+ description, the name of the environment entry, a type
3057+ (optional if the value is injected, otherwise required), and
3058+ an optional value.
3059+
3060+ It also includes optional elements to define injection of
3061+ the named resource into fields or JavaBeans properties.
3062+
3063+ If a value is not specified and injection is requested,
3064+ no injection will occur and no entry of the specified name
3065+ will be created. This allows an initial value to be
3066+ specified in the source code without being incorrectly
3067+ changed when no override has been specified.
3068+
3069+ If a value is not specified and no injection is requested,
3070+ a value must be supplied during deployment.
3071+
3072+ This type is used by env-entry elements.
3073+
3074+ </xsd:documentation>
3075+ </xsd:annotation>
3076+
3077+ <xsd:sequence>
3078+ <xsd:element name="description"
3079+ type="javaee:descriptionType"
3080+ minOccurs="0"
3081+ maxOccurs="unbounded"/>
3082+ <xsd:element name="env-entry-name"
3083+ type="javaee:jndi-nameType">
3084+ <xsd:annotation>
3085+ <xsd:documentation>
3086+ <![CDATA[
3087+
3088+ The env-entry-name element contains the name of a
3089+ Deployment Component's environment entry. The name
3090+ is a JNDI name relative to the java:comp/env
3091+ context. The name must be unique within a
3092+ Deployment Component. The uniqueness
3093+ constraints must be defined within the declared
3094+ context.
3095+
3096+ Example:
3097+
3098+ <env-entry-name>minAmount</env-entry-name>
3099+
3100+ ]]>
3101+ </xsd:documentation>
3102+ </xsd:annotation>
3103+ </xsd:element>
3104+
3105+ <xsd:element name="env-entry-type"
3106+ type="javaee:env-entry-type-valuesType"
3107+ minOccurs="0">
3108+ <xsd:annotation>
3109+ <xsd:documentation>
3110+ <![CDATA[
3111+
3112+ The env-entry-type element contains the Java language
3113+ type of the environment entry. If an injection target
3114+ is specified for the environment entry, the type may
3115+ be omitted, or must match the type of the injection
3116+ target. If no injection target is specified, the type
3117+ is required.
3118+
3119+ Example:
3120+
3121+ <env-entry-type>java.lang.Integer</env-entry-type>
3122+
3123+ ]]>
3124+ </xsd:documentation>
3125+ </xsd:annotation>
3126+ </xsd:element>
3127+
3128+ <xsd:element name="env-entry-value"
3129+ type="javaee:xsdStringType"
3130+ minOccurs="0">
3131+ <xsd:annotation>
3132+ <xsd:documentation>
3133+ <![CDATA[
3134+
3135+ The env-entry-value designates the value of a
3136+ Deployment Component's environment entry. The value
3137+ must be a String that is valid for the
3138+ constructor of the specified type that takes a
3139+ single String parameter, or for java.lang.Character,
3140+ a single character.
3141+
3142+ Example:
3143+
3144+ <env-entry-value>100.00</env-entry-value>
3145+
3146+ ]]>
3147+ </xsd:documentation>
3148+ </xsd:annotation>
3149+ </xsd:element>
3150+
3151+ <xsd:group ref="javaee:resourceGroup"/>
3152+
3153+ </xsd:sequence>
3154+ <xsd:attribute name="id" type="xsd:ID"/>
3155+ </xsd:complexType>
3156+
3157+<!-- **************************************************** -->
3158+
3159+ <xsd:complexType name="fully-qualified-classType">
3160+ <xsd:annotation>
3161+ <xsd:documentation>
3162+
3163+ The elements that use this type designate the name of a
3164+ Java class or interface. The name is in the form of a
3165+ "binary name", as defined in the JLS. This is the form
3166+ of name used in Class.forName(). Tools that need the
3167+ canonical name (the name used in source code) will need
3168+ to convert this binary name to the canonical name.
3169+
3170+ </xsd:documentation>
3171+ </xsd:annotation>
3172+ <xsd:simpleContent>
3173+ <xsd:restriction base="javaee:string"/>
3174+ </xsd:simpleContent>
3175+ </xsd:complexType>
3176+
3177+<!-- **************************************************** -->
3178+
3179+ <xsd:complexType name="generic-booleanType">
3180+ <xsd:annotation>
3181+ <xsd:documentation>
3182+
3183+ This type defines four different values which can designate
3184+ boolean values. This includes values yes and no which are
3185+ not designated by xsd:boolean
3186+
3187+ </xsd:documentation>
3188+ </xsd:annotation>
3189+ <xsd:simpleContent>
3190+ <xsd:restriction base="javaee:string">
3191+ <xsd:enumeration value="true"/>
3192+ <xsd:enumeration value="false"/>
3193+ <xsd:enumeration value="yes"/>
3194+ <xsd:enumeration value="no"/>
3195+ </xsd:restriction>
3196+ </xsd:simpleContent>
3197+ </xsd:complexType>
3198+
3199+<!-- **************************************************** -->
3200+
3201+ <xsd:complexType name="homeType">
3202+ <xsd:annotation>
3203+ <xsd:documentation>
3204+ <![CDATA[
3205+
3206+ The homeType defines the fully-qualified name of
3207+ an enterprise bean's home interface.
3208+
3209+ Example:
3210+
3211+ <home>com.aardvark.payroll.PayrollHome</home>
3212+
3213+ ]]>
3214+ </xsd:documentation>
3215+ </xsd:annotation>
3216+ <xsd:simpleContent>
3217+ <xsd:restriction base="javaee:fully-qualified-classType"/>
3218+ </xsd:simpleContent>
3219+ </xsd:complexType>
3220+
3221+<!-- **************************************************** -->
3222+
3223+ <xsd:complexType name="iconType">
3224+ <xsd:annotation>
3225+ <xsd:documentation>
3226+
3227+ The icon type contains small-icon and large-icon elements
3228+ that specify the file names for small and large GIF, JPEG,
3229+ or PNG icon images used to represent the parent element in a
3230+ GUI tool.
3231+
3232+ The xml:lang attribute defines the language that the
3233+ icon file names are provided in. Its value is "en" (English)
3234+ by default.
3235+
3236+ </xsd:documentation>
3237+ </xsd:annotation>
3238+
3239+ <xsd:sequence>
3240+ <xsd:element name="small-icon" type="javaee:pathType"
3241+ minOccurs="0">
3242+ <xsd:annotation>
3243+ <xsd:documentation>
3244+ <![CDATA[
3245+
3246+ The small-icon element contains the name of a file
3247+ containing a small (16 x 16) icon image. The file
3248+ name is a relative path within the Deployment
3249+ Component's Deployment File.
3250+
3251+ The image may be in the GIF, JPEG, or PNG format.
3252+ The icon can be used by tools.
3253+
3254+ Example:
3255+
3256+ <small-icon>employee-service-icon16x16.jpg</small-icon>
3257+
3258+ ]]>
3259+ </xsd:documentation>
3260+ </xsd:annotation>
3261+ </xsd:element>
3262+ <xsd:element name="large-icon" type="javaee:pathType"
3263+ minOccurs="0">
3264+ <xsd:annotation>
3265+ <xsd:documentation>
3266+ <![CDATA[
3267+
3268+ The large-icon element contains the name of a file
3269+ containing a large
3270+ (32 x 32) icon image. The file name is a relative
3271+ path within the Deployment Component's Deployment
3272+ File.
3273+
3274+ The image may be in the GIF, JPEG, or PNG format.
3275+ The icon can be used by tools.
3276+
3277+ Example:
3278+
3279+ <large-icon>employee-service-icon32x32.jpg</large-icon>
3280+
3281+ ]]>
3282+ </xsd:documentation>
3283+ </xsd:annotation>
3284+ </xsd:element>
3285+
3286+ </xsd:sequence>
3287+
3288+ <xsd:attribute ref="xml:lang"/>
3289+ <xsd:attribute name="id" type="xsd:ID"/>
3290+
3291+ </xsd:complexType>
3292+
3293+<!-- **************************************************** -->
3294+
3295+ <xsd:complexType name="injection-targetType">
3296+ <xsd:annotation>
3297+ <xsd:documentation>
3298+
3299+ An injection target specifies a class and a name within
3300+ that class into which a resource should be injected.
3301+
3302+ The injection target class specifies the fully qualified
3303+ class name that is the target of the injection. The
3304+ Java EE specifications describe which classes can be an
3305+ injection target.
3306+
3307+ The injection target name specifies the target within
3308+ the specified class. The target is first looked for as a
3309+ JavaBeans property name. If not found, the target is
3310+ looked for as a field name.
3311+
3312+ The specified resource will be injected into the target
3313+ during initialization of the class by either calling the
3314+ set method for the target property or by setting a value
3315+ into the named field.
3316+
3317+ </xsd:documentation>
3318+ </xsd:annotation>
3319+ <xsd:sequence>
3320+ <xsd:element name="injection-target-class"
3321+ type="javaee:fully-qualified-classType"/>
3322+ <xsd:element name="injection-target-name"
3323+ type="javaee:java-identifierType"/>
3324+ </xsd:sequence>
3325+ </xsd:complexType>
3326+
3327+<!-- **************************************************** -->
3328+
3329+ <xsd:complexType name="java-identifierType">
3330+ <xsd:annotation>
3331+ <xsd:documentation>
3332+
3333+ The java-identifierType defines a Java identifier.
3334+ The users of this type should further verify that
3335+ the content does not contain Java reserved keywords.
3336+
3337+ </xsd:documentation>
3338+ </xsd:annotation>
3339+ <xsd:simpleContent>
3340+ <xsd:restriction base="javaee:string">
3341+ <xsd:pattern value="($|_|\p{L})(\p{L}|\p{Nd}|_|$)*"/>
3342+ </xsd:restriction>
3343+ </xsd:simpleContent>
3344+ </xsd:complexType>
3345+
3346+<!-- **************************************************** -->
3347+
3348+ <xsd:complexType name="java-typeType">
3349+ <xsd:annotation>
3350+ <xsd:documentation>
3351+
3352+ This is a generic type that designates a Java primitive
3353+ type or a fully qualified name of a Java interface/type,
3354+ or an array of such types.
3355+
3356+ </xsd:documentation>
3357+ </xsd:annotation>
3358+ <xsd:simpleContent>
3359+ <xsd:restriction base="javaee:string">
3360+ <xsd:pattern value="[^\p{Z}]*"/>
3361+ </xsd:restriction>
3362+ </xsd:simpleContent>
3363+ </xsd:complexType>
3364+
3365+<!-- **************************************************** -->
3366+
3367+ <xsd:complexType name="jndi-nameType">
3368+ <xsd:annotation>
3369+ <xsd:documentation>
3370+
3371+ The jndi-nameType type designates a JNDI name in the
3372+ Deployment Component's environment and is relative to the
3373+ java:comp/env context. A JNDI name must be unique within the
3374+ Deployment Component.
3375+
3376+ </xsd:documentation>
3377+ </xsd:annotation>
3378+ <xsd:simpleContent>
3379+ <xsd:restriction base="javaee:string"/>
3380+ </xsd:simpleContent>
3381+ </xsd:complexType>
3382+
3383+<!-- **************************************************** -->
3384+
3385+ <xsd:group name="jndiEnvironmentRefsGroup">
3386+ <xsd:annotation>
3387+ <xsd:documentation>
3388+
3389+ This group keeps the usage of the contained JNDI environment
3390+ reference elements consistent across Java EE deployment descriptors.
3391+
3392+ </xsd:documentation>
3393+ </xsd:annotation>
3394+ <xsd:sequence>
3395+ <xsd:element name="env-entry"
3396+ type="javaee:env-entryType"
3397+ minOccurs="0" maxOccurs="unbounded"/>
3398+ <xsd:element name="ejb-ref"
3399+ type="javaee:ejb-refType"
3400+ minOccurs="0" maxOccurs="unbounded"/>
3401+ <xsd:element name="ejb-local-ref"
3402+ type="javaee:ejb-local-refType"
3403+ minOccurs="0" maxOccurs="unbounded"/>
3404+ <xsd:group ref="javaee:service-refGroup"/>
3405+ <xsd:element name="resource-ref"
3406+ type="javaee:resource-refType"
3407+ minOccurs="0" maxOccurs="unbounded"/>
3408+ <xsd:element name="resource-env-ref"
3409+ type="javaee:resource-env-refType"
3410+ minOccurs="0" maxOccurs="unbounded"/>
3411+ <xsd:element name="message-destination-ref"
3412+ type="javaee:message-destination-refType"
3413+ minOccurs="0" maxOccurs="unbounded"/>
3414+ <xsd:element name="persistence-context-ref"
3415+ type="javaee:persistence-context-refType"
3416+ minOccurs="0" maxOccurs="unbounded"/>
3417+ <xsd:element name="persistence-unit-ref"
3418+ type="javaee:persistence-unit-refType"
3419+ minOccurs="0" maxOccurs="unbounded"/>
3420+ <xsd:element name="post-construct"
3421+ type="javaee:lifecycle-callbackType"
3422+ minOccurs="0" maxOccurs="unbounded"/>
3423+ <xsd:element name="pre-destroy"
3424+ type="javaee:lifecycle-callbackType"
3425+ minOccurs="0" maxOccurs="unbounded"/>
3426+ </xsd:sequence>
3427+ </xsd:group>
3428+
3429+<!-- **************************************************** -->
3430+
3431+ <xsd:complexType name="lifecycle-callbackType">
3432+ <xsd:annotation>
3433+ <xsd:documentation>
3434+
3435+ The lifecycle-callback type specifies a method on a
3436+ class to be called when a lifecycle event occurs.
3437+ Note that each class may have only one lifecycle callback
3438+ method for any given event and that the method may not
3439+ be overloaded.
3440+
3441+ If the lifefycle-callback-class element is missing then
3442+ the class defining the callback is assumed to be the
3443+ component class in scope at the place in the descriptor
3444+ in which the callback definition appears.
3445+
3446+ </xsd:documentation>
3447+ </xsd:annotation>
3448+ <xsd:sequence>
3449+ <xsd:element name="lifecycle-callback-class"
3450+ type="javaee:fully-qualified-classType"
3451+ minOccurs="0"/>
3452+ <xsd:element name="lifecycle-callback-method"
3453+ type="javaee:java-identifierType"/>
3454+ </xsd:sequence>
3455+ </xsd:complexType>
3456+
3457+<!-- **************************************************** -->
3458+
3459+ <xsd:complexType name="listenerType">
3460+ <xsd:annotation>
3461+ <xsd:documentation>
3462+
3463+ The listenerType indicates the deployment properties for a web
3464+ application listener bean.
3465+
3466+ </xsd:documentation>
3467+ </xsd:annotation>
3468+
3469+ <xsd:sequence>
3470+ <xsd:group ref="javaee:descriptionGroup"/>
3471+ <xsd:element name="listener-class"
3472+ type="javaee:fully-qualified-classType">
3473+ <xsd:annotation>
3474+ <xsd:documentation>
3475+
3476+ The listener-class element declares a class in the
3477+ application must be registered as a web
3478+ application listener bean. The value is the fully
3479+ qualified classname of the listener class.
3480+
3481+ </xsd:documentation>
3482+ </xsd:annotation>
3483+ </xsd:element>
3484+ </xsd:sequence>
3485+ <xsd:attribute name="id" type="xsd:ID"/>
3486+ </xsd:complexType>
3487+
3488+<!-- **************************************************** -->
3489+
3490+ <xsd:complexType name="local-homeType">
3491+ <xsd:annotation>
3492+ <xsd:documentation>
3493+
3494+ The local-homeType defines the fully-qualified
3495+ name of an enterprise bean's local home interface.
3496+
3497+ </xsd:documentation>
3498+ </xsd:annotation>
3499+ <xsd:simpleContent>
3500+ <xsd:restriction base="javaee:fully-qualified-classType"/>
3501+ </xsd:simpleContent>
3502+ </xsd:complexType>
3503+
3504+<!-- **************************************************** -->
3505+
3506+ <xsd:complexType name="localType">
3507+ <xsd:annotation>
3508+ <xsd:documentation>
3509+
3510+ The localType defines the fully-qualified name of an
3511+ enterprise bean's local interface.
3512+
3513+ </xsd:documentation>
3514+ </xsd:annotation>
3515+ <xsd:simpleContent>
3516+ <xsd:restriction base="javaee:fully-qualified-classType"/>
3517+ </xsd:simpleContent>
3518+ </xsd:complexType>
3519+
3520+<!-- **************************************************** -->
3521+
3522+ <xsd:complexType name="message-destination-linkType">
3523+ <xsd:annotation>
3524+ <xsd:documentation>
3525+
3526+ The message-destination-linkType is used to link a message
3527+ destination reference or message-driven bean to a message
3528+ destination.
3529+
3530+ The Assembler sets the value to reflect the flow of messages
3531+ between producers and consumers in the application.
3532+
3533+ The value must be the message-destination-name of a message
3534+ destination in the same Deployment File or in another
3535+ Deployment File in the same Java EE application unit.
3536+
3537+ Alternatively, the value may be composed of a path name
3538+ specifying a Deployment File containing the referenced
3539+ message destination with the message-destination-name of the
3540+ destination appended and separated from the path name by
3541+ "#". The path name is relative to the Deployment File
3542+ containing Deployment Component that is referencing the
3543+ message destination. This allows multiple message
3544+ destinations with the same name to be uniquely identified.
3545+
3546+ </xsd:documentation>
3547+ </xsd:annotation>
3548+ <xsd:simpleContent>
3549+ <xsd:restriction base="javaee:string"/>
3550+ </xsd:simpleContent>
3551+ </xsd:complexType>
3552+
3553+<!-- **************************************************** -->
3554+
3555+ <xsd:complexType name="message-destination-refType">
3556+ <xsd:annotation>
3557+ <xsd:documentation>
3558+ <![CDATA[
3559+
3560+ The message-destination-ref element contains a declaration
3561+ of Deployment Component's reference to a message destination
3562+ associated with a resource in Deployment Component's
3563+ environment. It consists of:
3564+
3565+ - an optional description
3566+ - the message destination reference name
3567+ - an optional message destination type
3568+ - an optional specification as to whether
3569+ the destination is used for
3570+ consuming or producing messages, or both.
3571+ if not specified, "both" is assumed.
3572+ - an optional link to the message destination
3573+ - optional injection targets
3574+
3575+ The message destination type must be supplied unless an
3576+ injection target is specified, in which case the type
3577+ of the target is used. If both are specified, the type
3578+ must be assignment compatible with the type of the injection
3579+ target.
3580+
3581+ Examples:
3582+
3583+ <message-destination-ref>
3584+ <message-destination-ref-name>jms/StockQueue
3585+ </message-destination-ref-name>
3586+ <message-destination-type>javax.jms.Queue
3587+ </message-destination-type>
3588+ <message-destination-usage>Consumes
3589+ </message-destination-usage>
3590+ <message-destination-link>CorporateStocks
3591+ </message-destination-link>
3592+ </message-destination-ref>
3593+
3594+ ]]>
3595+ </xsd:documentation>
3596+ </xsd:annotation>
3597+ <xsd:sequence>
3598+ <xsd:element name="description"
3599+ type="javaee:descriptionType"
3600+ minOccurs="0"
3601+ maxOccurs="unbounded"/>
3602+ <xsd:element name="message-destination-ref-name"
3603+ type="javaee:jndi-nameType">
3604+ <xsd:annotation>
3605+ <xsd:documentation>
3606+
3607+ The message-destination-ref-name element specifies
3608+ the name of a message destination reference; its
3609+ value is the environment entry name used in
3610+ Deployment Component code. The name is a JNDI name
3611+ relative to the java:comp/env context and must be
3612+ unique within an ejb-jar (for enterprise beans) or a
3613+ Deployment File (for others).
3614+
3615+ </xsd:documentation>
3616+ </xsd:annotation>
3617+ </xsd:element>
3618+ <xsd:element name="message-destination-type"
3619+ type="javaee:message-destination-typeType"
3620+ minOccurs="0"/>
3621+ <xsd:element name="message-destination-usage"
3622+ type="javaee:message-destination-usageType"
3623+ minOccurs="0"/>
3624+ <xsd:element name="message-destination-link"
3625+ type="javaee:message-destination-linkType"
3626+ minOccurs="0"/>
3627+
3628+ <xsd:group ref="javaee:resourceGroup"/>
3629+
3630+ </xsd:sequence>
3631+ <xsd:attribute name="id" type="xsd:ID"/>
3632+
3633+ </xsd:complexType>
3634+
3635+<!-- **************************************************** -->
3636+
3637+ <xsd:complexType name="message-destination-typeType">
3638+ <xsd:annotation>
3639+ <xsd:documentation>
3640+ <![CDATA[
3641+
3642+ The message-destination-typeType specifies the type of
3643+ the destination. The type is specified by the Java interface
3644+ expected to be implemented by the destination.
3645+
3646+ Example:
3647+
3648+ <message-destination-type>javax.jms.Queue
3649+ </message-destination-type>
3650+
3651+ ]]>
3652+ </xsd:documentation>
3653+ </xsd:annotation>
3654+ <xsd:simpleContent>
3655+ <xsd:restriction base="javaee:fully-qualified-classType"/>
3656+ </xsd:simpleContent>
3657+ </xsd:complexType>
3658+
3659+<!-- **************************************************** -->
3660+
3661+ <xsd:complexType name="message-destination-usageType">
3662+ <xsd:annotation>
3663+ <xsd:documentation>
3664+
3665+ The message-destination-usageType specifies the use of the
3666+ message destination indicated by the reference. The value
3667+ indicates whether messages are consumed from the message
3668+ destination, produced for the destination, or both. The
3669+ Assembler makes use of this information in linking producers
3670+ of a destination with its consumers.
3671+
3672+ The value of the message-destination-usage element must be
3673+ one of the following:
3674+ Consumes
3675+ Produces
3676+ ConsumesProduces
3677+
3678+ </xsd:documentation>
3679+ </xsd:annotation>
3680+ <xsd:simpleContent>
3681+ <xsd:restriction base="javaee:string">
3682+ <xsd:enumeration value="Consumes"/>
3683+ <xsd:enumeration value="Produces"/>
3684+ <xsd:enumeration value="ConsumesProduces"/>
3685+ </xsd:restriction>
3686+ </xsd:simpleContent>
3687+ </xsd:complexType>
3688+
3689+<!-- **************************************************** -->
3690+
3691+ <xsd:complexType name="message-destinationType">
3692+ <xsd:annotation>
3693+ <xsd:documentation>
3694+ <![CDATA[
3695+
3696+ The message-destinationType specifies a message
3697+ destination. The logical destination described by this
3698+ element is mapped to a physical destination by the Deployer.
3699+
3700+ The message destination element contains:
3701+
3702+ - an optional description
3703+ - an optional display-name
3704+ - an optional icon
3705+ - a message destination name which must be unique
3706+ among message destination names within the same
3707+ Deployment File.
3708+ - an optional mapped name
3709+
3710+ Example:
3711+
3712+ <message-destination>
3713+ <message-destination-name>CorporateStocks
3714+ </message-destination-name>
3715+ </message-destination>
3716+
3717+ ]]>
3718+ </xsd:documentation>
3719+ </xsd:annotation>
3720+ <xsd:sequence>
3721+ <xsd:group ref="javaee:descriptionGroup"/>
3722+ <xsd:element name="message-destination-name"
3723+ type="javaee:string">
3724+ <xsd:annotation>
3725+ <xsd:documentation>
3726+
3727+ The message-destination-name element specifies a
3728+ name for a message destination. This name must be
3729+ unique among the names of message destinations
3730+ within the Deployment File.
3731+
3732+ </xsd:documentation>
3733+ </xsd:annotation>
3734+ </xsd:element>
3735+ <xsd:element name="mapped-name"
3736+ type="javaee:xsdStringType"
3737+ minOccurs="0">
3738+ <xsd:annotation>
3739+ <xsd:documentation>
3740+ <![CDATA[
3741+
3742+ A product specific name that this message destination
3743+ should be mapped to. Each message-destination-ref
3744+ element that references this message destination will
3745+ define a name in the namespace of the referencing
3746+ component. (It's a name in the JNDI java:comp/env
3747+ namespace.) Many application servers provide a way to
3748+ map these local names to names of resources known to the
3749+ application server. This mapped name is often a global
3750+ JNDI name, but may be a name of any form. Each of the
3751+ local names should be mapped to this same global name.
3752+
3753+ Application servers are not required to support any
3754+ particular form or type of mapped name, nor the ability
3755+ to use mapped names. The mapped name is
3756+ product-dependent and often installation-dependent. No
3757+ use of a mapped name is portable.
3758+
3759+ ]]>
3760+ </xsd:documentation>
3761+ </xsd:annotation>
3762+ </xsd:element>
3763+ </xsd:sequence>
3764+ <xsd:attribute name="id" type="xsd:ID"/>
3765+ </xsd:complexType>
3766+
3767+<!-- **************************************************** -->
3768+
3769+ <xsd:complexType name="param-valueType">
3770+ <xsd:annotation>
3771+ <xsd:documentation>
3772+
3773+ This type is a general type that can be used to declare
3774+ parameter/value lists.
3775+
3776+ </xsd:documentation>
3777+ </xsd:annotation>
3778+
3779+ <xsd:sequence>
3780+ <xsd:element name="description"
3781+ type="javaee:descriptionType"
3782+ minOccurs="0"
3783+ maxOccurs="unbounded"/>
3784+ <xsd:element name="param-name"
3785+ type="javaee:string">
3786+ <xsd:annotation>
3787+ <xsd:documentation>
3788+
3789+ The param-name element contains the name of a
3790+ parameter.
3791+
3792+ </xsd:documentation>
3793+ </xsd:annotation>
3794+ </xsd:element>
3795+
3796+ <xsd:element name="param-value"
3797+ type="javaee:xsdStringType">
3798+ <xsd:annotation>
3799+ <xsd:documentation>
3800+
3801+ The param-value element contains the value of a
3802+ parameter.
3803+
3804+ </xsd:documentation>
3805+ </xsd:annotation>
3806+ </xsd:element>
3807+ </xsd:sequence>
3808+ <xsd:attribute name="id" type="xsd:ID"/>
3809+ </xsd:complexType>
3810+
3811+<!-- **************************************************** -->
3812+
3813+ <xsd:complexType name="pathType">
3814+ <xsd:annotation>
3815+ <xsd:documentation>
3816+
3817+ The elements that use this type designate either a relative
3818+ path or an absolute path starting with a "/".
3819+
3820+ In elements that specify a pathname to a file within the
3821+ same Deployment File, relative filenames (i.e., those not
3822+ starting with "/") are considered relative to the root of
3823+ the Deployment File's namespace. Absolute filenames (i.e.,
3824+ those starting with "/") also specify names in the root of
3825+ the Deployment File's namespace. In general, relative names
3826+ are preferred. The exception is .war files where absolute
3827+ names are preferred for consistency with the Servlet API.
3828+
3829+ </xsd:documentation>
3830+ </xsd:annotation>
3831+ <xsd:simpleContent>
3832+ <xsd:restriction base="javaee:string"/>
3833+ </xsd:simpleContent>
3834+ </xsd:complexType>
3835+
3836+<!-- **************************************************** -->
3837+
3838+ <xsd:complexType name="persistence-context-refType">
3839+ <xsd:annotation>
3840+ <xsd:documentation>
3841+ <![CDATA[
3842+
3843+ The persistence-context-ref element contains a declaration
3844+ of Deployment Component's reference to a persistence context
3845+ associated within a Deployment Component's
3846+ environment. It consists of:
3847+
3848+ - an optional description
3849+ - the persistence context reference name
3850+ - an optional persistence unit name. If not specified,
3851+ the default persistence unit is assumed.
3852+ - an optional specification as to whether
3853+ the persistence context type is Transaction or
3854+ Extended. If not specified, Transaction is assumed.
3855+ - an optional list of persistence properties
3856+ - optional injection targets
3857+
3858+ Examples:
3859+
3860+ <persistence-context-ref>
3861+ <persistence-context-ref-name>myPersistenceContext
3862+ </persistence-context-ref-name>
3863+ </persistence-context-ref>
3864+
3865+ <persistence-context-ref>
3866+ <persistence-context-ref-name>myPersistenceContext
3867+ </persistence-context-ref-name>
3868+ <persistence-unit-name>PersistenceUnit1
3869+ </persistence-unit-name>
3870+ <persistence-context-type>Extended</persistence-context-type>
3871+ </persistence-context-ref>
3872+
3873+ ]]>
3874+ </xsd:documentation>
3875+ </xsd:annotation>
3876+ <xsd:sequence>
3877+ <xsd:element name="description"
3878+ type="javaee:descriptionType"
3879+ minOccurs="0"
3880+ maxOccurs="unbounded"/>
3881+ <xsd:element name="persistence-context-ref-name"
3882+ type="javaee:jndi-nameType">
3883+ <xsd:annotation>
3884+ <xsd:documentation>
3885+
3886+ The persistence-context-ref-name element specifies
3887+ the name of a persistence context reference; its
3888+ value is the environment entry name used in
3889+ Deployment Component code. The name is a JNDI name
3890+ relative to the java:comp/env context.
3891+
3892+ </xsd:documentation>
3893+ </xsd:annotation>
3894+ </xsd:element>
3895+ <xsd:element name="persistence-unit-name"
3896+ type="javaee:string"
3897+ minOccurs="0">
3898+ <xsd:annotation>
3899+ <xsd:documentation>
3900+
3901+ The Application Assembler(or BeanProvider) may use the
3902+ following syntax to avoid the need to rename persistence
3903+ units to have unique names within a Java EE application.
3904+
3905+ The Application Assembler specifies the pathname of the
3906+ root of the persistence.xml file for the referenced
3907+ persistence unit and appends the name of the persistence
3908+ unit separated from the pathname by #. The pathname is
3909+ relative to the referencing application component jar file.
3910+ In this manner, multiple persistence units with the same
3911+ persistence unit name may be uniquely identified when the
3912+ Application Assembler cannot change persistence unit names.
3913+
3914+ </xsd:documentation>
3915+ </xsd:annotation>
3916+ </xsd:element>
3917+
3918+ <xsd:element name="persistence-context-type"
3919+ type="javaee:persistence-context-typeType"
3920+ minOccurs="0"/>
3921+
3922+ <xsd:element name="persistence-property"
3923+ type="javaee:propertyType"
3924+ minOccurs="0"
3925+ maxOccurs="unbounded">
3926+ <xsd:annotation>
3927+ <xsd:documentation>
3928+
3929+ Used to specify properties for the container or persistence
3930+ provider. Vendor-specific properties may be included in
3931+ the set of properties. Properties that are not recognized
3932+ by a vendor must be ignored. Entries that make use of the
3933+ namespace javax.persistence and its subnamespaces must not
3934+ be used for vendor-specific properties. The namespace
3935+ javax.persistence is reserved for use by the specification.
3936+
3937+ </xsd:documentation>
3938+ </xsd:annotation>
3939+ </xsd:element>
3940+
3941+ <xsd:group ref="javaee:resourceGroup"/>
3942+
3943+ </xsd:sequence>
3944+ <xsd:attribute name="id" type="xsd:ID"/>
3945+
3946+ </xsd:complexType>
3947+
3948+<!-- **************************************************** -->
3949+
3950+ <xsd:complexType name="persistence-context-typeType">
3951+ <xsd:annotation>
3952+ <xsd:documentation>
3953+
3954+ The persistence-context-typeType specifies the transactional
3955+ nature of a persistence context reference.
3956+
3957+ The value of the persistence-context-type element must be
3958+ one of the following:
3959+ Transaction
3960+ Extended
3961+
3962+ </xsd:documentation>
3963+ </xsd:annotation>
3964+ <xsd:simpleContent>
3965+ <xsd:restriction base="javaee:string">
3966+ <xsd:enumeration value="Transaction"/>
3967+ <xsd:enumeration value="Extended"/>
3968+ </xsd:restriction>
3969+ </xsd:simpleContent>
3970+ </xsd:complexType>
3971+
3972+<!-- **************************************************** -->
3973+
3974+ <xsd:complexType name="persistence-unit-refType">
3975+ <xsd:annotation>
3976+ <xsd:documentation>
3977+ <![CDATA[
3978+
3979+ The persistence-unit-ref element contains a declaration
3980+ of Deployment Component's reference to a persistence unit
3981+ associated within a Deployment Component's
3982+ environment. It consists of:
3983+
3984+ - an optional description
3985+ - the persistence unit reference name
3986+ - an optional persistence unit name. If not specified,
3987+ the default persistence unit is assumed.
3988+ - optional injection targets
3989+
3990+ Examples:
3991+
3992+ <persistence-unit-ref>
3993+ <persistence-unit-ref-name>myPersistenceUnit
3994+ </persistence-unit-ref-name>
3995+ </persistence-unit-ref>
3996+
3997+ <persistence-unit-ref>
3998+ <persistence-unit-ref-name>myPersistenceUnit
3999+ </persistence-unit-ref-name>
4000+ <persistence-unit-name>PersistenceUnit1
4001+ </persistence-unit-name>
4002+ </persistence-unit-ref>
4003+
4004+ ]]>
4005+ </xsd:documentation>
4006+ </xsd:annotation>
4007+ <xsd:sequence>
4008+ <xsd:element name="description"
4009+ type="javaee:descriptionType"
4010+ minOccurs="0"
4011+ maxOccurs="unbounded"/>
4012+ <xsd:element name="persistence-unit-ref-name"
4013+ type="javaee:jndi-nameType">
4014+ <xsd:annotation>
4015+ <xsd:documentation>
4016+
4017+ The persistence-unit-ref-name element specifies
4018+ the name of a persistence unit reference; its
4019+ value is the environment entry name used in
4020+ Deployment Component code. The name is a JNDI name
4021+ relative to the java:comp/env context.
4022+
4023+ </xsd:documentation>
4024+ </xsd:annotation>
4025+ </xsd:element>
4026+ <xsd:element name="persistence-unit-name"
4027+ type="javaee:string"
4028+ minOccurs="0">
4029+ <xsd:annotation>
4030+ <xsd:documentation>
4031+
4032+ The Application Assembler(or BeanProvider) may use the
4033+ following syntax to avoid the need to rename persistence
4034+ units to have unique names within a Java EE application.
4035+
4036+ The Application Assembler specifies the pathname of the
4037+ root of the persistence.xml file for the referenced
4038+ persistence unit and appends the name of the persistence
4039+ unit separated from the pathname by #. The pathname is
4040+ relative to the referencing application component jar file.
4041+ In this manner, multiple persistence units with the same
4042+ persistence unit name may be uniquely identified when the
4043+ Application Assembler cannot change persistence unit names.
4044+
4045+ </xsd:documentation>
4046+ </xsd:annotation>
4047+ </xsd:element>
4048+
4049+ <xsd:group ref="javaee:resourceGroup"/>
4050+
4051+ </xsd:sequence>
4052+ <xsd:attribute name="id" type="xsd:ID"/>
4053+
4054+ </xsd:complexType>
4055+
4056+<!-- **************************************************** -->
4057+
4058+ <xsd:complexType name="propertyType">
4059+ <xsd:annotation>
4060+ <xsd:documentation>
4061+
4062+ Specifies a name/value pair.
4063+
4064+ </xsd:documentation>
4065+ </xsd:annotation>
4066+
4067+ <xsd:sequence>
4068+ <xsd:element name="name"
4069+ type="javaee:xsdStringType">
4070+ </xsd:element>
4071+ <xsd:element name="value"
4072+ type="javaee:xsdStringType">
4073+ </xsd:element>
4074+ </xsd:sequence>
4075+ <xsd:attribute name="id" type="xsd:ID"/>
4076+ </xsd:complexType>
4077+
4078+<!-- **************************************************** -->
4079+
4080+ <xsd:complexType name="remoteType">
4081+ <xsd:annotation>
4082+ <xsd:documentation>
4083+ <![CDATA[
4084+
4085+ The remote element contains the fully-qualified name
4086+ of the enterprise bean's remote interface.
4087+
4088+ Example:
4089+
4090+ <remote>com.wombat.empl.EmployeeService</remote>
4091+
4092+ ]]>
4093+ </xsd:documentation>
4094+ </xsd:annotation>
4095+ <xsd:simpleContent>
4096+ <xsd:restriction base="javaee:fully-qualified-classType"/>
4097+ </xsd:simpleContent>
4098+ </xsd:complexType>
4099+
4100+<!-- **************************************************** -->
4101+
4102+ <xsd:complexType name="res-authType">
4103+ <xsd:annotation>
4104+ <xsd:documentation>
4105+
4106+ The res-authType specifies whether the Deployment Component
4107+ code signs on programmatically to the resource manager, or
4108+ whether the Container will sign on to the resource manager
4109+ on behalf of the Deployment Component. In the latter case,
4110+ the Container uses information that is supplied by the
4111+ Deployer.
4112+
4113+ The value must be one of the two following:
4114+
4115+ Application
4116+ Container
4117+
4118+ </xsd:documentation>
4119+ </xsd:annotation>
4120+ <xsd:simpleContent>
4121+ <xsd:restriction base="javaee:string">
4122+ <xsd:enumeration value="Application"/>
4123+ <xsd:enumeration value="Container"/>
4124+ </xsd:restriction>
4125+ </xsd:simpleContent>
4126+ </xsd:complexType>
4127+
4128+<!-- **************************************************** -->
4129+
4130+ <xsd:complexType name="res-sharing-scopeType">
4131+ <xsd:annotation>
4132+ <xsd:documentation>
4133+
4134+ The res-sharing-scope type specifies whether connections
4135+ obtained through the given resource manager connection
4136+ factory reference can be shared. The value, if specified,
4137+ must be one of the two following:
4138+
4139+ Shareable
4140+ Unshareable
4141+
4142+ The default value is Shareable.
4143+
4144+ </xsd:documentation>
4145+ </xsd:annotation>
4146+ <xsd:simpleContent>
4147+ <xsd:restriction base="javaee:string">
4148+ <xsd:enumeration value="Shareable"/>
4149+ <xsd:enumeration value="Unshareable"/>
4150+ </xsd:restriction>
4151+ </xsd:simpleContent>
4152+ </xsd:complexType>
4153+
4154+<!-- **************************************************** -->
4155+
4156+ <xsd:complexType name="resource-env-refType">
4157+ <xsd:annotation>
4158+ <xsd:documentation>
4159+ <![CDATA[
4160+
4161+ The resource-env-refType is used to define
4162+ resource-env-type elements. It contains a declaration of a
4163+ Deployment Component's reference to an administered object
4164+ associated with a resource in the Deployment Component's
4165+ environment. It consists of an optional description, the
4166+ resource environment reference name, and an optional
4167+ indication of the resource environment reference type
4168+ expected by the Deployment Component code.
4169+
4170+ It also includes optional elements to define injection of
4171+ the named resource into fields or JavaBeans properties.
4172+
4173+ The resource environment type must be supplied unless an
4174+ injection target is specified, in which case the type
4175+ of the target is used. If both are specified, the type
4176+ must be assignment compatible with the type of the injection
4177+ target.
4178+
4179+ Example:
4180+
4181+ <resource-env-ref>
4182+ <resource-env-ref-name>jms/StockQueue
4183+ </resource-env-ref-name>
4184+ <resource-env-ref-type>javax.jms.Queue
4185+ </resource-env-ref-type>
4186+ </resource-env-ref>
4187+
4188+ ]]>
4189+ </xsd:documentation>
4190+ </xsd:annotation>
4191+
4192+ <xsd:sequence>
4193+ <xsd:element name="description"
4194+ type="javaee:descriptionType"
4195+ minOccurs="0"
4196+ maxOccurs="unbounded"/>
4197+ <xsd:element name="resource-env-ref-name"
4198+ type="javaee:jndi-nameType">
4199+ <xsd:annotation>
4200+ <xsd:documentation>
4201+
4202+ The resource-env-ref-name element specifies the name
4203+ of a resource environment reference; its value is
4204+ the environment entry name used in
4205+ the Deployment Component code. The name is a JNDI
4206+ name relative to the java:comp/env context and must
4207+ be unique within a Deployment Component.
4208+
4209+ </xsd:documentation>
4210+ </xsd:annotation>
4211+ </xsd:element>
4212+
4213+ <xsd:element name="resource-env-ref-type"
4214+ type="javaee:fully-qualified-classType"
4215+ minOccurs="0">
4216+ <xsd:annotation>
4217+ <xsd:documentation>
4218+
4219+ The resource-env-ref-type element specifies the type
4220+ of a resource environment reference. It is the
4221+ fully qualified name of a Java language class or
4222+ interface.
4223+
4224+ </xsd:documentation>
4225+ </xsd:annotation>
4226+ </xsd:element>
4227+
4228+ <xsd:group ref="javaee:resourceGroup"/>
4229+
4230+ </xsd:sequence>
4231+ <xsd:attribute name="id" type="xsd:ID"/>
4232+ </xsd:complexType>
4233+
4234+<!-- **************************************************** -->
4235+
4236+ <xsd:complexType name="resource-refType">
4237+ <xsd:annotation>
4238+ <xsd:documentation>
4239+ <![CDATA[
4240+
4241+ The resource-refType contains a declaration of a
4242+ Deployment Component's reference to an external resource. It
4243+ consists of an optional description, the resource manager
4244+ connection factory reference name, an optional indication of
4245+ the resource manager connection factory type expected by the
4246+ Deployment Component code, an optional type of authentication
4247+ (Application or Container), and an optional specification of
4248+ the shareability of connections obtained from the resource
4249+ (Shareable or Unshareable).
4250+
4251+ It also includes optional elements to define injection of
4252+ the named resource into fields or JavaBeans properties.
4253+
4254+ The connection factory type must be supplied unless an
4255+ injection target is specified, in which case the type
4256+ of the target is used. If both are specified, the type
4257+ must be assignment compatible with the type of the injection
4258+ target.
4259+
4260+ Example:
4261+
4262+ <resource-ref>
4263+ <res-ref-name>jdbc/EmployeeAppDB</res-ref-name>
4264+ <res-type>javax.sql.DataSource</res-type>
4265+ <res-auth>Container</res-auth>
4266+ <res-sharing-scope>Shareable</res-sharing-scope>
4267+ </resource-ref>
4268+
4269+ ]]>
4270+ </xsd:documentation>
4271+ </xsd:annotation>
4272+
4273+ <xsd:sequence>
4274+ <xsd:element name="description"
4275+ type="javaee:descriptionType"
4276+ minOccurs="0"
4277+ maxOccurs="unbounded"/>
4278+ <xsd:element name="res-ref-name"
4279+ type="javaee:jndi-nameType">
4280+ <xsd:annotation>
4281+ <xsd:documentation>
4282+
4283+ The res-ref-name element specifies the name of a
4284+ resource manager connection factory reference.
4285+ The name is a JNDI name relative to the
4286+ java:comp/env context.
4287+ The name must be unique within a Deployment File.
4288+
4289+ </xsd:documentation>
4290+ </xsd:annotation>
4291+ </xsd:element>
4292+
4293+ <xsd:element name="res-type"
4294+ type="javaee:fully-qualified-classType"
4295+ minOccurs="0">
4296+ <xsd:annotation>
4297+ <xsd:documentation>
4298+
4299+ The res-type element specifies the type of the data
4300+ source. The type is specified by the fully qualified
4301+ Java language class or interface
4302+ expected to be implemented by the data source.
4303+
4304+ </xsd:documentation>
4305+ </xsd:annotation>
4306+ </xsd:element>
4307+
4308+ <xsd:element name="res-auth"
4309+ type="javaee:res-authType"
4310+ minOccurs="0"/>
4311+
4312+ <xsd:element name="res-sharing-scope"
4313+ type="javaee:res-sharing-scopeType"
4314+ minOccurs="0"/>
4315+
4316+ <xsd:group ref="javaee:resourceGroup"/>
4317+
4318+ </xsd:sequence>
4319+ <xsd:attribute name="id" type="xsd:ID"/>
4320+ </xsd:complexType>
4321+
4322+<!-- **************************************************** -->
4323+
4324+ <xsd:group name="resourceGroup">
4325+ <xsd:annotation>
4326+ <xsd:documentation>
4327+
4328+ This group collects elements that are common to all the
4329+ JNDI resource elements.
4330+
4331+ </xsd:documentation>
4332+ </xsd:annotation>
4333+ <xsd:sequence>
4334+ <xsd:element name="mapped-name"
4335+ type="javaee:xsdStringType"
4336+ minOccurs="0">
4337+ <xsd:annotation>
4338+ <xsd:documentation>
4339+ <![CDATA[
4340+
4341+ A product specific name that this resource should be
4342+ mapped to. The name of this resource, as defined by the
4343+ resource's name element or defaulted, is a name that is
4344+ local to the application component using the resource.
4345+ (It's a name in the JNDI java:comp/env namespace.) Many
4346+ application servers provide a way to map these local
4347+ names to names of resources known to the application
4348+ server. This mapped name is often a global JNDI name,
4349+ but may be a name of any form.
4350+
4351+ Application servers are not required to support any
4352+ particular form or type of mapped name, nor the ability
4353+ to use mapped names. The mapped name is
4354+ product-dependent and often installation-dependent. No
4355+ use of a mapped name is portable.
4356+
4357+ ]]>
4358+ </xsd:documentation>
4359+ </xsd:annotation>
4360+ </xsd:element>
4361+
4362+ <xsd:element name="injection-target"
4363+ type="javaee:injection-targetType"
4364+ minOccurs="0"
4365+ maxOccurs="unbounded"/>
4366+ </xsd:sequence>
4367+ </xsd:group>
4368+
4369+<!-- **************************************************** -->
4370+
4371+ <xsd:complexType name="role-nameType">
4372+ <xsd:annotation>
4373+ <xsd:documentation>
4374+
4375+ The role-nameType designates the name of a security role.
4376+
4377+ The name must conform to the lexical rules for a token.
4378+
4379+ </xsd:documentation>
4380+ </xsd:annotation>
4381+
4382+ <xsd:simpleContent>
4383+ <xsd:restriction base="javaee:string"/>
4384+ </xsd:simpleContent>
4385+ </xsd:complexType>
4386+
4387+<!-- **************************************************** -->
4388+
4389+ <xsd:complexType name="run-asType">
4390+ <xsd:annotation>
4391+ <xsd:documentation>
4392+
4393+ The run-asType specifies the run-as identity to be
4394+ used for the execution of a component. It contains an
4395+ optional description, and the name of a security role.
4396+
4397+ </xsd:documentation>
4398+ </xsd:annotation>
4399+
4400+ <xsd:sequence>
4401+ <xsd:element name="description"
4402+ type="javaee:descriptionType"
4403+ minOccurs="0"
4404+ maxOccurs="unbounded"/>
4405+ <xsd:element name="role-name"
4406+ type="javaee:role-nameType"/>
4407+ </xsd:sequence>
4408+ <xsd:attribute name="id" type="xsd:ID"/>
4409+ </xsd:complexType>
4410+
4411+<!-- **************************************************** -->
4412+
4413+ <xsd:complexType name="security-role-refType">
4414+ <xsd:annotation>
4415+ <xsd:documentation>
4416+
4417+ The security-role-refType contains the declaration of a
4418+ security role reference in a component's or a
4419+ Deployment Component's code. The declaration consists of an
4420+ optional description, the security role name used in the
4421+ code, and an optional link to a security role. If the
4422+ security role is not specified, the Deployer must choose an
4423+ appropriate security role.
4424+
4425+ </xsd:documentation>
4426+ </xsd:annotation>
4427+
4428+ <xsd:sequence>
4429+ <xsd:element name="description"
4430+ type="javaee:descriptionType"
4431+ minOccurs="0"
4432+ maxOccurs="unbounded"/>
4433+ <xsd:element name="role-name"
4434+ type="javaee:role-nameType">
4435+ <xsd:annotation>
4436+ <xsd:documentation>
4437+
4438+ The value of the role-name element must be the String used
4439+ as the parameter to the
4440+ EJBContext.isCallerInRole(String roleName) method or the
4441+ HttpServletRequest.isUserInRole(String role) method.
4442+
4443+ </xsd:documentation>
4444+ </xsd:annotation>
4445+ </xsd:element>
4446+
4447+ <xsd:element name="role-link"
4448+ type="javaee:role-nameType"
4449+ minOccurs="0">
4450+ <xsd:annotation>
4451+ <xsd:documentation>
4452+
4453+ The role-link element is a reference to a defined
4454+ security role. The role-link element must contain
4455+ the name of one of the security roles defined in the
4456+ security-role elements.
4457+
4458+ </xsd:documentation>
4459+ </xsd:annotation>
4460+ </xsd:element>
4461+ </xsd:sequence>
4462+ <xsd:attribute name="id" type="xsd:ID"/>
4463+ </xsd:complexType>
4464+
4465+<!-- **************************************************** -->
4466+
4467+ <xsd:complexType name="security-roleType">
4468+ <xsd:annotation>
4469+ <xsd:documentation>
4470+ <![CDATA[
4471+
4472+ The security-roleType contains the definition of a security
4473+ role. The definition consists of an optional description of
4474+ the security role, and the security role name.
4475+
4476+ Example:
4477+
4478+ <security-role>
4479+ <description>
4480+ This role includes all employees who are authorized
4481+ to access the employee service application.
4482+ </description>
4483+ <role-name>employee</role-name>
4484+ </security-role>
4485+
4486+ ]]>
4487+ </xsd:documentation>
4488+ </xsd:annotation>
4489+
4490+ <xsd:sequence>
4491+ <xsd:element name="description"
4492+ type="javaee:descriptionType"
4493+ minOccurs="0"
4494+ maxOccurs="unbounded"/>
4495+ <xsd:element name="role-name"
4496+ type="javaee:role-nameType"/>
4497+ </xsd:sequence>
4498+ <xsd:attribute name="id" type="xsd:ID"/>
4499+ </xsd:complexType>
4500+
4501+<!-- **************************************************** -->
4502+
4503+ <xsd:complexType name="string">
4504+ <xsd:annotation>
4505+ <xsd:documentation>
4506+
4507+ This is a special string datatype that is defined by Java EE as
4508+ a base type for defining collapsed strings. When schemas
4509+ require trailing/leading space elimination as well as
4510+ collapsing the existing whitespace, this base type may be
4511+ used.
4512+
4513+ </xsd:documentation>
4514+ </xsd:annotation>
4515+ <xsd:simpleContent>
4516+ <xsd:extension base="xsd:token">
4517+ <xsd:attribute name="id" type="xsd:ID"/>
4518+ </xsd:extension>
4519+ </xsd:simpleContent>
4520+ </xsd:complexType>
4521+
4522+<!-- **************************************************** -->
4523+
4524+ <xsd:complexType name="true-falseType">
4525+ <xsd:annotation>
4526+ <xsd:documentation>
4527+
4528+ This simple type designates a boolean with only two
4529+ permissible values
4530+
4531+ - true
4532+ - false
4533+
4534+ </xsd:documentation>
4535+ </xsd:annotation>
4536+ <xsd:simpleContent>
4537+ <xsd:restriction base="javaee:xsdBooleanType">
4538+ <xsd:pattern value="(true|false)"/>
4539+ </xsd:restriction>
4540+ </xsd:simpleContent>
4541+ </xsd:complexType>
4542+
4543+<!-- **************************************************** -->
4544+
4545+ <xsd:complexType name="url-patternType">
4546+ <xsd:annotation>
4547+ <xsd:documentation>
4548+
4549+ The url-patternType contains the url pattern of the mapping.
4550+ It must follow the rules specified in Section 11.2 of the
4551+ Servlet API Specification. This pattern is assumed to be in
4552+ URL-decoded form and must not contain CR(#xD) or LF(#xA).
4553+ If it contains those characters, the container must inform
4554+ the developer with a descriptive error message.
4555+ The container must preserve all characters including whitespaces.
4556+
4557+ </xsd:documentation>
4558+ </xsd:annotation>
4559+ <xsd:simpleContent>
4560+ <xsd:extension base="xsd:string"/>
4561+ </xsd:simpleContent>
4562+ </xsd:complexType>
4563+
4564+<!-- **************************************************** -->
4565+
4566+ <xsd:complexType name="xsdAnyURIType">
4567+ <xsd:annotation>
4568+ <xsd:documentation>
4569+
4570+ This type adds an "id" attribute to xsd:anyURI.
4571+
4572+ </xsd:documentation>
4573+ </xsd:annotation>
4574+ <xsd:simpleContent>
4575+ <xsd:extension base="xsd:anyURI">
4576+ <xsd:attribute name="id" type="xsd:ID"/>
4577+ </xsd:extension>
4578+ </xsd:simpleContent>
4579+ </xsd:complexType>
4580+
4581+<!-- **************************************************** -->
4582+
4583+ <xsd:complexType name="xsdBooleanType">
4584+ <xsd:annotation>
4585+ <xsd:documentation>
4586+
4587+ This type adds an "id" attribute to xsd:boolean.
4588+
4589+ </xsd:documentation>
4590+ </xsd:annotation>
4591+ <xsd:simpleContent>
4592+ <xsd:extension base="xsd:boolean">
4593+ <xsd:attribute name="id" type="xsd:ID"/>
4594+ </xsd:extension>
4595+ </xsd:simpleContent>
4596+ </xsd:complexType>
4597+
4598+<!-- **************************************************** -->
4599+
4600+ <xsd:complexType name="xsdIntegerType">
4601+ <xsd:annotation>
4602+ <xsd:documentation>
4603+
4604+ This type adds an "id" attribute to xsd:integer.
4605+
4606+ </xsd:documentation>
4607+ </xsd:annotation>
4608+ <xsd:simpleContent>
4609+ <xsd:extension base="xsd:integer">
4610+ <xsd:attribute name="id" type="xsd:ID"/>
4611+ </xsd:extension>
4612+ </xsd:simpleContent>
4613+ </xsd:complexType>
4614+
4615+<!-- **************************************************** -->
4616+
4617+ <xsd:complexType name="xsdNMTOKENType">
4618+ <xsd:annotation>
4619+ <xsd:documentation>
4620+
4621+ This type adds an "id" attribute to xsd:NMTOKEN.
4622+
4623+ </xsd:documentation>
4624+ </xsd:annotation>
4625+ <xsd:simpleContent>
4626+ <xsd:extension base="xsd:NMTOKEN">
4627+ <xsd:attribute name="id" type="xsd:ID"/>
4628+ </xsd:extension>
4629+ </xsd:simpleContent>
4630+ </xsd:complexType>
4631+
4632+<!-- **************************************************** -->
4633+
4634+ <xsd:complexType name="xsdNonNegativeIntegerType">
4635+ <xsd:annotation>
4636+ <xsd:documentation>
4637+
4638+ This type adds an "id" attribute to xsd:nonNegativeInteger.
4639+
4640+ </xsd:documentation>
4641+ </xsd:annotation>
4642+ <xsd:simpleContent>
4643+ <xsd:extension base="xsd:nonNegativeInteger">
4644+ <xsd:attribute name="id" type="xsd:ID"/>
4645+ </xsd:extension>
4646+ </xsd:simpleContent>
4647+ </xsd:complexType>
4648+
4649+<!-- **************************************************** -->
4650+
4651+ <xsd:complexType name="xsdPositiveIntegerType">
4652+ <xsd:annotation>
4653+ <xsd:documentation>
4654+
4655+ This type adds an "id" attribute to xsd:positiveInteger.
4656+
4657+ </xsd:documentation>
4658+ </xsd:annotation>
4659+ <xsd:simpleContent>
4660+ <xsd:extension base="xsd:positiveInteger">
4661+ <xsd:attribute name="id" type="xsd:ID"/>
4662+ </xsd:extension>
4663+ </xsd:simpleContent>
4664+ </xsd:complexType>
4665+
4666+<!-- **************************************************** -->
4667+
4668+ <xsd:complexType name="xsdQNameType">
4669+ <xsd:annotation>
4670+ <xsd:documentation>
4671+
4672+ This type adds an "id" attribute to xsd:QName.
4673+
4674+ </xsd:documentation>
4675+ </xsd:annotation>
4676+ <xsd:simpleContent>
4677+ <xsd:extension base="xsd:QName">
4678+ <xsd:attribute name="id" type="xsd:ID"/>
4679+ </xsd:extension>
4680+ </xsd:simpleContent>
4681+ </xsd:complexType>
4682+
4683+<!-- **************************************************** -->
4684+
4685+ <xsd:complexType name="xsdStringType">
4686+ <xsd:annotation>
4687+ <xsd:documentation>
4688+
4689+ This type adds an "id" attribute to xsd:string.
4690+
4691+ </xsd:documentation>
4692+ </xsd:annotation>
4693+ <xsd:simpleContent>
4694+ <xsd:extension base="xsd:string">
4695+ <xsd:attribute name="id" type="xsd:ID"/>
4696+ </xsd:extension>
4697+ </xsd:simpleContent>
4698+ </xsd:complexType>
4699+
4700+</xsd:schema>
4701+
4702Index: jenkins-winstone/src/conf/javax/servlet/resources/javaee_web_services_client_1_2.xsd
4703===================================================================
4704--- /dev/null 1970-01-01 00:00:00.000000000 +0000
4705+++ jenkins-winstone/src/conf/javax/servlet/resources/javaee_web_services_client_1_2.xsd 2011-08-18 09:36:00.211504693 +0100
4706@@ -0,0 +1,585 @@
4707+<?xml version="1.0" encoding="UTF-8"?>
4708+<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
4709+ targetNamespace="http://java.sun.com/xml/ns/javaee"
4710+ xmlns:javaee="http://java.sun.com/xml/ns/javaee"
4711+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
4712+ elementFormDefault="qualified"
4713+ attributeFormDefault="unqualified"
4714+ version="1.2">
4715+ <xsd:annotation>
4716+ <xsd:documentation>
4717+ @(#)javaee_web_services_client_1_2.xsds 1.19 02/13/06
4718+ </xsd:documentation>
4719+ </xsd:annotation>
4720+
4721+ <xsd:annotation>
4722+ <xsd:documentation>
4723+
The diff has been truncated for viewing.

Subscribers

People subscribed via source and target branches

to all changes: