removed Sun J2EE files due to licensing concerns
git-svn-id: https://svn.apache.org/repos/asf/xmlbeans/trunk@1917899 13f79535-47bb-0310-9956-ffa450edef68
diff --git a/build.gradle b/build.gradle
index 452e8f8..9b16bae 100644
--- a/build.gradle
+++ b/build.gradle
@@ -445,7 +445,6 @@
'**/zvon*.xml',
'**/xmldsig-core-schema.xsd',
'src/test/resources/xbean/xmlobject/japanese',
- 'src/test/resources/xbean/compile/scomp/j2ee',
'src/test/resources/xbean/dom/W3C/level2/core/files',
'src/test/resources/xbean/xmlobject/soap-envelope.xsd',
'src/test/resources/xbean/xmlobject/soap12-encoding.xsd',
diff --git a/src/test/java/compile/scomp/checkin/CompilationTests.java b/src/test/java/compile/scomp/checkin/CompilationTests.java
index 68a197e..a374905 100644
--- a/src/test/java/compile/scomp/checkin/CompilationTests.java
+++ b/src/test/java/compile/scomp/checkin/CompilationTests.java
@@ -135,38 +135,6 @@
"</xs:schema>\n",
};
-
- @Test
- void testJ2EE() {
- deltree(xbeanOutput("compile/scomp/j2ee"));
- // First, compile schema
- File srcdir = xbeanOutput("compile/scomp/j2ee/j2eeconfigxml/src");
- File classesdir = xbeanOutput("compile/scomp/j2ee/j2eeconfigxml/classes");
- File outputjar = xbeanOutput("compile/scomp/j2ee/j2eeconfigxml.jar");
- Parameters params = new Parameters();
- params.setXsdFiles(
- xbeanCase("j2ee/application-client_1_4.xsd"),
- xbeanCase("j2ee/application_1_4.xsd"),
- xbeanCase("j2ee/connector_1_5.xsd"),
- xbeanCase("j2ee/ejb-jar_2_1.xsd"),
- xbeanCase("j2ee/j2ee_1_4.xsd"),
- xbeanCase("j2ee/jsp_2_0.xsd"),
- xbeanCase("j2ee/web-app_2_4.xsd"),
- xbeanCase("j2ee/XML.xsd"));
- params.setSrcDir(srcdir);
- params.setClassesDir(classesdir);
- params.setOutputJar(outputjar);
- params.setMdefNamespaces(Collections.singleton("http://java.sun.com/xml/ns/j2ee"));
- List<XmlError> errors = new ArrayList<>();
- params.setErrorListener(errors);
- boolean result = SchemaCompiler.compile(params);
- StringWriter message = new StringWriter();
- if (!result)
- dumpErrors(errors, new PrintWriter(message));
- assertTrue(result, "Build failed:" + message);
- assertTrue(outputjar.exists(), "Cannot find " + outputjar);
- }
-
@Test
void testIncrementalCompilation() throws IOException, XmlException {
File[] files = new File[]{
@@ -192,7 +160,7 @@
XmlOptions options = (new XmlOptions()).setErrorListener(errors);
SchemaTypeSystem builtin = XmlBeans.getBuiltinTypeSystem();
system = XmlBeans.compileXsd(schemas, builtin, options);
- assertNotNull(system, "Compilation failed during inititial compile.");
+ assertNotNull(system, "Compilation failed during initial compile.");
System.out.println("-= Initial Compile =-");
for (int i = 0; i < system.globalTypes().length; i++) {
@@ -332,41 +300,6 @@
}
@Test
- @Disabled
- public void testDownload() {
- deltree(xbeanOutput("compile/scomp/include"));
-
- {
- // First, compile schema without download and verify failure
- File srcdir = xbeanOutput("compile/scomp/include/shouldfail/src");
- File classesdir = xbeanOutput("compile/scomp/include/shouldfail/classes");
- File outputjar = xbeanOutput("compile/scomp/include/shouldfail.jar");
- Parameters params = new Parameters();
- params.setXsdFiles(xbeanCase("compile/scomp/j2ee/j2ee_1_4.xsd"));
- params.setSrcDir(srcdir);
- params.setClassesDir(classesdir);
- params.setOutputJar(outputjar);
- assertFalse(SchemaCompiler.compile(params), "Build should have failed");
- assertFalse(outputjar.exists(), "Should not have created " + outputjar);
- }
-
- {
- // now turn on download and verify success
- File srcdir = xbeanOutput("compile/scomp/include/shouldsucceed/src");
- File classesdir = xbeanOutput("compile/scomp/include/shouldsucceed/classes");
- File outputjar = xbeanOutput("compile/scomp/include/shouldsucceed.jar");
- Parameters params = new Parameters();
- params.setDownload(true);
- params.setXsdFiles(xbeanCase("compile/scomp/j2ee/j2ee_1_4.xsd"));
- params.setSrcDir(srcdir);
- params.setClassesDir(classesdir);
- params.setOutputJar(outputjar);
- assertTrue(SchemaCompiler.compile(params), "Build failed");
- assertTrue(outputjar.exists(), "Cannot find " + outputjar);
- }
- }
-
- @Test
void testPricequote() {
deltree(xbeanOutput("compile/scomp/pricequote"));
// First, compile schema
diff --git a/src/test/resources/xbean/compile/scomp/j2ee/XML.xsd b/src/test/resources/xbean/compile/scomp/j2ee/XML.xsd
deleted file mode 100755
index e8172d7..0000000
--- a/src/test/resources/xbean/compile/scomp/j2ee/XML.xsd
+++ /dev/null
@@ -1,285 +0,0 @@
-<?xml version='1.0'?>
-<xs:schema targetNamespace="http://www.w3.org/XML/1998/namespace"
- xmlns:xs="http://www.w3.org/2001/XMLSchema"
- xmlns ="http://www.w3.org/1999/xhtml"
- xml:lang="en">
-
- <xs:annotation>
- <xs:documentation>
- <div>
- <h1>About the XML namespace</h1>
-
- <div class="bodytext">
- <p>
- This schema document describes the XML namespace, in a form
- suitable for import by other schema documents.
- </p>
- <p>
- See <a href="http://www.w3.org/XML/1998/namespace.html">
- http://www.w3.org/XML/1998/namespace.html</a> and
- <a href="http://www.w3.org/TR/REC-xml">
- http://www.w3.org/TR/REC-xml</a> for information
- about this namespace.
- </p>
- <p>
- Note that local names in this namespace are intended to be
- defined only by the World Wide Web Consortium or its subgroups.
- The names currently defined in this namespace are listed below.
- They should not be used with conflicting semantics by any Working
- Group, specification, or document instance.
- </p>
- <p>
- See further below in this document for more information about <a
- href="#usage">how to refer to this schema document from your own
- XSD schema documents</a> and about <a href="#nsversioning">the
- namespace-versioning policy governing this schema document</a>.
- </p>
- </div>
- </div>
- </xs:documentation>
- </xs:annotation>
-
- <xs:attribute name="lang">
- <xs:annotation>
- <xs:documentation>
- <div>
-
- <h3>lang (as an attribute name)</h3>
- <p>
- denotes an attribute whose value
- is a language code for the natural language of the content of
- any element; its value is inherited. This name is reserved
- by virtue of its definition in the XML specification.</p>
-
- </div>
- <div>
- <h4>Notes</h4>
- <p>
- Attempting to install the relevant ISO 2- and 3-letter
- codes as the enumerated possible values is probably never
- going to be a realistic possibility.
- </p>
- <p>
- See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">
- http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>
- and the IANA language subtag registry at
- <a href="http://www.iana.org/assignments/language-subtag-registry">
- http://www.iana.org/assignments/language-subtag-registry</a>
- for further information.
- </p>
- <p>
- The union allows for the 'un-declaration' of xml:lang with
- the empty string.
- </p>
- </div>
- </xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:union memberTypes="xs:language">
- <xs:simpleType>
- <xs:restriction base="xs:string">
- <xs:enumeration value=""/>
- </xs:restriction>
- </xs:simpleType>
- </xs:union>
- </xs:simpleType>
- </xs:attribute>
-
- <xs:attribute name="space">
- <xs:annotation>
- <xs:documentation>
- <div>
-
- <h3>space (as an attribute name)</h3>
- <p>
- denotes an attribute whose
- value is a keyword indicating what whitespace processing
- discipline is intended for the content of the element; its
- value is inherited. This name is reserved by virtue of its
- definition in the XML specification.</p>
-
- </div>
- </xs:documentation>
- </xs:annotation>
- <xs:simpleType>
- <xs:restriction base="xs:NCName">
- <xs:enumeration value="default"/>
- <xs:enumeration value="preserve"/>
- </xs:restriction>
- </xs:simpleType>
- </xs:attribute>
-
- <xs:attribute name="base" type="xs:anyURI"> <xs:annotation>
- <xs:documentation>
- <div>
-
- <h3>base (as an attribute name)</h3>
- <p>
- denotes an attribute whose value
- provides a URI to be used as the base for interpreting any
- relative URIs in the scope of the element on which it
- appears; its value is inherited. This name is reserved
- by virtue of its definition in the XML Base specification.</p>
-
- <p>
- See <a
- href="http://www.w3.org/TR/xmlbase/">http://www.w3.org/TR/xmlbase/</a>
- for information about this attribute.
- </p>
- </div>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
-
- <xs:attribute name="id" type="xs:ID">
- <xs:annotation>
- <xs:documentation>
- <div>
-
- <h3>id (as an attribute name)</h3>
- <p>
- denotes an attribute whose value
- should be interpreted as if declared to be of type ID.
- This name is reserved by virtue of its definition in the
- xml:id specification.</p>
-
- <p>
- See <a
- href="http://www.w3.org/TR/xml-id/">http://www.w3.org/TR/xml-id/</a>
- for information about this attribute.
- </p>
- </div>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
-
- <xs:attributeGroup name="specialAttrs">
- <xs:attribute ref="xml:base"/>
- <xs:attribute ref="xml:lang"/>
- <xs:attribute ref="xml:space"/>
- <xs:attribute ref="xml:id"/>
- </xs:attributeGroup>
-
- <xs:annotation>
- <xs:documentation>
- <div>
-
- <h3>Father (in any context at all)</h3>
-
- <div class="bodytext">
- <p>
- denotes Jon Bosak, the chair of
- the original XML Working Group. This name is reserved by
- the following decision of the W3C XML Plenary and
- XML Coordination groups:
- </p>
- <blockquote>
- <p>
- In appreciation for his vision, leadership and
- dedication the W3C XML Plenary on this 10th day of
- February, 2000, reserves for Jon Bosak in perpetuity
- the XML name "xml:Father".
- </p>
- </blockquote>
- </div>
- </div>
- </xs:documentation>
- </xs:annotation>
-
- <xs:annotation>
- <xs:documentation>
- <div xml:id="usage" id="usage">
- <h2><a name="usage">About this schema document</a></h2>
-
- <div class="bodytext">
- <p>
- This schema defines attributes and an attribute group suitable
- for use by schemas wishing to allow <code>xml:base</code>,
- <code>xml:lang</code>, <code>xml:space</code> or
- <code>xml:id</code> attributes on elements they define.
- </p>
- <p>
- To enable this, such a schema must import this schema for
- the XML namespace, e.g. as follows:
- </p>
- <pre>
- <schema . . .>
- . . .
- <import namespace="http://www.w3.org/XML/1998/namespace"
- schemaLocation="http://www.w3.org/2001/xml.xsd"/>
- </pre>
- <p>
- or
- </p>
- <pre>
- <import namespace="http://www.w3.org/XML/1998/namespace"
- schemaLocation="http://www.w3.org/2009/01/xml.xsd"/>
- </pre>
- <p>
- Subsequently, qualified reference to any of the attributes or the
- group defined below will have the desired effect, e.g.
- </p>
- <pre>
- <type . . .>
- . . .
- <attributeGroup ref="xml:specialAttrs"/>
- </pre>
- <p>
- will define a type which will schema-validate an instance element
- with any of those attributes.
- </p>
- </div>
- </div>
- </xs:documentation>
- </xs:annotation>
-
- <xs:annotation>
- <xs:documentation>
- <div id="nsversioning" xml:id="nsversioning">
- <h2><a name="nsversioning">Versioning policy for this schema document</a></h2>
- <div class="bodytext">
- <p>
- In keeping with the XML Schema WG's standard versioning
- policy, this schema document will persist at
- <a href="http://www.w3.org/2009/01/xml.xsd">
- http://www.w3.org/2009/01/xml.xsd</a>.
- </p>
- <p>
- At the date of issue it can also be found at
- <a href="http://www.w3.org/2001/xml.xsd">
- http://www.w3.org/2001/xml.xsd</a>.
- </p>
- <p>
- The schema document at that URI may however change in the future,
- in order to remain compatible with the latest version of XML
- Schema itself, or with the XML namespace itself. In other words,
- if the XML Schema or XML namespaces change, the version of this
- document at <a href="http://www.w3.org/2001/xml.xsd">
- http://www.w3.org/2001/xml.xsd
- </a>
- will change accordingly; the version at
- <a href="http://www.w3.org/2009/01/xml.xsd">
- http://www.w3.org/2009/01/xml.xsd
- </a>
- will not change.
- </p>
- <p>
- Previous dated (and unchanging) versions of this schema
- document are at:
- </p>
- <ul>
- <li><a href="http://www.w3.org/2009/01/xml.xsd">
- http://www.w3.org/2009/01/xml.xsd</a></li>
- <li><a href="http://www.w3.org/2007/08/xml.xsd">
- http://www.w3.org/2007/08/xml.xsd</a></li>
- <li><a href="http://www.w3.org/2004/10/xml.xsd">
- http://www.w3.org/2004/10/xml.xsd</a></li>
- <li><a href="http://www.w3.org/2001/03/xml.xsd">
- http://www.w3.org/2001/03/xml.xsd</a></li>
- </ul>
- </div>
- </div>
- </xs:documentation>
- </xs:annotation>
-
-</xs:schema>
diff --git a/src/test/resources/xbean/compile/scomp/j2ee/application-client_1_4.xsd b/src/test/resources/xbean/compile/scomp/j2ee/application-client_1_4.xsd
deleted file mode 100755
index 9602c0a..0000000
--- a/src/test/resources/xbean/compile/scomp/j2ee/application-client_1_4.xsd
+++ /dev/null
@@ -1,276 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
- targetNamespace="http://java.sun.com/xml/ns/j2ee"
- xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- elementFormDefault="qualified"
- attributeFormDefault="unqualified"
- version="1.4">
-<xsd:annotation>
-<xsd:documentation>
-@(#)application-client_1_4.xsds 1.7 07/08/02
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:annotation>
-<xsd:documentation>
-
-Copyright 2002 Sun Microsystems, Inc., 901 San Antonio
-Road, Palo Alto, California 94303, U.S.A. All rights
-reserved.
-
-Sun Microsystems, Inc. has intellectual property rights
-relating to technology described in this document. In
-particular, and without limitation, these intellectual
-property rights may include one or more of the U.S. patents
-listed at http://www.sun.com/patents and one or more
-additional patents or pending patent applications in the
-U.S. and other countries.
-
-This document and the technology which it describes are
-distributed under licenses restricting their use, copying,
-distribution, and decompilation. No part of this document
-may be reproduced in any form by any means without prior
-written authorization of Sun and its licensors, if any.
-
-Third-party software, including font technology, is
-copyrighted and licensed from Sun suppliers.
-
-Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
-JavaServer Pages, Enterprise JavaBeans and the Java Coffee
-Cup logo are trademarks or registered trademarks of Sun
-Microsystems, Inc. in the U.S. and other countries.
-
-Federal Acquisitions: Commercial Software - Government Users
-Subject to Standard License Terms and Conditions.
-
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:annotation>
-<xsd:documentation>
-<![CDATA[
-This is the XML Schema for the application client 1.4
-deployment descriptor. All application client deployment
-descriptors must indicate the application client
-schema by using the J2EE namespace:
-
-http://java.sun.com/xml/ns/j2ee
-
-and by indicating the version of the schema by
-using the version element as shown below:
-
- <application-client xmlns="http://java.sun.com/xml/ns/j2ee"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
- http://java.sun.com/xml/ns/j2ee/application-client_1_4.xsd"
- version="1.4">
-
- ...
- </application-client>
-]]>
-The instance documents may indicate the published version of
-the schema using the xsi:schemaLocation attribute for J2EE
-namespace with the following location:
-
-http://java.sun.com/xml/ns/j2ee/application-client_1_4.xsd
-
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:annotation>
-<xsd:documentation>
-
-The following conventions apply to all J2EE
-deployment descriptor elements unless indicated otherwise.
-
-- In elements that specify a pathname to a file within the
- same JAR file, relative filenames (i.e., those not
- starting with "/") are considered relative to the root of
- the JAR file's namespace. Absolute filenames (i.e., those
- starting with "/") also specify names in the root of the
- JAR file's namespace. In general, relative names are
- preferred. The exception is .war files where absolute
- names are preferred for consistency with the Servlet API.
-
-</xsd:documentation>
-</xsd:annotation>
-
-<include schemaLocation="j2ee_1_4.xsd"/>
-
-
-<!-- **************************************************** -->
-
-
-<xsd:element name="application-client" type="j2ee:application-clientType">
- <xsd:annotation>
- <xsd:documentation>
-
- The application-client element is the root element of an
- application client deployment descriptor. The application
- client deployment descriptor describes the EJB components
- and external resources referenced by the application
- client.
-
- </xsd:documentation>
- </xsd:annotation>
-
- <xsd:unique name="env-entry-name-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The env-entry-name element contains the name of an
- application client's environment entry. The name is a JNDI
- name relative to the java:comp/env context. The name must
- be unique within an application client.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:env-entry"/>
- <xsd:field xpath="j2ee:env-entry-name"/>
- </xsd:unique>
-
- <xsd:unique name="ejb-ref-name-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The ejb-ref-name element contains the name of an EJB
- reference. The EJB reference is an entry in the application
- client's environment and is relative to the
- java:comp/env context. The name must be unique within the
- application client.
-
- It is recommended that name is prefixed with "ejb/".
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:ejb-ref"/>
- <xsd:field xpath="j2ee:ejb-ref-name"/>
- </xsd:unique>
-
- <xsd:unique name="res-ref-name-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The res-ref-name element specifies the name of a
- resource manager connection factory reference.The name
- is a JNDI name relative to the java:comp/env context.
- The name must be unique within an application client.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:resource-ref"/>
- <xsd:field xpath="j2ee:res-ref-name"/>
- </xsd:unique>
-
- <xsd:unique name="resource-env-ref-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The resource-env-ref-name element specifies the name of
- a resource environment reference; its value is the
- environment entry name used in the application client
- code. The name is a JNDI name relative to the
- java:comp/env context and must be unique within an
- application client.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:resource-env-ref"/>
- <xsd:field xpath="j2ee:resource-env-ref-name"/>
- </xsd:unique>
-
- <xsd:unique name="message-destination-ref-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The message-destination-ref-name element specifies the
- name of a message destination reference; its value is
- the message destination reference name used in the
- application client code. The name is a JNDI name
- relative to the java:comp/env context and must be unique
- within an application client.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:message-destination-ref"/>
- <xsd:field xpath="j2ee:message-destination-ref-name"/>
- </xsd:unique>
-
-</xsd:element>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="application-clientType">
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="display-name"
- type="j2ee:display-nameType"
- maxOccurs="unbounded"/>
- <xsd:element name="icon"
- type="j2ee:iconType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="env-entry"
- type="j2ee:env-entryType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="ejb-ref"
- type="j2ee:ejb-refType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="resource-ref"
- type="j2ee:resource-refType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="resource-env-ref"
- type="j2ee:resource-env-refType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="message-destination-ref"
- type="j2ee:message-destination-refType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="callback-handler"
- type="j2ee:fully-qualified-classType"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- The callback-handler element names a class provided by
- the application. The class must have a no args
- constructor and must implement the
- javax.security.auth.callback.CallbackHandler
- interface. The class will be instantiated by the
- application client container and used by the container
- to collect authentication information from the user.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="message-destination"
- type="j2ee:message-destinationType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="deployment-extension"
- type="j2ee:deployment-extensionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
-
- </xsd:sequence>
-
- <xsd:attribute name="version"
- type="j2ee:dewey-versionType"
- fixed="1.4"
- use="required">
- <xsd:annotation>
- <xsd:documentation>
-
- The required value for the version is 1.4.
-
- </xsd:documentation>
- </xsd:annotation>
-
- </xsd:attribute>
-
-</xsd:complexType>
-
-</xsd:schema>
-
diff --git a/src/test/resources/xbean/compile/scomp/j2ee/application_1_4.xsd b/src/test/resources/xbean/compile/scomp/j2ee/application_1_4.xsd
deleted file mode 100755
index ac57583..0000000
--- a/src/test/resources/xbean/compile/scomp/j2ee/application_1_4.xsd
+++ /dev/null
@@ -1,329 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
- targetNamespace="http://java.sun.com/xml/ns/j2ee"
- xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- elementFormDefault="qualified"
- attributeFormDefault="unqualified"
- version="1.4">
-<xsd:annotation>
-<xsd:documentation>
-@(#)application_1_4.xsds 1.6 08/09/02
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:annotation>
-<xsd:documentation>
-
-Copyright 2002 Sun Microsystems, Inc., 901 San Antonio
-Road, Palo Alto, California 94303, U.S.A. All rights
-reserved.
-
-Sun Microsystems, Inc. has intellectual property rights
-relating to technology described in this document. In
-particular, and without limitation, these intellectual
-property rights may include one or more of the U.S. patents
-listed at http://www.sun.com/patents and one or more
-additional patents or pending patent applications in the
-U.S. and other countries.
-
-This document and the technology which it describes are
-distributed under licenses restricting their use, copying,
-distribution, and decompilation. No part of this document
-may be reproduced in any form by any means without prior
-written authorization of Sun and its licensors, if any.
-
-Third-party software, including font technology, is
-copyrighted and licensed from Sun suppliers.
-
-Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
-JavaServer Pages, Enterprise JavaBeans and the Java Coffee
-Cup logo are trademarks or registered trademarks of Sun
-Microsystems, Inc. in the U.S. and other countries.
-
-Federal Acquisitions: Commercial Software - Government Users
-Subject to Standard License Terms and Conditions.
-
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:annotation>
-<xsd:documentation>
-<![CDATA[
-This is the XML Schema for the application 1.4 deployment
-descriptor. All application deployment descriptors must
-indicate that the schema by using the J2EE namespace
-
-http://java.sun.com/xml/ns/j2ee
-
-and by indicating the version of the schema by
-using the version element as shown below:
-
- <application xmlns="http://java.sun.com/xml/ns/j2ee"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
- http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"
- version="1.4">
-
- ...
- </application>
-
-The instance documents may indicate the published version of
-the schema using the xsi:schemaLocation attribute for J2EE
-namespace with the following location:
-
-http://java.sun.com/xml/ns/j2ee/application_1_4.xsd
-]]>
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:annotation>
-<xsd:documentation>
-
-The following conventions apply to all J2EE
-deployment descriptor elements unless indicated otherwise.
-
-- In elements that specify a pathname to a file within the
- same JAR file, relative filenames (i.e., those not
- starting with "/") are considered relative to the root of
- the JAR file's namespace. Absolute filenames (i.e., those
- starting with "/") also specify names in the root of the
- JAR file's namespace. In general, relative names are
- preferred. The exception is .war files where absolute
- names are preferred for consistency with the Servlet API.
-
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:include schemaLocation="j2ee_1_4.xsd"/>
-
-
-<!-- **************************************************** -->
-
-
-<xsd:element name="application" type="j2ee:applicationType">
- <xsd:annotation>
- <xsd:documentation>
-
- The application element is the root element of a J2EE
- application deployment descriptor.
-
- </xsd:documentation>
- </xsd:annotation>
-
- <xsd:unique name="context-root-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The context-root element content must be unique
- in the ear.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:module/j2ee:web"/>
- <xsd:field xpath="j2ee:context-root"/>
- </xsd:unique>
-
- <xsd:unique name="security-role-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The security-role-name element content
- must be unique in the ear.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:security-role"/>
- <xsd:field xpath="j2ee:role-name"/>
- </xsd:unique>
-
-</xsd:element>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="applicationType">
-<xsd:annotation>
-<xsd:documentation>
-
-The applicationType defines the structure of the
-application.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="display-name"
- type="j2ee:display-nameType"
- maxOccurs="unbounded"/>
- <xsd:element name="icon"
- type="j2ee:iconType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="module"
- type="j2ee:moduleType"
- maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
-
- The application deployment descriptor must have one
- module element for each J2EE module in the
- application package. A module element is defined
- by moduleType definition.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="security-role"
- type="j2ee:security-roleType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="deployment-extension"
- type="j2ee:deployment-extensionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- </xsd:sequence>
- <xsd:attribute name="version"
- type="j2ee:dewey-versionType"
- fixed="1.4"
- use="required">
- <xsd:annotation>
- <xsd:documentation>
-
- The required value for the version is 1.4.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:attribute>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="moduleType">
-<xsd:annotation>
-<xsd:documentation>
-
-The moduleType defines a single J2EE module and contains a
-connector, ejb, java, or web element, which indicates the
-module type and contains a path to the module file, and an
-optional alt-dd element, which specifies an optional URI to
-the post-assembly version of the deployment descriptor.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:choice>
- <xsd:element name="connector"
- type="j2ee:pathType">
- <xsd:annotation>
- <xsd:documentation>
-
- The connector element specifies the URI of a
- resource adapter archive file, relative to the
- top level of the application package.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="ejb"
- type="j2ee:pathType">
- <xsd:annotation>
- <xsd:documentation>
-
- The ejb element specifies the URI of an ejb-jar,
- relative to the top level of the application
- package.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="java"
- type="j2ee:pathType">
- <xsd:annotation>
- <xsd:documentation>
-
- The java element specifies the URI of a java
- application client module, relative to the top
- level of the application package.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="web"
- type="j2ee:webType"/>
- </xsd:choice>
- <xsd:element name="alt-dd"
- type="j2ee:pathType"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- The alt-dd element specifies an optional URI to the
- post-assembly version of the deployment descriptor
- file for a particular J2EE module. The URI must
- specify the full pathname of the deployment
- descriptor file relative to the application's root
- directory. If alt-dd is not specified, the deployer
- must read the deployment descriptor from the default
- location and file name required by the respective
- component specification.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="deployment-extension"
- type="j2ee:deployment-extensionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
-
- </xsd:sequence>
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="webType">
-<xsd:annotation>
-<xsd:documentation>
-
-The webType defines the web-uri and context-root of
-a web application module.
-
-</xsd:documentation>
-</xsd:annotation>
- <xsd:sequence>
- <xsd:element name="web-uri"
- type="j2ee:pathType">
- <xsd:annotation>
- <xsd:documentation>
-
- The web-uri element specifies the URI of a web
- application file, relative to the top level of the
- application package.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="context-root"
- type="j2ee:string">
-
- <xsd:annotation>
- <xsd:documentation>
-
- The context-root element specifies the context root
- of a web application.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="deployment-extension"
- type="j2ee:deployment-extensionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- </xsd:sequence>
-</xsd:complexType>
-
-</xsd:schema>
-
diff --git a/src/test/resources/xbean/compile/scomp/j2ee/connector_1_5.xsd b/src/test/resources/xbean/compile/scomp/j2ee/connector_1_5.xsd
deleted file mode 100755
index 2b7728c..0000000
--- a/src/test/resources/xbean/compile/scomp/j2ee/connector_1_5.xsd
+++ /dev/null
@@ -1,1011 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
- targetNamespace="http://java.sun.com/xml/ns/j2ee"
- xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- elementFormDefault="qualified"
- attributeFormDefault="unqualified"
- version="1.5">
-<xsd:annotation>
-<xsd:documentation>
-@(#)connector_1_5.xsds 1.16 07/06/02
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:annotation>
-<xsd:documentation>
-
-Copyright 2002 Sun Microsystems, Inc., 901 San Antonio
-Road, Palo Alto, California 94303, U.S.A. All rights
-reserved.
-
-Sun Microsystems, Inc. has intellectual property rights
-relating to technology described in this document. In
-particular, and without limitation, these intellectual
-property rights may include one or more of the U.S. patents
-listed at http://www.sun.com/patents and one or more
-additional patents or pending patent applications in the
-U.S. and other countries.
-
-This document and the technology which it describes are
-distributed under licenses restricting their use, copying,
-distribution, and decompilation. No part of this document
-may be reproduced in any form by any means without prior
-written authorization of Sun and its licensors, if any.
-
-Third-party software, including font technology, is
-copyrighted and licensed from Sun suppliers.
-
-Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
-JavaServer Pages, Enterprise JavaBeans and the Java Coffee
-Cup logo are trademarks or registered trademarks of Sun
-Microsystems, Inc. in the U.S. and other countries.
-
-Federal Acquisitions: Commercial Software - Government Users
-Subject to Standard License Terms and Conditions.
-
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:annotation>
-<xsd:documentation>
-<![CDATA[
-This is the XML Schema for the Connector 1.5 deployment
-descriptor. All Connector deployment descriptors must
-indicate the connector resource adapter schema by using the
-J2EE namespace:
-
-http://java.sun.com/xml/ns/j2ee
-
-and by indicating the version of the schema by
-using the version element as shown below:
-
- <connector xmlns="http://java.sun.com/xml/ns/j2ee"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
- http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd"
- version="1.5">
- ...
- </connector>
-
-The instance documents may indicate the published version of
-the schema using the xsi:schemaLocation attribute for J2EE
-namespace with the following location:
-
-http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd
-]]>
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:annotation>
-<xsd:documentation>
-
-The following conventions apply to all J2EE
-deployment descriptor elements unless indicated otherwise.
-
-- In elements that specify a pathname to a file within the
- same JAR file, relative filenames (i.e., those not
- starting with "/") are considered relative to the root of
- the JAR file's namespace. Absolute filenames (i.e., those
- starting with "/") also specify names in the root of the
- JAR file's namespace. In general, relative names are
- preferred. The exception is .war files where absolute
- names are preferred for consistency with the Servlet API.
-
-</xsd:documentation>
-</xsd:annotation>
-
-<include schemaLocation="j2ee_1_4.xsd"/>
-
-
-<!-- **************************************************** -->
-
-
-<xsd:element name="connector" type="j2ee:connectorType">
-<xsd:annotation>
-<xsd:documentation>
-
-The connector element is the root element of the deployment
-descriptor for the resource adapter. This element includes
-general information - vendor name, resource adapter version,
-icon - about the resource adapter module. It also includes
-information specific to the implementation of the resource
-adapter library as specified through the element
-resourceadapter.
-
-</xsd:documentation>
-</xsd:annotation>
-
-</xsd:element>
-
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="activationspecType">
-<xsd:annotation>
-<xsd:documentation>
-
-The activationspecType specifies an activation
-specification. The information includes fully qualified
-Java class name of an activation specification and a set of
-required configuration property names.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="activationspec-class"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
-
- The element activationspec-class specifies the fully
- qualified Java class name of the activation
- specification class. This class must implement the
- javax.resource.spi.ActivationSpec interface. The
- implementation of this class is required to be a
- JavaBean.
-
- Example:
- <activationspec-class>com.wombat.ActivationSpecImpl
- </activationspec-class>
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="required-config-property"
- type="j2ee:required-config-propertyType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="adminobjectType">
-<xsd:annotation>
-<xsd:documentation>
-
-The adminobjectType specifies information about an
-administered object. Administered objects are specific to a
-messaging style or message provider. This contains
-information on the Java type of the interface implemented by
-an administered object, its Java class name and its
-configuration properties.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="adminobject-interface"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
-
- The element adminobject-interface specifies the
- fully qualified name of the Java type of the
- interface implemented by an administered object.
-
- Example:
- <adminobject-interface>javax.jms.Destination
- </adminobject-interface>
-
- </xsd:documentation>
- </xsd:annotation>
-
- </xsd:element>
- <xsd:element name="adminobject-class"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
-
- The element adminobject-class specifies the fully
- qualified Java class name of an administered object.
-
- Example:
- <adminobject-class>com.wombat.DestinationImpl
- </adminobject-class>
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
-
- <xsd:element name="config-property"
- type="j2ee:config-propertyType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="authentication-mechanismType">
-<xsd:annotation>
-<xsd:documentation>
-
-The authentication-mechanismType specifies an authentication
-mechanism supported by the resource adapter. Note that this
-support is for the resource adapter and not for the
-underlying EIS instance. The optional description specifies
-any resource adapter specific requirement for the support of
-security contract and authentication mechanism.
-
-Note that BasicPassword mechanism type should support the
-javax.resource.spi.security.PasswordCredential interface.
-The Kerbv5 mechanism type should support the
-org.ietf.jgss.GSSCredential interface or the deprecated
-javax.resource.spi.security.GenericCredential interface.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="authentication-mechanism-type"
- type="xsd:string">
- <xsd:annotation>
- <xsd:documentation>
-
- The element authentication-mechanism-type specifies
- type of an authentication mechanism.
-
- The example values are:
-
- <authentication-mechanism-type>BasicPassword
- </authentication-mechanism-type>
-
- <authentication-mechanism-type>Kerbv5
- </authentication-mechanism-type>
-
- Any additional security mechanisms are outside the
- scope of the Connector architecture specification.
-
- </xsd:documentation>
- </xsd:annotation>
-
- </xsd:element>
- <xsd:element name="credential-interface"
- type="j2ee:credential-interfaceType"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="config-property-nameType">
-<xsd:annotation>
-<xsd:documentation>
-
-The config-property-nameType contains the name of a
-configuration property.
-
-The connector architecture defines a set of well-defined
-properties all of type java.lang.String. These are as
-follows.
-
- ServerName
- PortNumber
- UserName
- Password
- ConnectionURL
-
-A resource adapter provider can extend this property set to
-include properties specific to the resource adapter and its
-underlying EIS.
-
-Possible values include
- ServerName
- PortNumber
- UserName
- Password
- ConnectionURL
-
-Example: <config-property-name>ServerName</config-property-name>
-
-</xsd:documentation>
-</xsd:annotation>
- <xsd:restriction base="xsd:string">
- </xsd:restriction>
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="config-property-typeType">
-<xsd:annotation>
-<xsd:documentation>
-
-The config-property-typeType contains the fully
-qualified Java type of a configuration property.
-
-The following are the legal values:
- java.lang.Boolean, java.lang.String, java.lang.Integer,
- java.lang.Double, java.lang.Byte, java.lang.Short,
- java.lang.Long, java.lang.Float, java.lang.Character
-
-Used in: config-property
-
-Example:
-<config-property-type>java.lang.String</config-property-type>
-
-</xsd:documentation>
-</xsd:annotation>
- <xsd:restriction base="j2ee:string">
- <xsd:enumeration value="java.lang.Boolean"/>
- <xsd:enumeration value="java.lang.String"/>
- <xsd:enumeration value="java.lang.Integer"/>
- <xsd:enumeration value="java.lang.Double"/>
- <xsd:enumeration value="java.lang.Byte"/>
- <xsd:enumeration value="java.lang.Short"/>
- <xsd:enumeration value="java.lang.Long"/>
- <xsd:enumeration value="java.lang.Float"/>
- <xsd:enumeration value="java.lang.Character"/>
- </xsd:restriction>
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="config-propertyType">
-<xsd:annotation>
-<xsd:documentation>
-
-The config-propertyType contains a declaration of a single
-configuration property that may be used for providing
-configuration information.
-
-The declaration consists of an optional description, name,
-type and an optional value of the configuration property. If
-the resource adapter provider does not specify a value than
-the deployer is responsible for providing a valid value for
-a configuration property.
-
-Any bounds or well-defined values of properties should be
-described in the description element.
-
-</xsd:documentation>
-</xsd:annotation>
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="config-property-name"
- type="j2ee:config-property-nameType"/>
- <xsd:element name="config-property-type"
- type="j2ee:config-property-typeType"/>
- <xsd:element name="config-property-value"
- type="xsd:string"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- The element config-property-value contains the value
- of a configuration entry. Note, it is possible for a
- resource adapter deployer to override this
- configuration information during deployment.
-
- Example:
- <config-property-value>WombatServer</config-property-value>
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="connection-definitionType">
-<xsd:annotation>
-<xsd:documentation>
-
-The connection-definitionType defines a set of connection
-interfaces and classes pertaining to a particular connection
-type. This also includes configurable properties for
-ManagedConnectionFactory instances that may be produced out
-of this set.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="managedconnectionfactory-class"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
-
- The element managedconnectionfactory-class specifies
- the fully qualified name of the Java class that
- implements the
- javax.resource.spi.ManagedConnectionFactory interface.
- This Java class is provided as part of resource
- adapter's implementation of connector architecture
- specified contracts. The implementation of this
- class is required to be a JavaBean.
-
- Example:
- <managedconnectionfactory-class>
- com.wombat.ManagedConnectionFactoryImpl
- </managedconnectionfactory-class>
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="config-property"
- type="j2ee:config-propertyType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="connectionfactory-interface"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
-
- The element connectionfactory-interface specifies
- the fully qualified name of the ConnectionFactory
- interface supported by the resource adapter.
-
- Example:
- <connectionfactory-interface>com.wombat.ConnectionFactory
- </connectionfactory-interface>
-
- OR
-
- <connectionfactory-interface>javax.resource.cci.ConnectionFactory
- </connectionfactory-interface>
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
-
- <xsd:element name="connectionfactory-impl-class"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
-
- The element connectionfactory-impl-class specifies
- the fully qualified name of the ConnectionFactory
- class that implements resource adapter
- specific ConnectionFactory interface.
-
- Example:
-
- <connectionfactory-impl-class>com.wombat.ConnectionFactoryImpl
- </connectionfactory-impl-class>
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="connection-interface"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
-
- The connection-interface element specifies the fully
- qualified name of the Connection interface supported
- by the resource adapter.
-
- Example:
-
- <connection-interface>javax.resource.cci.Connection
- </connection-interface>
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="connection-impl-class"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
-
- The connection-impl-classType specifies the fully
- qualified name of the Connection class that
- implements resource adapter specific Connection
- interface. It is used by the connection-impl-class
- elements.
-
- Example:
-
- <connection-impl-class>com.wombat.ConnectionImpl
- </connection-impl-class>
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="connectorType">
-<xsd:annotation>
-<xsd:documentation>
-
-The connectorType defines a resource adapter.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="display-name"
- type="j2ee:display-nameType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="icon"
- type="j2ee:iconType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="vendor-name">
- <xsd:annotation>
- <xsd:documentation>
-
- The element vendor-name specifies the name of
- resource adapter provider vendor.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="eis-type"
- type="xsd:string">
- <xsd:annotation>
- <xsd:documentation>
-
- The element eis-type contains information about the
- type of the EIS. For example, the type of an EIS can
- be product name of EIS independent of any version
- info.
-
- This helps in identifying EIS instances that can be
- used with this resource adapter.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="resourceadapter-version"
- type="xsd:string">
- <xsd:annotation>
- <xsd:documentation>
-
- The element version specifies a string-based version
- of the resource adapter from the resource adapter
- provider.
-
- </xsd:documentation>
- </xsd:annotation>
-
- </xsd:element>
- <xsd:element name="license"
- type="j2ee:licenseType"
- minOccurs="0"/>
- <xsd:element name="resourceadapter"
- type="j2ee:resourceadapterType"/>
- <xsd:element name="deployment-extension"
- type="j2ee:deployment-extensionType"
- minOccurs="0"
- maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
-
- Resource adapter specific extensions can be
- specified by using the deployment-extension
- elements.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
-
- </xsd:sequence>
- <xsd:attribute name="version"
- type="j2ee:dewey-versionType"
- fixed="1.5"
- use="required">
- <xsd:annotation>
- <xsd:documentation>
-
- The version specifies the version of the
- connector architecture specification that is
- supported by this resource adapter. This information
- enables deployer to configure the resource adapter to
- support deployment and runtime requirements of the
- corresponding connector architecture specification.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:attribute>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="credential-interfaceType">
-<xsd:annotation>
-<xsd:documentation>
-
-The credential-interfaceType specifies the
-interface that the resource adapter implementation
-supports for the representation of the
-credentials. This element(s) that use this type,
-i.e. credential-interface, should be used by
-application server to find out the Credential
-interface it should use as part of the security
-contract.
-
-The possible values are:
-
-javax.resource.spi.security.PasswordCredential
-org.ietf.jgss.GSSCredential
-javax.resource.spi.security.GenericCredential
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:fully-qualified-classType">
- <xsd:enumeration
- value="javax.resource.spi.security.PasswordCredential"/>
- <xsd:enumeration
- value="org.ietf.jgss.GSSCredential"/>
- <xsd:enumeration
- value="javax.resource.spi.security.GenericCredential"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="inbound-resourceadapterType">
-<xsd:annotation>
-<xsd:documentation>
-
-The inbound-resourceadapterType specifies information
-about an inbound resource adapter. This contains information
-specific to the implementation of the resource adapter
-library as specified through the messageadapter element.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="messageadapter"
- type="j2ee:messageadapterType"
- minOccurs="0">
- <xsd:unique name="messagelistener-type-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The messagelistener-type element content must be
- unique in the messageadapter. Several messagelisteners
- can not use the same messagelistener-type.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:messagelistener"/>
- <xsd:field xpath="j2ee:messagelistener-type"/>
- </xsd:unique>
- </xsd:element>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="licenseType">
-<xsd:annotation>
-<xsd:documentation>
-
-The licenseType specifies licensing requirements for the
-resource adapter module. This type specifies whether a
-license is required to deploy and use this resource adapter,
-and an optional description of the licensing terms
-(examples: duration of license, number of connection
-restrictions). It is used by the license element.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="license-required"
- type="j2ee:true-falseType">
- <xsd:annotation>
- <xsd:documentation>
-
- The element license-required specifies whether a
- license is required to deploy and use the
- resource adapter. This element must be one of
- the following, "true" or "false".
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- </xsd:sequence>
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="messageadapterType">
-<xsd:annotation>
-<xsd:documentation>
-
-The messageadapterType specifies information about the
-messaging capabilities of the resource adapter. This
-contains information specific to the implementation of the
-resource adapter library as specified through the
-messagelistener element.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="messagelistener"
- type="j2ee:messagelistenerType"
- maxOccurs="unbounded"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="messagelistenerType">
-<xsd:annotation>
-<xsd:documentation>
-
-The messagelistenerType specifies information about a
-specific message listener supported by the messaging
-resource adapter. It contains information on the Java type
-of the message listener interface and an activation
-specification.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="messagelistener-type"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
-
- The element messagelistener-type specifies the fully
- qualified name of the Java type of a message
- listener interface.
-
- Example:
-
- <messagelistener-type>javax.jms.MessageListener
- </messagelistener-type>
-
- </xsd:documentation>
- </xsd:annotation>
-
- </xsd:element>
- <xsd:element name="activationspec"
- type="j2ee:activationspecType"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="outbound-resourceadapterType">
-<xsd:annotation>
-<xsd:documentation>
-
-The outbound-resourceadapterType specifies information about
-an outbound resource adapter. The information includes fully
-qualified names of classes/interfaces required as part of
-the connector architecture specified contracts for
-connection management, level of transaction support
-provided, one or more authentication mechanisms supported
-and additional required security permissions.
-
-If there is no authentication-mechanism specified as part of
-resource adapter element then the resource adapter does not
-support any standard security authentication mechanisms as
-part of security contract. The application server ignores
-the security part of the system contracts in this case.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="connection-definition"
- type="j2ee:connection-definitionType"
- maxOccurs="unbounded"/>
- <xsd:element name="transaction-support"
- type="j2ee:transaction-supportType"/>
- <xsd:element name="authentication-mechanism"
- type="j2ee:authentication-mechanismType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="reauthentication-support"
- type="j2ee:true-falseType">
- <xsd:annotation>
- <xsd:documentation>
-
- The element reauthentication-support specifies
- whether the resource adapter implementation supports
- re-authentication of existing Managed- Connection
- instance. Note that this information is for the
- resource adapter implementation and not for the
- underlying EIS instance. This element must have
- either a "true" or "false" value.
-
- </xsd:documentation>
- </xsd:annotation>
-
- </xsd:element>
- <xsd:element name="security-permission"
- type="j2ee:security-permissionType"
- minOccurs="0"
- maxOccurs="unbounded">
- </xsd:element>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="required-config-propertyType">
-<xsd:annotation>
-<xsd:documentation>
-
-The required-config-propertyType contains a declaration
-of a single configuration property used for specifying a
-required configuration property name. It is used
-by required-config-property elements.
-
-Example:
-
-<required-config-property>Destination</required-config-property>
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="config-property-name"
- type="j2ee:config-property-nameType"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="resourceadapterType">
-<xsd:annotation>
-<xsd:documentation>
-
-The resourceadapterType specifies information about the
-resource adapter. The information includes fully qualified
-resource adapter Java class name, configuration properties,
-information specific to the implementation of the resource
-adapter library as specified through the
-outbound-resourceadapter and inbound-resourceadapter
-elements, and an optional set of administered objects.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="resourceadapter-class"
- type="j2ee:fully-qualified-classType"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- The element resourceadapter-class specifies the
- fully qualified name of a Java class that implements
- the javax.resource.spi.ResourceAdapter
- interface. This Java class is provided as part of
- resource adapter's implementation of connector
- architecture specified contracts. The implementation
- of this class is required to be a JavaBean.
-
- </xsd:documentation>
- </xsd:annotation>
-
- </xsd:element>
- <xsd:element name="config-property"
- type="j2ee:config-propertyType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="outbound-resourceadapter"
- type="j2ee:outbound-resourceadapterType"
- minOccurs="0"/>
- <xsd:element name="inbound-resourceadapter"
- type="j2ee:inbound-resourceadapterType"
- minOccurs="0"/>
- <xsd:element name="adminobject"
- type="j2ee:adminobjectType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="security-permissionType">
-<xsd:annotation>
-<xsd:documentation>
-
-The security-permissionType specifies a security
-permission that is required by the resource adapter code.
-
-The security permission listed in the deployment descriptor
-are ones that are different from those required by the
-default permission set as specified in the connector
-specification. The optional description can mention specific
-reason that resource adapter requires a given security
-permission.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="security-permission-spec"
- type="xsd:string">
- <xsd:annotation>
- <xsd:documentation>
-
- The element permission-spec specifies a security
- permission based on the Security policy file
- syntax. Refer to the following URL for Sun's
- implementation of the security permission
- specification:
-
- http://java.sun.com/products/jdk/1.4/docs/guide/security/PolicyFiles.html#FileSyntax
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="transaction-supportType">
-<xsd:annotation>
-<xsd:documentation>
-
-The transaction-supportType specifies the level of
-transaction support provided by the resource adapter. It is
-used by transaction-support elements.
-
-The value must be one of the following:
-
- NoTransaction
- LocalTransaction
- XATransaction
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:enumeration value="NoTransaction"/>
- <xsd:enumeration value="LocalTransaction"/>
- <xsd:enumeration value="XATransaction"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-</xsd:schema>
-
diff --git a/src/test/resources/xbean/compile/scomp/j2ee/ejb-jar_2_1.xsd b/src/test/resources/xbean/compile/scomp/j2ee/ejb-jar_2_1.xsd
deleted file mode 100755
index 9eb340f..0000000
--- a/src/test/resources/xbean/compile/scomp/j2ee/ejb-jar_2_1.xsd
+++ /dev/null
@@ -1,2383 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
- targetNamespace="http://java.sun.com/xml/ns/j2ee"
- xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- elementFormDefault="qualified"
- attributeFormDefault="unqualified"
- version="2.1">
-<xsd:annotation>
-<xsd:documentation>
-@(#)ejb-jar_2_1.xsds 1.10 07/24/02
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:annotation>
-<xsd:documentation>
-
-Copyright 2002 Sun Microsystems, Inc., 901 San Antonio
-Road, Palo Alto, California 94303, U.S.A. All rights
-reserved.
-
-Sun Microsystems, Inc. has intellectual property rights
-relating to technology described in this document. In
-particular, and without limitation, these intellectual
-property rights may include one or more of the U.S. patents
-listed at http://www.sun.com/patents and one or more
-additional patents or pending patent applications in the
-U.S. and other countries.
-
-This document and the technology which it describes are
-distributed under licenses restricting their use, copying,
-distribution, and decompilation. No part of this document
-may be reproduced in any form by any means without prior
-written authorization of Sun and its licensors, if any.
-
-Third-party software, including font technology, is
-copyrighted and licensed from Sun suppliers.
-
-Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
-JavaServer Pages, Enterprise JavaBeans and the Java Coffee
-Cup logo are trademarks or registered trademarks of Sun
-Microsystems, Inc. in the U.S. and other countries.
-
-Federal Acquisitions: Commercial Software - Government Users
-Subject to Standard License Terms and Conditions.
-
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:annotation>
-<xsd:documentation>
-
-This is the XML Schema for the EJB 2.1 deployment
-descriptor. All EJB deployment descriptors must indicate
-the ejb-jar schema by using the J2EE namespace:
-
-http://java.sun.com/xml/ns/j2ee
-
-and by indicating the version of the schema by
-using the version element as shown below:
-<!--
- <ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
- http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd"
- version="2.1">
- ...
- </ejb-jar>
--->
-The instance documents may indicate the published version of
-the schema using the xsi:schemaLocation attribute for the
-J2EE namespace with the following location:
-
-http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd
-
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:annotation>
-<xsd:documentation>
-
-The following conventions apply to all J2EE
-deployment descriptor elements unless indicated otherwise.
-
-- In elements that specify a pathname to a file within the
- same JAR file, relative filenames (i.e., those not
- starting with "/") are considered relative to the root of
- the JAR file's namespace. Absolute filenames (i.e., those
- starting with "/") also specify names in the root of the
- JAR file's namespace. In general, relative names are
- preferred. The exception is .war files where absolute
- names are preferred for consistency with the Servlet API.
-
-</xsd:documentation>
-</xsd:annotation>
-
-<include schemaLocation="j2ee_1_4.xsd"/>
-
-
-<!-- **************************************************** -->
-
-
-<xsd:element name="ejb-jar" type="j2ee:ejb-jarType">
- <xsd:annotation>
- <xsd:documentation>
-
- This is the root of the ejb-jar deployment descriptor.
-
- </xsd:documentation>
- </xsd:annotation>
-
- <xsd:key name="ejb-name-key">
- <xsd:annotation>
- <xsd:documentation>
-
- The ejb-name element contains the name of an enterprise
- bean. The name must be unique within the ejb-jar file.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:enterprise-beans/*"/>
- <xsd:field xpath="j2ee:ejb-name"/>
- </xsd:key>
-
- <xsd:keyref name="ejb-name-references"
- refer="j2ee:ejb-name-key">
- <xsd:annotation>
- <xsd:documentation>
-
- The keyref indicates the references from
- relationship-role-source must be to a specific ejb-name
- defined within the scope of enterprise-beans element.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector
- xpath=".//j2ee:ejb-relationship-role/j2ee:relationship-role-source"/>
- <xsd:field
- xpath="j2ee:ejb-name"/>
- </xsd:keyref>
-
- <xsd:key name="role-name-key">
- <xsd:annotation>
- <xsd:documentation>
-
- A role-name-key is specified to allow the references
- from the security-role-refs.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:enterprise-beans/*/j2ee:security-role"/>
- <xsd:field xpath="j2ee:role-name"/>
- </xsd:key>
-
- <xsd:keyref name="role-name-references"
- refer="j2ee:role-name-key">
- <xsd:annotation>
- <xsd:documentation>
-
- The keyref indicates the references from
- security-role-ref to a specified role-name.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:enterprise-beans/*/j2ee:security-role-ref"/>
- <xsd:field xpath="j2ee:role-link"/>
- </xsd:keyref>
-
-</xsd:element>
-
-
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="activation-config-propertyType">
-<xsd:annotation>
-<xsd:documentation>
-
-The activation-config-propertyType contains a name/value
-configuration property pair for a message-driven bean.
-
-The properties that are recognized for a particular
-message-driven bean are determined by the messaging type.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="activation-config-property-name"
- type="xsd:string">
- <xsd:annotation>
- <xsd:documentation>
-
- The activation-config-property-name element contains
- the name for an activation configuration property of
- a message-driven bean.
-
- For JMS message-driven beans, the following property
- names are recognized: acknowledgeMode,
- messageSelector, destinationType, subscriptionDurability
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="activation-config-property-value"
- type="xsd:string">
- <xsd:annotation>
- <xsd:documentation>
-
- The activation-config-property-value element
- contains the value for an activation configuration
- property of a message-driven bean.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="activation-configType">
-<xsd:annotation>
-<xsd:documentation>
-
-The activation-configType defines information about the
-expected configuration properties of the message-driven bean
-in its operational environment. This may include information
-about message acknowledgement, message selector, expected
-destination type, etc.
-
-The configuration information is expressed in terms of
-name/value configuration properties.
-
-The properties that are recognized for a particular
-message-driven bean are determined by the messaging type.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="activation-config-property"
- type="j2ee:activation-config-propertyType"
- maxOccurs="unbounded"/>
- <xsd:element name="deployment-extension"
- type="j2ee:deployment-extensionType"
- minOccurs="0" maxOccurs="unbounded"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="assembly-descriptorType">
-<xsd:annotation>
-<xsd:documentation>
-
-The assembly-descriptorType defines
-application-assembly information.
-
-The application-assembly information consists of the
-following parts: the definition of security roles, the
-definition of method permissions, the definition of
-transaction attributes for enterprise beans with
-container-managed transaction demarcation and a list of
-methods to be excluded from being invoked.
-
-All the parts are optional in the sense that they are
-omitted if the lists represented by them are empty.
-
-Providing an assembly-descriptor in the deployment
-descriptor is optional for the ejb-jar file producer.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="security-role"
- type="j2ee:security-roleType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="method-permission"
- type="j2ee:method-permissionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="container-transaction"
- type="j2ee:container-transactionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="message-destination"
- type="j2ee:message-destinationType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="exclude-list"
- type="j2ee:exclude-listType"
- minOccurs="0"/>
- <xsd:element name="deployment-extension"
- type="j2ee:deployment-extensionType"
- minOccurs="0" maxOccurs="unbounded"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="cmp-fieldType">
-<xsd:annotation>
-<xsd:documentation>
-
-The cmp-fieldType describes a container-managed field. The
-cmp-fieldType contains an optional description of the field,
-and the name of the field.
-
-</xsd:documentation>
-</xsd:annotation>
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="field-name"
- type="j2ee:java-identifierType">
- <xsd:annotation>
- <xsd:documentation>
-
- The field-name element specifies the name of a
- container managed field.
-
- The name of the cmp-field of an entity bean with
- cmp-version 2.x must begin with a lowercase
- letter. This field is accessed by methods whose
- names consists of the name of the field specified by
- field-name in which the first letter is uppercased,
- prefixed by "get" or "set".
-
- The name of the cmp-field of an entity bean with
- cmp-version 1.x must denote a public field of the
- enterprise bean class or one of its superclasses.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="deployment-extension"
- type="j2ee:deployment-extensionType"
- minOccurs="0" maxOccurs="unbounded"/>
- </xsd:sequence>
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="cmp-versionType">
-<xsd:annotation>
-<xsd:documentation>
-
-The cmp-versionType specifies the version of an entity bean
-with container-managed persistence. It is used by
-cmp-version elements.
-
-The value must be one of the two following:
-
- 1.x
- 2.x
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:enumeration value="1.x"/>
- <xsd:enumeration value="2.x"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="cmr-field-typeType">
-<xsd:annotation>
-<xsd:documentation>
-
-The cmr-field-type element specifies the class of a
-collection-valued logical relationship field in the entity
-bean class. The value of an element using cmr-field-typeType
-must be either: java.util.Collection or java.util.Set.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:enumeration value="java.util.Collection"/>
- <xsd:enumeration value="java.util.Set"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="cmr-fieldType">
-<xsd:annotation>
-<xsd:documentation>
-
-The cmr-fieldType describes the bean provider's view of
-a relationship. It consists of an optional description, and
-the name and the class type of a field in the source of a
-role of a relationship. The cmr-field-name element
-corresponds to the name used for the get and set accessor
-methods for the relationship. The cmr-field-type element is
-used only for collection-valued cmr-fields. It specifies the
-type of the collection that is used.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="cmr-field-name"
- type="j2ee:string">
- <xsd:annotation>
- <xsd:documentation>
-
- The cmr-field-name element specifies the name of a
- logical relationship field in the entity bean
- class. The name of the cmr-field must begin with a
- lowercase letter. This field is accessed by methods
- whose names consist of the name of the field
- specified by cmr-field-name in which the first
- letter is uppercased, prefixed by "get" or "set".
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="cmr-field-type"
- type="j2ee:cmr-field-typeType"
- minOccurs="0"/>
- <xsd:element name="deployment-extension"
- type="j2ee:deployment-extensionType"
- minOccurs="0" maxOccurs="unbounded"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="container-transactionType">
-<xsd:annotation>
-<xsd:documentation>
-
-The container-transactionType specifies how the container
-must manage transaction scopes for the enterprise bean's
-method invocations. It defines an optional description, a
-list of method elements, and a transaction attribute. The
-transaction attribute is to be applied to all the specified
-methods.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="method"
- type="j2ee:methodType"
- maxOccurs="unbounded"/>
- <xsd:element name="trans-attribute"
- type="j2ee:trans-attributeType"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="ejb-classType">
-<xsd:annotation>
-<xsd:documentation>
-
-The ejb-classType contains the fully-qualified name of the
-enterprise bean's class. It is used by ejb-class elements.
-
-Example:
-
- <ejb-class>com.wombat.empl.EmployeeServiceBean</ejb-class>
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:fully-qualified-classType"/>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="ejb-jarType">
-<xsd:annotation>
-<xsd:documentation>
-
-The ejb-jarType defines the root element of the EJB
-deployment descriptor. It contains
-
- - an optional description of the ejb-jar file
- - an optional display name
- - an optional icon that contains a small and a large
- icon file name
- - mandatory structural information about all included
- enterprise beans
- - a descriptor for container managed relationships,
- if any
- - an optional application-assembly descriptor
- - an optional name of an ejb-client-jar file for the
- ejb-jar.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="display-name"
- type="j2ee:display-nameType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="icon"
- type="j2ee:iconType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="enterprise-beans"
- type="j2ee:enterprise-beansType"/>
- <xsd:element name="relationships"
- type="j2ee:relationshipsType"
- minOccurs="0">
- <xsd:unique name="relationship-name-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The ejb-relation-name contains the name of a
- relation. The name must be unique within
- relationships.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:ejb-relation"/>
- <xsd:field xpath="j2ee:ejb-relation-name"/>
- </xsd:unique>
- </xsd:element>
- <xsd:element name="assembly-descriptor"
- type="j2ee:assembly-descriptorType"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- Providing an assembly-descriptor in the deployment
- descriptor is optional for the ejb-jar file
- producer.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="ejb-client-jar"
- type="j2ee:pathType"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- The optional ejb-client-jar element specifies a JAR
- file that contains the class files necessary for a
- client program to access the
- enterprise beans in the ejb-jar file.
-
- Example:
-
- <ejb-client-jar>employee_service_client.jar
- </ejb-client-jar>
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="deployment-extension"
- type="j2ee:deployment-extensionType"
- minOccurs="0" maxOccurs="unbounded"/>
-
- </xsd:sequence>
- <xsd:attribute name="version"
- type="j2ee:dewey-versionType"
- fixed="2.1"
- use="required">
- <xsd:annotation>
- <xsd:documentation>
-
- The version specifies the version of the
- EJB specification that the instance document must
- comply with. This information enables deployment tools
- to validate a particular EJB Deployment
- Descriptor with respect to a specific version of the EJB
- schema.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:attribute>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="ejb-nameType">
-<xsd:annotation>
-<xsd:documentation>
-
-The ejb-nameType specifies an enterprise bean's name. It is
-used by ejb-name elements. This name is assigned by the
-ejb-jar file producer to name the enterprise bean in the
-ejb-jar file's deployment descriptor. The name must be
-unique among the names of the enterprise beans in the same
-ejb-jar file.
-
-There is no architected relationship between the used
-ejb-name in the deployment descriptor and the JNDI name that
-the Deployer will assign to the enterprise bean's home.
-
-The name for an entity bean must conform to the lexical
-rules for an NMTOKEN.
-
-Example:
-
-<ejb-name>EmployeeService</ejb-name>
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="xsd:NMTOKEN">
- <xsd:whiteSpace value="collapse"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="ejb-relationType">
-<xsd:annotation>
-<xsd:documentation>
-
-The ejb-relationType describes a relationship between two
-entity beans with container-managed persistence. It is used
-by ejb-relation elements. It contains a description; an
-optional ejb-relation-name element; and exactly two
-relationship role declarations, defined by the
-ejb-relationship-role elements. The name of the
-relationship, if specified, is unique within the ejb-jar
-file.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="ejb-relation-name"
- type="j2ee:string"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- The ejb-relation-name element provides a unique name
- within the ejb-jar file for a relationship.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="ejb-relationship-role"
- type="j2ee:ejb-relationship-roleType"/>
- <xsd:element name="ejb-relationship-role"
- type="j2ee:ejb-relationship-roleType"/>
- <xsd:element name="deployment-extension"
- type="j2ee:deployment-extensionType"
- minOccurs="0" maxOccurs="unbounded"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="ejb-relationship-roleType">
-<xsd:annotation>
-<xsd:documentation>
-
-The ejb-relationship-roleType describes a role within a
-relationship. There are two roles in each relationship.
-
-The ejb-relationship-roleType contains an optional
-description; an optional name for the relationship role; a
-specification of the multiplicity of the role; an optional
-specification of cascade-delete functionality for the role;
-the role source; and a declaration of the cmr-field, if any,
-by means of which the other side of the relationship is
-accessed from the perspective of the role source.
-
-The multiplicity and role-source element are mandatory.
-
-The relationship-role-source element designates an entity
-bean by means of an ejb-name element. For bidirectional
-relationships, both roles of a relationship must declare a
-relationship-role-source element that specifies a cmr-field
-in terms of which the relationship is accessed. The lack of
-a cmr-field element in an ejb-relationship-role specifies
-that the relationship is unidirectional in navigability and
-the entity bean that participates in the relationship is
-"not aware" of the relationship.
-
-Example:
-
-<ejb-relation>
- <ejb-relation-name>Product-LineItem</ejb-relation-name>
- <ejb-relationship-role>
- <ejb-relationship-role-name>product-has-lineitems
- </ejb-relationship-role-name>
- <multiplicity>One</multiplicity>
- <relationship-role-source>
- <ejb-name>ProductEJB</ejb-name>
- </relationship-role-source>
- </ejb-relationship-role>
-</ejb-relation>
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="ejb-relationship-role-name"
- type="j2ee:string"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- The ejb-relationship-role-name element defines a
- name for a role that is unique within an
- ejb-relation. Different relationships can use the
- same name for a role.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="multiplicity"
- type="j2ee:multiplicityType"/>
- <xsd:element name="cascade-delete"
- type="j2ee:emptyType"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- The cascade-delete element specifies that, within a
- particular relationship, the lifetime of one or more
- entity beans is dependent upon the lifetime of
- another entity bean. The cascade-delete element can
- only be specified for an ejb-relationship-role
- element contained in an ejb-relation element in
- which the other ejb-relationship-role
- element specifies a multiplicity of One.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="relationship-role-source"
- type="j2ee:relationship-role-sourceType"/>
- <xsd:element name="cmr-field"
- type="j2ee:cmr-fieldType"
- minOccurs="0"/>
- <xsd:element name="deployment-extension"
- type="j2ee:deployment-extensionType"
- minOccurs="0" maxOccurs="unbounded"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="enterprise-beansType">
-<xsd:annotation>
-<xsd:documentation>
-
-The enterprise-beansType declares one or more enterprise
-beans. Each bean can be a session, entity or message-driven
-bean.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:choice maxOccurs="unbounded">
- <xsd:element name="session"
- type="j2ee:session-beanType">
- <xsd:unique name="session-ejb-local-ref-name-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The ejb-ref-name element contains the name of
- an EJB reference. The EJB reference is an entry in
- the component's environment and is relative to the
- java:comp/env context. The name must be unique within
- the component.
-
- It is recommended that name be prefixed with "ejb/".
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:ejb-local-ref"/>
- <xsd:field xpath="j2ee:ejb-ref-name"/>
- </xsd:unique>
-
- <xsd:unique name="session-ejb-ref-name-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The ejb-ref-name element contains the name of an EJB
- reference. The EJB reference is an entry in the
- component's environment and is relative to the
- java:comp/env context. The name must be unique
- within the component.
-
- It is recommended that name is prefixed with "ejb/".
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:ejb-ref"/>
- <xsd:field xpath="j2ee:ejb-ref-name"/>
- </xsd:unique>
-
- <xsd:unique name="session-resource-env-ref-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The resource-env-ref-name element specifies the name
- of a resource environment reference; its value is
- the environment entry name used in the component
- code. The name is a JNDI name relative to the
- java:comp/env context and must be unique within an
- component.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:resource-env-ref"/>
- <xsd:field xpath="j2ee:resource-env-ref-name"/>
- </xsd:unique>
-
- <xsd:unique name="session-message-destination-ref-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The message-destination-ref-name element specifies the name
- of a message destination reference; its value is
- the message destination reference name used in the component
- code. The name is a JNDI name relative to the
- java:comp/env context and must be unique within an
- component.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:message-destination-ref"/>
- <xsd:field xpath="j2ee:message-destination-ref-name"/>
- </xsd:unique>
-
- <xsd:unique name="session-res-ref-name-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The res-ref-name element specifies the name of a
- resource manager connection factory reference. The name
- is a JNDI name relative to the java:comp/env context.
- The name must be unique within an component.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:resource-ref"/>
- <xsd:field xpath="j2ee:res-ref-name"/>
- </xsd:unique>
-
- <xsd:unique name="session-env-entry-name-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The env-entry-name element contains the name of a
- component's environment entry. The name is a JNDI
- name relative to the java:comp/env context. The
- name must be unique within an component.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:env-entry"/>
- <xsd:field xpath="j2ee:env-entry-name"/>
- </xsd:unique>
- </xsd:element>
-
- <xsd:element name="entity"
- type="j2ee:entity-beanType">
- <xsd:unique name="entity-ejb-local-ref-name-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The ejb-ref-name element contains the name of
- an EJB reference. The EJB reference is an entry in
- the component's environment and is relative to the
- java:comp/env context. The name must be unique within
- the component.
-
- It is recommended that name be prefixed with "ejb/".
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:ejb-local-ref"/>
- <xsd:field xpath="j2ee:ejb-ref-name"/>
- </xsd:unique>
-
- <xsd:unique name="entity-ejb-ref-name-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The ejb-ref-name element contains the name of an EJB
- reference. The EJB reference is an entry in the
- component's environment and is relative to the
- java:comp/env context. The name must be unique
- within the component.
-
- It is recommended that name is prefixed with "ejb/".
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:ejb-ref"/>
- <xsd:field xpath="j2ee:ejb-ref-name"/>
- </xsd:unique>
-
- <xsd:unique name="entity-resource-env-ref-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The resource-env-ref-name element specifies the name
- of a resource environment reference; its value is
- the environment entry name used in the component
- code. The name is a JNDI name relative to the
- java:comp/env context and must be unique within an
- component.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:resource-env-ref"/>
- <xsd:field xpath="j2ee:resource-env-ref-name"/>
- </xsd:unique>
-
- <xsd:unique name="entity-message-destination-ref-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The message-destination-ref-name element specifies the name
- of a message destination reference; its value is
- the message destination reference name used in the component
- code. The name is a JNDI name relative to the
- java:comp/env context and must be unique within an
- component.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:message-destination-ref"/>
- <xsd:field xpath="j2ee:message-destination-ref-name"/>
- </xsd:unique>
-
- <xsd:unique name="entity-res-ref-name-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The res-ref-name element specifies the name of a
- resource manager connection factory reference. The name
- is a JNDI name relative to the java:comp/env context.
- The name must be unique within an component.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:resource-ref"/>
- <xsd:field xpath="j2ee:res-ref-name"/>
- </xsd:unique>
-
- <xsd:unique name="entity-env-entry-name-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The env-entry-name element contains the name of a
- component's environment entry. The name is a JNDI
- name relative to the java:comp/env context. The
- name must be unique within an component.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:env-entry"/>
- <xsd:field xpath="j2ee:env-entry-name"/>
- </xsd:unique>
- </xsd:element>
-
- <xsd:element name="message-driven"
- type="j2ee:message-driven-beanType">
- <xsd:unique name="messaged-ejb-local-ref-name-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The ejb-ref-name element contains the name of
- an EJB reference. The EJB reference is an entry in
- the component's environment and is relative to the
- java:comp/env context. The name must be unique within
- the component.
-
- It is recommended that name be prefixed with "ejb/".
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:ejb-local-ref"/>
- <xsd:field xpath="j2ee:ejb-ref-name"/>
- </xsd:unique>
-
- <xsd:unique name="messaged-ejb-ref-name-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The ejb-ref-name element contains the name of an EJB
- reference. The EJB reference is an entry in the
- component's environment and is relative to the
- java:comp/env context. The name must be unique
- within the component.
-
- It is recommended that name is prefixed with "ejb/".
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:ejb-ref"/>
- <xsd:field xpath="j2ee:ejb-ref-name"/>
- </xsd:unique>
-
- <xsd:unique name="messaged-resource-env-ref-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The resource-env-ref-name element specifies the name
- of a resource environment reference; its value is
- the environment entry name used in the component
- code. The name is a JNDI name relative to the
- java:comp/env context and must be unique within an
- component.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:resource-env-ref"/>
- <xsd:field xpath="j2ee:resource-env-ref-name"/>
- </xsd:unique>
-
- <xsd:unique name="messaged-message-destination-ref-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The message-destination-ref-name element specifies the name
- of a message destination reference; its value is
- the message destination reference name used in the component
- code. The name is a JNDI name relative to the
- java:comp/env context and must be unique within an
- component.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:message-destination-ref"/>
- <xsd:field xpath="j2ee:message-destination-ref-name"/>
- </xsd:unique>
-
- <xsd:unique name="messaged-res-ref-name-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The res-ref-name element specifies the name of a
- resource manager connection factory reference. The name
- is a JNDI name relative to the java:comp/env context.
- The name must be unique within an component.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:resource-ref"/>
- <xsd:field xpath="j2ee:res-ref-name"/>
- </xsd:unique>
-
- <xsd:unique name="messaged-env-entry-name-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The env-entry-name element contains the name of a
- component's environment entry. The name is a JNDI
- name relative to the java:comp/env context. The
- name must be unique within an component.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:env-entry"/>
- <xsd:field xpath="j2ee:env-entry-name"/>
- </xsd:unique>
- </xsd:element>
-
- </xsd:choice>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="entity-beanType">
-<xsd:annotation>
-<xsd:documentation>
-
-The entity-beanType declares an entity bean. The declaration
-consists of:
-
- - an optional description
- - an optional display name
- - an optional icon element that contains a small and a large
- icon file name
- - a unique name assigned to the enterprise bean
- in the deployment descriptor
- - the names of the entity bean's remote home
- and remote interfaces, if any
- - the names of the entity bean's local home and local
- interfaces, if any
- - the entity bean's implementation class
- - the entity bean's persistence management type
- - the entity bean's primary key class name
- - an indication of the entity bean's reentrancy
- - an optional specification of the
- entity bean's cmp-version
- - an optional specification of the entity bean's
- abstract schema name
- - an optional list of container-managed fields
- - an optional specification of the primary key
- field
- - an optional declaration of the bean's environment
- entries
- - an optional declaration of the bean's EJB
- references
- - an optional declaration of the bean's local
- EJB references
- - an optional declaration of the bean's web
- service references
- - an optional declaration of the security role
- references
- - an optional declaration of the security identity
- to be used for the execution of the bean's methods
- - an optional declaration of the bean's
- resource manager connection factory references
- - an optional declaration of the bean's
- resource environment references
- - an optional declaration of the bean's message
- destination references
- - an optional set of query declarations
- for finder and select methods for an entity
- bean with cmp-version 2.x.
- - an optional set of deployment-extension
- declarations.
-
-The optional abstract-schema-name element must be specified
-for an entity bean with container-managed persistence and
-cmp-version 2.x.
-
-The optional primkey-field may be present in the descriptor
-if the entity's persistence-type is Container.
-
-The optional cmp-version element may be present in the
-descriptor if the entity's persistence-type is Container. If
-the persistence-type is Container and the cmp-version
-element is not specified, its value defaults to 2.x.
-
-The optional home and remote elements must be specified if
-the entity bean cmp-version is 1.x.
-
-The optional home and remote elements must be specified if
-the entity bean has a remote home and remote interface.
-
-The optional local-home and local elements must be specified
-if the entity bean has a local home and local interface.
-
-Either both the local-home and the local elements or both
-the home and the remote elements must be specified.
-
-The optional query elements must be present if the
-persistence-type is Container and the cmp-version is 2.x and
-query methods other than findByPrimaryKey have been defined
-for the entity bean.
-
-The other elements that are optional are "optional" in the
-sense that they are omitted if the lists represented by them
-are empty.
-
-At least one cmp-field element must be present in the
-descriptor if the entity's persistence-type is Container and
-the cmp-version is 1.x, and none must not be present if the
-entity's persistence-type is Bean.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="display-name"
- type="j2ee:display-nameType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="icon"
- type="j2ee:iconType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="ejb-name"
- type="j2ee:ejb-nameType"/>
- <xsd:element name="home"
- type="j2ee:homeType"
- minOccurs="0"/>
- <xsd:element name="remote"
- type="j2ee:remoteType"
- minOccurs="0"/>
- <xsd:element name="local-home"
- type="j2ee:local-homeType"
- minOccurs="0"/>
- <xsd:element name="local"
- type="j2ee:localType"
- minOccurs="0"/>
- <xsd:element name="ejb-class"
- type="j2ee:ejb-classType"/>
- <xsd:element name="persistence-type"
- type="j2ee:persistence-typeType"/>
- <xsd:element name="prim-key-class"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
-
- The prim-key-class element contains the
- fully-qualified name of an
- entity bean's primary key class.
-
- If the definition of the primary key class is
- deferred to deployment time, the prim-key-class
- element should specify java.lang.Object.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="reentrant"
- type="j2ee:true-falseType">
- <xsd:annotation>
- <xsd:documentation>
-
- The reentrant element specifies whether an entity
- bean is reentrant or not.
-
- The reentrant element must be one of the two
- following: true or false
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="cmp-version"
- type="j2ee:cmp-versionType"
- minOccurs="0"/>
- <xsd:element name="abstract-schema-name"
- type="j2ee:java-identifierType"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- The abstract-schema-name element specifies the name
- of the abstract schema type of an entity bean with
- cmp-version 2.x. It is used in EJB QL queries.
-
- For example, the abstract-schema-name for an entity
- bean whose local interface is
- com.acme.commerce.Order might be Order.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="cmp-field"
- type="j2ee:cmp-fieldType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="primkey-field"
- type="j2ee:string"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- The primkey-field element is used to specify the
- name of the primary key field for an entity with
- container-managed persistence.
-
- The primkey-field must be one of the fields declared
- in the cmp-field element, and the type of the field
- must be the same as the primary key type.
-
- The primkey-field element is not used if the primary
- key maps to multiple container-managed fields
- (i.e. the key is a compound key). In this case, the
- fields of the primary key class must be public, and
- their names must correspond to the field names of
- the entity bean class that comprise the key.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="env-entry"
- type="j2ee:env-entryType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="ejb-ref"
- type="j2ee:ejb-refType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="ejb-local-ref"
- type="j2ee:ejb-local-refType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="service-ref"
- type="j2ee:service-refType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="security-role-ref"
- type="j2ee:security-role-refType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="security-identity"
- type="j2ee:security-identityType"
- minOccurs="0"/>
- <xsd:element name="resource-ref"
- type="j2ee:resource-refType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="resource-env-ref"
- type="j2ee:resource-env-refType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="message-destination-ref"
- type="j2ee:message-destination-refType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="query"
- type="j2ee:queryType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="deployment-extension"
- type="j2ee:deployment-extensionType"
- minOccurs="0" maxOccurs="unbounded"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="exclude-listType">
-<xsd:annotation>
-<xsd:documentation>
-
-The exclude-listType specifies one or more methods which
-the Assembler marks to be uncallable.
-
-If the method permission relation contains methods that are
-in the exclude list, the Deployer should consider those
-methods to be uncallable.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="method"
- type="j2ee:methodType"
- maxOccurs="unbounded"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="java-typeType">
-<xsd:annotation>
-<xsd:documentation>
-
-This is a generic type that designates a Java primitive
-type or a fully qualified name of a Java interface/type.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:pattern value="[^\p{Z}]*"/>
- </xsd:restriction>
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="message-driven-beanType">
-<xsd:annotation>
-<xsd:documentation>
-
-The message-driven element declares a message-driven
-bean. The declaration consists of:
-
- - an optional description
- - an optional display name
- - an optional icon element that contains a small and a large
- icon file name.
- - a name assigned to the enterprise bean in
- the deployment descriptor
- - the message-driven bean's implementation class
- - an optional declaration of the bean's messaging
- type
- - the message-driven bean's transaction management type
- - an optional declaration of the bean's
- message-destination-type
- - an optional declaration of the bean's
- message-destination-link
- - an optional declaration of the message-driven bean's
- activation configuration properties
- - an optional declaration of the bean's environment
- entries
- - an optional declaration of the bean's EJB references
- - an optional declaration of the bean's local EJB
- references
- - an optional declaration of the bean's web service
- references
- - an optional declaration of the security
- identity to be used for the execution of the bean's
- methods
- - an optional declaration of the bean's
- resource manager connection factory
- references
- - an optional declaration of the bean's resource
- environment references.
- - an optional declaration of the bean's message
- destination references
- - an optional declaration of deployment extensions
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"/>
- <xsd:element name="display-name"
- type="j2ee:display-nameType"
- minOccurs="0"/>
- <xsd:element name="icon"
- type="j2ee:iconType"
- minOccurs="0"/>
- <xsd:element name="ejb-name"
- type="j2ee:ejb-nameType"/>
- <xsd:element name="ejb-class"
- type="j2ee:ejb-classType"/>
- <xsd:element name="messaging-type"
- type="j2ee:fully-qualified-classType"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- The messaging-type element specifies the message
- listener interface of the message-driven bean. If
- the messaging-type element is not specified, it is
- assumed to be javax.jms.MessageListener.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="transaction-type"
- type="j2ee:transaction-typeType"/>
- <xsd:element name="message-destination-type"
- type="j2ee:message-destination-typeType"
- minOccurs="0"/>
- <xsd:element name="message-destination-link"
- type="j2ee:message-destination-linkType"
- minOccurs="0"/>
- <xsd:element name="activation-config"
- type="j2ee:activation-configType"
- minOccurs="0"/>
- <xsd:element name="env-entry"
- type="j2ee:env-entryType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="ejb-ref"
- type="j2ee:ejb-refType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="ejb-local-ref"
- type="j2ee:ejb-local-refType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="service-ref"
- type="j2ee:service-refType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="security-identity"
- type="j2ee:security-identityType"
- minOccurs="0"/>
- <xsd:element name="resource-ref"
- type="j2ee:resource-refType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="resource-env-ref"
- type="j2ee:resource-env-refType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="message-destination-ref"
- type="j2ee:message-destination-refType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="deployment-extension"
- type="j2ee:deployment-extensionType"
- minOccurs="0" maxOccurs="unbounded"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="method-intfType">
-
-<xsd:annotation>
-<xsd:documentation>
-
-The method-intf element allows a method element to
-differentiate between the methods with the same name and
-signature that are multiply defined across the home and
-component interfaces (e.g, in both an enterprise bean's
-remote and local interfaces or in both an enterprise bean's
-home and remote interfaces, etc.); the component and web
-service endpoint interfaces, and so on.
-
-The method-intf element must be one of the following:
-
- Home
- Remote
- LocalHome
- Local
- ServiceEndpoint
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:enumeration value="Home"/>
- <xsd:enumeration value="Remote"/>
- <xsd:enumeration value="LocalHome"/>
- <xsd:enumeration value="Local"/>
- <xsd:enumeration value="ServiceEndpoint"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="method-nameType">
-<xsd:annotation>
-<xsd:documentation>
-
-The method-nameType contains a name of an enterprise
-bean method or the asterisk (*) character. The asterisk is
-used when the element denotes all the methods of an
-enterprise bean's client view interfaces.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string"/>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="method-paramsType">
-<xsd:annotation>
-<xsd:documentation>
-
-The method-paramsType defines a list of the
-fully-qualified Java type names of the method parameters.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="method-param"
- type="j2ee:java-typeType"
- minOccurs="0"
- maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
-
- The method-param element contains a primitive
- or a fully-qualified Java type name of a method
- parameter.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="method-permissionType">
-<xsd:annotation>
-<xsd:documentation>
-
-The method-permissionType specifies that one or more
-security roles are allowed to invoke one or more enterprise
-bean methods. The method-permissionType consists of an
-optional description, a list of security role names or an
-indicator to state that the method is unchecked for
-authorization, and a list of method elements.
-
-The security roles used in the method-permissionType
-must be defined in the security-role elements of the
-deployment descriptor, and the methods must be methods
-defined in the enterprise bean's home, component and/or web
-service endpoint interfaces.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:choice>
- <xsd:element name="role-name"
- type="j2ee:role-nameType"
- maxOccurs="unbounded"/>
- <xsd:element name="unchecked"
- type="j2ee:emptyType">
- <xsd:annotation>
- <xsd:documentation>
-
- The unchecked element specifies that a method is
- not checked for authorization by the container
- prior to invocation of the method.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- </xsd:choice>
- <xsd:element name="method"
- type="j2ee:methodType"
- maxOccurs="unbounded"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="methodType">
-<xsd:annotation>
-<xsd:documentation>
-
-The methodType is used to denote a method of an enterprise
-bean's home, component, and/or web service endpoint
-interface, or, in the case of a message-driven bean, the
-bean's message listener method, or a set of such
-methods. The ejb-name element must be the name of one of the
-enterprise beans declared in the deployment descriptor; the
-optional method-intf element allows to distinguish between a
-method with the same signature that is multiply defined
-across the home, component, and/or web service endpoint
-interfaces; the method-name element specifies the method
-name; and the optional method-params elements identify a
-single method among multiple methods with an overloaded
-method name.
-
-There are three possible styles of using methodType element
-within a method element:
-
-1.
-<method>
- <ejb-name>EJBNAME</ejb-name>
- <method-name>*</method-name>
-</method>
-
- This style is used to refer to all the methods of the
- specified enterprise bean's home, component, and/or web
- service endpoint interfaces.
-
-2.
-<method>
- <ejb-name>EJBNAME</ejb-name>
- <method-name>METHOD</method-name>
-</method>>
-
- This style is used to refer to the specified method of
- the specified enterprise bean. If there are multiple
- methods with the same overloaded name, the element of
- this style refers to all the methods with the overloaded
- name.
-
-3.
-<method>
- <ejb-name>EJBNAME</ejb-name>
- <method-name>METHOD</method-name>
- <method-params>
- <method-param>PARAM-1</method-param>
- <method-param>PARAM-2</method-param>
- ...
- <method-param>PARAM-n</method-param>
- </method-params>
-</method>
-
- This style is used to refer to a single method within a
- set of methods with an overloaded name. PARAM-1 through
- PARAM-n are the fully-qualified Java types of the
- method's input parameters (if the method has no input
- arguments, the method-params element contains no
- method-param elements). Arrays are specified by the
- array element's type, followed by one or more pair of
- square brackets (e.g. int[][]). If there are multiple
- methods with the same overloaded name, this style refers
- to all of the overloaded methods.
-
-Examples:
-
-Style 1: The following method element refers to all the
-methods of the EmployeeService bean's home, component,
-and/or web service endpoint interfaces:
-
-<method>
- <ejb-name>EmployeeService</ejb-name>
- <method-name>*</method-name>
-</method>
-
-Style 2: The following method element refers to all the
-create methods of the EmployeeService bean's home
-interface(s).
-
-<method>
- <ejb-name>EmployeeService</ejb-name>
- <method-name>create</method-name>
-</method>
-
-Style 3: The following method element refers to the
-create(String firstName, String LastName) method of the
-EmployeeService bean's home interface(s).
-
-<method>
- <ejb-name>EmployeeService</ejb-name>
- <method-name>create</method-name>
- <method-params>
- <method-param>java.lang.String</method-param>
- <method-param>java.lang.String</method-param>
- </method-params>
-</method>
-
-The following example illustrates a Style 3 element with
-more complex parameter types. The method
-foobar(char s, int i, int[] iar, mypackage.MyClass mycl,
-mypackage.MyClass[][] myclaar) would be specified as:
-
-<method>
- <ejb-name>EmployeeService</ejb-name>
- <method-name>foobar</method-name>
- <method-params>
- <method-param>char</method-param>
- <method-param>int</method-param>
- <method-param>int[]</method-param>
- <method-param>mypackage.MyClass</method-param>
- <method-param>mypackage.MyClass[][]</method-param>
- </method-params>
-</method>
-
-The optional method-intf element can be used when it becomes
-necessary to differentiate between a method that is multiply
-defined across the enterprise bean's home, component, and/or
-web service endpoint interfaces with the same name and
-signature.
-
-For example, the method element
-
-<method>
- <ejb-name>EmployeeService</ejb-name>
- <method-intf>Remote</method-intf>
- <method-name>create</method-name>
- <method-params>
- <method-param>java.lang.String</method-param>
- <method-param>java.lang.String</method-param>
- </method-params>
-</method>
-
-can be used to differentiate the create(String, String)
-method defined in the remote interface from the
-create(String, String) method defined in the remote home
-interface, which would be defined as
-
-<method>
- <ejb-name>EmployeeService</ejb-name>
- <method-intf>Home</method-intf>
- <method-name>create</method-name>
- <method-params>
- <method-param>java.lang.String</method-param>
- <method-param>java.lang.String</method-param>
- </method-params>
-</method>
-
-and the create method that is defined in the local home
-interface which would be defined as
-
-<method>
- <ejb-name>EmployeeService</ejb-name>
- <method-intf>LocalHome</method-intf>
- <method-name>create</method-name>
- <method-params>
- <method-param>java.lang.String</method-param>
- <method-param>java.lang.String</method-param>
- </method-params>
-</method>
-
-The method-intf element can be used with all th ree Styles
-of the method element usage. For example, the following
-method element example could be used to refer to all the
-methods of the EmployeeService bean's remote home interface.
-
-<method>
- <ejb-name>EmployeeService</ejb-name>
- <method-intf>Home</method-intf>
- <method-name>*</method-name>
-</method>
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="ejb-name"
- type="j2ee:ejb-nameType"/>
- <xsd:element name="method-intf"
- type="j2ee:method-intfType"
- minOccurs="0">
- </xsd:element>
- <xsd:element name="method-name"
- type="j2ee:method-nameType"/>
- <xsd:element name="method-params"
- type="j2ee:method-paramsType"
- minOccurs="0"/>
- </xsd:sequence>
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="multiplicityType">
-<xsd:annotation>
-<xsd:documentation>
-
-The multiplicityType describes the multiplicity of the
-role that participates in a relation.
-
-The value must be one of the two following:
-
- One
- Many
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:enumeration value="One"/>
- <xsd:enumeration value="Many"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="persistence-typeType">
-<xsd:annotation>
-<xsd:documentation>
-
-The persistence-typeType specifies an entity bean's persistence
-management type.
-
-The persistence-type element must be one of the two following:
-
- Bean
- Container
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:enumeration value="Bean"/>
- <xsd:enumeration value="Container"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="query-methodType">
-<xsd:annotation>
-<xsd:documentation>
-
-The query-method specifies the method for a finder or select
-query.
-
-The method-name element specifies the name of a finder or select
-method in the entity bean's implementation class.
-
-Each method-param must be defined for a query-method using the
-method-params element.
-
-It is used by the query-method element.
-
-Example:
-
-<query>
- <description>Method finds large orders</description>
- <query-method>
- <method-name>findLargeOrders</method-name>
- <method-params></method-params>
- </query-method>
- <ejb-ql>SELECT OBJECT(o) FROM Order o WHERE o.amount > 1000</ejb-ql>
-</query>
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="method-name"
- type="j2ee:method-nameType"/>
- <xsd:element name="method-params"
- type="j2ee:method-paramsType"/>
- <xsd:element name="deployment-extension"
- type="j2ee:deployment-extensionType"
- minOccurs="0" maxOccurs="unbounded"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="queryType">
-<xsd:annotation>
-<xsd:documentation>
-
-The queryType defines a finder or select
-query. It contains
- - an optional description of the query
- - the specification of the finder or select
- method it is used by
- - an optional specification of the result type
- mapping, if the query is for a select method
- and entity objects are returned.
- - the EJB QL query string that defines the query.
- - an optional declaration of deployment extensions
-
-Queries that are expressible in EJB QL must use the ejb-ql
-element to specify the query. If a query is not expressible
-in EJB QL, the description element should be used to
-describe the semantics of the query and the ejb-ql element
-should be empty.
-
-The result-type-mapping is an optional element. It can only
-be present if the query-method specifies a select method
-that returns entity objects. The default value for the
-result-type-mapping element is "Local".
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType" minOccurs="0"/>
- <xsd:element name="query-method"
- type="j2ee:query-methodType"/>
- <xsd:element name="result-type-mapping"
- type="j2ee:result-type-mappingType"
- minOccurs="0"/>
- <xsd:element name="ejb-ql"
- type="xsd:string"/>
- <xsd:element name="deployment-extension"
- type="j2ee:deployment-extensionType"
- minOccurs="0" maxOccurs="unbounded"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="relationship-role-sourceType">
-<xsd:annotation>
-<xsd:documentation>
-
-The relationship-role-sourceType designates the source of a
-role that participates in a relationship. A
-relationship-role-sourceType is used by
-relationship-role-source elements to uniquely identify an
-entity bean.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="ejb-name"
- type="j2ee:ejb-nameType"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="relationshipsType">
-<xsd:annotation>
-<xsd:documentation>
-
-The relationshipsType describes the relationships in
-which entity beans with container-managed persistence
-participate. The relationshipsType contains an optional
-description; and a list of ejb-relation elements, which
-specify the container managed relationships.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="ejb-relation"
- type="j2ee:ejb-relationType"
- maxOccurs="unbounded">
-
- <xsd:unique name="role-name-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The ejb-relationship-role-name contains the name of a
- relationship role. The name must be unique within
- a relationship, but can be reused in different
- relationships.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector
- xpath=".//j2ee:ejb-relationship-role-name"/>
- <xsd:field
- xpath="."/>
- </xsd:unique>
- </xsd:element>
- <xsd:element name="deployment-extension"
- type="j2ee:deployment-extensionType"
- minOccurs="0" maxOccurs="unbounded"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="result-type-mappingType">
-<xsd:annotation>
-<xsd:documentation>
-
-The result-type-mappingType is used in the query element to
-specify whether an abstract schema type returned by a query
-for a select method is to be mapped to an EJBLocalObject or
-EJBObject type.
-
-The value must be one of the following:
-
- Local
- Remote
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:enumeration value="Local"/>
- <xsd:enumeration value="Remote"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="security-identityType">
-<xsd:annotation>
-<xsd:documentation>
-
-The security-identityType specifies whether the caller's
-security identity is to be used for the execution of the
-methods of the enterprise bean or whether a specific run-as
-identity is to be used. It contains an optional description
-and a specification of the security identity to be used.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:choice>
- <xsd:element name="use-caller-identity"
- type="j2ee:emptyType">
- <xsd:annotation>
- <xsd:documentation>
-
- The use-caller-identity element specifies that
- the caller's security identity be used as the
- security identity for the execution of the
- enterprise bean's methods.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="run-as"
- type="j2ee:run-asType"/>
- </xsd:choice>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="service-refType">
-<xsd:annotation>
-<xsd:documentation>
-
-THIS IS A PLACEHOLDER TYPE which will
-be REPLACED. It will be defined based on
-definition to be supplied by JSR109.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:simpleContent>
- <xsd:extension base="xsd:string">
- </xsd:extension>
- </xsd:simpleContent>
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="session-beanType">
-<xsd:annotation>
-<xsd:documentation>
-
-The session-beanType declares an session bean. The
-declaration consists of:
-
- - an optional description
- - an optional display name
- - an optional icon element that contains a small and a large
- icon file name
- - a name assigned to the enterprise bean
- in the deployment description
- - the names of the session bean's remote home and
- remote interfaces, if any
- - the names of the session bean's local home and
- local interfaces, if any
- - the name of the session bean's web service endpoint
- interface, if any
- - the session bean's implementation class
- - the session bean's state management type
- - the session bean's transaction management type
- - an optional declaration of the bean's
- environment entries
- - an optional declaration of the bean's EJB references
- - an optional declaration of the bean's local
- EJB references
- - an optional declaration of the bean's web
- service references
- - an optional declaration of the security role
- references
- - an optional declaration of the security identity
- to be used for the execution of the bean's methods
- - an optional declaration of the bean's resource
- manager connection factory references
- - an optional declaration of the bean's resource
- environment references.
- - an optional declaration of the bean's message
- destination references
- - an optional declaration deployment extensions
-
-The elements that are optional are "optional" in the sense
-that they are omitted when if lists represented by them are
-empty.
-
-Either both the local-home and the local elements or both
-the home and the remote elements must be specified for the
-session bean.
-
-The service-endpoint element may only be specified if the
-bean is a stateless session bean.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="display-name"
- type="j2ee:display-nameType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="icon"
- type="j2ee:iconType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="ejb-name"
- type="j2ee:ejb-nameType"/>
- <xsd:element name="home"
- type="j2ee:homeType"
- minOccurs="0"/>
- <xsd:element name="remote"
- type="j2ee:remoteType"
- minOccurs="0"/>
- <xsd:element name="local-home"
- type="j2ee:local-homeType"
- minOccurs="0"/>
- <xsd:element name="local"
- type="j2ee:localType"
- minOccurs="0"/>
- <xsd:element name="service-endpoint"
- type="j2ee:fully-qualified-classType"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- The service-endpoint element contains the
- fully-qualified name of the enterprise bean's web
- service endpoint interface. The service-endpoint
- element may only be specified for a stateless
- session bean. The specified interface must be a
- valid JAX-RPC service endpoint interface.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="ejb-class"
- type="j2ee:ejb-classType"/>
- <xsd:element name="session-type"
- type="j2ee:session-typeType"/>
- <xsd:element name="transaction-type"
- type="j2ee:transaction-typeType"/>
- <xsd:element name="env-entry"
- type="j2ee:env-entryType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="ejb-ref"
- type="j2ee:ejb-refType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="ejb-local-ref"
- type="j2ee:ejb-local-refType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="service-ref"
- type="j2ee:service-refType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="security-role-ref"
- type="j2ee:security-role-refType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="security-identity"
- type="j2ee:security-identityType"
- minOccurs="0"/>
- <xsd:element name="resource-ref"
- type="j2ee:resource-refType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="resource-env-ref"
- type="j2ee:resource-env-refType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="message-destination-ref"
- type="j2ee:message-destination-refType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="deployment-extension"
- type="j2ee:deployment-extensionType"
- minOccurs="0" maxOccurs="unbounded"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="session-typeType">
-<xsd:annotation>
-<xsd:documentation>
-
-The session-typeType describes whether the session bean is a
-stateful session or stateless session. It is used by
-session-type elements.
-
-The value must be one of the two following:
-
- Stateful
- Stateless
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:enumeration value="Stateful"/>
- <xsd:enumeration value="Stateless"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="trans-attributeType">
-<xsd:annotation>
-<xsd:documentation>
-
-The trans-attributeType specifies how the container must
-manage the transaction boundaries when delegating a method
-invocation to an enterprise bean's business method.
-
-The value must be one of the following:
-
- NotSupported
- Supports
- Required
- RequiresNew
- Mandatory
- Never
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:enumeration value="NotSupported"/>
- <xsd:enumeration value="Supports"/>
- <xsd:enumeration value="Required"/>
- <xsd:enumeration value="RequiresNew"/>
- <xsd:enumeration value="Mandatory"/>
- <xsd:enumeration value="Never"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="transaction-typeType">
-<xsd:annotation>
-<xsd:documentation>
-
-The transaction-typeType specifies an enterprise bean's
-transaction management type.
-
-The transaction-type must be one of the two following:
-
- Bean
- Container
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:enumeration value="Bean"/>
- <xsd:enumeration value="Container"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-</xsd:schema>
-
diff --git a/src/test/resources/xbean/compile/scomp/j2ee/j2ee_1_4.xsd b/src/test/resources/xbean/compile/scomp/j2ee/j2ee_1_4.xsd
deleted file mode 100755
index 6714272..0000000
--- a/src/test/resources/xbean/compile/scomp/j2ee/j2ee_1_4.xsd
+++ /dev/null
@@ -1,1406 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--Generated by Umit Yalcinalp March 2002-->
-<xsd:schema
- targetNamespace="http://java.sun.com/xml/ns/j2ee"
- xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- elementFormDefault="qualified"
- attributeFormDefault="unqualified"
- version="1.4">
-<xsd:annotation>
-<xsd:documentation>
-@(#)j2ee_1_4.xsds 1.20 02/07/12
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:annotation>
-<xsd:documentation>
-
-Copyright 2002 Sun Microsystems, Inc., 901 San Antonio
-Road, Palo Alto, California 94303, U.S.A. All rights
-reserved.
-
-Sun Microsystems, Inc. has intellectual property rights
-relating to technology described in this document. In
-particular, and without limitation, these intellectual
-property rights may include one or more of the U.S. patents
-listed at http://www.sun.com/patents and one or more
-additional patents or pending patent applications in the
-U.S. and other countries.
-
-This document and the technology which it describes are
-distributed under licenses restricting their use, copying,
-distribution, and decompilation. No part of this document
-may be reproduced in any form by any means without prior
-written authorization of Sun and its licensors, if any.
-
-Third-party software, including font technology, is
-copyrighted and licensed from Sun suppliers.
-
-Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
-JavaServer Pages, Enterprise JavaBeans and the Java Coffee
-Cup logo are trademarks or registered trademarks of Sun
-Microsystems, Inc. in the U.S. and other countries.
-
-Federal Acquisitions: Commercial Software - Government Users
-Subject to Standard License Terms and Conditions.
-
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:annotation>
-<xsd:documentation>
-
-The following definitions that appear in the common
-shareable schema(s) of J2EE deployment descriptors should be
-interpreted with respect to the context they are included:
-
-Deployment Component may indicate one of the following:
- j2ee application;
- application client;
- web application;
- enterprise bean;
- resource adapter;
-
-Deployment File may indicate one of the following:
- ear file;
- war file;
- jar file;
- rar file;
-
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:import namespace="http://www.w3.org/XML/1998/namespace"
- schemaLocation="http://www.w3.org/2001/xml.xsd"/>
-
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="deployment-extensionType">
-<xsd:annotation>
-<xsd:documentation>
-
-The deployment-extensionType is used to indicate
-extensions to the specific Deployment Component.
-
-It is used by deployment-extension elements to designate an
-extension block that is targeted to a specific extension
-designated by a set of extension elements that are declared
-by a namespace. The namespace identifies the extension to
-the deployment tool that processes the extension.
-
-The mustUnderstand attribute is provided by the Application
-Assembler to indicate whether the extension described is an
-essential extension that must exist in the container. If
-mustUnderstand is "true", the deployment tool must indicate
-an error when processing a deployment-extension element with
-a namespace it does not understand. Extensions that are not
-essential are declared by default as optional extensions
-that need not be provided by a container. Applications that
-use such extensions are portable to other containers because
-deployment tools will ignore extensions that they don't
-support.
-
-The type of the extension-element is abstract. Therefore, a
-concrete type must be specified by the deployment descriptor
-using xsi:type attribute for each extension-element.
-
-The value of the mustUnderstand attribute is "false"
-by default.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="extension-element"
- type="j2ee:extensibleType"
- maxOccurs="unbounded"/>
- </xsd:sequence>
-
- <xsd:attribute name="namespace"
- use="required"
- type="xsd:anyURI"/>
- <xsd:attribute name="mustUnderstand"
- type="xsd:boolean"/>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="descriptionType">
-<xsd:annotation>
-<xsd:documentation>
-
-The description type is used by a description element to
-provide text describing the parent element. The elements
-that use this type should include any information that the
-Deployment Component's Deployment File file producer wants
-to provide to the consumer of the Deployment Component's
-Deployment File (i.e., to the Deployer). Typically, the
-tools used by such a Deployment File consumer will display
-the description when processing the parent element that
-contains the description.
-
-The lang attribute defines the language that the
-description is provided in. The default value is "en" (English).
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:simpleContent>
- <xsd:extension base="xsd:string">
- <xsd:attribute ref="xml:lang"/>
- </xsd:extension>
- </xsd:simpleContent>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="dewey-versionType">
-<xsd:annotation>
-<xsd:documentation>
-
-This type defines a dewey decimal which is used
-to describe versions of documents.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="xsd:decimal">
- <xsd:whiteSpace value="collapse"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="display-nameType">
-<xsd:annotation>
-<xsd:documentation>
-
-The display-name type contains a short name that is intended
-to be displayed by tools. It is used by display-name
-elements. The display name need not be unique.
-
-Example:
-
-...
- <display-name xml:lang="en">Employee Self Service</display-name>
-
-The value of the xml:lang attribute is "en" (English) by default.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:simpleContent>
- <xsd:extension base="j2ee:string">
- <xsd:attribute ref="xml:lang"/>
- </xsd:extension>
- </xsd:simpleContent>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="ejb-linkType">
-<xsd:annotation>
-<xsd:documentation>
-
-The ejb-linkType is used by ejb-link
-elements in the ejb-ref or ejb-local-ref elements to specify
-that an EJB reference is linked to enterprise bean.
-
-The value of the ejb-link element must be the ejb-name of an
-enterprise bean in the same ejb-jar file or in another ejb-jar
-file in the same J2EE application unit.
-
-Alternatively, the name in the ejb-link element may be composed of a
-path name specifying the ejb-jar containing the referenced enterprise
-bean with the ejb-name of the target bean appended and separated from
-the path name by "#". The path name is relative to the Deployment File
-containing Deployment Component that is referencing the enterprise bean.
-This allows multiple enterprise beans with the same ejb-name to be
-uniquely identified.
-
-Examples:
-
- <ejb-link>EmployeeRecord</ejb-link>
-
- <ejb-link>../products/product.jar#ProductEJB</ejb-link>
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string"/>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="ejb-local-refType">
-<xsd:annotation>
-<xsd:documentation>
-
-The ejb-local-refType is used by ejb-local-ref elements for
-the declaration of a reference to an enterprise bean's local
-home. The declaration consists of:
-
- - an optional description
- - the EJB reference name used in the code of the Deployment
- Component that's referencing the enterprise bean
- - the expected type of the referenced enterprise bean
- - the expected local home and local interfaces of the
- referenced enterprise bean
- - optional ejb-link information, used to specify the
- referenced enterprise bean
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="ejb-ref-name"
- type="j2ee:ejb-ref-nameType"/>
- <xsd:element name="ejb-ref-type"
- type="j2ee:ejb-ref-typeType"/>
- <xsd:element name="local-home"
- type="j2ee:local-homeType"/>
- <xsd:element name="local"
- type="j2ee:localType"/>
- <xsd:element name="ejb-link"
- type="j2ee:ejb-linkType"
- minOccurs="0"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="ejb-ref-nameType">
-<xsd:annotation>
-<xsd:documentation>
-
-The ejb-ref-name element contains the name of an EJB
-reference. The EJB reference is an entry in the
-Deployment Component's environment and is relative to the
-java:comp/env context. The name must be unique within the
-Deployment Component.
-
-It is recommended that name is prefixed with "ejb/".
-
-Example:
-
-<ejb-ref-name>ejb/Payroll</ejb-ref-name>
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:jndi-nameType"/>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="ejb-ref-typeType">
-<xsd:annotation>
-<xsd:documentation>
-
-The ejb-ref-typeType contains the expected type of the
-referenced enterprise bean.
-
-The ejb-ref-type designates a value
-that must be one of the following:
-
- Entity
- Session
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:enumeration value="Entity"/>
- <xsd:enumeration value="Session"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="ejb-refType">
-<xsd:annotation>
-<xsd:documentation>
-
-The ejb-refType is used by ejb-ref elements for the
-declaration of a reference to an enterprise bean's home. The
-declaration consists of:
-
- - an optional description
- - the EJB reference name used in the code of
- the Deployment Component that's referencing the enterprise
- bean
- - the expected type of the referenced enterprise bean
- - the expected home and remote interfaces of the referenced
- enterprise bean
- - optional ejb-link information, used to specify the
- referenced enterprise bean
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="ejb-ref-name"
- type="j2ee:ejb-ref-nameType"/>
- <xsd:element name="ejb-ref-type"
- type="j2ee:ejb-ref-typeType"/>
-
- <xsd:element name="home"
- type="j2ee:homeType"/>
- <xsd:element name="remote"
- type="j2ee:remoteType"/>
- <xsd:element name="ejb-link"
- type="j2ee:ejb-linkType"
- minOccurs="0"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="emptyType">
-<xsd:annotation>
-<xsd:documentation>
-
-This type is used to designate an empty
-element when used.
-
-</xsd:documentation>
-</xsd:annotation>
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="env-entry-type-valuesType">
-<xsd:annotation>
-<xsd:documentation>
-
-This type contains the fully-qualified Java type of the
-environment entry value that is expected by the
-application's code.
-
-The following are the legal values of env-entry-type-valuesType:
-
- java.lang.Boolean
- java.lang.Byte
- java.lang.Character
- java.lang.String
- java.lang.Short
- java.lang.Integer
- java.lang.Long
- java.lang.Float
- java.lang.Double
-
-Example:
-
-<env-entry-type>java.lang.Boolean</env-entry-type>
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:enumeration value="java.lang.Boolean"/>
- <xsd:enumeration value="java.lang.Byte"/>
- <xsd:enumeration value="java.lang.Character"/>
- <xsd:enumeration value="java.lang.String"/>
- <xsd:enumeration value="java.lang.Short"/>
- <xsd:enumeration value="java.lang.Integer"/>
- <xsd:enumeration value="java.lang.Long"/>
- <xsd:enumeration value="java.lang.Float"/>
- <xsd:enumeration value="java.lang.Double"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="env-entryType">
-<xsd:annotation>
-<xsd:documentation>
-
-The env-entryType is used to declare an application's
-environment entry. The declaration consists of an optional
-description, the name of the environment entry, and an
-optional value. If a value is not specified, one must be
-supplied during deployment.
-
-It is used by env-entry elements.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="env-entry-name"
- type="j2ee:jndi-nameType">
- <xsd:annotation>
- <xsd:documentation>
-
- The env-entry-name element contains the name of a
- Deployment Component's environment entry. The name
- is a JNDI name relative to the java:comp/env
- context. The name must be unique within a
- Deployment Component. The uniqueness
- constraints must be defined within the declared
- context.
-
- Example:
-
- <env-entry-name>minAmount</env-entry-name>
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
-
- <xsd:element name="env-entry-type"
- type="j2ee:env-entry-type-valuesType"/>
-
- <xsd:element name="env-entry-value"
- type="xsd:string"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- The env-entry-value designates the value of a
- Deployment Component's environment entry. The value
- must be a String that is valid for the
- constructor of the specified type that takes a
- single String parameter, or for java.lang.Character,
- a single character.
-
- Example:
-
- <env-entry-value>100.00</env-entry-value>
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
-
- </xsd:sequence>
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="extensibleType" abstract="true">
-<xsd:annotation>
-<xsd:documentation>
-
-The extensibleType is an abstract base type which is used to
-define the type of extension-elements. Instance documents
-must substitute a known type to define the extension by
-using xsi:type attribute to define the actual type of
-extension-elements.
-
-</xsd:documentation>
-</xsd:annotation>
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="fully-qualified-classType">
-<xsd:annotation>
-<xsd:documentation>
-
-The elements that use this type designate the name of a
-Java class or interface.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string"/>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="generic-booleanType">
-<xsd:annotation>
-<xsd:documentation>
-
-This type defines four different values which can designate
-boolean values. This includes values yes and no which are
-not designated by xsd:boolean
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:enumeration value="true"/>
- <xsd:enumeration value="false"/>
- <xsd:enumeration value="yes"/>
- <xsd:enumeration value="no"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="homeType">
-<xsd:annotation>
-<xsd:documentation>
-
-The homeType defines the fully-qualified name of
-an enterprise bean's home interface.
-
-Example:
-
- <home>com.aardvark.payroll.PayrollHome</home>
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:fully-qualified-classType"/>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="iconType">
-<xsd:annotation>
-<xsd:documentation>
-
-The icon type contains small-icon and large-icon elements
-that specify the file names for small and large GIF or
-JPEG icon images used to represent the parent element in a
-GUI tool.
-
-The xml:lang attribute defines the language that the
-icon file names are provided in. Its value is "en" (English)
-by default.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="small-icon" type="j2ee:pathType"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
- The small-icon element contains the name of a file
- containing a small (16 x 16) icon image. The file
- name is a relative path within the Deployment
- Component's Deployment File.
-
- The image may be either in the JPEG or GIF format.
- The icon can be used by tools.
-
- Example:
-
- <small-icon>employee-service-icon16x16.jpg</small-icon>
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="large-icon" type="j2ee:pathType"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- The large-icon element contains the name of a file
- containing a large
- (32 x 32) icon image. The file name is a relative
- path within the Deployment Component's Deployment
- File.
-
- The image may be either in the JPEG or GIF format.
- The icon can be used by tools.
-
- Example:
-
- <large-icon>employee-service-icon32x32.jpg</large-icon>
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
-
- </xsd:sequence>
-
- <xsd:attribute ref="xml:lang"/>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="java-identifierType">
-<xsd:annotation>
-<xsd:documentation>
-
-The java-identifierType defines a Java identifier.
-The users of this type should further verify that
-the content does not contain Java reserved keywords.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:pattern value="($|_|\p{L})(\p{L}|\p{Nd}|_|$)*"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="jndi-nameType">
-<xsd:annotation>
-<xsd:documentation>
-
-The jndi-nameType type designates a JNDI name in the
-Deployment Component's environment and is relative to the
-java:comp/env context. A JNDI name must be unique within the
-Deployment Component.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string"/>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="local-homeType">
-<xsd:annotation>
-<xsd:documentation>
-
-The local-homeType defines the fully-qualified
-name of an enterprise bean's local home interface.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:fully-qualified-classType"/>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="localType">
-<xsd:annotation>
-<xsd:documentation>
-
-The localType defines the fully-qualified name of an
-enterprise bean's local interface.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:fully-qualified-classType"/>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="message-destination-linkType">
-<xsd:annotation>
-<xsd:documentation>
-
-The message-destination-linkType is used to link a message
-destination reference or message-driven bean to a message
-destination.
-
-The Assembler sets the value to reflect the flow of messages
-between producers and consumers in the application.
-
-The value must be the message-destination-name of a message
-destination in the same Deployment File or in another
-Deployment File in the same J2EE application unit.
-
-Alternatively, the value may be composed of a path name
-specifying a Deployment File containing the referenced
-message destination with the message-destination-name of the
-destination appended and separated from the path name by
-"#". The path name is relative to the Deployment File
-containing Deployment Component that is referencing the
-message destination. This allows multiple message
-destinations with the same name to be uniquely identified.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:fully-qualified-classType"/>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="message-destination-refType">
-<xsd:annotation>
-<xsd:documentation>
-
-The message-destination-ref element contains a declaration
-of Deployment Component's reference to a message destination
-associated with a resource in Deployment Component's
-environment. It consists of:
-
- - an optional description
- - the message destination reference name
- - the message destination type
- - a specification as to whether the
- destination is used for
- consuming or producing messages, or both
- - a link to the message destination
-
-Examples:
-
-<message-destination-ref>
- <message-destination-ref-name>jms/StockQueue
- </message-destination-ref-name>
- <message-destination-type>javax.jms.Queue
- </message-destination-type>
- <message-destination-usage>Consumes
- </message-destination-usage>
- <message-destination-link>CorporateStocks
- </message-destination-link>
-</message-destination-ref>
-
-</xsd:documentation>
-</xsd:annotation>
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="message-destination-ref-name"
- type="j2ee:jndi-nameType">
- <xsd:annotation>
- <xsd:documentation>
-
- The message-destination-ref-name element specifies
- the name of a message destination reference; its
- value is the environment entry name used in
- Deployment Component code. The name is a JNDI name
- relative to the java:comp/env context and must be
- unique within an ejb-jar (for enterprise beans) or a
- Deployment File (for others).
- %%%
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="message-destination-type"
- type="j2ee:message-destination-typeType"/>
- <xsd:element name="message-destination-usage"
- type="j2ee:message-destination-usageType"/>
- <xsd:element name="message-destination-link"
- type="j2ee:message-destination-linkType"
- minOccurs="0"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="message-destination-typeType">
-<xsd:annotation>
-<xsd:documentation>
-
-The message-destination-typeType specifies the type of
-the destination. The type is specified by the Java interface
-expected to be implemented by the destination.
-
-Example:
-
- <message-destination-type>javax.jms.Queue
- </message-destination-type>
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:fully-qualified-classType"/>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="message-destination-usageType">
-<xsd:annotation>
-<xsd:documentation>
-
-The message-destination-usageType specifies the use of the
-message destination indicated by the reference. The value
-indicates whether messages are consumed from the message
-destination, produced for the destination, or both. The
-Assembler makes use of this information in linking producers
-of a destination with its consumers.
-
-The value of the message-destination-usage element must be
-one of the following:
- Consumes
- Produces
- ConsumesProduces
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:enumeration value="Consumes"/>
- <xsd:enumeration value="Produces"/>
- <xsd:enumeration value="ConsumesProduces"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="message-destinationType">
-<xsd:annotation>
-<xsd:documentation>
-
-The message-destinationType specifies a message
-destination. The logical destination described by this
-element is mapped to a physical destination by the Deployer.
-
-The message destination element contains:
-
- - an optional description
- - an optional display-name
- - an optional icon
- - a message destination name which must be unique
- among message destination names within the same
- Deployment File.
-
-Example:
-
-<message-destination>
- <message-destination-name>CorporateStocks
- </message-destination-name>
-</message-destination>
-
-</xsd:documentation>
-</xsd:annotation>
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="display-name"
- type="j2ee:display-nameType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="icon"
- type="j2ee:iconType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="message-destination-name"
- type="j2ee:string">
- <xsd:annotation>
- <xsd:documentation>
-
- The message-destination-name element specifies a
- name for a message destination. This name must be
- unique among the names of message destinations
- within the Deployment File.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
-
- </xsd:sequence>
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="param-valueType">
-<xsd:annotation>
-<xsd:documentation>
-
-This type is a general type that can be used to declare
-parameter/value lists.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="param-name"
- type="j2ee:string">
- <xsd:annotation>
- <xsd:documentation>
-
- The param-name element contains the name of a
- parameter.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
-
- <xsd:element name="param-value"
- type="xsd:string">
- <xsd:annotation>
- <xsd:documentation>
-
- The param-value element contains the value of a
- parameter.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="pathType">
-<xsd:annotation>
-<xsd:documentation>
-
-The elements that use this type designate either a relative
-path or an absolute path starting with a "/".
-
-In elements that specify a pathname to a file within the
-same Deployment File, relative filenames (i.e., those not
-starting with "/") are considered relative to the root of
-the Deployment File's namespace. Absolute filenames (i.e.,
-those starting with "/") also specify names in the root of
-the Deployment File's namespace. In general, relative names
-are preferred. The exception is .war files where absolute
-names are preferred for consistency with the Servlet API.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string"/>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="remoteType">
-<xsd:annotation>
-<xsd:documentation>
-
-The remote element contains the fully-qualified name
-of the enterprise bean's remote interface.
-
-Example:
-
- <remote>com.wombat.empl.EmployeeService</remote>
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:fully-qualified-classType"/>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="res-authType">
-<xsd:annotation>
-<xsd:documentation>
-
-The res-authType specifies whether the Deployment Component
-code signs on programmatically to the resource manager, or
-whether the Container will sign on to the resource manager
-on behalf of the Deployment Component. In the latter case,
-the Container uses information that is supplied by the
-Deployer.
-
-The value must be one of the two following:
-
- Application
- Container
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:enumeration value="Application"/>
- <xsd:enumeration value="Container"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="res-sharing-scopeType">
-<xsd:annotation>
-<xsd:documentation>
-
-The res-sharing-scope type specifies whether connections
-obtained through the given resource manager connection
-factory reference can be shared. The value, if specified,
-must be one of the two following:
-
- Shareable
- Unshareable
-
-The default value is Shareable.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:enumeration value="Shareable"/>
- <xsd:enumeration value="Unshareable"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="resource-env-refType">
-<xsd:annotation>
-<xsd:documentation>
-
-The resource-env-refType is used to define
-resource-env-type elements. It contains a declaration of a
-Deployment Component's reference to an administered object
-associated with a resource in the Deployment Component's
-environment. It consists of an optional description, the
-resource environment reference name, and an indication of
-the resource environment reference type expected by the
-Deployment Component code.
-
-Example:
-
-<resource-env-ref>
- <resource-env-ref-name>jms/StockQueue
- </resource-env-ref-name>
- <resource-env-ref-type>javax.jms.Queue
- </resource-env-ref-type>
-</resource-env-ref>
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="resource-env-ref-name"
- type="j2ee:jndi-nameType">
- <xsd:annotation>
- <xsd:documentation>
-
- The resource-env-ref-name element specifies the name
- of a resource environment reference; its value is
- the environment entry name used in
- the Deployment Component code. The name is a JNDI
- name relative to the java:comp/env context and must
- be unique within a Deployment Component.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
-
- <xsd:element name="resource-env-ref-type"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
-
- The resource-env-ref-type element specifies the type
- of a resource environment reference. It is the
- fully qualified name of a Java language class or
- interface.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
-
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="resource-refType">
-<xsd:annotation>
-<xsd:documentation>
-
-The resource-refType contains a declaration of a
-Deployment Component's reference to an external resource. It
-consists of an optional description, the resource manager
-connection factory reference name, the indication of the
-resource manager connection factory type expected by the
-Deployment Component code, the type of authentication
-(Application or Container), and an optional specification of
-the shareability of connections obtained from the resource
-(Shareable or Unshareable).
-
-Example:
-
-<resource-ref>
- <res-ref-name>jdbc/EmployeeAppDB</res-ref-name>
- <res-type>javax.sql.DataSource</res-type>
- <res-auth>Container</res-auth>
- <res-sharing-scope>Shareable</res-sharing-scope>
-</resource-ref>
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="res-ref-name"
- type="j2ee:jndi-nameType">
- <xsd:annotation>
- <xsd:documentation>
-
- The res-ref-name element specifies the name of a
- resource manager connection factory reference.
- The name is a JNDI name relative to the
- java:comp/env context.
- The name must be unique within a Deployment File.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
-
- <xsd:element name="res-type"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
-
- The res-type element specifies the type of the data
- source. The type is specified by the fully qualified
- Java language class or interface
- expected to be implemented by the data source.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
-
- <xsd:element name="res-auth"
- type="j2ee:res-authType"/>
-
- <xsd:element name="res-sharing-scope"
- type="j2ee:res-sharing-scopeType"
- minOccurs="0"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="role-nameType">
-<xsd:annotation>
-<xsd:documentation>
-
-The role-nameType designates the name of a security role.
-
-The name must conform to the lexical rules for an NMTOKEN.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="xsd:NMTOKEN"/>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="run-asType">
-<xsd:annotation>
-<xsd:documentation>
-
-The run-asType specifies the run-as identity to be
-used for the execution of a component. It contains an
-optional description, and the name of a security role.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="role-name"
- type="j2ee:role-nameType"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="security-role-refType">
-<xsd:annotation>
-<xsd:documentation>
-
-The security-role-refType contains the declaration of a
-security role reference in a component's or a
-Deployment Component's code. The declaration consists of an
-optional description, the security role name used in the
-code, and an optional link to a security role. If the
-security role is not specified, the Deployer must choose an
-appropriate security role.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="role-name"
- type="j2ee:role-nameType">
- <xsd:annotation>
- <xsd:documentation>
-
- The value of the role-name element must be the String used
- as the parameter to the
- EJBContext.isCallerInRole(String roleName) method or the
- HttpServletRequest.isUserInRole(String role) method.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
-
- <xsd:element name="role-link"
- type="j2ee:role-nameType"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- The role-link element is a reference to a defined
- security role. The role-link element must contain
- the name of one of the security roles defined in the
- security-role elements.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="security-roleType">
-<xsd:annotation>
-<xsd:documentation>
-
-The security-roleType contains the definition of a security
-role. The definition consists of an optional description of the
-security role, and the security role name.
-
-Example:
-
- <security-role>
- <description>
- This role includes all employees who are authorized
- to access the employee service application.
- </description>
- <role-name>employee</role-name>
- </security-role>
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="role-name"
- type="j2ee:role-nameType"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="string">
-<xsd:annotation>
-<xsd:documentation>
-
-This is a special string datatype that is defined by J2EE as
-a base type for defining collapsed strings. When schemas
-require trailing/leading space elimination as well as
-collapsing the existing whitespace, this base type may be
-used.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="xsd:string">
- <xsd:whiteSpace value="collapse"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="true-falseType">
-<xsd:annotation>
-<xsd:documentation>
-
-This simple type designates a boolean with only two
-permissible values
-
-- true
-- false
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="xsd:boolean">
- <xsd:pattern value="(true|false)"/>
- </xsd:restriction>
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="url-patternType">
-<xsd:annotation>
-<xsd:documentation>
-
-The url-patternType contains the url pattern of the mapping. It must
-follow the rules specified in Section 11.2 of the Servlet API
-Specification.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string"/>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="war-pathType">
-<xsd:annotation>
-<xsd:documentation>
-
-The elements that use this type designate a path starting
-with a "/" and interpreted relative to the root of a WAR
-file.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:pattern value="/.*"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-</xsd:schema>
-
diff --git a/src/test/resources/xbean/compile/scomp/j2ee/jsp_2_0.xsd b/src/test/resources/xbean/compile/scomp/j2ee/jsp_2_0.xsd
deleted file mode 100755
index 61d5668..0000000
--- a/src/test/resources/xbean/compile/scomp/j2ee/jsp_2_0.xsd
+++ /dev/null
@@ -1,304 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
- targetNamespace="http://java.sun.com/xml/ns/j2ee"
- xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- elementFormDefault="qualified"
- attributeFormDefault="unqualified"
- version="2.0">
-<xsd:annotation>
-<xsd:documentation>
-@(#)jsp_2_0.xsds 1.10 08/20/02
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:annotation>
-<xsd:documentation>
-
-Copyright 2002 Sun Microsystems, Inc., 901 San Antonio
-Road, Palo Alto, California 94303, U.S.A. All rights
-reserved.
-
-Sun Microsystems, Inc. has intellectual property rights
-relating to technology described in this document. In
-particular, and without limitation, these intellectual
-property rights may include one or more of the U.S. patents
-listed at http://www.sun.com/patents and one or more
-additional patents or pending patent applications in the
-U.S. and other countries.
-
-This document and the technology which it describes are
-distributed under licenses restricting their use, copying,
-distribution, and decompilation. No part of this document
-may be reproduced in any form by any means without prior
-written authorization of Sun and its licensors, if any.
-
-Third-party software, including font technology, is
-copyrighted and licensed from Sun suppliers.
-
-Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
-JavaServer Pages, Enterprise JavaBeans and the Java Coffee
-Cup logo are trademarks or registered trademarks of Sun
-Microsystems, Inc. in the U.S. and other countries.
-
-Federal Acquisitions: Commercial Software - Government Users
-Subject to Standard License Terms and Conditions.
-
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:annotation>
-<xsd:documentation>
-
-This is the XML Schema for the JSP 2.0 deployment descriptor
-types. The JSP 2.0 schema contains all the special
-structures and datatypes that are necessary to use JSP files
-from a web application.
-
-The contents of this schema is used by the web-app_2_4.xsd
-file to define JSP specific content.
-
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:annotation>
-<xsd:documentation>
-
-The following conventions apply to all J2EE
-deployment descriptor elements unless indicated otherwise.
-
-- In elements that specify a pathname to a file within the
- same JAR file, relative filenames (i.e., those not
- starting with "/") are considered relative to the root of
- the JAR file's namespace. Absolute filenames (i.e., those
- starting with "/") also specify names in the root of the
- JAR file's namespace. In general, relative names are
- preferred. The exception is .war files where absolute
- names are preferred for consistency with the Servlet API.
-
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:include schemaLocation="j2ee_1_4.xsd"/>
-
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="jsp-configType">
-<xsd:annotation>
-<xsd:documentation>
-
-The jsp-configType is used to provide global configuration
-information for the JSP files in a web application. It has
-two subelements, taglib and jsp-property-group.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="taglib"
- type="j2ee:taglibType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="jsp-property-group"
- type="j2ee:jsp-property-groupType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="jsp-fileType">
-<xsd:annotation>
-<xsd:documentation>
-
-The jsp-file element contains the full path to a JSP file
-within the web application beginning with a `/'.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:pathType"/>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="jsp-property-groupType">
-<xsd:annotation>
-<xsd:documentation>
-
-The jsp-property-groupType is used to group a number of
-files so they can be given global property information.
-All files so described are deemed to be JSP files. The
-following additional properties can be described:
-
- - Control enabling of EL evaluation.
- - Control enabling of Scripting elements.
- - Indicate pageEncoding information.
- - Indicating that a resource is a JSP document
- - Prelude and Coda automatic includes.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="display-name"
- type="j2ee:display-nameType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="url-pattern"
- type="j2ee:url-patternType"
- maxOccurs="unbounded"/>
- <xsd:element name="el-enabled"
- type="j2ee:true-falseType"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- Can be used to easily set the isELEnabled
- property of a group of JSP pages. By default, the
- EL evaluation is enabled for Web Applications using
- a Servlet 2.4 or greater web.xml.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="page-encoding"
- type="j2ee:string"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- The valid values of page-encoding are those of the
- pageEncoding page directive. It is a
- translation-time error to define the pageEncoding
- of a JSP page through one value in the JSP
- configuration element and then give it a different
- value in a pageEncoding directive, but it is legal
- to give it the same value.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="scripting-enabled"
- type="j2ee:true-falseType"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- Can be used to easily set the isScriptingEnabled
- property of a group of JSP pages. By default,
- scripting is enabled.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="is-xml"
- type="j2ee:true-falseType"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- If true, denotes that the group of resources
- that match the URL pattern are JSP documents,
- and thus must be interpreted as XML documents.
- If false, the resources are assumed to not
- be JSP documents, unless there is another
- property group that indicates otherwise.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="include-prelude"
- type="j2ee:pathType"
- minOccurs="0"
- maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
-
- The include-prelude element is a context-relative
- path that must correspond to an element in the
- Web Application. When the element is present,
- the given path will be automatically included (as
- in an include directive) at the beginning of each
- JSP page in this jsp-property-group.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="include-coda"
- type="j2ee:pathType"
- minOccurs="0"
- maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
-
- The include-coda element is a context-relative
- path that must correspond to an element in the
- Web Application. When the element is present,
- the given path will be automatically included (as
- in an include directive) at the end of each
- JSP page in this jsp-property-group.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="taglibType">
-<xsd:annotation>
-<xsd:documentation>
-
-A taglib can be used to provide information on a tag
-library that is used by a JSP page within the Web
-Application.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="taglib-uri"
- type="j2ee:string">
- <xsd:annotation>
- <xsd:documentation>
-
- A taglib-uri element describes a URI identifying a
- tag library used in the web application. The body
- of the taglib-uri element may be either an
- absolute URI specification, or a relative URI.
- There should be no entries in web.xml with the
- same taglib-uri value.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
-
- <xsd:element name="taglib-location"
- type="j2ee:pathType">
- <xsd:annotation>
- <xsd:documentation>
-
- the taglib-location element contains the location
- (as a resource relative to the root of the web
- application) where to find the Tag Library
- Description file for the tag library.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
-
- </xsd:sequence>
-
-</xsd:complexType>
-
-</xsd:schema>
-
diff --git a/src/test/resources/xbean/compile/scomp/j2ee/web-app_2_4.xsd b/src/test/resources/xbean/compile/scomp/j2ee/web-app_2_4.xsd
deleted file mode 100755
index b9e7b43..0000000
--- a/src/test/resources/xbean/compile/scomp/j2ee/web-app_2_4.xsd
+++ /dev/null
@@ -1,1278 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
- targetNamespace="http://java.sun.com/xml/ns/j2ee"
- xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- elementFormDefault="qualified"
- attributeFormDefault="unqualified"
- version="2.4">
-<xsd:annotation>
-<xsd:documentation>
-@(#)web-app_2_4.xsds 1.34 02/08/01
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:annotation>
-<xsd:documentation>
-
-Copyright 2002 Sun Microsystems, Inc., 901 San Antonio
-Road, Palo Alto, California 94303, U.S.A. All rights
-reserved.
-
-Sun Microsystems, Inc. has intellectual property rights
-relating to technology described in this document. In
-particular, and without limitation, these intellectual
-property rights may include one or more of the U.S. patents
-listed at http://www.sun.com/patents and one or more
-additional patents or pending patent applications in the
-U.S. and other countries.
-
-This document and the technology which it describes are
-distributed under licenses restricting their use, copying,
-distribution, and decompilation. No part of this document
-may be reproduced in any form by any means without prior
-written authorization of Sun and its licensors, if any.
-
-Third-party software, including font technology, is
-copyrighted and licensed from Sun suppliers.
-
-Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
-JavaServer Pages, Enterprise JavaBeans and the Java Coffee
-Cup logo are trademarks or registered trademarks of Sun
-Microsystems, Inc. in the U.S. and other countries.
-
-Federal Acquisitions: Commercial Software - Government Users
-Subject to Standard License Terms and Conditions.
-
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:annotation>
-<xsd:documentation>
-<![CDATA[
-This is the XML Schema for the Servlet 2.4 deployment
-descriptor. All Servlet deployment descriptors must
-indicate the web application schema by using the J2EE
-namespace:
-
-http://java.sun.com/xml/ns/j2ee
-
-and by indicating the version of the schema by
-using the version element as shown below:
-
- <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="..."
- version="2.4">
- ...
- </web-app>
-
-The instance documents may indicate the published version of
-the schema using the xsi:schemaLocation attribute for J2EE
-namespace with the following location:
-
-http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd
-]]>
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:annotation>
-<xsd:documentation>
-
-The following conventions apply to all J2EE
-deployment descriptor elements unless indicated otherwise.
-
-- In elements that specify a pathname to a file within the
- same JAR file, relative filenames (i.e., those not
- starting with "/") are considered relative to the root of
- the JAR file's namespace. Absolute filenames (i.e., those
- starting with "/") also specify names in the root of the
- JAR file's namespace. In general, relative names are
- preferred. The exception is .war files where absolute
- names are preferred for consistency with the Servlet API.
-
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:include schemaLocation="j2ee_1_4.xsd"/>
-<xsd:include schemaLocation="jsp_2_0.xsd"/>
-
-
-<!-- **************************************************** -->
-
-
-<xsd:element name="web-app" type="j2ee:web-appType">
- <xsd:annotation>
- <xsd:documentation>
-
- The web-app element is the root of the deployment
- descriptor for a web application.
-
- </xsd:documentation>
- </xsd:annotation>
-
- <xsd:unique name="servlet-name-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The servlet element contains the name of a servlet.
- The name must be unique within the web application.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:servlet"/>
- <xsd:field xpath="j2ee:servlet-name"/>
- </xsd:unique>
-
- <xsd:unique name="filter-name-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The filter element contains the name of a filter.
- The name must be unique within the web application.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:filter"/>
- <xsd:field xpath="j2ee:filter-name"/>
- </xsd:unique>
-
- <xsd:unique name="ejb-local-ref-name-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The ejb-local-ref-name element contains the name of an EJB
- reference. The EJB reference is an entry in the web
- application's environment and is relative to the
- java:comp/env context. The name must be unique within
- the web application.
-
- It is recommended that name is prefixed with "ejb/".
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:ejb-local-ref"/>
- <xsd:field xpath="j2ee:ejb-ref-name"/>
- </xsd:unique>
-
- <xsd:unique name="ejb-ref-name-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The ejb-ref-name element contains the name of an EJB
- reference. The EJB reference is an entry in the web
- application's environment and is relative to the
- java:comp/env context. The name must be unique within
- the web application.
-
- It is recommended that name is prefixed with "ejb/".
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:ejb-ref"/>
- <xsd:field xpath="j2ee:ejb-ref-name"/>
- </xsd:unique>
-
- <xsd:unique name="resource-env-ref-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The resource-env-ref-name element specifies the name of
- a resource environment reference; its value is the
- environment entry name used in the web application code.
- The name is a JNDI name relative to the java:comp/env
- context and must be unique within a web application.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:resource-env-ref"/>
- <xsd:field xpath="j2ee:resource-env-ref-name"/>
- </xsd:unique>
-
- <xsd:unique name="message-destination-ref-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The message-destination-ref-name element specifies the name of
- a message destination reference; its value is the
- environment entry name used in the web application code.
- The name is a JNDI name relative to the java:comp/env
- context and must be unique within a web application.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:message-destination-ref"/>
- <xsd:field xpath="j2ee:message-destination-ref-name"/>
- </xsd:unique>
-
- <xsd:unique name="res-ref-name-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The res-ref-name element specifies the name of a
- resource manager connection factory reference. The name
- is a JNDI name relative to the java:comp/env context.
- The name must be unique within a web application.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:resource-ref"/>
- <xsd:field xpath="j2ee:res-ref-name"/>
- </xsd:unique>
-
- <xsd:unique name="env-entry-name-uniqueness">
- <xsd:annotation>
- <xsd:documentation>
-
- The env-entry-name element contains the name of a web
- application's environment entry. The name is a JNDI
- name relative to the java:comp/env context. The name
- must be unique within a web application.
-
- </xsd:documentation>
- </xsd:annotation>
-
- <xsd:selector xpath="j2ee:env-entry"/>
- <xsd:field xpath="j2ee:env-entry-name"/>
- </xsd:unique>
-
- <xsd:key name="role-name-key">
- <xsd:annotation>
- <xsd:documentation>
-
- A role-name-key is specified to allow the references
- from the security-role-refs.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:security-role"/>
- <xsd:field xpath="j2ee:role-name"/>
- </xsd:key>
-
- <xsd:keyref name="role-name-references"
- refer="j2ee:role-name-key">
- <xsd:annotation>
- <xsd:documentation>
-
- The keyref indicates the references from
- security-role-ref to a specified role-name.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:servlet/j2ee:security-role-ref"/>
- <xsd:field xpath="j2ee:role-link"/>
- </xsd:keyref>
-
-</xsd:element>
-
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="auth-constraintType">
-<xsd:annotation>
-<xsd:documentation>
-
-The auth-constraintType indicates the user roles that
-should be permitted access to this resource
-collection. The role-name used here must either correspond
-to the role-name of one of the security-role elements
-defined for this web application, or be the specially
-reserved role-name "*" that is a compact syntax for
-indicating all roles in the web application. If both "*"
-and rolenames appear, the container interprets this as all
-roles. If no roles are defined, no user is allowed access
-to the portion of the web application described by the
-containing security-constraint. The container matches
-role names case sensitively when determining access.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="role-name"
- type="j2ee:role-nameType"
- minOccurs="0" maxOccurs="unbounded"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="auth-methodType">
-<xsd:annotation>
-<xsd:documentation>
-
-The auth-methodType is used to configure the authentication
-mechanism for the web application. As a prerequisite to
-gaining access to any web resources which are protected by
-an authorization constraint, a user must have authenticated
-using the configured mechanism. Legal values are "BASIC",
-"DIGEST", "FORM", or "CLIENT-CERT".
-
-Used in: login-config
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:enumeration value="BASIC"/>
- <xsd:enumeration value="DIGEST"/>
- <xsd:enumeration value="FORM"/>
- <xsd:enumeration value="CLIENT-CERT"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="dispatcherType">
-<xsd:annotation>
-<xsd:documentation>
-
-The dispatcher has three legal values, FORWARD and REQUEST
-and INCLUDE. A value of FORWARD means the Filter
-will be applied under RequestDispatcher.forward() calls.
-A value of REQUEST means the Filter will be applied
-under ordinary client calls to the path or servlet. A value of
-INCLUDE means the Filter will be applied under
-RequestDispatcher.include() calls.
-The absence of any dispatcher elements in a
-filter-mapping indicates a default of applying
-filters only under ordinary client calls to the path or servlet.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:enumeration value="FORWARD"/>
- <xsd:enumeration value="INCLUDE"/>
- <xsd:enumeration value="REQUEST"/>
-
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="error-codeType">
-<xsd:annotation>
-<xsd:documentation>
-
-The error-code contains an HTTP error code, ex: 404
-
-Used in: error-page
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="positiveInteger"/>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="error-pageType">
-<xsd:annotation>
-<xsd:documentation>
-
-The error-pageType contains a mapping between an error code
-or exception type to the path of a resource in the web
-application.
-
-Used in: web-app
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <choice>
- <xsd:element name="error-code"
- type="j2ee:error-codeType"/>
-
- <xsd:element name="exception-type"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
-
- The exception-type contains a fully qualified class
- name of a Java exception type.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- </choice>
-
- <xsd:element name="location"
- type="j2ee:pathType">
- <xsd:annotation>
- <xsd:documentation>
-
- The location element contains the location of the
- resource in the web application relative to the root of
- the web application. The value of the location must have
- a leading `/'.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="filter-mappingType">
-<xsd:annotation>
-<xsd:documentation>
-
-Declaration of the filter mappings in this web
-application is done by using filter-mappingType.
-The container uses the filter-mapping
-declarations to decide which filters to apply to a request,
-and in what order. The container matches the request URI to
-a Servlet in the normal way. To determine which filters to
-apply it matches filter-mapping declarations either on
-servlet-name, or on url-pattern for each filter-mapping
-element, depending on which style is used. The order in
-which filters are invoked is the order in which
-filter-mapping declarations that match a request URI for a
-servlet appear in the list of filter-mapping elements.The
-filter-name value must be the value of the filter-name
-sub-elements of one of the filter declarations in the
-deployment descriptor.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="filter-name"
- type="j2ee:filter-nameType"/>
- <choice>
- <xsd:element name="url-pattern"
- type="j2ee:url-patternType"/>
- <xsd:element name="servlet-name"
- type="j2ee:servlet-nameType"/>
- </choice>
- <xsd:element name="dispatcher"
- type="j2ee:dispatcherType"
- minOccurs="0" maxOccurs="unbounded"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="filter-nameType">
-<xsd:annotation>
-<xsd:documentation>
-
-The logical name of the filter is declare
-by using filter-nameType. This name is used to map the
-filter. Each filter name is unique within the web
-application.
-
-Used in: filter, filter-mapping
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string"/>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="filterType">
-<xsd:annotation>
-<xsd:documentation>
-
-The filterType is used to declare a filter in the web
-application. The filter is mapped to either a servlet or a
-URL pattern in the filter-mapping element, using the
-filter-name value to reference. Filters can access the
-initialization parameters declared in the deployment
-descriptor at runtime via the FilterConfig interface.
-
-Used in: web-app
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="display-name"
- type="j2ee:display-nameType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="icon"
- type="j2ee:iconType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="filter-name"
- type="j2ee:filter-nameType"/>
- <xsd:element name="filter-class"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
-
- The fully qualified classname of the filter.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
-
- <xsd:element name="init-param"
- type="j2ee:param-valueType"
- minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
-
- The init-param element contains a name/value pair as
- an initialization param of a servlet filter
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="form-login-configType">
-<xsd:annotation>
-<xsd:documentation>
-
-The form-login-configType specifies the login and error
-pages that should be used in form based login. If form based
-authentication is not used, these elements are ignored.
-
-Used in: login-config
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
-
- <xsd:element name="form-login-page"
- type="j2ee:war-pathType">
- <xsd:annotation>
- <xsd:documentation>
-
- The form-login-page element defines the location in the web app
- where the page that can be used for login can be found.
- The path begins with a leading / and is
- interpreted relative to the root of the WAR.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
-
- <xsd:element name="form-error-page"
- type="j2ee:war-pathType">
- <xsd:annotation>
- <xsd:documentation>
-
- The form-error-page element defines the location in
- the web app where the error page that is displayed
- when login is not successful can be found.
- The path begins with a leading / and is interpreted
- relative to the root of the WAR.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
-
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="http-methodType">
-<xsd:annotation>
-
-<xsd:documentation>
-The http-method contains an HTTP method recognized by the web-app, i.e.
-(GET | POST |...).
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:enumeration value="GET"/>
- <xsd:enumeration value="POST"/>
- <xsd:enumeration value="PUT"/>
- <xsd:enumeration value="DELETE"/>
- <xsd:enumeration value="HEAD"/>
- <xsd:enumeration value="OPTIONS"/>
- <xsd:enumeration value="TRACE"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="listenerType">
-<xsd:annotation>
-<xsd:documentation>
-
-The listenerType indicates the deployment properties for a web
-application listener bean.
-
-Used in: web-app:listenerType
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="display-name"
- type="j2ee:display-nameType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="icon"
- type="j2ee:iconType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="listener-class"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
-
- The listener-class element declares a class in the
- application must be registered as a web
- application listener bean. The value is the fully
- qualified classname of the listener class.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="locale-encoding-mapping-listType">
-<xsd:annotation>
-<xsd:documentation>
-
-The locale-encoding-mapping-list contains one or more
-locale-encoding-mapping(s).
-
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:sequence>
- <xsd:element name="locale-encoding-mapping"
- type="j2ee:locale-encoding-mappingType"
- maxOccurs="unbounded"/>
-</xsd:sequence>
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="locale-encoding-mappingType">
-<xsd:annotation>
-<xsd:documentation>
-
-The locale-encoding-mapping contains locale name and
-encoding name. The locale name must be either "Language-code",
-such as "ja", defined by ISO-639 or "Language-code_Country-code",
-such as "ja_JP". "Country code" is defined by ISO-3166.
-
-</xsd:documentation>
-</xsd:annotation>
-
-<xsd:sequence>
- <xsd:element name="locale"
- type="j2ee:string"/>
- <xsd:element name="encoding"
- type="j2ee:string"/>
-</xsd:sequence>
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="login-configType">
-<xsd:annotation>
-<xsd:documentation>
-
-The login-configType is used to configure the authentication
-method that should be used, the realm name that should be
-used for this application, and the attributes that are
-needed by the form login mechanism.
-
-Used in: web-app
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="auth-method"
- type="j2ee:auth-methodType"
- minOccurs="0"/>
- <xsd:element name="realm-name"
- type="j2ee:string" minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- The realm name element specifies the realm name to
- use in HTTP Basic authorization.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="form-login-config"
- type="j2ee:form-login-configType"
- minOccurs="0"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="mime-mappingType">
-<xsd:annotation>
-<xsd:documentation>
-
-The mime-mappingType defines a mapping between an extension
-and a mime type.
-
-Used in: web-app
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:annotation>
- <xsd:documentation>
-
- The extension element contains a string describing an
- extension. example: "txt"
-
- </xsd:documentation>
- </xsd:annotation>
-
- <xsd:element name="extension"
- type="j2ee:string"/>
- <xsd:element name="mime-type"
- type="j2ee:mime-typeType"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="mime-typeType">
-<xsd:annotation>
-<xsd:documentation>
-
-The mime-typeType is used to indicate a defined mime type.
-
-Example:
-"text/plain"
-
-Used in: mime-mapping
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:pattern value="[\p{L}\-\p{Nd}]+/[\p{L}\-\p{Nd}\.]+"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="security-constraintType">
-<xsd:annotation>
-<xsd:documentation>
-
-The security-constraintType is used to associate
-security constraints with one or more web resource
-collections
-
-Used in: web-app
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="display-name"
- type="j2ee:display-nameType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="web-resource-collection"
- type="j2ee:web-resource-collectionType"
- maxOccurs="unbounded"/>
- <xsd:element name="auth-constraint"
- type="j2ee:auth-constraintType"
- minOccurs="0"/>
- <xsd:element name="user-data-constraint"
- type="j2ee:user-data-constraintType"
- minOccurs="0"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="servlet-mappingType">
-<xsd:annotation>
-<xsd:documentation>
-
-The servlet-mappingType defines a mapping between a
-servlet and a url pattern.
-
-Used in: web-app
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="servlet-name"
- type="j2ee:servlet-nameType"/>
- <xsd:element name="url-pattern"
- type="j2ee:url-patternType"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="servlet-nameType">
-<xsd:annotation>
-<xsd:documentation>
-
-The servlet-name element contains the canonical name of the
-servlet. Each servlet name is unique within the web
-application.
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string"/>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="servletType">
-<xsd:annotation>
-<xsd:documentation>
-
-The servletType is used to declare a servlet.
-It contains the declarative data of a
-servlet. If a jsp-file is specified and the load-on-startup
-element is present, then the JSP should be precompiled and
-loaded.
-
-Used in: web-app
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="display-name"
- type="j2ee:display-nameType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="icon"
- type="j2ee:iconType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="servlet-name"
- type="j2ee:servlet-nameType"/>
- <choice>
- <xsd:element name="servlet-class"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
-
- The servlet-class element contains the fully
- qualified class name of the servlet.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
-
- <xsd:element name="jsp-file"
- type="j2ee:jsp-fileType"/>
-
- </choice>
-
- <xsd:element name="init-param"
- type="j2ee:param-valueType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="load-on-startup"
- type="xsd:integer"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- The load-on-startup element indicates that this
- servlet should be loaded (instantiated and have
- its init() called) on the startup of the web
- application. The optional contents of these
- element must be an integer indicating the order in
- which the servlet should be loaded. If the value
- is a negative integer, or the element is not
- present, the container is free to load the servlet
- whenever it chooses. If the value is a positive
- integer or 0, the container must load and
- initialize the servlet as the application is
- deployed. The container must guarantee that
- servlets marked with lower integers are loaded
- before servlets marked with higher integers. The
- container may choose the order of loading of
- servlets with the same load-on-start-up value.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="run-as"
- type="j2ee:run-asType"
- minOccurs="0"/>
- <xsd:element name="security-role-ref"
- type="j2ee:security-role-refType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="deployment-extension"
- type="j2ee:deployment-extensionType"
- minOccurs="0" maxOccurs="unbounded"/>
- </xsd:sequence>
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="session-configType">
-<xsd:annotation>
-<xsd:documentation>
-
-The session-configType defines the session parameters
-for this web application.
-
-Used in: web-app
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="session-timeout"
- type="xsd:nonNegativeInteger"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- The session-timeout element defines the default
- session timeout interval for all sessions created
- in this web application. The specified timeout
- must be expressed in a whole number of minutes.
- If the timeout is 0 or less, the container ensures
- the default behaviour of sessions is never to time
- out. If this element is not specified, the container
- must set its default timeout period.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="transport-guaranteeType">
-<xsd:annotation>
-<xsd:documentation>
-
-The transport-guaranteeType specifies that the communication
-between client and server should be NONE, INTEGRAL, or
-CONFIDENTIAL. NONE means that the application does not
-require any transport guarantees. A value of INTEGRAL means
-that the application requires that the data sent between the
-client and server be sent in such a way that it can't be
-changed in transit. CONFIDENTIAL means that the application
-requires that the data be transmitted in a fashion that
-prevents other entities from observing the contents of the
-transmission. In most cases, the presence of the INTEGRAL or
-CONFIDENTIAL flag will indicate that the use of SSL is
-required.
-
-Used in: user-data-constraint
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:enumeration value="NONE"/>
- <xsd:enumeration value="INTEGRAL"/>
- <xsd:enumeration value="CONFIDENTIAL"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="user-data-constraintType">
-<xsd:annotation>
-<xsd:documentation>
-
-The user-data-constraintType is used to indicate how
-data communicated between the client and container should be
-protected.
-
-Used in: security-constraint
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="transport-guarantee"
- type="j2ee:transport-guaranteeType"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:simpleType name="web-app-versionType">
-<xsd:annotation>
-<xsd:documentation>
-
-This type contains the recognized versions of
-web-application supported. It is used to designate the
-version of the web application.
-
-Example:
-
-<web-app>
- <version>2.4</version>
-...
-</web-app>
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:restriction base="j2ee:string">
- <xsd:enumeration value="2.4"/>
- </xsd:restriction>
-
-</xsd:simpleType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="web-appType">
-
- <xsd:sequence>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="display-name"
- type="j2ee:display-nameType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="icon"
- type="j2ee:iconType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="distributable"
- type="j2ee:emptyType"
- minOccurs="0"/>
- <xsd:element name="context-param"
- type="j2ee:param-valueType"
- minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
-
- The context-param element contains the declaration
- of a web application's servlet context
- initialization parameters.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
-
- <xsd:element name="filter"
- type="j2ee:filterType"
- minOccurs="0" maxOccurs="unbounded"/>
- <xsd:element name="filter-mapping"
- type="j2ee:filter-mappingType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="listener"
- type="j2ee:listenerType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="servlet"
- type="j2ee:servletType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="servlet-mapping"
- type="j2ee:servlet-mappingType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="session-config"
- type="j2ee:session-configType"
- minOccurs="0"/>
- <xsd:element name="mime-mapping"
- type="j2ee:mime-mappingType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="welcome-file-list"
- type="j2ee:welcome-file-listType"
- minOccurs="0"/>
- <xsd:element name="error-page"
- type="j2ee:error-pageType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="jsp-config"
- type="j2ee:jsp-configType"
- minOccurs="0"/>
- <xsd:element name="resource-env-ref"
- type="j2ee:resource-env-refType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="message-destination-ref"
- type="j2ee:message-destination-refType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="resource-ref"
- type="j2ee:resource-refType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="security-constraint"
- type="j2ee:security-constraintType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="login-config"
- type="j2ee:login-configType"
- minOccurs="0"/>
- <xsd:element name="security-role"
- type="j2ee:security-roleType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="env-entry"
- type="j2ee:env-entryType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="ejb-ref"
- type="j2ee:ejb-refType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="ejb-local-ref"
- type="j2ee:ejb-local-refType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="message-destination"
- type="j2ee:message-destinationType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="locale-encoding-mapping-list"
- type="j2ee:locale-encoding-mapping-listType"
- minOccurs="0"
- maxOccurs="1"/>
- <xsd:element name="deployment-extension"
- type="j2ee:deployment-extensionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- </xsd:sequence>
-
- <xsd:attribute name="version"
- type="j2ee:web-app-versionType"
- use="required"/>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="web-resource-collectionType">
-<xsd:annotation>
-<xsd:documentation>
-
-The web-resource-collectionType is used to identify a subset
-of the resources and HTTP methods on those resources within
-a web application to which a security constraint applies. If
-no HTTP methods are specified, then the security constraint
-applies to all HTTP methods.
-
-Used in: security-constraint
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="web-resource-name"
- type="j2ee:string">
- <xsd:annotation>
- <xsd:documentation>
-
- The web-resource-name contains the name of this web
- resource collection.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
- <xsd:element name="url-pattern"
- type="j2ee:url-patternType"
- maxOccurs="unbounded"/>
- <xsd:element name="http-method"
- type="j2ee:http-methodType"
- minOccurs="0" maxOccurs="unbounded"/>
- </xsd:sequence>
-
-</xsd:complexType>
-
-<!-- **************************************************** -->
-
-<xsd:complexType name="welcome-file-listType">
-<xsd:annotation>
-<xsd:documentation>
-
-The welcome-file-list contains an ordered list of welcome
-files elements.
-
-Used in: web-app
-
-</xsd:documentation>
-</xsd:annotation>
-
- <xsd:sequence>
- <xsd:element name="welcome-file"
- type="j2ee:string"
- maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
-
- The welcome-file element contains file name to use
- as a default welcome file, such as index.html
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- </xsd:sequence>
-
-</xsd:complexType>
-
-</xsd:schema>
-
