Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
WINDUP-1099 adding java ee schemas (#1003)
- Loading branch information
1 parent
4edea56
commit 1c8894b
Showing
54 changed files
with
52,714 additions
and
4 deletions.
There are no files selected for viewing
310 changes: 310 additions & 0 deletions
310
rules-xml/api/src/main/resources/catalog/xsd/application-client_5.xsd
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,310 @@ | ||
<?xml version="1.0" encoding="UTF-8"?> | ||
<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema" | ||
targetNamespace="http://java.sun.com/xml/ns/javaee" | ||
xmlns:javaee="http://java.sun.com/xml/ns/javaee" | ||
xmlns:xsd="http://www.w3.org/2001/XMLSchema" | ||
elementFormDefault="qualified" | ||
attributeFormDefault="unqualified" | ||
version="5"> | ||
<xsd:annotation> | ||
<xsd:documentation> | ||
@(#)application-client_5.xsds 1.26 02/17/06 | ||
</xsd:documentation> | ||
</xsd:annotation> | ||
|
||
<xsd:annotation> | ||
<xsd:documentation> | ||
|
||
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER. | ||
|
||
Copyright 2003-2007 Sun Microsystems, Inc. All rights reserved. | ||
|
||
The contents of this file are subject to the terms of either the | ||
GNU General Public License Version 2 only ("GPL") or the Common | ||
Development and Distribution License("CDDL") (collectively, the | ||
"License"). You may not use this file except in compliance with | ||
the License. You can obtain a copy of the License at | ||
https://glassfish.dev.java.net/public/CDDL+GPL.html or | ||
glassfish/bootstrap/legal/LICENSE.txt. See the License for the | ||
specific language governing permissions and limitations under the | ||
License. | ||
|
||
When distributing the software, include this License Header | ||
Notice in each file and include the License file at | ||
glassfish/bootstrap/legal/LICENSE.txt. Sun designates this | ||
particular file as subject to the "Classpath" exception as | ||
provided by Sun in the GPL Version 2 section of the License file | ||
that accompanied this code. If applicable, add the following | ||
below the License Header, with the fields enclosed by brackets [] | ||
replaced by your own identifying information: | ||
"Portions Copyrighted [year] [name of copyright owner]" | ||
|
||
Contributor(s): | ||
|
||
If you wish your version of this file to be governed by only the | ||
CDDL or only the GPL Version 2, indicate your decision by adding | ||
"[Contributor] elects to include this software in this | ||
distribution under the [CDDL or GPL Version 2] license." If you | ||
don't indicate a single choice of license, a recipient has the | ||
option to distribute your version of this file under either the | ||
CDDL, the GPL Version 2 or to extend the choice of license to its | ||
licensees as provided above. However, if you add GPL Version 2 | ||
code and therefore, elected the GPL Version 2 license, then the | ||
option applies only if the new code is made subject to such | ||
option by the copyright holder. | ||
|
||
</xsd:documentation> | ||
</xsd:annotation> | ||
|
||
<xsd:annotation> | ||
<xsd:documentation> | ||
<![CDATA[ | ||
This is the XML Schema for the application client 5 | ||
deployment descriptor. The deployment descriptor must | ||
be named "META-INF/application-client.xml" in the | ||
application client's jar file. All application client | ||
deployment descriptors must indicate the application | ||
client schema by using the Java EE namespace: | ||
http://java.sun.com/xml/ns/javaee | ||
and indicate the version of the schema by | ||
using the version element as shown below: | ||
<application-client xmlns="http://java.sun.com/xml/ns/javaee" | ||
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | ||
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee | ||
http://java.sun.com/xml/ns/javaee/application-client_5.xsd" | ||
version="5"> | ||
... | ||
</application-client> | ||
The instance documents may indicate the published version of | ||
the schema using the xsi:schemaLocation attribute for Java EE | ||
namespace with the following location: | ||
http://java.sun.com/xml/ns/javaee/application-client_5.xsd | ||
]]> | ||
</xsd:documentation> | ||
</xsd:annotation> | ||
|
||
<xsd:annotation> | ||
<xsd:documentation> | ||
|
||
The following conventions apply to all Java EE | ||
deployment descriptor elements unless indicated otherwise. | ||
|
||
- In elements that specify a pathname to a file within the | ||
same JAR file, relative filenames (i.e., those not | ||
starting with "/") are considered relative to the root of | ||
the JAR file's namespace. Absolute filenames (i.e., those | ||
starting with "/") also specify names in the root of the | ||
JAR file's namespace. In general, relative names are | ||
preferred. The exception is .war files where absolute | ||
names are preferred for consistency with the Servlet API. | ||
|
||
</xsd:documentation> | ||
</xsd:annotation> | ||
|
||
<xsd:include schemaLocation="javaee_5.xsd"/> | ||
|
||
|
||
<!-- **************************************************** --> | ||
|
||
<xsd:element name="application-client" type="javaee: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="javaee:env-entry"/> | ||
<xsd:field xpath="javaee: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="javaee:ejb-ref"/> | ||
<xsd:field xpath="javaee: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="javaee:resource-ref"/> | ||
<xsd:field xpath="javaee: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="javaee:resource-env-ref"/> | ||
<xsd:field xpath="javaee: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="javaee:message-destination-ref"/> | ||
<xsd:field xpath="javaee:message-destination-ref-name"/> | ||
</xsd:unique> | ||
</xsd:element> | ||
|
||
<!-- **************************************************** --> | ||
|
||
<xsd:complexType name="application-clientType"> | ||
<xsd:sequence> | ||
<xsd:group ref="javaee:descriptionGroup"/> | ||
<xsd:element name="env-entry" | ||
type="javaee:env-entryType" | ||
minOccurs="0" maxOccurs="unbounded"/> | ||
<xsd:element name="ejb-ref" | ||
type="javaee:ejb-refType" | ||
minOccurs="0" maxOccurs="unbounded"/> | ||
<xsd:group ref="javaee:service-refGroup"/> | ||
<xsd:element name="resource-ref" | ||
type="javaee:resource-refType" | ||
minOccurs="0" maxOccurs="unbounded"/> | ||
<xsd:element name="resource-env-ref" | ||
type="javaee:resource-env-refType" | ||
minOccurs="0" maxOccurs="unbounded"/> | ||
<xsd:element name="message-destination-ref" | ||
type="javaee:message-destination-refType" | ||
minOccurs="0" maxOccurs="unbounded"/> | ||
<xsd:element name="persistence-unit-ref" | ||
type="javaee:persistence-unit-refType" | ||
minOccurs="0" maxOccurs="unbounded"/> | ||
<xsd:element name="post-construct" | ||
type="javaee:lifecycle-callbackType" | ||
minOccurs="0" maxOccurs="unbounded"/> | ||
<xsd:element name="pre-destroy" | ||
type="javaee:lifecycle-callbackType" | ||
minOccurs="0" maxOccurs="unbounded"/> | ||
<xsd:element name="callback-handler" | ||
type="javaee: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="javaee:message-destinationType" | ||
minOccurs="0" | ||
maxOccurs="unbounded"/> | ||
</xsd:sequence> | ||
|
||
<xsd:attribute name="version" | ||
type="javaee:dewey-versionType" | ||
fixed="5" | ||
use="required"> | ||
<xsd:annotation> | ||
<xsd:documentation> | ||
|
||
The required value for the version is 5. | ||
|
||
</xsd:documentation> | ||
</xsd:annotation> | ||
|
||
</xsd:attribute> | ||
|
||
<xsd:attribute name="metadata-complete" type="xsd:boolean"> | ||
<xsd:annotation> | ||
<xsd:documentation> | ||
|
||
The metadata-complete attribute defines whether this | ||
deployment descriptor and other related deployment | ||
descriptors for this module (e.g., web service | ||
descriptors) are complete, or whether the class | ||
files available to this module and packaged with | ||
this application should be examined for annotations | ||
that specify deployment information. | ||
|
||
If metadata-complete is set to "true", the deployment | ||
tool must ignore any annotations that specify deployment | ||
information, which might be present in the class files | ||
of the application. | ||
|
||
If metadata-complete is not specified or is set to | ||
"false", the deployment tool must examine the class | ||
files of the application for annotations, as | ||
specified by the specifications. | ||
|
||
</xsd:documentation> | ||
</xsd:annotation> | ||
|
||
</xsd:attribute> | ||
|
||
<xsd:attribute name="id" type="xsd:ID"/> | ||
</xsd:complexType> | ||
|
||
</xsd:schema> | ||
|
Oops, something went wrong.