schemas.application-client_7.xsd Maven / Gradle / Ivy
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
Copyright (c) 2009-2013 Oracle and/or its affiliates. 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_1_1.html
or packager/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 packager/legal/LICENSE.txt.
GPL Classpath Exception:
Oracle designates this particular file as subject to the "Classpath"
exception as provided by Oracle in the GPL Version 2 section of the License
file that accompanied this code.
Modifications:
If applicable, add the following below the License Header, with the fields
enclosed by brackets [] replaced by your own identifying information:
"Portions Copyright [year] [name of copyright owner]"
Contributor(s):
If you wish your version of this file to be governed by only the CDDL or
only the GPL Version 2, indicate your decision by adding "[Contributor]
elects to include this software in this distribution under the [CDDL or GPL
Version 2] license." If you don't indicate a single choice of license, a
recipient has the option to distribute your version of this file under
either the CDDL, the GPL Version 2 or to extend the choice of license to
its licensees as provided above. However, if you add GPL Version 2 code
and therefore, elected the GPL Version 2 license, then the option applies
only if the new code is made subject to such option by the copyright
holder.
...
The instance documents may indicate the published version of
the schema using the xsi:schemaLocation attribute for Java EE
namespace with the following location:
http://xmlns.jcp.org/xml/ns/javaee/application-client_7.xsd
]]>
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.
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.
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.
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/".
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.
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.
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.
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.
The required value for the version is 7.
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.
© 2015 - 2025 Weber Informatics LLC | Privacy Policy