add base image

Dockerfile

@@ -1,25 +1,7 @@
-#FROM jboss/base-jdk:7
-FROM airdock/oracle-jdk:1.7
+FROM code.senomas.com:5000/jboss-as-base:7.2.0.Final
+MAINTAINER agus@senomas.com
 
-RUN apt-get update && apt-get install -y telnet vim
-RUN groupadd -r jboss -g 1001 && useradd -u 1001 -r -g jboss -m -d /opt/jboss -s /sbin/nologin -c "JBoss user" jboss && \
-    chmod 755 /opt/jboss
-
-# Set the working directory to jboss' user home directory
-WORKDIR /opt/jboss
-
-# Specify the user which should be used to execute all commands below
-USER jboss
-
-USER root
-ADD jboss-as-7.2.0.Final /opt/jboss/jboss-as-7.2.0.Final
-RUN chown -R jboss:jboss /opt/jboss/jboss-as-7.2.0.Final
 USER jboss
 
 ADD gotmpl /usr/bin/gotmpl
-
-ENV JBOSS_HOME=/opt/jboss/jboss-as-7.2.0.Final
-
-EXPOSE 8080 9997
-
-CMD ["/opt/jboss/jboss-as-7.2.0.Final/bin/standalone.sh", "-b", "0.0.0.0", "-bmanagement", "0.0.0.0"]
+ADD standalone.sh /opt/jboss/jboss-as-7.2.0.Final/bin/standalone.sh

jboss-as-7.2.0.Final/LICENSE.txt

@@ -1,502 +0,0 @@
-                  GNU LESSER GENERAL PUBLIC LICENSE
-                       Version 2.1, February 1999
-
- Copyright (C) 1991, 1999 Free Software Foundation, Inc.
- 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-[This is the first released version of the Lesser GPL.  It also counts
- as the successor of the GNU Library Public License, version 2, hence
- the version number 2.1.]
-
-                            Preamble
-
-  The licenses for most software are designed to take away your
-freedom to share and change it.  By contrast, the GNU General Public
-Licenses are intended to guarantee your freedom to share and change
-free software--to make sure the software is free for all its users.
-
-  This license, the Lesser General Public License, applies to some
-specially designated software packages--typically libraries--of the
-Free Software Foundation and other authors who decide to use it.  You
-can use it too, but we suggest you first think carefully about whether
-this license or the ordinary General Public License is the better
-strategy to use in any particular case, based on the explanations below.
-
-  When we speak of free software, we are referring to freedom of use,
-not price.  Our General Public Licenses are designed to make sure that
-you have the freedom to distribute copies of free software (and charge
-for this service if you wish); that you receive source code or can get
-it if you want it; that you can change the software and use pieces of
-it in new free programs; and that you are informed that you can do
-these things.
-
-  To protect your rights, we need to make restrictions that forbid
-distributors to deny you these rights or to ask you to surrender these
-rights.  These restrictions translate to certain responsibilities for
-you if you distribute copies of the library or if you modify it.
-
-  For example, if you distribute copies of the library, whether gratis
-or for a fee, you must give the recipients all the rights that we gave
-you.  You must make sure that they, too, receive or can get the source
-code.  If you link other code with the library, you must provide
-complete object files to the recipients, so that they can relink them
-with the library after making changes to the library and recompiling
-it.  And you must show them these terms so they know their rights.
-
-  We protect your rights with a two-step method: (1) we copyright the
-library, and (2) we offer you this license, which gives you legal
-permission to copy, distribute and/or modify the library.
-
-  To protect each distributor, we want to make it very clear that
-there is no warranty for the free library.  Also, if the library is
-modified by someone else and passed on, the recipients should know
-that what they have is not the original version, so that the original
-author's reputation will not be affected by problems that might be
-introduced by others.
-
-  Finally, software patents pose a constant threat to the existence of
-any free program.  We wish to make sure that a company cannot
-effectively restrict the users of a free program by obtaining a
-restrictive license from a patent holder.  Therefore, we insist that
-any patent license obtained for a version of the library must be
-consistent with the full freedom of use specified in this license.
-
-  Most GNU software, including some libraries, is covered by the
-ordinary GNU General Public License.  This license, the GNU Lesser
-General Public License, applies to certain designated libraries, and
-is quite different from the ordinary General Public License.  We use
-this license for certain libraries in order to permit linking those
-libraries into non-free programs.
-
-  When a program is linked with a library, whether statically or using
-a shared library, the combination of the two is legally speaking a
-combined work, a derivative of the original library.  The ordinary
-General Public License therefore permits such linking only if the
-entire combination fits its criteria of freedom.  The Lesser General
-Public License permits more lax criteria for linking other code with
-the library.
-
-  We call this license the "Lesser" General Public License because it
-does Less to protect the user's freedom than the ordinary General
-Public License.  It also provides other free software developers Less
-of an advantage over competing non-free programs.  These disadvantages
-are the reason we use the ordinary General Public License for many
-libraries.  However, the Lesser license provides advantages in certain
-special circumstances.
-
-  For example, on rare occasions, there may be a special need to
-encourage the widest possible use of a certain library, so that it becomes
-a de-facto standard.  To achieve this, non-free programs must be
-allowed to use the library.  A more frequent case is that a free
-library does the same job as widely used non-free libraries.  In this
-case, there is little to gain by limiting the free library to free
-software only, so we use the Lesser General Public License.
-
-  In other cases, permission to use a particular library in non-free
-programs enables a greater number of people to use a large body of
-free software.  For example, permission to use the GNU C Library in
-non-free programs enables many more people to use the whole GNU
-operating system, as well as its variant, the GNU/Linux operating
-system.
-
-  Although the Lesser General Public License is Less protective of the
-users' freedom, it does ensure that the user of a program that is
-linked with the Library has the freedom and the wherewithal to run
-that program using a modified version of the Library.
-
-  The precise terms and conditions for copying, distribution and
-modification follow.  Pay close attention to the difference between a
-"work based on the library" and a "work that uses the library".  The
-former contains code derived from the library, whereas the latter must
-be combined with the library in order to run.
-
-                  GNU LESSER GENERAL PUBLIC LICENSE
-   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
-  0. This License Agreement applies to any software library or other
-program which contains a notice placed by the copyright holder or
-other authorized party saying it may be distributed under the terms of
-this Lesser General Public License (also called "this License").
-Each licensee is addressed as "you".
-
-  A "library" means a collection of software functions and/or data
-prepared so as to be conveniently linked with application programs
-(which use some of those functions and data) to form executables.
-
-  The "Library", below, refers to any such software library or work
-which has been distributed under these terms.  A "work based on the
-Library" means either the Library or any derivative work under
-copyright law: that is to say, a work containing the Library or a
-portion of it, either verbatim or with modifications and/or translated
-straightforwardly into another language.  (Hereinafter, translation is
-included without limitation in the term "modification".)
-
-  "Source code" for a work means the preferred form of the work for
-making modifications to it.  For a library, complete source code means
-all the source code for all modules it contains, plus any associated
-interface definition files, plus the scripts used to control compilation
-and installation of the library.
-
-  Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope.  The act of
-running a program using the Library is not restricted, and output from
-such a program is covered only if its contents constitute a work based
-on the Library (independent of the use of the Library in a tool for
-writing it).  Whether that is true depends on what the Library does
-and what the program that uses the Library does.
-
-  1. You may copy and distribute verbatim copies of the Library's
-complete source code as you receive it, in any medium, provided that
-you conspicuously and appropriately publish on each copy an
-appropriate copyright notice and disclaimer of warranty; keep intact
-all the notices that refer to this License and to the absence of any
-warranty; and distribute a copy of this License along with the
-Library.
-
-  You may charge a fee for the physical act of transferring a copy,
-and you may at your option offer warranty protection in exchange for a
-fee.
-
-  2. You may modify your copy or copies of the Library or any portion
-of it, thus forming a work based on the Library, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
-    a) The modified work must itself be a software library.
-
-    b) You must cause the files modified to carry prominent notices
-    stating that you changed the files and the date of any change.
-
-    c) You must cause the whole of the work to be licensed at no
-    charge to all third parties under the terms of this License.
-
-    d) If a facility in the modified Library refers to a function or a
-    table of data to be supplied by an application program that uses
-    the facility, other than as an argument passed when the facility
-    is invoked, then you must make a good faith effort to ensure that,
-    in the event an application does not supply such function or
-    table, the facility still operates, and performs whatever part of
-    its purpose remains meaningful.
-
-    (For example, a function in a library to compute square roots has
-    a purpose that is entirely well-defined independent of the
-    application.  Therefore, Subsection 2d requires that any
-    application-supplied function or table used by this function must
-    be optional: if the application does not supply it, the square
-    root function must still compute square roots.)
-
-These requirements apply to the modified work as a whole.  If
-identifiable sections of that work are not derived from the Library,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works.  But when you
-distribute the same sections as part of a whole which is a work based
-on the Library, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote
-it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Library.
-
-In addition, mere aggregation of another work not based on the Library
-with the Library (or with a work based on the Library) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
-  3. You may opt to apply the terms of the ordinary GNU General Public
-License instead of this License to a given copy of the Library.  To do
-this, you must alter all the notices that refer to this License, so
-that they refer to the ordinary GNU General Public License, version 2,
-instead of to this License.  (If a newer version than version 2 of the
-ordinary GNU General Public License has appeared, then you can specify
-that version instead if you wish.)  Do not make any other change in
-these notices.
-
-  Once this change is made in a given copy, it is irreversible for
-that copy, so the ordinary GNU General Public License applies to all
-subsequent copies and derivative works made from that copy.
-
-  This option is useful when you wish to copy part of the code of
-the Library into a program that is not a library.
-
-  4. You may copy and distribute the Library (or a portion or
-derivative of it, under Section 2) in object code or executable form
-under the terms of Sections 1 and 2 above provided that you accompany
-it with the complete corresponding machine-readable source code, which
-must be distributed under the terms of Sections 1 and 2 above on a
-medium customarily used for software interchange.
-
-  If distribution of object code is made by offering access to copy
-from a designated place, then offering equivalent access to copy the
-source code from the same place satisfies the requirement to
-distribute the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
-  5. A program that contains no derivative of any portion of the
-Library, but is designed to work with the Library by being compiled or
-linked with it, is called a "work that uses the Library".  Such a
-work, in isolation, is not a derivative work of the Library, and
-therefore falls outside the scope of this License.
-
-  However, linking a "work that uses the Library" with the Library
-creates an executable that is a derivative of the Library (because it
-contains portions of the Library), rather than a "work that uses the
-library".  The executable is therefore covered by this License.
-Section 6 states terms for distribution of such executables.
-
-  When a "work that uses the Library" uses material from a header file
-that is part of the Library, the object code for the work may be a
-derivative work of the Library even though the source code is not.
-Whether this is true is especially significant if the work can be
-linked without the Library, or if the work is itself a library.  The
-threshold for this to be true is not precisely defined by law.
-
-  If such an object file uses only numerical parameters, data
-structure layouts and accessors, and small macros and small inline
-functions (ten lines or less in length), then the use of the object
-file is unrestricted, regardless of whether it is legally a derivative
-work.  (Executables containing this object code plus portions of the
-Library will still fall under Section 6.)
-
-  Otherwise, if the work is a derivative of the Library, you may
-distribute the object code for the work under the terms of Section 6.
-Any executables containing that work also fall under Section 6,
-whether or not they are linked directly with the Library itself.
-
-  6. As an exception to the Sections above, you may also combine or
-link a "work that uses the Library" with the Library to produce a
-work containing portions of the Library, and distribute that work
-under terms of your choice, provided that the terms permit
-modification of the work for the customer's own use and reverse
-engineering for debugging such modifications.
-
-  You must give prominent notice with each copy of the work that the
-Library is used in it and that the Library and its use are covered by
-this License.  You must supply a copy of this License.  If the work
-during execution displays copyright notices, you must include the
-copyright notice for the Library among them, as well as a reference
-directing the user to the copy of this License.  Also, you must do one
-of these things:
-
-    a) Accompany the work with the complete corresponding
-    machine-readable source code for the Library including whatever
-    changes were used in the work (which must be distributed under
-    Sections 1 and 2 above); and, if the work is an executable linked
-    with the Library, with the complete machine-readable "work that
-    uses the Library", as object code and/or source code, so that the
-    user can modify the Library and then relink to produce a modified
-    executable containing the modified Library.  (It is understood
-    that the user who changes the contents of definitions files in the
-    Library will not necessarily be able to recompile the application
-    to use the modified definitions.)
-
-    b) Use a suitable shared library mechanism for linking with the
-    Library.  A suitable mechanism is one that (1) uses at run time a
-    copy of the library already present on the user's computer system,
-    rather than copying library functions into the executable, and (2)
-    will operate properly with a modified version of the library, if
-    the user installs one, as long as the modified version is
-    interface-compatible with the version that the work was made with.
-
-    c) Accompany the work with a written offer, valid for at
-    least three years, to give the same user the materials
-    specified in Subsection 6a, above, for a charge no more
-    than the cost of performing this distribution.
-
-    d) If distribution of the work is made by offering access to copy
-    from a designated place, offer equivalent access to copy the above
-    specified materials from the same place.
-
-    e) Verify that the user has already received a copy of these
-    materials or that you have already sent this user a copy.
-
-  For an executable, the required form of the "work that uses the
-Library" must include any data and utility programs needed for
-reproducing the executable from it.  However, as a special exception,
-the materials to be distributed need not include anything that is
-normally distributed (in either source or binary form) with the major
-components (compiler, kernel, and so on) of the operating system on
-which the executable runs, unless that component itself accompanies
-the executable.
-
-  It may happen that this requirement contradicts the license
-restrictions of other proprietary libraries that do not normally
-accompany the operating system.  Such a contradiction means you cannot
-use both them and the Library together in an executable that you
-distribute.
-
-  7. You may place library facilities that are a work based on the
-Library side-by-side in a single library together with other library
-facilities not covered by this License, and distribute such a combined
-library, provided that the separate distribution of the work based on
-the Library and of the other library facilities is otherwise
-permitted, and provided that you do these two things:
-
-    a) Accompany the combined library with a copy of the same work
-    based on the Library, uncombined with any other library
-    facilities.  This must be distributed under the terms of the
-    Sections above.
-
-    b) Give prominent notice with the combined library of the fact
-    that part of it is a work based on the Library, and explaining
-    where to find the accompanying uncombined form of the same work.
-
-  8. You may not copy, modify, sublicense, link with, or distribute
-the Library except as expressly provided under this License.  Any
-attempt otherwise to copy, modify, sublicense, link with, or
-distribute the Library is void, and will automatically terminate your
-rights under this License.  However, parties who have received copies,
-or rights, from you under this License will not have their licenses
-terminated so long as such parties remain in full compliance.
-
-  9. You are not required to accept this License, since you have not
-signed it.  However, nothing else grants you permission to modify or
-distribute the Library or its derivative works.  These actions are
-prohibited by law if you do not accept this License.  Therefore, by
-modifying or distributing the Library (or any work based on the
-Library), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Library or works based on it.
-
-  10. Each time you redistribute the Library (or any work based on the
-Library), the recipient automatically receives a license from the
-original licensor to copy, distribute, link with or modify the Library
-subject to these terms and conditions.  You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties with
-this License.
-
-  11. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License.  If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Library at all.  For example, if a patent
-license would not permit royalty-free redistribution of the Library by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Library.
-
-If any portion of this section is held invalid or unenforceable under any
-particular circumstance, the balance of the section is intended to apply,
-and the section as a whole is intended to apply in other circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system which is
-implemented by public license practices.  Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
-  12. If the distribution and/or use of the Library is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Library under this License may add
-an explicit geographical distribution limitation excluding those countries,
-so that distribution is permitted only in or among countries not thus
-excluded.  In such case, this License incorporates the limitation as if
-written in the body of this License.
-
-  13. The Free Software Foundation may publish revised and/or new
-versions of the Lesser General Public License from time to time.
-Such new versions will be similar in spirit to the present version,
-but may differ in detail to address new problems or concerns.
-
-Each version is given a distinguishing version number.  If the Library
-specifies a version number of this License which applies to it and
-"any later version", you have the option of following the terms and
-conditions either of that version or of any later version published by
-the Free Software Foundation.  If the Library does not specify a
-license version number, you may choose any version ever published by
-the Free Software Foundation.
-
-  14. If you wish to incorporate parts of the Library into other free
-programs whose distribution conditions are incompatible with these,
-write to the author to ask for permission.  For software which is
-copyrighted by the Free Software Foundation, write to the Free
-Software Foundation; we sometimes make exceptions for this.  Our
-decision will be guided by the two goals of preserving the free status
-of all derivatives of our free software and of promoting the sharing
-and reuse of software generally.
-
-                            NO WARRANTY
-
-  15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
-WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
-EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
-OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
-KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
-LIBRARY IS WITH YOU.  SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
-THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
-  16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
-WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
-AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
-FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
-CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
-LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
-RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
-FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
-SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
-DAMAGES.
-
-                     END OF TERMS AND CONDITIONS
-
-           How to Apply These Terms to Your New Libraries
-
-  If you develop a new library, and you want it to be of the greatest
-possible use to the public, we recommend making it free software that
-everyone can redistribute and change.  You can do so by permitting
-redistribution under these terms (or, alternatively, under the terms of the
-ordinary General Public License).
-
-  To apply these terms, attach the following notices to the library.  It is
-safest to attach them to the start of each source file to most effectively
-convey the exclusion of warranty; and each file should have at least the
-"copyright" line and a pointer to where the full notice is found.
-
-    <one line to give the library's name and a brief idea of what it does.>
-    Copyright (C) <year>  <name of author>
-
-    This library is free software; you can redistribute it and/or
-    modify it under the terms of the GNU Lesser General Public
-    License as published by the Free Software Foundation; either
-    version 2.1 of the License, or (at your option) any later version.
-
-    This library is distributed in the hope that it will be useful,
-    but WITHOUT ANY WARRANTY; without even the implied warranty of
-    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
-    Lesser General Public License for more details.
-
-    You should have received a copy of the GNU Lesser General Public
-    License along with this library; if not, write to the Free Software
-    Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
-
-Also add information on how to contact you by electronic and paper mail.
-
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a "copyright disclaimer" for the library, if
-necessary.  Here is a sample; alter the names:
-
-  Yoyodyne, Inc., hereby disclaims all copyright interest in the
-  library `Frob' (a library for tweaking knobs) written by James Random Hacker.
-
-  <signature of Ty Coon>, 1 April 1990
-  Ty Coon, President of Vice
-
-That's all there is to it!

jboss-as-7.2.0.Final/README.txt

@@ -1,81 +0,0 @@
-       ______                     ___   _____    _____
-      / / __ )____  __________   /   | / ___/   /__  /
- __  / / __  / __ \/ ___/ ___/  / /| | \__ \      / / 
-/ /_/ / /_/ / /_/ (__  |__  )  / ___ |___/ /     / /  
-\____/_____/\____/____/____/  /_/  |_/____/     /_/   
-
-Welcome to JBoss Application Server 7.2.0
-http://www.jboss.org/jbossas/
-
-Go to the above link for documentation, and additional downloads.
-
-Also, once JBoss AS7 is started you can go to http://localhost:8080/
-for additional information.
-
-
-Key Features
---------------
-* Java EE 6
-* Fast Startup
-* Small Footprint
-* Modular Design
-* Unified Configuration and Management
-* Distributed Domain Management
-* OSGi
-
-Release Notes
--------------
-You can obtain the release notes here:
-https://community.jboss.org/wiki/AS711FinalReleaseNotes
-
-Getting Started
-----------------
-JBoss AS 7 requires JDK 1.6 or later.  For information regarding installation
-of the JDK, see http://www.oracle.com/technetwork/java/index.html
-
-JBoss AS 7 has two modes of operation: Standalone and Domain.  For more
-information regarding these modes, please refer to the documentation 
-available on the JBoss.org site:
-
-https://docs.jboss.org/author/display/AS71/Documentation
-
-
-Starting a Standalone Server
-----------------------------
-An AS7 standalone server runs a single instance of AS7.
-
-<JBOSS_HOME>/bin/standalone.sh      (Unix / Linux)
-
-<JBOSS_HOME>\bin\standalone.bat     (Windows)
-
-
-Starting a Managed Domain
---------------------------
-An AS7 managed domain allows you to control and configure multiple instances 
-of AS7, potentially across several physical (or virtual) machines.  The default 
-configuration includes a domain controller and a single server group with three 
-servers (two of which start automatically), all running on the localhost.
-
-<JBOSS_HOME>/bin/domain.sh      (Unix / Linux)
-
-<JBOSS_HOME>\bin\domain.bat     (Windows)
- 
-
-Accessing the Web Console
---------------------------
-Once the server has started you can access the landing page:
-
-http:/localhost:8080/
-
-This page includes links to online documentation, quick start guides, forums 
-and the administration console.
-
-
-Stopping the Server
--------------------
-The JBoss AS7 server can be stopped by pressing Ctrl-C on the command line.
-If the server is running in a background process, the server can be stopped
-using the JBoss CLI:
-
-<JBOSS_HOME>/bin/jboss-cli.sh --connect --command=:shutdown
-

jboss-as-7.2.0.Final/appclient/configuration/appclient.xml

@@ -1,174 +0,0 @@
-<!--
-  ~ JBoss, Home of Professional Open Source.
-  ~ Copyright 2011, Red Hat, Inc., and individual contributors
-  ~ as indicated by the @author tags. See the copyright.txt file in the
-  ~ distribution for a full listing of individual contributors.
-  ~
-  ~ This is free software; you can redistribute it and/or modify it
-  ~ under the terms of the GNU Lesser General Public License as
-  ~ published by the Free Software Foundation; either version 2.1 of
-  ~ the License, or (at your option) any later version.
-  ~
-  ~ This software is distributed in the hope that it will be useful,
-  ~ but WITHOUT ANY WARRANTY; without even the implied warranty of
-  ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-  ~ Lesser General Public License for more details.
-  ~
-  ~ You should have received a copy of the GNU Lesser General Public
-  ~ License along with this software; if not, write to the Free
-  ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
-  ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
-  -->
-
-<server xmlns="urn:jboss:domain:1.4">
-
-    <extensions>
-        <extension module="org.jboss.as.connector"/>
-        <extension module="org.jboss.as.ee"/>
-        <extension module="org.jboss.as.ejb3"/>
-        <extension module="org.jboss.as.jacorb"/>
-        <extension module="org.jboss.as.jaxr"/>
-        <extension module="org.jboss.as.jpa"/>
-        <extension module="org.jboss.as.logging"/>
-        <extension module="org.jboss.as.naming"/>
-        <extension module="org.jboss.as.security"/>
-        <extension module="org.jboss.as.transactions"/>
-        <extension module="org.jboss.as.webservices"/>
-    </extensions>
-
-    <profile>
-        <subsystem xmlns="urn:jboss:domain:logging:1.2">
-            <console-handler name="CONSOLE">
-                <level name="INFO"/>
-                <formatter>
-                    <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
-                </formatter>
-            </console-handler>
-
-            <periodic-rotating-file-handler name="FILE">
-                <level name="INFO"/>
-                <formatter>
-                    <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
-                </formatter>
-                <file relative-to="jboss.server.log.dir" path="appclient.log"/>
-                <suffix value=".yyyy-MM-dd"/>
-                <append value="true"/>
-            </periodic-rotating-file-handler>
-
-            <logger category="com.arjuna">
-                <level name="WARN"/>
-            </logger>
-            <logger category="sun.rmi">
-                <level name="WARN"/>
-            </logger>
-            <logger category="jacorb">
-                <level name="WARN"/>
-            </logger>
-            <!-- set jacorb.config to ERROR to avoid the "jacorb.properties not found" messages during startup -->
-            <logger category="jacorb.config">
-                <level name="ERROR"/>
-            </logger>
-
-            <root-logger>
-                <level name="INFO"/>
-                <handlers>
-                    <handler name="CONSOLE"/>
-                    <handler name="FILE"/>
-                </handlers>
-            </root-logger>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:datasources:1.1">
-            <datasources>
-                <datasource jndi-name="java:jboss/datasources/ExampleDS" enabled="false" use-java-context="true"
-                            pool-name="java:jboss/datasources/ExampleDS">
-                    <connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1</connection-url>
-                    <driver>h2</driver>
-                    <pool></pool>
-                    <security>
-                        <user-name>sa</user-name>
-                        <password>sa</password>
-                    </security>
-                </datasource>
-                <drivers>
-                    <driver name="h2" module="com.h2database.h2">
-                        <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
-                    </driver>
-                </drivers>
-            </datasources>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:ee:1.1">
-            <spec-descriptor-property-replacement>false</spec-descriptor-property-replacement>
-            <jboss-descriptor-property-replacement>false</jboss-descriptor-property-replacement>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:ejb3:1.2" />
-        <subsystem xmlns="urn:jboss:domain:jacorb:1.1"/>
-        <subsystem xmlns="urn:jboss:domain:jpa:1.0">
-            <jpa default-datasource=""/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:jca:1.1">
-            <archive-validation enabled="false" />
-            <bean-validation enabled="true" />
-            <default-workmanager>
-                <short-running-threads>
-                    <core-threads count="50"/>
-                    <queue-length count="50"/>
-                    <max-threads count="50"/>
-                    <keepalive-time time="10" unit="seconds"/>
-                </short-running-threads>
-                <long-running-threads>
-                    <core-threads count="50"/>
-                    <queue-length count="50"/>
-                    <max-threads count="50"/>
-                    <keepalive-time time="10" unit="seconds"/>
-                </long-running-threads>
-            </default-workmanager>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:naming:1.0"/>
-        <subsystem xmlns="urn:jboss:domain:security:1.0">
-            <security-domains>
-                <security-domain name="other" cache-type="default">
-                    <authentication>
-                        <login-module code="UsersRoles" flag="required"/>
-                    </authentication>
-                </security-domain>
-                <security-domain name="jboss-web-policy" cache-type="default">
-                    <authorization>
-                        <policy-module code="Delegating" flag="required"/>
-                    </authorization>
-                </security-domain>
-                <security-domain name="jboss-ejb-policy" cache-type="default">
-                    <authorization>
-                        <policy-module code="Delegating" flag="required"/>
-                    </authorization>
-                </security-domain>
-            </security-domains>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:jaxr:1.1">
-            <connection-factory jndi-name="java:jboss/jaxr/ConnectionFactory"/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:transactions:1.2">
-            <recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/>
-            <core-environment>
-                <process-id>
-                    <uuid/>
-                </process-id>
-            </core-environment>
-            <coordinator-environment default-timeout="300"/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:webservices:1.1"/>
-    </profile>
-
-    <interfaces>
-        <interface name="public">
-           <inet-address value="${jboss.bind.address:127.0.0.1}"/>
-        </interface>
-    </interfaces>
-
-    <socket-binding-group name="standard-sockets" default-interface="public">
-        <socket-binding name="jacorb" port="3628"/>
-        <socket-binding name="jacorb-ssl" port="3629"/>
-        <socket-binding name="txn-recovery-environment" port="4712"/>
-        <socket-binding name="txn-status-manager" port="4713"/>
-    </socket-binding-group>
-
-</server>

jboss-as-7.2.0.Final/appclient/configuration/logging.properties

@@ -1,65 +0,0 @@
-#
-# JBoss, Home of Professional Open Source.
-# Copyright 2010, Red Hat, Inc., and individual contributors
-# as indicated by the @author tags. See the copyright.txt file in the
-# distribution for a full listing of individual contributors.
-#
-# This is free software; you can redistribute it and/or modify it
-# under the terms of the GNU Lesser General Public License as
-# published by the Free Software Foundation; either version 2.1 of
-# the License, or (at your option) any later version.
-#
-# This software is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-# Lesser General Public License for more details.
-#
-# You should have received a copy of the GNU Lesser General Public
-# License along with this software; if not, write to the Free
-# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
-# 02110-1301 USA, or see the FSF site: http://www.fsf.org.
-#
-
-# Additional loggers to configure (the root logger is always configured)
-loggers=jacorb,com.arjuna,jacorb.config,sun.rmi
-
-logger.level=INFO
-logger.handlers=CONSOLE,FILE
-
-logger.jacorb.level=WARN
-logger.jacorb.useParentHandlers=true
-
-logger.com.arjuna.level=WARN
-logger.com.arjuna.useParentHandlers=true
-
-logger.jacorb.config.level=ERROR
-logger.jacorb.config.useParentHandlers=true
-
-logger.sun.rmi.level=WARN
-logger.sun.rmi.useParentHandlers=true
-
-handler.CONSOLE=org.jboss.logmanager.handlers.ConsoleHandler
-handler.CONSOLE.level=INFO
-handler.CONSOLE.formatter=CONSOLE
-handler.CONSOLE.properties=autoFlush,target
-handler.CONSOLE.autoFlush=true
-handler.CONSOLE.target=SYSTEM_OUT
-
-handler.FILE=org.jboss.logmanager.handlers.PeriodicRotatingFileHandler
-handler.FILE.level=INFO
-handler.FILE.formatter=FILE
-handler.FILE.properties=autoFlush,append,fileName,suffix
-handler.FILE.constructorProperties=fileName,append
-handler.FILE.autoFlush=true
-handler.FILE.append=true
-handler.FILE.fileName=${org.jboss.boot.log.file:boot.log}
-handler.FILE.suffix=.yyyy-MM-dd
-
-formatter.CONSOLE=org.jboss.logmanager.formatters.PatternFormatter
-formatter.CONSOLE.properties=pattern
-formatter.CONSOLE.pattern=%K{level}%d{HH\:mm\:ss,SSS} %-5p [%c] (%t) %s%E%n
-
-formatter.FILE=org.jboss.logmanager.formatters.PatternFormatter
-formatter.FILE.properties=pattern
-formatter.FILE.constructorProperties=pattern
-formatter.FILE.pattern=%d{HH\:mm\:ss,SSS} %-5p [%c] (%t) %s%E%n

jboss-as-7.2.0.Final/bin/add-user.bat

@@ -1,82 +0,0 @@
-@echo off
-rem -------------------------------------------------------------------------
-rem Add User script for Windows
-rem -------------------------------------------------------------------------
-rem
-rem A simple utility for adding new users to the properties file used 
-rem for domain management authentication out of the box.
-
-rem $Id$
-
-@if not "%ECHO%" == ""  echo %ECHO%
-@if "%OS%" == "Windows_NT" setlocal
-
-if "%OS%" == "Windows_NT" (
-  set "DIRNAME=%~dp0%"
-) else (
-  set DIRNAME=.\
-)
-
-pushd %DIRNAME%..
-set "RESOLVED_JBOSS_HOME=%CD%"
-popd
-
-if "x%JBOSS_HOME%" == "x" (
-  set "JBOSS_HOME=%RESOLVED_JBOSS_HOME%" 
-)
-
-pushd "%JBOSS_HOME%"
-set "SANITIZED_JBOSS_HOME=%CD%"
-popd
-
-if "%RESOLVED_JBOSS_HOME%" NEQ "%SANITIZED_JBOSS_HOME%" (
-    echo WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur.
-)
-
-set DIRNAME=
-
-if "%OS%" == "Windows_NT" (
-  set "PROGNAME=%~nx0%"
-) else (
-  set "PROGNAME=jdr.bat"
-)
-
-rem Setup JBoss specific properties
-if "x%JAVA_HOME%" == "x" (
-  set  JAVA=java
-  echo JAVA_HOME is not set. Unexpected results may occur.
-  echo Set JAVA_HOME to the directory of your local JDK to avoid this message.
-) else (
-  set "JAVA=%JAVA_HOME%\bin\java"
-)
-
-rem Find jboss-modules.jar, or we can't continue
-if exist "%JBOSS_HOME%\jboss-modules.jar" (
-    set "RUNJAR=%JBOSS_HOME%\jboss-modules.jar"
-) else (
-  echo Could not locate "%JBOSS_HOME%\jboss-modules.jar".
-  echo Please check that you are in the bin directory when running this script.
-  goto END
-)
-
-rem Setup JBoss specific properties
-
-rem Setup the java endorsed dirs
-set JBOSS_ENDORSED_DIRS=%JBOSS_HOME%\lib\endorsed
-
-rem Set default module root paths
-if "x%JBOSS_MODULEPATH%" == "x" (
-  set  "JBOSS_MODULEPATH=%JBOSS_HOME%\modules"
-)
-
-rem Uncomment to override standalone and domain user location  
-rem set "JAVA_OPTS=%JAVA_OPTS% -Djboss.server.config.user.dir=..\standalone\configuration -Djboss.domain.config.user.dir=..\domain\configuration"
-
-"%JAVA%" %JAVA_OPTS% ^
-    -jar "%JBOSS_HOME%\jboss-modules.jar" ^
-    -mp "%JBOSS_MODULEPATH%" ^
-     org.jboss.as.domain-add-user ^
-     %*
-
-:END
-if "x%NOPAUSE%" == "x" pause

jboss-as-7.2.0.Final/bin/add-user.sh

@@ -1,72 +0,0 @@
-#!/bin/sh
-
-# Add User Utility
-#
-# A simple utility for adding new users to the properties file used
-# for domain management authentication out of the box.
-#
-
-DIRNAME=`dirname "$0"`
-
-# OS specific support (must be 'true' or 'false').
-cygwin=false;
-if  [ `uname|grep -i CYGWIN` ]; then
-    cygwin = true;
-fi
-
-# For Cygwin, ensure paths are in UNIX format before anything is touched
-if $cygwin ; then
-    [ -n "$JBOSS_HOME" ] &&
-        JBOSS_HOME=`cygpath --unix "$JBOSS_HOME"`
-    [ -n "$JAVA_HOME" ] &&
-        JAVA_HOME=`cygpath --unix "$JAVA_HOME"`
-    [ -n "$JAVAC_JAR" ] &&
-        JAVAC_JAR=`cygpath --unix "$JAVAC_JAR"`
-fi
-
-# Setup JBOSS_HOME
-RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
-if [ "x$JBOSS_HOME" = "x" ]; then
-    # get the full path (without any relative bits)
-    JBOSS_HOME=$RESOLVED_JBOSS_HOME
-else
- SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME"; pwd`
- if [ "$RESOLVED_JBOSS_HOME" != "$SANITIZED_JBOSS_HOME" ]; then
-   echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
-   echo ""
- fi
-fi
-export JBOSS_HOME
-
-# Setup the JVM
-if [ "x$JAVA" = "x" ]; then
-    if [ "x$JAVA_HOME" != "x" ]; then
-        JAVA="$JAVA_HOME/bin/java"
-    else
-        JAVA="java"
-    fi
-fi
-
-if [ "x$JBOSS_MODULEPATH" = "x" ]; then
-    JBOSS_MODULEPATH="$JBOSS_HOME/modules"
-fi
-
-# For Cygwin, switch paths to Windows format before running java
-if $cygwin; then
-    JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
-    JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
-    JBOSS_CLASSPATH=`cygpath --path --windows "$JBOSS_CLASSPATH"`
-    JBOSS_ENDORSED_DIRS=`cygpath --path --windows "$JBOSS_ENDORSED_DIRS"`
-    JBOSS_MODULEPATH=`cygpath --path --windows "$JBOSS_MODULEPATH"`
-fi
-
-# Sample JPDA settings for remote socket debugging
-#JAVA_OPTS="$JAVA_OPTS -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=y"
-# Uncomment to override standalone and domain user location  
-#JAVA_OPTS="$JAVA_OPTS -Djboss.server.config.user.dir=../standalone/configuration -Djboss.domain.config.user.dir=../domain/configuration"
-
-eval \"$JAVA\" $JAVA_OPTS \
-         -jar \"$JBOSS_HOME/jboss-modules.jar\" \
-         -mp \"${JBOSS_MODULEPATH}\" \
-         org.jboss.as.domain-add-user \
-         '"$@"'

jboss-as-7.2.0.Final/bin/appclient.bat

@@ -1,98 +0,0 @@
-@echo off
-rem -------------------------------------------------------------------------
-rem JBoss Application Client Bootstrap Script for Windows
-rem -------------------------------------------------------------------------
-
-rem $Id$
-
-@if not "%ECHO%" == ""  echo %ECHO%
-@if "%OS%" == "Windows_NT" setlocal
-
-if "%OS%" == "Windows_NT" (
-  set "DIRNAME=%~dp0%"
-) else (
-  set DIRNAME=.\
-)
-
-rem Read an optional configuration file.
-if "x%APPCLIENT_CONF%" == "x" (
-   set "APPCLIENT_CONF=%DIRNAME%appclient.conf.bat"
-)
-if exist "%APPCLIENT_CONF%" (
-   echo Calling %APPCLIENT_CONF%
-   call "%APPCLIENT_CONF%" %*
-) else (
-   echo Config file not found %APPCLIENT_CONF%
-)
-
-pushd %DIRNAME%..
-set "RESOLVED_JBOSS_HOME=%CD%"
-popd
-
-if "x%JBOSS_HOME%" == "x" (
-  set "JBOSS_HOME=%RESOLVED_JBOSS_HOME%"
-)
-
-pushd "%JBOSS_HOME%"
-set "SANITIZED_JBOSS_HOME=%CD%"
-popd
-
-if "%RESOLVED_JBOSS_HOME%" NEQ "%SANITIZED_JBOSS_HOME%" (
-    echo WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur.
-)
-
-set DIRNAME=
-
-if "%OS%" == "Windows_NT" (
-  set "PROGNAME=%~nx0%"
-) else (
-  set "PROGNAME=appclient.bat"
-)
-
-rem Setup JBoss specific properties
-set JAVA_OPTS=-Dprogram.name=%PROGNAME% %JAVA_OPTS%
-
-if "x%JAVA_HOME%" == "x" (
-  set  JAVA=java
-  echo JAVA_HOME is not set. Unexpected results may occur.
-  echo Set JAVA_HOME to the directory of your local JDK to avoid this message.
-) else (
-  set "JAVA=%JAVA_HOME%\bin\java"
-)
-
-rem Add -server to the JVM options, if supported
-"%JAVA%" -server -version 2>&1 | findstr /I hotspot > nul
-if not errorlevel == 1 (
-  set "JAVA_OPTS=%JAVA_OPTS% -server"
-)
-
-rem Find run.jar, or we can't continue
-if exist "%JBOSS_HOME%\jboss-modules.jar" (
-    set "RUNJAR=%JBOSS_HOME%\jboss-modules.jar"
-) else (
-  echo Could not locate "%JBOSS_HOME%\jboss-modules.jar".
-  echo Please check that you are in the bin directory when running this script.
-  goto END
-)
-
-rem Setup JBoss specific properties
-
-rem Setup the java endorsed dirs
-set JBOSS_ENDORSED_DIRS=%JBOSS_HOME%\lib\endorsed
-
-rem Set default module root paths
-if "x%JBOSS_MODULEPATH%" == "x" (
-  set  "JBOSS_MODULEPATH=%JBOSS_HOME%\modules"
-)
-
-
-"%JAVA%" %JAVA_OPTS% ^
- "-Dorg.jboss.boot.log.file=%JBOSS_HOME%\appclient\log\appclient.log" ^
- "-Dlogging.configuration=file:%JBOSS_HOME%/appclient/configuration/logging.properties" ^
-    -jar "%JBOSS_HOME%\jboss-modules.jar" ^
-    -mp "%JBOSS_MODULEPATH%" ^
-    -jaxpmodule "javax.xml.jaxp-provider" ^
-     org.jboss.as.appclient ^
-    -Djboss.home.dir="%JBOSS_HOME%" ^
-    -Djboss.server.base.dir="%JBOSS_HOME%\appclient" ^
-     %*

jboss-as-7.2.0.Final/bin/appclient.conf

@@ -1,59 +0,0 @@
-## -*- shell-script -*- ######################################################
-##                                                                          ##
-##  JBoss Bootstrap Script Configuration                                    ##
-##                                                                          ##
-##############################################################################
-
-#
-# This file is optional; it may be removed if not needed.
-#
-
-#
-# Specify the maximum file descriptor limit, use "max" or "maximum" to use
-# the default, as queried by the system.
-#
-# Defaults to "maximum"
-#
-#MAX_FD="maximum"
-
-#
-# Specify the profiler configuration file to load.
-#
-# Default is to not load profiler configuration file.
-#
-#PROFILER=""
-
-#
-# Specify the location of the Java home directory.  If set then $JAVA will
-# be defined to $JAVA_HOME/bin/java, else $JAVA will be "java".
-#
-#JAVA_HOME="/opt/java/jdk"
-
-#
-# Specify the exact Java VM executable to use.
-#
-#JAVA=""
-
-if [ "x$JBOSS_MODULES_SYSTEM_PKGS" = "x" ]; then
-   JBOSS_MODULES_SYSTEM_PKGS="org.jboss.byteman"
-fi
-
-#
-# Specify options to pass to the Java VM.
-#
-if [ "x$JAVA_OPTS" = "x" ]; then
-   JAVA_OPTS="-Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true"
-   JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
-fi
-
-# Sample JPDA settings for remote socket debugging
-#JAVA_OPTS="$JAVA_OPTS -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n"
-
-# Sample JPDA settings for shared memory debugging
-#JAVA_OPTS="$JAVA_OPTS -agentlib:jdwp=transport=dt_shmem,server=y,suspend=n,address=jboss"
-
-# Allow JProfiler to find its classes
-#JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=com.jprofiler"
-
-# Use JBoss Modules lockless mode
-#JAVA_OPTS="$JAVA_OPTS -Djboss.modules.lockless=true"

jboss-as-7.2.0.Final/bin/appclient.conf.bat

@@ -1,61 +0,0 @@
-rem ### -*- batch file -*- ######################################################
-rem #                                                                          ##
-rem #  JBoss Bootstrap Script Configuration                                    ##
-rem #                                                                          ##
-rem #############################################################################
-
-rem # $Id: run.conf.bat 88820 2009-05-13 15:25:44Z dimitris@jboss.org $
-
-rem #
-rem # This batch file is executed by run.bat to initialize the environment
-rem # variables that run.bat uses. It is recommended to use this file to
-rem # configure these variables, rather than modifying run.bat itself.
-rem #
-
-if not "x%JAVA_OPTS%" == "x" goto JAVA_OPTS_SET
-
-rem #
-rem # Specify the JBoss Profiler configuration file to load.
-rem #
-rem # Default is to not load a JBoss Profiler configuration file.
-rem #
-rem set "PROFILER=%JBOSS_HOME%\bin\jboss-profiler.properties"
-
-rem #
-rem # Specify the location of the Java home directory (it is recommended that
-rem # this always be set). If set, then "%JAVA_HOME%\bin\java" will be used as
-rem # the Java VM executable; otherwise, "%JAVA%" will be used (see below).
-rem #
-rem set "JAVA_HOME=C:\opt\jdk1.6.0_23"
-
-rem #
-rem # Specify the exact Java VM executable to use - only used if JAVA_HOME is
-rem # not set. Default is "java".
-rem #
-rem set "JAVA=C:\opt\jdk1.6.0_23\bin\java"
-
-rem #
-rem # Specify options to pass to the Java VM. Note, there are some additional
-rem # options that are always passed by run.bat.
-rem #
-
-rem # JVM memory allocation pool parameters - modify as appropriate.
-set "JAVA_OPTS=-Xms64M -Xmx512M -XX:MaxPermSize=256M"
-
-rem # Prefer IPv4
-set "JAVA_OPTS=%JAVA_OPTS%  -Djava.net.preferIPv4Stack=true "
-
-rem # Make Byteman classes visible in all module loaders
-rem # This is necessary to inject Byteman rules into AS7 deployments
-set "JAVA_OPTS=%JAVA_OPTS% -Djboss.modules.system.pkgs=org.jboss.byteman"
-
-rem # Sample JPDA settings for remote socket debugging
-rem set "JAVA_OPTS=%JAVA_OPTS% -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n"
-
-rem # Sample JPDA settings for shared memory debugging
-rem set "JAVA_OPTS=%JAVA_OPTS% -agentlib:jdwp=transport=dt_shmem,address=jboss,server=y,suspend=n"
-
-rem # Use JBoss Modules lockless mode
-rem set "JAVA_OPTS=%JAVA_OPTS% -Djboss.modules.lockless=true"
-
-:JAVA_OPTS_SET

jboss-as-7.2.0.Final/bin/appclient.sh

@@ -1,130 +0,0 @@
-#!/bin/sh
-
-DIRNAME=`dirname "$0"`
-PROGNAME=`basename "$0"`
-GREP="grep"
-
-# Use the maximum available, or set MAX_FD != -1 to use that
-MAX_FD="maximum"
-
-# OS specific support (must be 'true' or 'false').
-cygwin=false;
-darwin=false;
-linux=false;
-case "`uname`" in
-    CYGWIN*)
-        cygwin=true
-        ;;
-
-    Darwin*)
-        darwin=true
-        ;;
-
-    Linux)
-        linux=true
-        ;;
-esac
-
-# Read an optional running configuration file
-if [ "x$RUN_CONF" = "x" ]; then
-    RUN_CONF="$DIRNAME/appclient.conf"
-fi
-if [ -r "$RUN_CONF" ]; then
-    . "$RUN_CONF"
-fi
-
-# For Cygwin, ensure paths are in UNIX format before anything is touched
-if $cygwin ; then
-    [ -n "$JBOSS_HOME" ] &&
-        JBOSS_HOME=`cygpath --unix "$JBOSS_HOME"`
-    [ -n "$JAVA_HOME" ] &&
-        JAVA_HOME=`cygpath --unix "$JAVA_HOME"`
-    [ -n "$JAVAC_JAR" ] &&
-        JAVAC_JAR=`cygpath --unix "$JAVAC_JAR"`
-fi
-
-# Setup JBOSS_HOME
-RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
-if [ "x$JBOSS_HOME" = "x" ]; then
-    # get the full path (without any relative bits)
-    JBOSS_HOME=$RESOLVED_JBOSS_HOME
-else
- SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME"; pwd`
- if [ "$RESOLVED_JBOSS_HOME" != "$SANITIZED_JBOSS_HOME" ]; then
-   echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
-   echo ""
- fi
-fi
-export JBOSS_HOME
-
-# Setup the JVM
-if [ "x$JAVA" = "x" ]; then
-    if [ "x$JAVA_HOME" != "x" ]; then
-        JAVA="$JAVA_HOME/bin/java"
-    else
-        JAVA="java"
-    fi
-fi
-
-# Check for -d32/-d64 in JAVA_OPTS
-JVM_OPTVERSION="-version"
-JVM_D64_OPTION=`echo $JAVA_OPTS | $GREP "\-d64"`
-JVM_D32_OPTION=`echo $JAVA_OPTS | $GREP "\-d32"`
-test "x$JVM_D64_OPTION" != "x" && JVM_OPTVERSION="-d64 $JVM_OPTVERSION"
-test "x$JVM_D32_OPTION" != "x" && JVM_OPTVERSION="-d32 $JVM_OPTVERSION"
-
-# If -server not set in JAVA_OPTS, set it, if supported
-SERVER_SET=`echo $JAVA_OPTS | $GREP "\-server"`
-if [ "x$SERVER_SET" = "x" ]; then
-
-    # Check for SUN(tm) JVM w/ HotSpot support
-    if [ "x$HAS_HOTSPOT" = "x" ]; then
-        HAS_HOTSPOT=`"$JAVA" $JVM_OPTVERSION -version 2>&1 | $GREP -i HotSpot`
-    fi
-
-    # Check for OpenJDK JVM w/server support
-    if [ "x$HAS_OPENJDK_" = "x" ]; then
-        HAS_OPENJDK=`"$JAVA" $JVM_OPTVERSION 2>&1 | $GREP -i OpenJDK`
-    fi
-
-    # Enable -server if we have Hotspot or OpenJDK, unless we can't
-    if [ "x$HAS_HOTSPOT" != "x" -o "x$HAS_OPENJDK" != "x" ]; then
-        # MacOS does not support -server flag
-        if [ "$darwin" != "true" ]; then
-            JAVA_OPTS="-server $JAVA_OPTS"
-            JVM_OPTVERSION="-server $JVM_OPTVERSION"
-        fi
-    fi
-else
-    JVM_OPTVERSION="-server $JVM_OPTVERSION"
-fi
-
-if [ "x$JBOSS_MODULEPATH" = "x" ]; then
-    JBOSS_MODULEPATH="$JBOSS_HOME/modules"
-fi
-
-# For Cygwin, switch paths to Windows format before running java
-if $cygwin; then
-    JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
-    JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
-    JBOSS_CLASSPATH=`cygpath --path --windows "$JBOSS_CLASSPATH"`
-    JBOSS_ENDORSED_DIRS=`cygpath --path --windows "$JBOSS_ENDORSED_DIRS"`
-    JBOSS_MODULEPATH=`cygpath --path --windows "$JBOSS_MODULEPATH"`
-fi
-
-CLASSPATH="$CLASSPATH:$JBOSS_HOME/jboss-modules.jar"
-
-# Execute the JVM in the foreground
-eval \"$JAVA\" $JAVA_OPTS \
- -cp "$CLASSPATH" \
- \"-Dorg.jboss.boot.log.file=$JBOSS_HOME/appclient/log/appclient.log\" \
- \"-Dlogging.configuration=file:$JBOSS_HOME/appclient/configuration/logging.properties\" \
- org.jboss.modules.Main \
- -mp \"${JBOSS_MODULEPATH}\" \
- -jaxpmodule javax.xml.jaxp-provider \
- org.jboss.as.appclient \
- -Djboss.home.dir=\"$JBOSS_HOME\" \
- -Djboss.server.base.dir=\"$JBOSS_HOME/appclient\" \
- '"$@"'
-JBOSS_STATUS=$?
-exit $JBOSS_STATUS

jboss-as-7.2.0.Final/bin/client/README-CLI-JCONSOLE.txt

@@ -1,16 +0,0 @@
-The jboss-cli-client jar can be used to remotely manage a JBoss AS instance with CLI or jconsole.  Copy jboss-cli-client.jar to your client machine.  You do not need to install JBoss AS.
-
-TO RUN CLI:
-java -jar <PATH TO jboss-cli-client.jar> [--help] [--version] [--controller=host:port]
-                                         [--gui] [--connect] [--file=file_path]
-                                         [--commands=command_or_operation1,command_or_operation2...]
-                                         [--command=command_or_operation]
-                                         [--user=username --password=password]
-
-Use --help for an explanation of the CLI command line options.
-
-
-TO RUN JCONSOLE:
-jconsole -J-Djava.class.path=<PATH TO jconsole.jar>;<PATH TO tools.jar>;<PATH TO jboss-cli-client.jar>
-
-Path to jconsole.jar and tools.jar is typically <JAVA_HOME>/lib/jconsole.jar and <JAVA_HOME>/lib/tools.jar.

jboss-as-7.2.0.Final/bin/client/README-EJB-JMS.txt

@@ -1,41 +0,0 @@
-jboss-client.jar is a combined client jar for JBoss AS7, for use in non-maven environments. This jar should be used
-with standalone clients only, not with deployments are that deployed to an AS7 instance.
-
-This jar contains the classes required for remote JMS and EJB usage, and consists of the following shaded artifacts:
-
-org.jboss.spec.javax.jms:jboss-jms-api_1.1_spec
-org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec
-org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec
-
-org.jboss:jboss-ejb-client
-org.jboss:jboss-remote-naming
-org.jboss.logging:jboss-logging
-org.jboss.marshalling:jboss-marshalling
-org.jboss.marshalling:jboss-marshalling-river
-org.jboss.remoting3:jboss-remoting
-org.jboss.remoting3:remoting-jmx
-org.jboss.sasl:jboss-sasl
-org.jboss.xnio:xnio-api
-org.jboss.xnio:xnio-nio
-org.jboss.netty:netty
-org.hornetq:hornetq-core-client
-org.hornetq:hornetq-jms-client
-
-
-Maven users should not use this jar, but should use the following BOM dependencies instead
-
-    <dependencies>
-        <dependency>
-            <groupId>org.jboss.as</groupId>
-            <artifactId>jboss-as-ejb-client-bom</artifactId>
-            <type>pom</type>
-        </dependency>
-        <dependency>
-            <groupId>org.jboss.as</groupId>
-            <artifactId>jboss-as-jms-client-bom</artifactId>
-            <type>pom</type>
-        </dependency>
-    </dependencies>
-
-This is because using maven with a shaded jar has a very high chance of causing class version conflicts, which is why
-we do not publish this jar to the maven repository.

jboss-as-7.2.0.Final/bin/domain.bat

@@ -1,138 +0,0 @@
-@echo off
-rem -------------------------------------------------------------------------
-rem JBoss Bootstrap Script for Windows
-rem -------------------------------------------------------------------------
-
-rem $Id$
-
-@if not "%ECHO%" == ""  echo %ECHO%
-@if "%OS%" == "Windows_NT" setlocal
-
-if "%OS%" == "Windows_NT" (
-  set "DIRNAME=%~dp0%"
-) else (
-  set DIRNAME=.\
-)
-
-rem Read an optional configuration file.
-if "x%DOMAIN_CONF%" == "x" (
-   set "DOMAIN_CONF=%DIRNAME%domain.conf.bat"
-)
-if exist "%DOMAIN_CONF%" (
-   echo Calling "%DOMAIN_CONF%"
-   call "%DOMAIN_CONF%" %*
-) else (
-   echo Config file not found "%DOMAIN_CONF%"
-)
-
-pushd %DIRNAME%..
-set "RESOLVED_JBOSS_HOME=%CD%"
-popd
-
-if "x%JBOSS_HOME%" == "x" (
-  set "JBOSS_HOME=%RESOLVED_JBOSS_HOME%"
-)
-
-pushd "%JBOSS_HOME%"
-set "SANITIZED_JBOSS_HOME=%CD%"
-popd
-
-if "%RESOLVED_JBOSS_HOME%" NEQ "%SANITIZED_JBOSS_HOME%" (
-    echo WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur.
-)
-
-set DIRNAME=
-
-if "%OS%" == "Windows_NT" (
-  set "PROGNAME=%~nx0%"
-) else (
-  set "PROGNAME=domain.bat"
-)
-
-rem Setup JBoss specific properties
-set JAVA_OPTS=-Dprogram.name=%PROGNAME% %JAVA_OPTS%
-
-if "x%JAVA_HOME%" == "x" (
-  set  JAVA=java
-  echo JAVA_HOME is not set. Unexpected results may occur.
-  echo Set JAVA_HOME to the directory of your local JDK to avoid this message.
-) else (
-  set "JAVA=%JAVA_HOME%\bin\java"
-)
-
-rem Add -server to the JVM options, if supported
-"%JAVA%" -server -version 2>&1 | findstr /I hotspot > nul
-if not errorlevel == 1 (
-  set "PROCESS_CONTROLLER_JAVA_OPTS=%PROCESS_CONTROLLER_JAVA_OPTS% -server"
-  set "HOST_CONTROLLER_JAVA_OPTS=%HOST_CONTROLLER_JAVA_OPTS% -server"
-)
-
-rem Find run.jar, or we can't continue
-if exist "%JBOSS_HOME%\jboss-modules.jar" (
-    set "RUNJAR=%JBOSS_HOME%\jboss-modules.jar"
-) else (
-  echo Could not locate "%JBOSS_HOME%\jboss-modules.jar".
-  echo Please check that you are in the bin directory when running this script.
-  goto END
-)
-
-rem Setup JBoss specific properties
-
-rem Setup the java endorsed dirs
-set JBOSS_ENDORSED_DIRS=%JBOSS_HOME%\lib\endorsed
-
-rem Set default module root paths
-if "x%JBOSS_MODULEPATH%" == "x" (
-  set  "JBOSS_MODULEPATH=%JBOSS_HOME%\modules"
-)
-
-rem Set the domain base dir
-if "x%JBOSS_BASE_DIR%" == "x" (
-  set  "JBOSS_BASE_DIR=%JBOSS_HOME%\domain"
-)
-rem Set the domain log dir
-if "x%JBOSS_LOG_DIR%" == "x" (
-  set  "JBOSS_LOG_DIR=%JBOSS_BASE_DIR%\log"
-)
-rem Set the domain configuration dir
-if "x%JBOSS_CONFIG_DIR%" == "x" (
-  set  "JBOSS_CONFIG_DIR=%JBOSS_BASE_DIR%/configuration"
-)
-
-echo ===============================================================================
-echo.
-echo   JBoss Bootstrap Environment
-echo.
-echo   JBOSS_HOME: %JBOSS_HOME%
-echo.
-echo   JAVA: %JAVA%
-echo.
-echo   JAVA_OPTS: %JAVA_OPTS%
-echo.
-echo ===============================================================================
-echo.
-
-:RESTART
-"%JAVA%" %PROCESS_CONTROLLER_JAVA_OPTS% ^
- "-Dorg.jboss.boot.log.file=%JBOSS_LOG_DIR%\process-controller.log" ^
- "-Dlogging.configuration=file:%JBOSS_CONFIG_DIR%/logging.properties" ^
-    -jar "%JBOSS_HOME%\jboss-modules.jar" ^
-    -mp "%JBOSS_MODULEPATH%" ^
-     org.jboss.as.process-controller ^
-    -jboss-home "%JBOSS_HOME%" ^
-    -jvm "%JAVA%" ^
-    -mp "%JBOSS_MODULEPATH%" ^
-    -- ^
-    "-Dorg.jboss.boot.log.file=%JBOSS_LOG_DIR%\host-controller.log" ^
-    "-Dlogging.configuration=file:%JBOSS_CONFIG_DIR%/logging.properties" ^
-    %HOST_CONTROLLER_JAVA_OPTS% ^
-    -- ^
-    -default-jvm "%JAVA%" ^
-    %*
-
-if ERRORLEVEL 10 goto RESTART
-
-:END
-if "x%NOPAUSE%" == "x" pause
-
-:END_NO_PAUSE

jboss-as-7.2.0.Final/bin/domain.conf

@@ -1,70 +0,0 @@
-## -*- shell-script -*- ######################################################
-##                                                                          ##
-##  JBoss Bootstrap Script Configuration                                    ##
-##                                                                          ##
-##############################################################################
-
-#
-# This file is optional; it may be removed if not needed.
-#
-
-#
-# Specify the maximum file descriptor limit, use "max" or "maximum" to use
-# the default, as queried by the system.
-#
-# Defaults to "maximum"
-#
-#MAX_FD="maximum"
-
-#
-# Specify the profiler configuration file to load.
-#
-# Default is to not load profiler configuration file.
-#
-#PROFILER=""
-
-#
-# Specify the location of the Java home directory.  If set then $JAVA will
-# be defined to $JAVA_HOME/bin/java, else $JAVA will be "java".
-#
-#JAVA_HOME="/opt/java/jdk"
-
-#
-# Specify the exact Java VM executable to use.
-#
-#JAVA=""
-
-if [ "x$JBOSS_MODULES_SYSTEM_PKGS" = "x" ]; then
-   JBOSS_MODULES_SYSTEM_PKGS="org.jboss.byteman"
-fi
-
-#
-# Specify options to pass to the Java VM.
-#
-if [ "x$JAVA_OPTS" = "x" ]; then
-   JAVA_OPTS="-Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true"
-   JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
-else
-   echo "JAVA_OPTS already set in environment; overriding default settings with values: $JAVA_OPTS"
-fi
-
-# Use JBoss Modules lockless mode
-#JAVA_OPTS="$JAVA_OPTS -Djboss.modules.lockless=true"
-
-# The ProcessController process uses its own set of java options
-if [ "x$PROCESS_CONTROLLER_JAVA_OPTS" = "x" ]; then
-    PROCESS_CONTROLLER_JAVA_OPTS="$JAVA_OPTS"
-fi
-
-# The HostController process uses its own set of java options
-if [ "x$HOST_CONTROLLER_JAVA_OPTS" = "x" ]; then
-    HOST_CONTROLLER_JAVA_OPTS="$JAVA_OPTS"
-fi
-
-# Sample JPDA settings for remote socket debuging.
-#PROCESS_CONTROLLER_JAVA_OPTS="$PROCESS_CONTROLLER_JAVA_OPTS -agentlib:jdwp=transport=dt_socket,address=8788,server=y,suspend=n"
-#HOST_CONTROLLER_JAVA_OPTS="$HOST_CONTROLLER_JAVA_OPTS -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n"
-
-# Sample JPDA settings for shared memory debugging
-#PROCESS_CONTROLLER_JAVA_OPTS="$PROCESS_CONTROLLER_JAVA_OPTS -agentlib:jdwp=transport=dt_shmem,server=y,suspend=n,address=jboss"
-#HOST_CONTROLLER_JAVA_OPTS="$HOST_CONTROLLER_JAVA_OPTS -agentlib:jdwp=transport=dt_shmem,server=y,suspend=n,address=jboss"

jboss-as-7.2.0.Final/bin/domain.conf.bat

@@ -1,73 +0,0 @@
-rem ### -*- batch file -*- ######################################################
-rem #                                                                          ##
-rem #  JBoss Bootstrap Script Configuration                                    ##
-rem #                                                                          ##
-rem #############################################################################
-
-rem # $Id: run.conf.bat 88820 2009-05-13 15:25:44Z dimitris@jboss.org $
-
-rem #
-rem # This batch file is executed by run.bat to initialize the environment
-rem # variables that run.bat uses. It is recommended to use this file to
-rem # configure these variables, rather than modifying run.bat itself.
-rem #
-
-if not "x%JAVA_OPTS%" == "x" (
-  echo "JAVA_OPTS already set in environment; overriding default settings with values: %JAVA_OPTS%"
-  goto JAVA_OPTS_SET
-)
-
-rem #
-rem # Specify the JBoss Profiler configuration file to load.
-rem #
-rem # Default is to not load a JBoss Profiler configuration file.
-rem #
-rem set "PROFILER=%JBOSS_HOME%\bin\jboss-profiler.properties"
-
-rem #
-rem # Specify the location of the Java home directory (it is recommended that
-rem # this always be set). If set, then "%JAVA_HOME%\bin\java" will be used as
-rem # the Java VM executable; otherwise, "%JAVA%" will be used (see below).
-rem #
-rem set "JAVA_HOME=C:\opt\jdk1.6.0_23"
-
-rem #
-rem # Specify the exact Java VM executable to use - only used if JAVA_HOME is
-rem # not set. Default is "java".
-rem #
-rem set "JAVA=C:\opt\jdk1.6.0_23\bin\java"
-
-rem #
-rem # Specify options to pass to the Java VM. Note, there are some additional
-rem # options that are always passed by run.bat.
-rem #
-
-rem # JVM memory allocation pool parameters - modify as appropriate.
-set "JAVA_OPTS=-Xms64M -Xmx512M -XX:MaxPermSize=256M"
-
-rem # Prefer IPv4
-set "JAVA_OPTS=%JAVA_OPTS% -Djava.net.preferIPv4Stack=true"
-
-rem # Make Byteman classes visible in all module loaders
-rem # This is necessary to inject Byteman rules into AS7 deployments
-set "JAVA_OPTS=%JAVA_OPTS% -Djboss.modules.system.pkgs=org.jboss.byteman"
-
-rem # Use JBoss Modules lockless mode
-rem set "JAVA_OPTS=%JAVA_OPTS% -Djboss.modules.lockless=true"
-
-rem The ProcessController process uses its own set of java options
-set "PROCESS_CONTROLLER_JAVA_OPTS=%JAVA_OPTS%"
-
-rem The HostController process uses its own set of java options
-set "HOST_CONTROLLER_JAVA_OPTS=%JAVA_OPTS%"
-
-rem # Sample JPDA settings for remote socket debugging
-rem set "PROCESS_CONTROLLER_JAVA_OPTS=%PROCESS_CONTROLLER_JAVA_OPTS% -agentlib:jdwp=transport=dt_socket,address=8788,server=y,suspend=n"
-rem set "HOST_CONTROLLER_JAVA_OPTS=%HOST_CONTROLLER_JAVA_OPTS% -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n"
-
-rem # Sample JPDA settings for shared memory debugging
-rem set "PROCESS_CONTROLLER_JAVA_OPTS=%PROCESS_CONTROLLER_JAVA_OPTS% -agentlib:jdwp=transport=dt_shmem,address=jboss,server=y,suspend=n"
-rem set "HOST_CONTROLLER_JAVA_OPTS=%HOST_CONTROLLER_JAVA_OPTS% -agentlib:jdwp=transport=dt_shmem,address=jboss,server=y,suspend=n"
-
-:JAVA_OPTS_SET
-

jboss-as-7.2.0.Final/bin/domain.sh

@@ -1,250 +0,0 @@
-#!/bin/sh
-
-DIRNAME=`dirname "$0"`
-PROGNAME=`basename "$0"`
-GREP="grep"
-
-# Use the maximum available, or set MAX_FD != -1 to use that
-MAX_FD="maximum"
-
-# OS specific support (must be 'true' or 'false').
-cygwin=false;
-darwin=false;
-linux=false;
-case "`uname`" in
-    CYGWIN*)
-        cygwin=true
-        ;;
-
-    Darwin*)
-        darwin=true
-        ;;
-
-    Linux)
-        linux=true
-        ;;
-esac
-
-# Read an optional running configuration file
-if [ "x$DOMAIN_CONF" = "x" ]; then
-    DOMAIN_CONF="$DIRNAME/domain.conf"
-fi
-if [ -r "$DOMAIN_CONF" ]; then
-    . "$DOMAIN_CONF"
-fi
-
-# For Cygwin, ensure paths are in UNIX format before anything is touched
-if $cygwin ; then
-    [ -n "$JBOSS_HOME" ] &&
-        JBOSS_HOME=`cygpath --unix "$JBOSS_HOME"`
-    [ -n "$JAVA_HOME" ] &&
-        JAVA_HOME=`cygpath --unix "$JAVA_HOME"`
-    [ -n "$JAVAC_JAR" ] &&
-        JAVAC_JAR=`cygpath --unix "$JAVAC_JAR"`
-fi
-
-# Setup JBOSS_HOME
-RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
-if [ "x$JBOSS_HOME" = "x" ]; then
-    # get the full path (without any relative bits)
-    JBOSS_HOME=$RESOLVED_JBOSS_HOME
-else
- SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME"; pwd`
- if [ "$RESOLVED_JBOSS_HOME" != "$SANITIZED_JBOSS_HOME" ]; then
-   echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
-   echo ""
- fi
-fi
-export JBOSS_HOME
-
-# Setup the JVM
-if [ "x$JAVA" = "x" ]; then
-    if [ "x$JAVA_HOME" != "x" ]; then
-        JAVA="$JAVA_HOME/bin/java"
-    else
-        JAVA="java"
-    fi
-fi
-
-# Check for -d32/-d64 in JAVA_OPTS
-JVM_OPTVERSION="-version"
-JVM_D64_OPTION=`echo $JAVA_OPTS | $GREP "\-d64"`
-JVM_D32_OPTION=`echo $JAVA_OPTS | $GREP "\-d32"`
-test "x$JVM_D64_OPTION" != "x" && JVM_OPTVERSION="-d64 $JVM_OPTVERSION"
-test "x$JVM_D32_OPTION" != "x" && JVM_OPTVERSION="-d32 $JVM_OPTVERSION"
-
-# If -server not set in JAVA_OPTS, set it, if supported
-SERVER_SET=`echo $JAVA_OPTS | $GREP "\-server"`
-if [ "x$SERVER_SET" = "x" ]; then
-
-    # Check for SUN(tm) JVM w/ HotSpot support
-    if [ "x$HAS_HOTSPOT" = "x" ]; then
-        HAS_HOTSPOT=`"$JAVA" $JVM_OPTVERSION -version 2>&1 | $GREP -i HotSpot`
-    fi
-
-    # Check for OpenJDK JVM w/server support
-    if [ "x$HAS_OPENJDK" = "x" ]; then
-        HAS_OPENJDK=`"$JAVA" $JVM_OPTVERSION 2>&1 | $GREP -i OpenJDK`
-    fi
-
-    # Check for IBM JVM w/server support
-    if [ "x$HAS_IBM" = "x" ]; then
-        HAS_IBM=`"$JAVA" $JVM_OPTVERSION 2>&1 | $GREP -i "IBM J9"`
-    fi
-
-    # Enable -server if we have Hotspot or OpenJDK, unless we can't
-    if [ "x$HAS_HOTSPOT" != "x" -o "x$HAS_OPENJDK" != "x" -o "x$HAS_IBM" != "x" ]; then
-        # MacOS does not support -server flag
-        if [ "$darwin" != "true" ]; then
-            PROCESS_CONTROLLER_JAVA_OPTS="-server $PROCESS_CONTROLLER_JAVA_OPTS"
-            HOST_CONTROLLER_JAVA_OPTS="-server $HOST_CONTROLLER_JAVA_OPTS"
-            JVM_OPTVERSION="-server $JVM_OPTVERSION"
-        fi
-    fi
-else
-    JVM_OPTVERSION="-server $JVM_OPTVERSION"
-fi
-
-if [ "x$JBOSS_MODULEPATH" = "x" ]; then
-    JBOSS_MODULEPATH="$JBOSS_HOME/modules"
-fi
-
-if $linux; then
-    # consolidate the host-controller and command line opts
-    HOST_CONTROLLER_OPTS="$HOST_CONTROLLER_JAVA_OPTS $@"
-    # process the host-controller options
-    for var in $HOST_CONTROLLER_OPTS
-    do
-      case $var in
-        -Djboss.domain.base.dir=*)
-             JBOSS_BASE_DIR=`readlink -m ${var#*=}`
-             ;;
-        -Djboss.domain.log.dir=*)
-             JBOSS_LOG_DIR=`readlink -m ${var#*=}`
-             ;;
-        -Djboss.domain.config.dir=*)
-             JBOSS_CONFIG_DIR=`readlink -m ${var#*=}`
-             ;;
-      esac
-    done
-fi
-# determine the default base dir, if not set
-if [ "x$JBOSS_BASE_DIR" = "x" ]; then
-   JBOSS_BASE_DIR="$JBOSS_HOME/domain"
-fi
-# determine the default log dir, if not set
-if [ "x$JBOSS_LOG_DIR" = "x" ]; then
-   JBOSS_LOG_DIR="$JBOSS_BASE_DIR/log"
-fi
-# determine the default configuration dir, if not set
-if [ "x$JBOSS_CONFIG_DIR" = "x" ]; then
-   JBOSS_CONFIG_DIR="$JBOSS_BASE_DIR/configuration"
-fi
-
-# Setup the java path to invoke from JVM
-# Needed to start domain from cygwin when the JAVA path will result in an invalid path
-JAVA_FROM_JVM="$JAVA"
-
-# For Cygwin, switch paths to Windows format before running java
-if $cygwin; then
-    JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
-    JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
-    JAVA_FROM_JVM=`cygpath --path --absolute --windows "$JAVA_FROM_JVM"`
-    JBOSS_BASE_DIR=`cygpath --path --windows "$JBOSS_BASE_DIR"`
-    JBOSS_LOG_DIR=`cygpath --path --windows "$JBOSS_LOG_DIR"`
-    JBOSS_CONFIG_DIR=`cygpath --path --windows "$JBOSS_CONFIG_DIR"`
-    JBOSS_MODULEPATH=`cygpath --path --windows "$JBOSS_MODULEPATH"`
-fi
-
-# Display our environment
-echo "========================================================================="
-echo ""
-echo "  JBoss Bootstrap Environment"
-echo ""
-echo "  JBOSS_HOME: $JBOSS_HOME"
-echo ""
-echo "  JAVA: $JAVA"
-echo ""
-echo "  JAVA_OPTS: $JAVA_OPTS"
-echo ""
-echo "========================================================================="
-echo ""
-
-while true; do
-   if [ "x$LAUNCH_JBOSS_IN_BACKGROUND" = "x" ]; then
-      # Execute the JVM in the foreground
-      eval \"$JAVA\" -D\"[Process Controller]\" $PROCESS_CONTROLLER_JAVA_OPTS \
-         \"-Dorg.jboss.boot.log.file=$JBOSS_LOG_DIR/process-controller.log\" \
-         \"-Dlogging.configuration=file:$JBOSS_CONFIG_DIR/logging.properties\" \
-         -jar \"$JBOSS_HOME/jboss-modules.jar\" \
-         -mp \"${JBOSS_MODULEPATH}\" \
-         org.jboss.as.process-controller \
-         -jboss-home \"$JBOSS_HOME\" \
-         -jvm \"$JAVA_FROM_JVM\" \
-         -mp \"${JBOSS_MODULEPATH}\" \
-         -- \
-         \"-Dorg.jboss.boot.log.file=$JBOSS_LOG_DIR/host-controller.log\" \
-         \"-Dlogging.configuration=file:$JBOSS_CONFIG_DIR/logging.properties\" \
-         $HOST_CONTROLLER_JAVA_OPTS \
-         -- \
-         -default-jvm \"$JAVA_FROM_JVM\" \
-         '"$@"'
-      JBOSS_STATUS=$?
-   else
-      # Execute the JVM in the background
-      eval \"$JAVA\" -D\"[Process Controller]\" $PROCESS_CONTROLLER_JAVA_OPTS \
-         \"-Dorg.jboss.boot.log.file=$JBOSS_LOG_DIR/process-controller.log\" \
-         \"-Dlogging.configuration=file:$JBOSS_CONFIG_DIR/logging.properties\" \
-         -jar \"$JBOSS_HOME/jboss-modules.jar\" \
-         -mp \"${JBOSS_MODULEPATH}\" \
-         org.jboss.as.process-controller \
-         -jboss-home \"$JBOSS_HOME\" \
-         -jvm \"$JAVA_FROM_JVM\" \
-         -mp \"${JBOSS_MODULEPATH}\" \
-         -- \
-         \"-Dorg.jboss.boot.log.file=$JBOSS_LOG_DIR/host-controller.log\" \
-         \"-Dlogging.configuration=file:$JBOSS_CONFIG_DIR/logging.properties\" \
-         $HOST_CONTROLLER_JAVA_OPTS \
-         -- \
-         -default-jvm \"$JAVA_FROM_JVM\" \
-         '"$@"' "&"
-      JBOSS_PID=$!
-      # Trap common signals and relay them to the jboss process
-      trap "kill -HUP  $JBOSS_PID" HUP
-      trap "kill -TERM $JBOSS_PID" INT
-      trap "kill -QUIT $JBOSS_PID" QUIT
-      trap "kill -PIPE $JBOSS_PID" PIPE
-      trap "kill -TERM $JBOSS_PID" TERM
-      if [ "x$JBOSS_PIDFILE" != "x" ]; then
-        echo $JBOSS_PID > $JBOSS_PIDFILE
-      fi
-      # Wait until the background process exits
-      WAIT_STATUS=128
-      while [ "$WAIT_STATUS" -ge 128 ]; do
-         wait $JBOSS_PID 2>/dev/null
-         WAIT_STATUS=$?
-         if [ "$WAIT_STATUS" -gt 128 ]; then
-            SIGNAL=`expr $WAIT_STATUS - 128`
-            SIGNAL_NAME=`kill -l $SIGNAL`
-            echo "*** JBossAS process ($JBOSS_PID) received $SIGNAL_NAME signal ***" >&2
-         fi
-      done
-      if [ "$WAIT_STATUS" -lt 127 ]; then
-         JBOSS_STATUS=$WAIT_STATUS
-      else
-         JBOSS_STATUS=0
-      fi
-      if [ "$JBOSS_STATUS" -ne 10 ]; then
-            # Wait for a complete shudown
-            wait $JBOSS_PID 2>/dev/null
-      fi
-      if [ "x$JBOSS_PIDFILE" != "x" ]; then
-            grep "$JBOSS_PID" $JBOSS_PIDFILE && rm $JBOSS_PIDFILE
-      fi
-   fi
-   if [ "$JBOSS_STATUS" -eq 10 ]; then
-      echo "Restarting JBoss..."
-   else
-      exit $JBOSS_STATUS
-   fi
-done

jboss-as-7.2.0.Final/bin/init.d/jboss-as-domain.sh

@@ -1,179 +0,0 @@
-#!/bin/sh
-#
-# JBoss domain control script
-#
-# chkconfig: - 80 20
-# description: JBoss AS Domain
-# processname: domain
-# pidfile: /var/run/jboss-as/jboss-as-domain.pid
-# config: /etc/jboss-as/jboss-as.conf
-
-# Source function library.
-. /etc/init.d/functions
-
-# Load Java configuration.
-[ -r /etc/java/java.conf ] && . /etc/java/java.conf
-export JAVA_HOME
-
-# Load JBoss AS init.d configuration.
-if [ -z "$JBOSS_CONF" ]; then
-  JBOSS_CONF="/etc/jboss-as/jboss-as.conf"
-fi
-
-[ -r "$JBOSS_CONF" ] && . "${JBOSS_CONF}"
-
-# Set defaults.
-
-if [ -z "$JBOSS_HOME" ]; then
-  JBOSS_HOME=/usr/share/jboss-as
-fi
-export JBOSS_HOME
-
-if [ -z "$JBOSS_PIDFILE" ]; then
-  JBOSS_PIDFILE=/var/run/jboss-as/jboss-as-domain.pid
-fi
-export JBOSS_PIDFILE
-
-if [ -z "$JBOSS_CONSOLE_LOG" ]; then
-  JBOSS_CONSOLE_LOG=/var/log/jboss-as/console.log
-fi
-
-if [ -z "$STARTUP_WAIT" ]; then
-  STARTUP_WAIT=30
-fi
-
-if [ -z "$SHUTDOWN_WAIT" ]; then
-  SHUTDOWN_WAIT=30
-fi
-
-if [ -z "$JBOSS_DOMAIN_CONFIG" ]; then
-  JBOSS_DOMAIN_CONFIG=domain.xml
-fi
-
-if [ -z "$JBOSS_HOST_CONFIG" ]; then
-  JBOSS_HOST_CONFIG=host.xml
-fi
-
-JBOSS_SCRIPT=$JBOSS_HOME/bin/domain.sh
-
-prog='jboss-as'
-
-CMD_PREFIX=''
-
-if [ ! -z "$JBOSS_USER" ]; then
-  if [ -x /etc/rc.d/init.d/functions ]; then
-    CMD_PREFIX="daemon --user $JBOSS_USER"
-  else
-    CMD_PREFIX="su - $JBOSS_USER -c"
-  fi
-fi
-
-start() {
-  echo -n "Starting $prog: "
-  if [ -f $JBOSS_PIDFILE ]; then
-    read ppid < $JBOSS_PIDFILE
-    if [ `ps --pid $ppid 2> /dev/null | grep -c $ppid 2> /dev/null` -eq '1' ]; then
-      echo -n "$prog is already running"
-      failure
-      echo
-      return 1
-    else
-      rm -f $JBOSS_PIDFILE
-    fi
-  fi
-  mkdir -p $(dirname $JBOSS_CONSOLE_LOG)
-  cat /dev/null > $JBOSS_CONSOLE_LOG
-
-  mkdir -p $(dirname $JBOSS_PIDFILE)
-  chown $JBOSS_USER $(dirname $JBOSS_PIDFILE) || true
-  #$CMD_PREFIX JBOSS_PIDFILE=$JBOSS_PIDFILE $JBOSS_SCRIPT 2>&1 > $JBOSS_CONSOLE_LOG &
-  #$CMD_PREFIX JBOSS_PIDFILE=$JBOSS_PIDFILE $JBOSS_SCRIPT &
-
-  if [ ! -z "$JBOSS_USER" ]; then
-    if [ -r /etc/rc.d/init.d/functions ]; then
-      daemon --user $JBOSS_USER LAUNCH_JBOSS_IN_BACKGROUND=1 JBOSS_PIDFILE=$JBOSS_PIDFILE $JBOSS_SCRIPT --domain-config=$JBOSS_DOMAIN_CONFIG --host-config=$JBOSS_HOST_CONFIG 2>&1 > $JBOSS_CONSOLE_LOG &
-    else
-      su - $JBOSS_USER -c "LAUNCH_JBOSS_IN_BACKGROUND=1 JBOSS_PIDFILE=$JBOSS_PIDFILE $JBOSS_SCRIPT --domain-config=$JBOSS_DOMAIN_CONFIG --host-config=$JBOSS_HOST_CONFIG" 2>&1 > $JBOSS_CONSOLE_LOG &
-    fi
-  fi
-
-  count=0
-  launched=false
-
-  until [ $count -gt $STARTUP_WAIT ]
-  do
-    grep 'JBoss AS.*started in' $JBOSS_CONSOLE_LOG > /dev/null
-    if [ $? -eq 0 ] ; then
-      launched=true
-      break
-    fi
-    sleep 1
-    let count=$count+1;
-  done
-
-  success
-  echo
-  return 0
-}
-
-stop() {
-  echo -n $"Stopping $prog: "
-  count=0;
-
-  if [ -f $JBOSS_PIDFILE ]; then
-    read kpid < $JBOSS_PIDFILE
-    let kwait=$SHUTDOWN_WAIT
-
-    # Try issuing SIGTERM
-
-    kill -15 $kpid
-    until [ `ps --pid $kpid 2> /dev/null | grep -c $kpid 2> /dev/null` -eq '0' ] || [ $count -gt $kwait ]
-    do
-      sleep 1
-      let count=$count+1;
-    done
-
-    if [ $count -gt $kwait ]; then
-      kill -9 $kpid
-    fi
-  fi
-  rm -f $JBOSS_PIDFILE
-  success
-  echo
-}
-
-status() {
-  if [ -f $JBOSS_PIDFILE ]; then
-    read ppid < $JBOSS_PIDFILE
-    if [ `ps --pid $ppid 2> /dev/null | grep -c $ppid 2> /dev/null` -eq '1' ]; then
-      echo "$prog is running (pid $ppid)"
-      return 0
-    else
-      echo "$prog dead but pid file exists"
-      return 1
-    fi
-  fi
-  echo "$prog is not running"
-  return 3
-}
-
-case "$1" in
-  start)
-      start
-      ;;
-  stop)
-      stop
-      ;;
-  restart)
-      $0 stop
-      $0 start
-      ;;
-  status)
-      status
-      ;;
-  *)
-      ## If no parameters are given, print which are avaiable.
-      echo "Usage: $0 {start|stop|status|restart|reload}"
-      exit 1
-      ;;
-esac

jboss-as-7.2.0.Final/bin/init.d/jboss-as-standalone.sh

@@ -1,175 +0,0 @@
-#!/bin/sh
-#
-# JBoss standalone control script
-#
-# chkconfig: - 80 20
-# description: JBoss AS Standalone
-# processname: standalone
-# pidfile: /var/run/jboss-as/jboss-as-standalone.pid
-# config: /etc/jboss-as/jboss-as.conf
-
-# Source function library.
-. /etc/init.d/functions
-
-# Load Java configuration.
-[ -r /etc/java/java.conf ] && . /etc/java/java.conf
-export JAVA_HOME
-
-# Load JBoss AS init.d configuration.
-if [ -z "$JBOSS_CONF" ]; then
-  JBOSS_CONF="/etc/jboss-as/jboss-as.conf"
-fi
-
-[ -r "$JBOSS_CONF" ] && . "${JBOSS_CONF}"
-
-# Set defaults.
-
-if [ -z "$JBOSS_HOME" ]; then
-  JBOSS_HOME=/usr/share/jboss-as
-fi
-export JBOSS_HOME
-
-if [ -z "$JBOSS_PIDFILE" ]; then
-  JBOSS_PIDFILE=/var/run/jboss-as/jboss-as-standalone.pid
-fi
-export JBOSS_PIDFILE
-
-if [ -z "$JBOSS_CONSOLE_LOG" ]; then
-  JBOSS_CONSOLE_LOG=/var/log/jboss-as/console.log
-fi
-
-if [ -z "$STARTUP_WAIT" ]; then
-  STARTUP_WAIT=30
-fi
-
-if [ -z "$SHUTDOWN_WAIT" ]; then
-  SHUTDOWN_WAIT=30
-fi
-
-if [ -z "$JBOSS_CONFIG" ]; then
-  JBOSS_CONFIG=standalone.xml
-fi
-
-JBOSS_SCRIPT=$JBOSS_HOME/bin/standalone.sh
-
-prog='jboss-as'
-
-CMD_PREFIX=''
-
-if [ ! -z "$JBOSS_USER" ]; then
-  if [ -r /etc/rc.d/init.d/functions ]; then
-    CMD_PREFIX="daemon --user $JBOSS_USER"
-  else
-    CMD_PREFIX="su - $JBOSS_USER -c"
-  fi
-fi
-
-start() {
-  echo -n "Starting $prog: "
-  if [ -f $JBOSS_PIDFILE ]; then
-    read ppid < $JBOSS_PIDFILE
-    if [ `ps --pid $ppid 2> /dev/null | grep -c $ppid 2> /dev/null` -eq '1' ]; then
-      echo -n "$prog is already running"
-      failure
-      echo
-      return 1 
-    else
-      rm -f $JBOSS_PIDFILE
-    fi
-  fi
-  mkdir -p $(dirname $JBOSS_CONSOLE_LOG)
-  cat /dev/null > $JBOSS_CONSOLE_LOG
-
-  mkdir -p $(dirname $JBOSS_PIDFILE)
-  chown $JBOSS_USER $(dirname $JBOSS_PIDFILE) || true
-  #$CMD_PREFIX JBOSS_PIDFILE=$JBOSS_PIDFILE $JBOSS_SCRIPT 2>&1 > $JBOSS_CONSOLE_LOG &
-  #$CMD_PREFIX JBOSS_PIDFILE=$JBOSS_PIDFILE $JBOSS_SCRIPT &
-
-  if [ ! -z "$JBOSS_USER" ]; then
-    if [ -r /etc/rc.d/init.d/functions ]; then
-      daemon --user $JBOSS_USER LAUNCH_JBOSS_IN_BACKGROUND=1 JBOSS_PIDFILE=$JBOSS_PIDFILE $JBOSS_SCRIPT -c $JBOSS_CONFIG 2>&1 > $JBOSS_CONSOLE_LOG &
-    else
-      su - $JBOSS_USER -c "LAUNCH_JBOSS_IN_BACKGROUND=1 JBOSS_PIDFILE=$JBOSS_PIDFILE $JBOSS_SCRIPT -c $JBOSS_CONFIG" 2>&1 > $JBOSS_CONSOLE_LOG &
-    fi
-  fi
-
-  count=0
-  launched=false
-
-  until [ $count -gt $STARTUP_WAIT ]
-  do
-    grep 'JBAS015874:' $JBOSS_CONSOLE_LOG > /dev/null 
-    if [ $? -eq 0 ] ; then
-      launched=true
-      break
-    fi 
-    sleep 1
-    let count=$count+1;
-  done
-  
-  success
-  echo
-  return 0
-}
-
-stop() {
-  echo -n $"Stopping $prog: "
-  count=0;
-
-  if [ -f $JBOSS_PIDFILE ]; then
-    read kpid < $JBOSS_PIDFILE
-    let kwait=$SHUTDOWN_WAIT
-
-    # Try issuing SIGTERM
-
-    kill -15 $kpid
-    until [ `ps --pid $kpid 2> /dev/null | grep -c $kpid 2> /dev/null` -eq '0' ] || [ $count -gt $kwait ]
-    do
-      sleep 1
-      let count=$count+1;
-    done
-
-    if [ $count -gt $kwait ]; then
-      kill -9 $kpid
-    fi
-  fi
-  rm -f $JBOSS_PIDFILE
-  success
-  echo
-}
-
-status() {
-  if [ -f $JBOSS_PIDFILE ]; then
-    read ppid < $JBOSS_PIDFILE
-    if [ `ps --pid $ppid 2> /dev/null | grep -c $ppid 2> /dev/null` -eq '1' ]; then
-      echo "$prog is running (pid $ppid)"
-      return 0
-    else
-      echo "$prog dead but pid file exists"
-      return 1
-    fi
-  fi
-  echo "$prog is not running"
-  return 3
-}
-
-case "$1" in
-  start)
-      start
-      ;;
-  stop)
-      stop
-      ;;
-  restart)
-      $0 stop
-      $0 start
-      ;;
-  status)
-      status
-      ;;
-  *)
-      ## If no parameters are given, print which are avaiable.
-      echo "Usage: $0 {start|stop|status|restart|reload}"
-      exit 1
-      ;;
-esac

jboss-as-7.2.0.Final/bin/init.d/jboss-as.conf

@@ -1,18 +0,0 @@
-# General configuration for the init.d scripts,
-# not necessarily for JBoss AS itself.
-
-# The username who should own the process.
-#
-# JBOSS_USER=jboss-as
-
-# The amount of time to wait for startup
-#
-# STARTUP_WAIT=30
-
-# The amount of time to wait for shutdown
-#
-# SHUTDOWN_WAIT=30
-
-# Location to keep the console log
-#
-# JBOSS_CONSOLE_LOG=/var/log/jboss-as/console.log

jboss-as-7.2.0.Final/bin/jboss-cli-logging.properties

@@ -1,46 +0,0 @@
-#
-# JBoss, Home of Professional Open Source.
-# Copyright 2010, Red Hat, Inc., and individual contributors
-# as indicated by the @author tags. See the copyright.txt file in the
-# distribution for a full listing of individual contributors.
-#
-# This is free software; you can redistribute it and/or modify it
-# under the terms of the GNU Lesser General Public License as
-# published by the Free Software Foundation; either version 2.1 of
-# the License, or (at your option) any later version.
-#
-# This software is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-# Lesser General Public License for more details.
-#
-# You should have received a copy of the GNU Lesser General Public
-# License along with this software; if not, write to the Free
-# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
-# 02110-1301 USA, or see the FSF site: http://www.fsf.org.
-#
-
-# Additional logger names to configure (root logger is always configured)
-loggers=org,org.jboss.as.cli
-logger.org.level=OFF
-# assign a lower level to enable CLI logging
-logger.org.jboss.as.cli.level=OFF
-
-# Root logger level
-logger.level=${jboss.cli.log.level:INFO}
-# Root logger handlers
-# uncomment to enable logging to the file
-#logger.handlers=FILE
-
-# File handler configuration
-handler.FILE=org.jboss.logmanager.handlers.FileHandler
-handler.FILE.level=DEBUG
-handler.FILE.properties=autoFlush,fileName
-handler.FILE.autoFlush=true
-handler.FILE.fileName=${jboss.cli.log.file:jboss-cli.log}
-handler.FILE.formatter=PATTERN
-
-# Formatter pattern configuration
-formatter.PATTERN=org.jboss.logmanager.formatters.PatternFormatter
-formatter.PATTERN.properties=pattern
-formatter.PATTERN.pattern=%d{HH:mm:ss,SSS} %-5p [%c] %s%E%n

jboss-as-7.2.0.Final/bin/jboss-cli.bat

@@ -1,71 +0,0 @@
-@echo off
-rem -------------------------------------------------------------------------
-rem JBoss Admin CLI Script for Windows
-rem -------------------------------------------------------------------------
-
-rem $Id$
-
-@if not "%ECHO%" == ""  echo %ECHO%
-@if "%OS%" == "Windows_NT" setlocal
-
-if "%OS%" == "Windows_NT" (
-  set "DIRNAME=%~dp0%"
-) else (
-  set DIRNAME=.\
-)
-
-pushd %DIRNAME%..
-set "RESOLVED_JBOSS_HOME=%CD%"
-popd
-
-if "x%JBOSS_HOME%" == "x" (
-  set "JBOSS_HOME=%RESOLVED_JBOSS_HOME%"
-)
-
-pushd "%JBOSS_HOME%"
-set "SANITIZED_JBOSS_HOME=%CD%"
-popd
-
-if "%RESOLVED_JBOSS_HOME%" NEQ "%SANITIZED_JBOSS_HOME%" (
-    echo WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur.
-)
-
-set DIRNAME=
-
-if "%OS%" == "Windows_NT" (
-  set "PROGNAME=%~nx0%"
-) else (
-  set "PROGNAME=jboss-cli.bat"
-)
-
-rem Setup JBoss specific properties
-set JAVA_OPTS=-Dprogram.name=%PROGNAME% %JAVA_OPTS%
-
-if "x%JAVA_HOME%" == "x" (
-  set  JAVA=java
-  echo JAVA_HOME is not set. Unexpected results may occur.
-  echo Set JAVA_HOME to the directory of your local JDK to avoid this message.
-) else (
-  set "JAVA=%JAVA_HOME%\bin\java"
-)
-
-rem Find run.jar, or we can't continue
-if exist "%JBOSS_HOME%\jboss-modules.jar" (
-    set "RUNJAR=%JBOSS_HOME%\jboss-modules.jar"
-) else (
-  echo Could not locate "%JBOSS_HOME%\jboss-modules.jar".
-  echo Please check that you are in the bin directory when running this script.
-  goto END
-)
-
-rem Add base package for L&F
-set JAVA_OPTS=%JAVA_OPTS% -Djboss.modules.system.pkgs=com.sun.java.swing
-
-"%JAVA%" %JAVA_OPTS% ^
-    -jar "%JBOSS_HOME%\jboss-modules.jar" ^
-    -mp "%JBOSS_HOME%\modules" ^
-     org.jboss.as.cli ^
-     %*
-
-:END
-if "x%NOPAUSE%" == "x" pause

jboss-as-7.2.0.Final/bin/jboss-cli.sh

@@ -1,73 +0,0 @@
-#!/bin/sh
-
-DIRNAME=`dirname "$0"`
-
-# OS specific support (must be 'true' or 'false').
-cygwin=false;
-darwin=false;
-linux=false;
-case "`uname`" in
-    CYGWIN*)
-        cygwin=true
-        ;;
-
-    Darwin*)
-        darwin=true
-        ;;
-
-    Linux)
-        linux=true
-        ;;
-esac
-
-# For Cygwin, ensure paths are in UNIX format before anything is touched
-if $cygwin ; then
-    [ -n "$JBOSS_HOME" ] &&
-        JBOSS_HOME=`cygpath --unix "$JBOSS_HOME"`
-    [ -n "$JAVA_HOME" ] &&
-        JAVA_HOME=`cygpath --unix "$JAVA_HOME"`
-    [ -n "$JAVAC_JAR" ] &&
-        JAVAC_JAR=`cygpath --unix "$JAVAC_JAR"`
-fi
-
-# Setup JBOSS_HOME
-RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
-if [ "x$JBOSS_HOME" = "x" ]; then
-    # get the full path (without any relative bits)
-    JBOSS_HOME=$RESOLVED_JBOSS_HOME
-else
- SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME"; pwd`
- if [ "$RESOLVED_JBOSS_HOME" != "$SANITIZED_JBOSS_HOME" ]; then
-   echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
-   echo ""
- fi
-fi
-export JBOSS_HOME
-
-# Setup the JVM
-if [ "x$JAVA" = "x" ]; then
-    if [ "x$JAVA_HOME" != "x" ]; then
-        JAVA="$JAVA_HOME/bin/java"
-    else
-        JAVA="java"
-    fi
-fi
-
-# For Cygwin, switch paths to Windows format before running java
-if $cygwin; then
-    JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
-    JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
-fi
-
-if $darwin ; then
-    # Add the apple gui packages for the gui client
-    JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=com.apple.laf,com.apple.laf.resources"
-else
-    # Add base package for L&F
-    JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=com.sun.java.swing"
-fi
-
-# Sample JPDA settings for remote socket debugging
-#JAVA_OPTS="$JAVA_OPTS -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n"
-
-eval \"$JAVA\" $JAVA_OPTS \"-Dlogging.configuration=file:$JBOSS_HOME/bin/jboss-cli-logging.properties\" -jar \"$JBOSS_HOME/jboss-modules.jar\" -mp \"$JBOSS_HOME/modules\" org.jboss.as.cli '"$@"'

jboss-as-7.2.0.Final/bin/jboss-cli.xml

@@ -1,30 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-
-<!--
-   JBoss AS7 Command-line Interface configuration.
--->
-<jboss-cli xmlns="urn:jboss:cli:1.1">
-
-    <!-- The default controller to connect to when 'connect' command is executed w/o arguments -->
-    <default-controller>
-        <host>localhost</host>
-        <port>9999</port>
-    </default-controller>
-    
-    <validate-operation-requests>true</validate-operation-requests>
-    
-    <!-- whether to resolve system properties specified as command argument or operation parameter values
-         in the CLI VM before sending the operation requests to the controller -->
-    <resolve-parameter-values>false</resolve-parameter-values>
-    
-    <!-- Command and operation history log configuration -->
-    <history>
-        <enabled>true</enabled>
-        <file-name>.jboss-cli-history</file-name>
-        <file-dir>${user.home}</file-dir>
-        <max-size>500</max-size>
-    </history>
-    
-    <!-- Whether to write info and error messages to the terminal output -->
-    <silent>false</silent>
-</jboss-cli>

jboss-as-7.2.0.Final/bin/jconsole.bat

@@ -1,108 +0,0 @@
-@echo off
-rem -------------------------------------------------------------------------
-rem jconsole script for Windows
-rem -------------------------------------------------------------------------
-rem
-rem A script for running jconsole with the remoting-jmx libraries on the classpath.
-
-rem $Id$
-
-@if not "%ECHO%" == ""  echo %ECHO%
-@if "%OS%" == "Windows_NT" setlocal
-
-if "%OS%" == "Windows_NT" (
-  set "DIRNAME=%~dp0%"
-) else (
-  set DIRNAME=.\
-)
-
-pushd %DIRNAME%..
-set "RESOLVED_JBOSS_HOME=%CD%"
-popd
-
-if "x%JBOSS_HOME%" == "x" (
-  set "JBOSS_HOME=%RESOLVED_JBOSS_HOME%"
-)
-
-pushd "%JBOSS_HOME%"
-set "SANITIZED_JBOSS_HOME=%CD%"
-popd
-
-if "%RESOLVED_JBOSS_HOME%" NEQ "%SANITIZED_JBOSS_HOME%" (
-    echo WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur.
-)
-
-set DIRNAME=
-
-if "%OS%" == "Windows_NT" (
-  set "PROGNAME=%~nx0%"
-) else (
-  set "PROGNAME=jdr.bat"
-)
-
-rem Setup JBoss specific properties
-if "x%JAVA_HOME%" == "x" (
-  echo JAVA_HOME is not set. Unable to locate the jars needed to run jconsole.
-  goto END
-)
-
-rem Find jboss-modules.jar, or we can't continue
-if exist "%JBOSS_HOME%\jboss-modules.jar" (
-    set "RUNJAR=%JBOSS_HOME%\jboss-modules.jar"
-) else (
-  echo Could not locate "%JBOSS_HOME%\jboss-modules.jar".
-  echo Please check that you are in the bin directory when running this script.
-  goto END
-)
-
-rem Set default module root paths
-if "x%JBOSS_MODULEPATH%" == "x" (
-  set  "JBOSS_MODULEPATH=%JBOSS_HOME%\modules"
-)
-
-rem Setup The Classpath
-
-set CLASSPATH=%JAVA_HOME%\lib\jconsole.jar
-set CLASSPATH=%CLASSPATH%;%JAVA_HOME%\lib\tools.jar
-
-call :SearchForJars "%JBOSS_MODULEPATH%\system\layers\base\org\jboss\remoting-jmx\main"
-call :SearchForJars "%JBOSS_MODULEPATH%\system\layers\base\org\jboss\remoting3\main"
-call :SearchForJars "%JBOSS_MODULEPATH%\system\layers\base\org\jboss\logging\main"
-call :SearchForJars "%JBOSS_MODULEPATH%\system\layers\base\org\jboss\xnio\main"
-call :SearchForJars "%JBOSS_MODULEPATH%\system\layers\base\org\jboss\xnio\nio\main"
-call :SearchForJars "%JBOSS_MODULEPATH%\system\layers\base\org\jboss\sasl\main"
-call :SearchForJars "%JBOSS_MODULEPATH%\system\layers\base\org\jboss\marshalling\main"
-call :SearchForJars "%JBOSS_MODULEPATH%\system\layers\base\org\jboss\marshalling\river\main"
-call :SearchForJars "%JBOSS_MODULEPATH%\system\layers\base\org\jboss\as\cli\main"
-call :SearchForJars "%JBOSS_MODULEPATH%\system\layers\base\org\jboss\staxmapper\main"
-call :SearchForJars "%JBOSS_MODULEPATH%\system\layers\base\org\jboss\as\protocol\main"
-call :SearchForJars "%JBOSS_MODULEPATH%\system\layers\base\org\jboss\dmr\main"
-call :SearchForJars "%JBOSS_MODULEPATH%\system\layers\base\org\jboss\as\controller-client\main"
-call :SearchForJars "%JBOSS_MODULEPATH%\system\layers\base\org\jboss\threads\main"
-
-rem echo %CLASSPATH%
-
-"%JAVA_HOME%\bin\jconsole.exe" -J"-Djava.class.path=%CLASSPATH%"
-
-:END
-goto :EOF
-
-:SearchForJars
-set NEXT_MODULE_DIR=%1
-call :DeQuote NEXT_MODULE_DIR
-pushd %NEXT_MODULE_DIR%
-for %%j in (*.jar) do call :ClasspathAdd "%NEXT_MODULE_DIR%\%%j"
-popd
-goto :EOF
-
-:ClasspathAdd
-set NEXT_JAR=%1
-call :DeQuote NEXT_JAR
-set CLASSPATH=%CLASSPATH%;%NEXT_JAR%
-goto :EOF
-
-:DeQuote
-for /f "delims=" %%A in ('echo %%%1%%') do set %1=%%~A
-goto :EOF
-
-:EOF

jboss-as-7.2.0.Final/bin/jconsole.sh

@@ -1,90 +0,0 @@
-#!/bin/sh
-
-DIRNAME=`dirname "$0"`
-GREP="grep"
-
-# Use the maximum available, or set MAX_FD != -1 to use that
-MAX_FD="maximum"
-
-# OS specific support (must be 'true' or 'false').
-cygwin=false;
-darwin=false;
-linux=false;
-case "`uname`" in
-    CYGWIN*)
-        cygwin=true
-        ;;
-
-    Darwin*)
-        darwin=true
-        ;;
-
-    Linux)
-        linux=true
-        ;;
-esac
-
-# For Cygwin, ensure paths are in UNIX format before anything is touched
-if $cygwin ; then
-    [ -n "$JBOSS_HOME" ] &&
-        JBOSS_HOME=`cygpath --unix "$JBOSS_HOME"`
-    [ -n "$JAVA_HOME" ] &&
-        JAVA_HOME=`cygpath --unix "$JAVA_HOME"`
-    [ -n "$JAVAC_JAR" ] &&
-        JAVAC_JAR=`cygpath --unix "$JAVAC_JAR"`
-fi
-
-# Setup JBOSS_HOME
-RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
-if [ "x$JBOSS_HOME" = "x" ]; then
-    # get the full path (without any relative bits)
-    JBOSS_HOME=$RESOLVED_JBOSS_HOME
-else
- SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME"; pwd`
- if [ "$RESOLVED_JBOSS_HOME" != "$SANITIZED_JBOSS_HOME" ]; then
-   echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
-   echo ""
- fi
-fi
-export JBOSS_HOME
-
-# Setup the JVM
-if [ "x$JAVA" = "x" ]; then
-    if [ "x$JAVA_HOME" != "x" ]; then
-        JAVA="$JAVA_HOME/bin/java"
-    else
-        echo "JAVA_HOME is not set. Unable to locate the jars needed to run jconsole."
-        exit 2
-    fi
-fi
-
-if [ "x$JBOSS_MODULEPATH" = "x" ]; then
-    JBOSS_MODULEPATH="$JBOSS_HOME/modules"
-fi
-
-# For Cygwin, switch paths to Windows format before running java
-if $cygwin; then
-    JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
-    JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
-    JBOSS_CLASSPATH=`cygpath --path --windows "$JBOSS_CLASSPATH"`
-    JBOSS_ENDORSED_DIRS=`cygpath --path --windows "$JBOSS_ENDORSED_DIRS"`
-    JBOSS_MODULEPATH=`cygpath --path --windows "$JBOSS_MODULEPATH"`
-fi
-
-CLASSPATH=$JAVA_HOME/lib/jconsole.jar
-CLASSPATH=$CLASSPATH:$JAVA_HOME/lib/tools.jar
-
-MODULES="org/jboss/remoting-jmx org/jboss/remoting3 org/jboss/logging org/jboss/xnio org/jboss/xnio/nio org/jboss/sasl org/jboss/marshalling org/jboss/marshalling/river org/jboss/as/cli org/jboss/staxmapper org/jboss/as/protocol org/jboss/dmr org/jboss/as/controller-client org/jboss/threads"
-
-for MODULE in $MODULES
-do
-    for JAR in `cd "$JBOSS_MODULEPATH/system/layers/base/$MODULE/main/" && ls -1 *.jar`
-    do
-        CLASSPATH="$CLASSPATH:$JBOSS_MODULEPATH/system/layers/base/$MODULE/main/$JAR"
-    done
-done
-
-
-echo CLASSPATH $CLASSPATH
-
-jconsole -J-Djava.class.path="$CLASSPATH"

jboss-as-7.2.0.Final/bin/jdr.bat

@@ -1,79 +0,0 @@
-@echo off
-rem -------------------------------------------------------------------------
-rem JBoss Diagnostic Report (JDR) Script for Windows
-rem -------------------------------------------------------------------------
-rem
-rem This script creates a JDR report containing useful information for
-rem diagnosing problems with the application server.  The report consists 
-rem of a zip file containing log files, configuration, a list of all files
-rem in the distribution and, if available, runtime metrics.
-
-rem $Id$
-
-@if not "%ECHO%" == ""  echo %ECHO%
-@if "%OS%" == "Windows_NT" setlocal
-
-if "%OS%" == "Windows_NT" (
-  set "DIRNAME=%~dp0%"
-) else (
-  set DIRNAME=.\
-)
-
-pushd %DIRNAME%..
-set "RESOLVED_JBOSS_HOME=%CD%"
-popd
-
-if "x%JBOSS_HOME%" == "x" (
-  set "JBOSS_HOME=%RESOLVED_JBOSS_HOME%" 
-)
-
-pushd "%JBOSS_HOME%"
-set "SANITIZED_JBOSS_HOME=%CD%"
-popd
-
-if "%RESOLVED_JBOSS_HOME%" NEQ "%SANITIZED_JBOSS_HOME%" (
-    echo WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur.
-)
-
-set DIRNAME=
-
-if "%OS%" == "Windows_NT" (
-  set "PROGNAME=%~nx0%"
-) else (
-  set "PROGNAME=jdr.bat"
-)
-
-rem Setup JBoss specific properties
-if "x%JAVA_HOME%" == "x" (
-  set  JAVA=java
-  echo JAVA_HOME is not set. Unexpected results may occur.
-  echo Set JAVA_HOME to the directory of your local JDK to avoid this message.
-) else (
-  set "JAVA=%JAVA_HOME%\bin\java"
-)
-
-rem Find jboss-modules.jar, or we can't continue
-if exist "%JBOSS_HOME%\jboss-modules.jar" (
-    set "RUNJAR=%JBOSS_HOME%\jboss-modules.jar"
-) else (
-  echo Could not locate "%JBOSS_HOME%\jboss-modules.jar".
-  echo Please check that you are in the bin directory when running this script.
-  goto END
-)
-
-rem Setup JBoss specific properties
-
-rem Setup the java endorsed dirs
-set JBOSS_ENDORSED_DIRS=%JBOSS_HOME%\lib\endorsed
-
-rem Set default module root paths
-if "x%JBOSS_MODULEPATH%" == "x" (
-  set  "JBOSS_MODULEPATH=%JBOSS_HOME%\modules"
-)
-
-"%JAVA%" ^
-    -Djboss.home.dir="%JBOSS_HOME%" ^
-    -jar "%JBOSS_HOME%\jboss-modules.jar" ^
-    -mp "%JBOSS_MODULEPATH%" ^
-     org.jboss.as.jdr ^
-     %*

jboss-as-7.2.0.Final/bin/jdr.sh

@@ -1,70 +0,0 @@
-#!/bin/sh
-
-# JBoss Diagnostic Reporter (JDR)
-#
-# This script creates a JDR report containing useful information for
-# diagnosing problems with the application server.  The report consists 
-# of a zip file containing log files, configuration, a list of all files
-# in the distribution and, if available, runtime metrics.
-#
-
-DIRNAME=`dirname "$0"`
-
-# OS specific support (must be 'true' or 'false').
-cygwin=false;
-if  [ `uname|grep -i CYGWIN` ]; then
-    cygwin = true;
-fi
-
-# For Cygwin, ensure paths are in UNIX format before anything is touched
-if $cygwin ; then
-    [ -n "$JBOSS_HOME" ] &&
-        JBOSS_HOME=`cygpath --unix "$JBOSS_HOME"`
-    [ -n "$JAVA_HOME" ] &&
-        JAVA_HOME=`cygpath --unix "$JAVA_HOME"`
-    [ -n "$JAVAC_JAR" ] &&
-        JAVAC_JAR=`cygpath --unix "$JAVAC_JAR"`
-fi
-
-# Setup JBOSS_HOME
-RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
-if [ "x$JBOSS_HOME" = "x" ]; then
-    # get the full path (without any relative bits)
-    JBOSS_HOME=$RESOLVED_JBOSS_HOME
-else
- SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME"; pwd`
- if [ "$RESOLVED_JBOSS_HOME" != "$SANITIZED_JBOSS_HOME" ]; then
-   echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
-   echo ""
- fi
-fi
-export JBOSS_HOME
-
-# Setup the JVM
-if [ "x$JAVA" = "x" ]; then
-    if [ "x$JAVA_HOME" != "x" ]; then
-        JAVA="$JAVA_HOME/bin/java"
-    else
-        JAVA="java"
-    fi
-fi
-
-if [ "x$JBOSS_MODULEPATH" = "x" ]; then
-    JBOSS_MODULEPATH="$JBOSS_HOME/modules"
-fi
-
-# For Cygwin, switch paths to Windows format before running java
-if $cygwin; then
-    JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
-    JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
-    JBOSS_CLASSPATH=`cygpath --path --windows "$JBOSS_CLASSPATH"`
-    JBOSS_ENDORSED_DIRS=`cygpath --path --windows "$JBOSS_ENDORSED_DIRS"`
-    JBOSS_MODULEPATH=`cygpath --path --windows "$JBOSS_MODULEPATH"`
-fi
-
-eval \"$JAVA\" $JAVA_OPTS \
-         -Djboss.home.dir=\"$JBOSS_HOME\" \
-         -jar \"$JBOSS_HOME/jboss-modules.jar\" \
-         -mp \"${JBOSS_MODULEPATH}\" \
-         org.jboss.as.jdr \
-         "$@" 

jboss-as-7.2.0.Final/bin/run.bat

@@ -1,9 +0,0 @@
-@ECHO OFF
-REM Placeholder for people used to run.bat from older version redirecting them to read the readme
-echo.
-echo =======================================================================================
-echo.
-echo To start JBoss Application Server please see %CD%\..\README.txt
-echo.
-echo ========================================================================================
-echo.

jboss-as-7.2.0.Final/bin/run.sh

@@ -1,10 +0,0 @@
-#!/bin/sh
-# Placeholder for people used to run.sh from older version redirecting them to read the readme
-DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
-echo 
-echo ========================================================================================
-echo 
-echo To start JBoss Application Server please see $DIR/../README.txt
-echo 
-echo ========================================================================================
-echo

jboss-as-7.2.0.Final/bin/standalone.bat

@@ -1,212 +0,0 @@
-@echo off
-rem -------------------------------------------------------------------------
-rem JBoss Bootstrap Script for Windows
-rem -------------------------------------------------------------------------
-
-rem Use --debug to activate debug mode with an optional argument to specify the port
-rem Usage : standalone.bat --debug
-rem         standalone.bat --debug 9797
-
-rem By default debug mode is disable.
-set DEBUG_MODE=false
-set DEBUG_PORT=8787
-rem Set to all parameters by default
-set SERVER_OPTS=%*
-
-rem Get the program name before using shift as the command modify the variable ~nx0
-if "%OS%" == "Windows_NT" (
-  set "PROGNAME=%~nx0%"
-) else (
-  set "PROGNAME=standalone.bat"
-)
-
-@if not "%ECHO%" == ""  echo %ECHO%
-@if "%OS%" == "Windows_NT" setlocal
-
-if "%OS%" == "Windows_NT" (
-  set "DIRNAME=%~dp0%"
-) else (
-  set DIRNAME=.\
-)
-
-rem Read command-line args.
-:READ-ARGS
-if "%1" == "" ( 
-   goto MAIN
-) else if "%1" == "--debug" (
-   goto READ-DEBUG-PORT
-) else (
-   rem This doesn't work as Windows splits on = and spaces by default
-   rem set SERVER_OPTS=%SERVER_OPTS% %1
-   shift
-   goto READ-ARGS
-)
-
-:READ-DEBUG-PORT
-set "DEBUG_MODE=true"
-set DEBUG_ARG="%2"
-if not "x%DEBUG_ARG" == "x" (
-   if x%DEBUG_ARG:-=%==x%DEBUG_ARG% (
-      shift
-      set DEBUG_PORT=%DEBUG_ARG%
-   )
-   shift
-   goto READ-ARGS
-)
-
-:MAIN
-rem $Id$
-)
-
-pushd %DIRNAME%..
-set "RESOLVED_JBOSS_HOME=%CD%"
-popd
-
-if "x%JBOSS_HOME%" == "x" (
-  set "JBOSS_HOME=%RESOLVED_JBOSS_HOME%"
-)
-
-pushd "%JBOSS_HOME%"
-set "SANITIZED_JBOSS_HOME=%CD%"
-popd
-
-if /i "%RESOLVED_JBOSS_HOME%" NEQ "%SANITIZED_JBOSS_HOME%" (
-   echo.
-   echo   WARNING:  JBOSS_HOME may be pointing to a different installation - unpredictable results may occur.
-   echo.
-   echo             JBOSS_HOME: %JBOSS_HOME%
-   echo.
-   rem 2 seconds pause
-   ping 127.0.0.1 -n 3 > nul
-)
-
-rem Read an optional configuration file.
-if "x%STANDALONE_CONF%" == "x" (
-   set "STANDALONE_CONF=%DIRNAME%standalone.conf.bat"
-)
-if exist "%STANDALONE_CONF%" (
-   echo Calling "%STANDALONE_CONF%"
-   call "%STANDALONE_CONF%" %*
-) else (
-   echo Config file not found "%STANDALONE_CONF%"
-)
-
-
-rem Set debug settings if not already set
-if "%DEBUG_MODE%" == "true" (
-   echo "%JAVA_OPTS%" | findstr /I "\-agentlib:jdwp" > nul
-  if errorlevel == 1 (
-     echo Debug already enabled in JAVA_OPTS, ignoring --debug argument
-  ) else (
-     set "JAVA_OPTS=%JAVA_OPTS% -agentlib:jdwp=transport=dt_socket,address=%DEBUG_PORT%,server=y,suspend=n"
-  )
-)
-
-set DIRNAME=
-
-rem Setup JBoss specific properties
-set JAVA_OPTS=-Dprogram.name=%PROGNAME% %JAVA_OPTS%
-
-if "x%JAVA_HOME%" == "x" (
-  set  JAVA=java
-  echo JAVA_HOME is not set. Unexpected results may occur.
-  echo Set JAVA_HOME to the directory of your local JDK to avoid this message.
-) else (
-  set "JAVA=%JAVA_HOME%\bin\java"
-)
-
-if not "%PRESERVE_JAVA_OPTS%" == "true" (
-  rem Add -client to the JVM options, if supported (32 bit VM), and not overriden
-  echo "%JAVA_OPTS%" | findstr /I \-server > nul
-  if errorlevel == 1 (
-    "%JAVA%" -client -version 2>&1 | findstr /I /C:"Client VM" > nul
-    if not errorlevel == 1 (
-      set "JAVA_OPTS=-client %JAVA_OPTS%"
-    )
-  )
-)
-
-if not "%PRESERVE_JAVA_OPTS%" == "true" (
-  rem Add compressed oops, if supported (64 bit VM), and not overriden
-  echo "%JAVA_OPTS%" | findstr /I "\-XX:\-UseCompressedOops \-client" > nul
-  if errorlevel == 1 (
-    "%JAVA%" -XX:+UseCompressedOops -version > nul 2>&1
-    if not errorlevel == 1 (
-      set "JAVA_OPTS=-XX:+UseCompressedOops %JAVA_OPTS%"
-    )
-  )
-)
-
-if not "%PRESERVE_JAVA_OPTS%" == "true" (
-  rem Add tiered compilation, if supported (64 bit VM), and not overriden
-  echo "%JAVA_OPTS%" | findstr /I "\-XX:\-TieredCompilation \-client" > nul
-  if errorlevel == 1 (
-    "%JAVA%" -XX:+TieredCompilation -version > nul 2>&1
-    if not errorlevel == 1 (
-      set "JAVA_OPTS=-XX:+TieredCompilation %JAVA_OPTS%"
-    )
-  )
-)
-
-rem Find jboss-modules.jar, or we can't continue
-if exist "%JBOSS_HOME%\jboss-modules.jar" (
-    set "RUNJAR=%JBOSS_HOME%\jboss-modules.jar"
-) else (
-  echo Could not locate "%JBOSS_HOME%\jboss-modules.jar".
-  echo Please check that you are in the bin directory when running this script.
-  goto END
-)
-
-rem Setup JBoss specific properties
-
-rem Setup the java endorsed dirs
-set JBOSS_ENDORSED_DIRS=%JBOSS_HOME%\lib\endorsed
-
-rem Set default module root paths
-if "x%JBOSS_MODULEPATH%" == "x" (
-  set  "JBOSS_MODULEPATH=%JBOSS_HOME%\modules"
-)
-
-rem Set the standalone base dir
-if "x%JBOSS_BASE_DIR%" == "x" (
-  set  "JBOSS_BASE_DIR=%JBOSS_HOME%\standalone"
-)
-rem Set the standalone log dir
-if "x%JBOSS_LOG_DIR%" == "x" (
-  set  "JBOSS_LOG_DIR=%JBOSS_BASE_DIR%\log"
-)
-rem Set the standalone configuration dir
-if "x%JBOSS_CONFIG_DIR%" == "x" (
-  set  "JBOSS_CONFIG_DIR=%JBOSS_BASE_DIR%/configuration"
-)
-
-echo ===============================================================================
-echo.
-echo   JBoss Bootstrap Environment
-echo.
-echo   JBOSS_HOME: %JBOSS_HOME%
-echo.
-echo   JAVA: %JAVA%
-echo.
-echo   JAVA_OPTS: %JAVA_OPTS%
-echo.
-echo ===============================================================================
-echo.
-
-:RESTART
-"%JAVA%" %JAVA_OPTS% ^
- "-Dorg.jboss.boot.log.file=%JBOSS_LOG_DIR%\server.log" ^
- "-Dlogging.configuration=file:%JBOSS_CONFIG_DIR%/logging.properties" ^
-    -jar "%JBOSS_HOME%\jboss-modules.jar" ^
-    -mp "%JBOSS_MODULEPATH%" ^
-    -jaxpmodule "javax.xml.jaxp-provider" ^
-     org.jboss.as.standalone ^
-    -Djboss.home.dir="%JBOSS_HOME%" ^
-     %SERVER_OPTS%
-
-if ERRORLEVEL 10 goto RESTART
-
-:END
-if "x%NOPAUSE%" == "x" pause
-
-:END_NO_PAUSE

jboss-as-7.2.0.Final/bin/standalone.conf

@@ -1,67 +0,0 @@
-## -*- shell-script -*- ######################################################
-##                                                                          ##
-##  JBoss Bootstrap Script Configuration                                    ##
-##                                                                          ##
-##############################################################################
-
-#
-# This file is optional; it may be removed if not needed.
-#
-
-#
-# Specify the maximum file descriptor limit, use "max" or "maximum" to use
-# the default, as queried by the system.
-#
-# Defaults to "maximum"
-#
-#MAX_FD="maximum"
-
-#
-# Specify the profiler configuration file to load.
-#
-# Default is to not load profiler configuration file.
-#
-#PROFILER=""
-
-#
-# Specify the location of the Java home directory.  If set then $JAVA will
-# be defined to $JAVA_HOME/bin/java, else $JAVA will be "java".
-#
-#JAVA_HOME="/opt/java/jdk"
-
-#
-# Specify the exact Java VM executable to use.
-#
-#JAVA=""
-
-if [ "x$JBOSS_MODULES_SYSTEM_PKGS" = "x" ]; then
-   JBOSS_MODULES_SYSTEM_PKGS="org.jboss.byteman"
-fi
-
-# Uncomment the following line to prevent manipulation of JVM options
-# by shell scripts.
-#
-#PRESERVE_JAVA_OPTS=true
-
-#
-# Specify options to pass to the Java VM.
-#
-if [ "x$JAVA_OPTS" = "x" ]; then
-   JAVA_OPTS="-Xms1024m -Xmx2560m -XX:MaxPermSize=2048m -Djava.net.preferIPv4Stack=true"
-   JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
-else
-   echo "JAVA_OPTS already set in environment; overriding default settings with values: $JAVA_OPTS"
-fi
-
-# Sample JPDA settings for remote socket debugging
-#JAVA_OPTS="$JAVA_OPTS -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n"
-
-# Sample JPDA settings for shared memory debugging
-#JAVA_OPTS="$JAVA_OPTS -agentlib:jdwp=transport=dt_shmem,server=y,suspend=n,address=jboss"
-
-# Uncomment to not use JBoss Modules lockless mode
-#JAVA_OPTS="$JAVA_OPTS -Djboss.modules.lockless=false"
-
-# Uncomment to gather JBoss Modules metrics
-#JAVA_OPTS="$JAVA_OPTS -Djboss.modules.metrics=true"
-

jboss-as-7.2.0.Final/bin/standalone.conf.bat

@@ -1,67 +0,0 @@
-rem ### -*- batch file -*- ######################################################
-rem #                                                                          ##
-rem #  JBoss Bootstrap Script Configuration                                    ##
-rem #                                                                          ##
-rem #############################################################################
-
-rem # $Id: run.conf.bat 88820 2009-05-13 15:25:44Z dimitris@jboss.org $
-
-rem #
-rem # This batch file is executed by run.bat to initialize the environment
-rem # variables that run.bat uses. It is recommended to use this file to
-rem # configure these variables, rather than modifying run.bat itself.
-rem #
-
-rem Uncomment the following line to disable manipulation of JAVA_OPTS (JVM parameters)
-rem set PRESERVE_JAVA_OPTS=true
-
-if not "x%JAVA_OPTS%" == "x" (
-  echo "JAVA_OPTS already set in environment; overriding default settings with values: %JAVA_OPTS%"
-  goto JAVA_OPTS_SET
-)
-
-rem #
-rem # Specify the JBoss Profiler configuration file to load.
-rem #
-rem # Default is to not load a JBoss Profiler configuration file.
-rem #
-rem set "PROFILER=%JBOSS_HOME%\bin\jboss-profiler.properties"
-
-rem #
-rem # Specify the location of the Java home directory (it is recommended that
-rem # this always be set). If set, then "%JAVA_HOME%\bin\java" will be used as
-rem # the Java VM executable; otherwise, "%JAVA%" will be used (see below).
-rem #
-rem set "JAVA_HOME=C:\opt\jdk1.6.0_23"
-
-rem #
-rem # Specify the exact Java VM executable to use - only used if JAVA_HOME is
-rem # not set. Default is "java".
-rem #
-rem set "JAVA=C:\opt\jdk1.6.0_23\bin\java"
-
-rem #
-rem # Specify options to pass to the Java VM. Note, there are some additional
-rem # options that are always passed by run.bat.
-rem #
-
-rem # JVM memory allocation pool parameters - modify as appropriate.
-set "JAVA_OPTS=-Xms512M -Xmx1088M -XX:MaxPermSize=512M"
-
-rem # Prefer IPv4
-set "JAVA_OPTS=%JAVA_OPTS% -Djava.net.preferIPv4Stack=true"
-
-rem # Make Byteman classes visible in all module loaders
-rem # This is necessary to inject Byteman rules into AS7 deployments
-set "JAVA_OPTS=%JAVA_OPTS% -Djboss.modules.system.pkgs=org.jboss.byteman"
-
-rem # Sample JPDA settings for remote socket debugging
-rem set "JAVA_OPTS=%JAVA_OPTS% -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n"
-
-rem # Sample JPDA settings for shared memory debugging
-rem set "JAVA_OPTS=%JAVA_OPTS% -agentlib:jdwp=transport=dt_shmem,address=jboss,server=y,suspend=n"
-
-rem # Use JBoss Modules lockless mode
-rem set "JAVA_OPTS=%JAVA_OPTS% -Djboss.modules.lockless=true"
-
-:JAVA_OPTS_SET

jboss-as-7.2.0.Final/bin/vault.bat

@@ -1,54 +0,0 @@
-@echo off
-SETLOCAL
-
-rem Author: Gregory Charles, JBoss Community Member
-rem Date: January 24, 2012
-
-set DIRNAME="%~dp0"
-call :DeQuote DIRNAME
-set PROGNAME=%0
-
-rem Setup JBOSS_HOME
-set JBOSS_HOME=%DIRNAME%\..
-
-rem Setup the JVM
-IF NOT DEFINED JAVA (
-    IF DEFINED JAVA_HOME (
-        set JAVA="%JAVA_HOME%\bin\java"
-    ) ELSE (
-        set JAVA=java
-    )
-
-)
-
-IF NOT DEFINED MODULEPATH (
-    set MODULEPATH="%JBOSS_HOME%\modules"
-	call :DeQuote MODULEPATH
-)
-
-
-
-rem Display our environment
-echo =========================================================================
-echo.
-echo   JBoss Vault
-echo.
-echo   JBOSS_HOME: %JBOSS_HOME%
-echo.
-echo   JAVA: %JAVA%
-echo.
-echo =========================================================================
-echo.
-
-%JAVA% -jar %JBOSS_HOME%\jboss-modules.jar -mp %MODULEPATH% org.jboss.as.vault-tool %*
-
-ENDLOCAL
-
-:END
-goto :EOF
-
-:DeQuote
-for /f "delims=" %%A in ('echo %%%1%%') do set %1=%%~A
-goto :EOF
-
-:EOF

jboss-as-7.2.0.Final/bin/vault.sh

@@ -1,112 +0,0 @@
-#!/bin/sh
-
-DIRNAME=`dirname "$0"`
-PROGNAME=`basename "$0"`
-GREP="grep"
-
-# Use the maximum available, or set MAX_FD != -1 to use that
-MAX_FD="maximum"
-
-#
-# Helper to complain.
-#
-warn() {
-    echo "${PROGNAME}: $*"
-}
-
-#
-# Helper to puke.
-#
-die() {
-    warn $*
-    exit 1
-}
-
-# OS specific support (must be 'true' or 'false').
-cygwin=false;
-darwin=false;
-linux=false;
-case "`uname`" in
-    CYGWIN*)
-        cygwin=true
-        ;;
-
-    Darwin*)
-        darwin=true
-        ;;
-
-    Linux)
-        linux=true
-        ;;
-esac
-
-# For Cygwin, ensure paths are in UNIX format before anything is touched
-if $cygwin ; then
-    [ -n "$JBOSS_HOME" ] &&
-        JBOSS_HOME=`cygpath --unix "$JBOSS_HOME"`
-    [ -n "$JAVA_HOME" ] &&
-        JAVA_HOME=`cygpath --unix "$JAVA_HOME"`
-    [ -n "$JAVAC_JAR" ] &&
-        JAVAC_JAR=`cygpath --unix "$JAVAC_JAR"`
-fi
-
-# Setup JBOSS_HOME
-# Setup JBOSS_HOME
-RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
-if [ "x$JBOSS_HOME" = "x" ]; then
-    # get the full path (without any relative bits)
-    JBOSS_HOME=$RESOLVED_JBOSS_HOME
-else
- SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME/.."; pwd`
- if [ "$RESOLVED_JBOSS" != "$SANITIZED_JBOSS_HOME" ]; then
-   echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
-   echo ""
- fi
-fi
-export JBOSS_HOME
-
-# Setup the JVM
-if [ "x$JAVA" = "x" ]; then
-    if [ "x$JAVA_HOME" != "x" ]; then
-        JAVA="$JAVA_HOME/bin/java"
-    else
-        JAVA="java"
-    fi
-fi
-
-if [ "x$JBOSS_MODULEPATH" = "x" ]; then
-    JBOSS_MODULEPATH="$JBOSS_HOME/modules"
-fi
-
-###
-# Setup the JBoss Vault Tool classpath
-###
-
-
-# For Cygwin, switch paths to Windows format before running java
-if $cygwin; then
-    JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
-    JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
-    JBOSS_CLASSPATH=`cygpath --path --windows "$JBOSS_CLASSPATH"`
-    JBOSS_ENDORSED_DIRS=`cygpath --path --windows "$JBOSS_ENDORSED_DIRS"`
-    JBOSS_MODULEPATH=`cygpath --path --windows "$JBOSS_MODULEPATH"`
-fi
-
-# Display our environment
-echo "========================================================================="
-echo ""
-echo "  JBoss Vault"
-echo ""
-echo "  JBOSS_HOME: $JBOSS_HOME"
-echo ""
-echo "  JAVA: $JAVA"
-echo ""
-echo "========================================================================="
-echo ""
-
-eval \"$JAVA\" $JAVA_OPTS \
-         -jar \"$JBOSS_HOME/jboss-modules.jar\" \
-         -mp \"${JBOSS_MODULEPATH}\" \
-         org.jboss.as.vault-tool \
-         '"$@"'
-

jboss-as-7.2.0.Final/bin/wsconsume.bat

@@ -1,26 +0,0 @@
-@echo off
-
-@if not "%ECHO%" == ""  echo %ECHO%
-@if "%OS%" == "Windows_NT"  setlocal
-
-set DIRNAME=.\
-if "%OS%" == "Windows_NT" set DIRNAME=%~dp0%
-set PROGNAME=run.bat
-if "%OS%" == "Windows_NT" set PROGNAME=%~nx0%
-
-if "x%JAVA_HOME%" == "x" (
-  set  JAVA=java
-  echo JAVA_HOME is not set. Unexpected results may occur.
-  echo Set JAVA_HOME to the directory of your local JDK to avoid this message.
-) else (
-  set "JAVA=%JAVA_HOME%\bin\java"
-)
-set JBOSS_HOME=%DIRNAME%\..
-
-rem Execute the command
-"%JAVA%" %JAVA_OPTS% ^
-    -classpath "%JAVA_HOME%\lib\tools.jar;%JBOSS_HOME%\jboss-modules.jar" ^
-    org.jboss.modules.Main ^
-    -mp "%JBOSS_HOME%\modules" ^
-    org.jboss.ws.tools.wsconsume ^
-    %*

jboss-as-7.2.0.Final/bin/wsconsume.sh

@@ -1,79 +0,0 @@
-#!/bin/sh
-
-# Extract the directory and the program name
-# takes care of symlinks
-PRG="$0"
-while [ -h "$PRG" ] ; do
-  ls=`ls -ld "$PRG"`
-  link=`expr "$ls" : '.*-> \(.*\)$'`
-  if expr "$link" : '/.*' > /dev/null; then
-    PRG="$link"
-  else
-    PRG="`dirname "$PRG"`/$link"
-  fi
-done
-DIRNAME=`dirname "$PRG"`
-PROGNAME=`basename "$PRG"`
-
-# OS specific support (must be 'true' or 'false').
-cygwin=false;
-case "`uname`" in
-    CYGWIN*)
-        cygwin=true
-        ;;
-esac
-
-# For Cygwin, ensure paths are in UNIX format before anything is touched
-if $cygwin ; then
-    [ -n "$JBOSS_HOME" ] &&
-        JBOSS_HOME=`cygpath --unix "$JBOSS_HOME"`
-    [ -n "$JAVA_HOME" ] &&
-        JAVA_HOME=`cygpath --unix "$JAVA_HOME"`
-fi
-
-# Setup JBOSS_HOME
-RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
-if [ "x$JBOSS_HOME" = "x" ]; then
-    # get the full path (without any relative bits)
-    JBOSS_HOME=$RESOLVED_JBOSS_HOME
-else
- SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME"; pwd`
- if [ "$RESOLVED_JBOSS_HOME" != "$SANITIZED_JBOSS_HOME" ]; then
-   echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
-   echo ""
- fi
-fi
-export JBOSS_HOME
-
-# Setup the JVM
-if [ "x$JAVA" = "x" ]; then
-    if [ "x$JAVA_HOME" != "x" ]; then
-        JAVA="$JAVA_HOME/bin/java"
-    else
-        JAVA="java"
-    fi
-fi
-
-#JPDA options. Uncomment and modify as appropriate to enable remote debugging .
-#JAVA_OPTS="-classic -Xdebug -Xnoagent -Djava.compiler=NONE -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=y $JAVA_OPTS"
-
-# Setup JBoss sepecific properties
-JAVA_OPTS="$JAVA_OPTS"
-
-# Setup classpath
-JBOSS_CLASSPATH=$JAVA_HOME/lib/tools.jar:$JBOSS_HOME/jboss-modules.jar
-
-# For Cygwin, switch paths to Windows format before running java
-if $cygwin; then
-    JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
-    JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
-    JBOSS_CLASSPATH=`cygpath --path --windows "$JBOSS_CLASSPATH"`
-fi
-
-# Execute the command
-eval \"$JAVA\" $JAVA_OPTS \
-    -classpath \"$JBOSS_CLASSPATH\" \
-    org.jboss.modules.Main \
-    -mp \"$JBOSS_HOME/modules\" \
-    org.jboss.ws.tools.wsconsume \
-    '"$@"'

jboss-as-7.2.0.Final/bin/wsprovide.bat

@@ -1,25 +0,0 @@
-@echo off
-
-@if not "%ECHO%" == ""  echo %ECHO%
-@if "%OS%" == "Windows_NT"  setlocal
-
-set DIRNAME=.\
-if "%OS%" == "Windows_NT" set DIRNAME=%~dp0%
-set PROGNAME=run.bat
-if "%OS%" == "Windows_NT" set PROGNAME=%~nx0%
-
-if "x%JAVA_HOME%" == "x" (
-  set  JAVA=java
-  echo JAVA_HOME is not set. Unexpected results may occur.
-  echo Set JAVA_HOME to the directory of your local JDK to avoid this message.
-) else (
-  set "JAVA=%JAVA_HOME%\bin\java"
-)
-set JBOSS_HOME=%DIRNAME%\..
-
-rem Execute the command
-"%JAVA%" %JAVA_OPTS% ^
-    -jar "%JBOSS_HOME%\jboss-modules.jar" ^
-    -mp "%JBOSS_HOME%\modules" ^
-    org.jboss.ws.tools.wsprovide ^
-    %*

jboss-as-7.2.0.Final/bin/wsprovide.sh

@@ -1,74 +0,0 @@
-#!/bin/sh
-
-# Extract the directory and the program name
-# takes care of symlinks
-PRG="$0"
-while [ -h "$PRG" ] ; do
-  ls=`ls -ld "$PRG"`
-  link=`expr "$ls" : '.*-> \(.*\)$'`
-  if expr "$link" : '/.*' > /dev/null; then
-    PRG="$link"
-  else
-    PRG="`dirname "$PRG"`/$link"
-  fi
-done
-DIRNAME=`dirname "$PRG"`
-PROGNAME=`basename "$PRG"`
-
-# OS specific support (must be 'true' or 'false').
-cygwin=false;
-case "`uname`" in
-    CYGWIN*)
-        cygwin=true
-        ;;
-esac
-
-# For Cygwin, ensure paths are in UNIX format before anything is touched
-if $cygwin ; then
-    [ -n "$JBOSS_HOME" ] &&
-        JBOSS_HOME=`cygpath --unix "$JBOSS_HOME"`
-    [ -n "$JAVA_HOME" ] &&
-        JAVA_HOME=`cygpath --unix "$JAVA_HOME"`
-fi
-
-# Setup JBOSS_HOME
-RESOLVED_JBOSS_HOME=`cd "$DIRNAME/.."; pwd`
-if [ "x$JBOSS_HOME" = "x" ]; then
-    # get the full path (without any relative bits)
-    JBOSS_HOME=$RESOLVED_JBOSS_HOME
-else
- SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME"; pwd`
- if [ "$RESOLVED_JBOSS_HOME" != "$SANITIZED_JBOSS_HOME" ]; then
-   echo "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur."
-   echo ""
- fi
-fi
-export JBOSS_HOME
-
-# Setup the JVM
-if [ "x$JAVA" = "x" ]; then
-    if [ "x$JAVA_HOME" != "x" ]; then
-        JAVA="$JAVA_HOME/bin/java"
-    else
-        JAVA="java"
-    fi
-fi
-
-#JPDA options. Uncomment and modify as appropriate to enable remote debugging .
-#JAVA_OPTS="-classic -Xdebug -Xnoagent -Djava.compiler=NONE -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=y $JAVA_OPTS"
-
-# Setup JBoss sepecific properties
-JAVA_OPTS="$JAVA_OPTS"
-
-# For Cygwin, switch paths to Windows format before running java
-if $cygwin; then
-    JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
-    JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
-fi
-
-# Execute the command
-eval \"$JAVA\" $JAVA_OPTS \
-    -jar \"$JBOSS_HOME/jboss-modules.jar\" \
-    -mp \"$JBOSS_HOME/modules\" \
-    org.jboss.ws.tools.wsprovide \
-    '"$@"'

jboss-as-7.2.0.Final/copyright.txt

@@ -1,64 +0,0 @@
-Ales Justin <ales.justin@gmail.com>
-Alessio Soldano <alessio.soldano@jboss.com>
-Alexey Loubyansky <alex@jboss.org>
-Alexey Loubyansky <olubyans@tstudio.(none)>
-Andrew Dinn <adinn@redhat.com>
-Andrew Lee Rubinger <alr@jboss.org>
-Andy Taylor <ataylor@redhat.com>
-Anil Saldhana <anil.saldhana@jboss.com>
-Aslak Knutsen <aslak@redhat.com>
-Bob McWhirter <bob@mcwhirter.org>
-Brian Stansberry <brian.stansberry@jboss.com>
-Brian Stansberry <brian.stansberry@redhat.com>
-Brian Stansberry <bstansberry@jboss.com>
-Carlo de Wolf <carlo@nerdnet.nl>
-Carlo de Wolf <cdewolf@redhat.com>
-Darran Lofthouse <darran.lofthouse@jboss.com>
-David Bosschaert <david.bosschaert@gmail.com>
-David M. Lloyd <david.lloyd@redhat.com>
-David M. Lloyd <dmlloyd@flurg.com>
-Dimitris Andreadis <dandread@redhat.com>
-Dimitris Andreadis <dimitris@redhat.com>
-Emanuel Muckenhuber <emuckenh@redhat.com>
-Flavia Rainone <flavia.rainone@jboss.com>
-Heiko Braun <ike.braun@googlemail.com>
-Howard Gao <hgao@redhat.com>
-Jaikiran Pai <jaikiran.pai@gmail.com>
-James Perkins <jperkins@redhat.com>
-James Perkins <jrperkinsjr@gmail.com>
-Jason T. Greene <jason.greene@redhat.com>
-Jason T. Greene <jason@stacksmash.com>
-Jean-Frederic Clere <jfclere@gmail.com>
-Jean-Frederic Clere <jfclere@jfcpc.(none)>
-Jeff Zhang <jeff.zhang@jboss.org>
-Jesper Pedersen <jesper.pedersen@redhat.com>
-Jim Ma <ema@redhat.com>
-John Bailey <baileyje@gmail.com>
-John E. Bailey <baileyje@gmail.com>
-John E. Bailey <jbailey@redhat.com>
-Jonathan Pearlin <jdp.grails.dev@gmail.com>
-Kabir Khan <kkhan@redhat.com>
-Marcus Moyses <marcus.moyses@gmail.com>
-Marcus Moyses <mmoyses@redhat.com>
-Marius Bogoevici <marius.bogoevici@gmail.com>
-Max Rydahl Andersen <max@jboss.org>
-Paul Ferraro <paul.ferraro@redhat.com>
-Paul Gier <pgier@redhat.com>
-Pete Muir <pmuir@bleepbleep.org.uk>
-Richard Opalka <ropalka@redhat.com>
-Rémy Maucherat <remm@ws.remm.hd.free.fr>
-Rémy Maucherat <rmaucher@redhat.com>
-Scott M Stark <scott.stark@jboss.org>
-Scott Marlow <smarlow@redhat.com>
-Shelly McGowan <smcgowan@redhat.com>
-Stan Silvert <ssilvert@jboss.com>
-Stan Silvert <ssilvert@redhat.com>
-Stefan Guilhen <sguilhen@redhat.com>
-Stefano Maestri <stefano.maestri@javalinux.it>
-Steve Ebersole <steve@hibernate.org>
-Stuart Douglas <stuart.w.douglas@gmail.com>
-Stuart Douglas <stuart@stuart-thinkpad.localdomain>
-Thomas Diesler <thomas.diesler@jboss.com>
-Tomaz Cerar <tomaz.cerar@gmail.com>
-Vladimir Dosoudil <dosoudil@redhat.com>
-Weston Price <wmprice@redhat.com>

jboss-as-7.2.0.Final/docs/examples/configs/standalone-hornetq-colocated.xml

@@ -1,461 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-
-<server xmlns="urn:jboss:domain:1.4">
-    <extensions>
-        <extension module="org.jboss.as.clustering.infinispan"/>
-        <extension module="org.jboss.as.configadmin"/>
-        <extension module="org.jboss.as.connector"/>
-        <extension module="org.jboss.as.deployment-scanner"/>
-        <extension module="org.jboss.as.ee"/>
-        <extension module="org.jboss.as.ejb3"/>
-        <extension module="org.jboss.as.jacorb"/>
-        <extension module="org.jboss.as.jaxrs"/>
-        <extension module="org.jboss.as.jmx"/>
-        <extension module="org.jboss.as.jpa"/>
-        <extension module="org.jboss.as.jsf"/>
-        <extension module="org.jboss.as.logging"/>
-        <extension module="org.jboss.as.mail"/>
-        <extension module="org.jboss.as.messaging"/>
-        <extension module="org.jboss.as.naming"/>
-        <extension module="org.jboss.as.remoting"/>
-        <extension module="org.jboss.as.sar"/>
-        <extension module="org.jboss.as.security"/>
-        <extension module="org.jboss.as.threads"/>
-        <extension module="org.jboss.as.transactions"/>
-        <extension module="org.jboss.as.web"/>
-        <extension module="org.jboss.as.webservices"/>
-        <extension module="org.jboss.as.weld"/>
-    </extensions>
-    <management>
-        <security-realms>
-            <security-realm name="ManagementRealm">
-                <authentication>
-                    <local default-user="$local"/>
-                    <properties path="mgmt-users.properties" relative-to="jboss.server.config.dir"/>
-                </authentication>
-            </security-realm>
-            <security-realm name="ApplicationRealm">
-                <authentication>
-                    <local default-user="$local" allowed-users="*"/>
-                    <properties path="application-users.properties" relative-to="jboss.server.config.dir"/>
-                </authentication>
-                <authorization>
-                    <properties path="application-roles.properties" relative-to="jboss.server.config.dir"/>
-                </authorization>
-            </security-realm>
-        </security-realms>
-        <management-interfaces>
-            <native-interface security-realm="ManagementRealm">
-                <socket-binding native="management-native"/>
-            </native-interface>
-            <http-interface security-realm="ManagementRealm">
-                <socket-binding http="management-http"/>
-            </http-interface>
-        </management-interfaces>
-    </management>
-    <profile>
-        <subsystem xmlns="urn:jboss:domain:logging:1.2">
-            <console-handler name="CONSOLE">
-                <level name="INFO"/>
-                <formatter>
-                    <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
-                </formatter>
-            </console-handler>
-            <periodic-rotating-file-handler name="FILE" autoflush="true">
-                <formatter>
-                    <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
-                </formatter>
-                <file relative-to="jboss.server.log.dir" path="server.log"/>
-                <suffix value=".yyyy-MM-dd"/>
-                <append value="true"/>
-            </periodic-rotating-file-handler>
-            <logger category="com.arjuna">
-                <level name="WARN"/>
-            </logger>
-            <logger category="org.apache.tomcat.util.modeler">
-                <level name="WARN"/>
-            </logger>
-            <logger category="org.jboss.as.config">
-                <level name="DEBUG"/>
-            </logger>
-            <logger category="sun.rmi">
-                <level name="WARN"/>
-            </logger>
-            <logger category="jacorb">
-                <level name="WARN"/>
-            </logger>
-            <logger category="jacorb.config">
-                <level name="ERROR"/>
-            </logger>
-            <root-logger>
-                <level name="INFO"/>
-                <handlers>
-                    <handler name="CONSOLE"/>
-                    <handler name="FILE"/>
-                </handlers>
-            </root-logger>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:configadmin:1.0"/>
-        <subsystem xmlns="urn:jboss:domain:datasources:1.1">
-            <datasources>
-                <datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS" enabled="true" use-java-context="true">
-                    <connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1</connection-url>
-                    <driver>h2</driver>
-                    <security>
-                        <user-name>sa</user-name>
-                        <password>sa</password>
-                    </security>
-                </datasource>
-                <drivers>
-                    <driver name="h2" module="com.h2database.h2">
-                        <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
-                    </driver>
-                </drivers>
-            </datasources>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
-            <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000"/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:ee:1.1">
-            <spec-descriptor-property-replacement>false</spec-descriptor-property-replacement>
-            <jboss-descriptor-property-replacement>true</jboss-descriptor-property-replacement>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:ejb3:1.4">
-            <session-bean>
-                <stateless>
-                    <bean-instance-pool-ref pool-name="slsb-strict-max-pool"/>
-                </stateless>
-                <stateful default-access-timeout="5000" cache-ref="simple"/>
-                <singleton default-access-timeout="5000"/>
-            </session-bean>
-            <pools>
-                <bean-instance-pools>
-                    <strict-max-pool name="slsb-strict-max-pool" max-pool-size="20" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
-                    <strict-max-pool name="mdb-strict-max-pool" max-pool-size="20" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
-                </bean-instance-pools>
-            </pools>
-            <caches>
-                <cache name="simple" aliases="NoPassivationCache"/>
-                <cache name="passivating" passivation-store-ref="file" aliases="SimpleStatefulCache"/>
-            </caches>
-            <passivation-stores>
-                <file-passivation-store name="file"/>
-            </passivation-stores>
-            <async thread-pool-name="default"/>
-            <timer-service thread-pool-name="default">
-                <data-store path="timer-service-data" relative-to="jboss.server.data.dir"/>
-            </timer-service>
-            <remote connector-ref="remoting-connector" thread-pool-name="default"/>
-            <thread-pools>
-                <thread-pool name="default">
-                    <max-threads count="10"/>
-                    <keepalive-time time="100" unit="milliseconds"/>
-                </thread-pool>
-            </thread-pools>
-            <default-security-domain value="other"/>
-            <default-missing-method-permissions-deny-access value="true"/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:infinispan:1.4">
-            <cache-container name="web" aliases="standard-session-cache" default-cache="local-web" module="org.jboss.as.clustering.web.infinispan">
-                <local-cache name="local-web" batching="true">
-                    <file-store passivation="false" purge="false"/>
-                </local-cache>
-            </cache-container>
-            <cache-container name="hibernate" default-cache="local-query" module="org.jboss.as.jpa.hibernate:4">
-                <local-cache name="entity">
-                    <transaction mode="NON_XA"/>
-                    <eviction strategy="LRU" max-entries="10000"/>
-                    <expiration max-idle="100000"/>
-                </local-cache>
-                <local-cache name="local-query">
-                    <transaction mode="NONE"/>
-                    <eviction strategy="LRU" max-entries="10000"/>
-                    <expiration max-idle="100000"/>
-                </local-cache>
-                <local-cache name="timestamps">
-                    <transaction mode="NONE"/>
-                    <eviction strategy="NONE"/>
-                </local-cache>
-            </cache-container>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:jacorb:1.3">
-            <orb socket-binding="jacorb" ssl-socket-binding="jacorb-ssl">
-                <initializers transactions="spec" security="identity"/>
-            </orb>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:jaxrs:1.0"/>
-        <subsystem xmlns="urn:jboss:domain:jca:1.1">
-            <archive-validation enabled="true" fail-on-error="true" fail-on-warn="false"/>
-            <bean-validation enabled="true"/>
-            <default-workmanager>
-                <short-running-threads>
-                    <core-threads count="50"/>
-                    <queue-length count="50"/>
-                    <max-threads count="50"/>
-                    <keepalive-time time="10" unit="seconds"/>
-                </short-running-threads>
-                <long-running-threads>
-                    <core-threads count="50"/>
-                    <queue-length count="50"/>
-                    <max-threads count="50"/>
-                    <keepalive-time time="10" unit="seconds"/>
-                </long-running-threads>
-            </default-workmanager>
-            <cached-connection-manager/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:jmx:1.2">
-            <expose-resolved-model/>
-            <expose-expression-model/>
-            <remoting-connector/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:jpa:1.1">
-            <jpa default-datasource="" default-extended-persistence-inheritance="DEEP"/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:jsf:1.0"/>
-        <subsystem xmlns="urn:jboss:domain:mail:1.0">
-            <mail-session jndi-name="java:jboss/mail/Default">
-                <smtp-server outbound-socket-binding-ref="mail-smtp"/>
-            </mail-session>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:messaging:1.3">
-            <hornetq-server>
-                <persistence-enabled>true</persistence-enabled>
-                <shared-store>true</shared-store>
-                <journal-type>ASYNCIO</journal-type>
-                <journal-file-size>102400</journal-file-size>
-                <journal-min-files>2</journal-min-files>
-                <connectors>
-                    <netty-connector name="netty" socket-binding="messaging"/>
-                    <netty-connector name="netty-throughput" socket-binding="messaging-throughput">
-                        <param key="batch-delay" value="50"/>
-                    </netty-connector>
-                    <in-vm-connector name="in-vm" server-id="0"/>
-                </connectors>
-                <acceptors>
-                    <netty-acceptor name="netty" socket-binding="messaging"/>
-                    <netty-acceptor name="netty-throughput" socket-binding="messaging-throughput">
-                        <param key="batch-delay" value="50"/>
-                        <param key="direct-deliver" value="false"/>
-                    </netty-acceptor>
-                    <in-vm-acceptor name="in-vm" server-id="0"/>
-                </acceptors>
-                <broadcast-groups>
-                    <broadcast-group name="bg-group1">
-                        <group-address>231.7.7.7</group-address>
-                        <group-port>9876</group-port>
-                        <broadcast-period>5000</broadcast-period>
-                        <connector-ref>netty</connector-ref>
-                    </broadcast-group>
-                </broadcast-groups>
-                <discovery-groups>
-                    <discovery-group name="dg-group1">
-                        <group-address>231.7.7.7</group-address>
-                        <group-port>9876</group-port>
-                        <refresh-timeout>10000</refresh-timeout>
-                    </discovery-group>
-                </discovery-groups>
-                <cluster-connections>
-                    <cluster-connection name="my-cluster">
-                        <address>jms</address>
-                        <connector-ref>netty</connector-ref>
-                        <discovery-group-ref discovery-group-name="dg-group1"/>
-                    </cluster-connection>
-                </cluster-connections>
-                <security-settings>
-                    <security-setting match="#">
-                        <permission type="send" roles="guest"/>
-                        <permission type="consume" roles="guest"/>
-                        <permission type="createNonDurableQueue" roles="guest"/>
-                        <permission type="deleteNonDurableQueue" roles="guest"/>
-                    </security-setting>
-                </security-settings>
-                <address-settings>
-                    <!--default for catch all-->
-                    <address-setting match="#">
-                        <dead-letter-address>jms.queue.DLQ</dead-letter-address>
-                        <expiry-address>jms.queue.ExpiryQueue</expiry-address>
-                        <redelivery-delay>0</redelivery-delay>
-                        <max-size-bytes>10485760</max-size-bytes>
-                        <address-full-policy>BLOCK</address-full-policy>
-                        <message-counter-history-day-limit>10</message-counter-history-day-limit>
-                    </address-setting>
-                </address-settings>
-                <!--JMS Stuff-->
-                <jms-connection-factories>
-                    <connection-factory name="InVmConnectionFactory">
-                        <connectors>
-                            <connector-ref connector-name="in-vm"/>
-                        </connectors>
-                        <entries>
-                            <entry name="java:/ConnectionFactory"/>
-                        </entries>
-                    </connection-factory>
-                    <connection-factory name="RemoteConnectionFactory">
-                        <connectors>
-                            <connector-ref connector-name="netty"/>
-                        </connectors>
-                        <entries>
-                            <entry name="java:jboss/exported/jms/RemoteConnectionFactory"/>
-                        </entries>
-                    </connection-factory>
-                    <pooled-connection-factory name="hornetq-ra">
-                        <transaction mode="xa"/>
-                        <connectors>
-                            <connector-ref connector-name="in-vm"/>
-                        </connectors>
-                        <entries>
-                            <entry name="java:/JmsXA"/>
-                        </entries>
-                    </pooled-connection-factory>
-                </jms-connection-factories>
-                <jms-destinations>
-                    <jms-queue name="testQueue">
-                        <entry name="queue/test"/>
-                        <entry name="java:jboss/exported/jms/queue/test"/>
-                    </jms-queue>
-                    <jms-topic name="testTopic">
-                        <entry name="topic/test"/>
-                        <entry name="java:jboss/exported/jms/topic/test"/>
-                    </jms-topic>
-                </jms-destinations>
-            </hornetq-server>
-            <hornetq-server name="backup-server">
-                <persistence-enabled>true</persistence-enabled>
-                <backup>true</backup>
-                <shared-store>true</shared-store>
-                <journal-type>ASYNCIO</journal-type>
-                <journal-file-size>102400</journal-file-size>
-                <journal-min-files>2</journal-min-files>
-                <paging-directory path="messagingpaging2"/>
-                <bindings-directory path="messagingbindings2"/>
-                <journal-directory path="messagingjournal2"/>
-                <large-messages-directory path="messaginglargemessages2"/>
-                <connectors>
-                    <netty-connector name="netty" socket-binding="messaging-backup"/>
-                    <in-vm-connector name="in-vm" server-id="0"/>
-                </connectors>
-                <acceptors>
-                    <netty-acceptor name="netty" socket-binding="messaging-backup"/>
-                </acceptors>
-                <broadcast-groups>
-                    <broadcast-group name="bg-group1">
-                        <group-address>231.7.7.7</group-address>
-                        <group-port>9876</group-port>
-                        <broadcast-period>5000</broadcast-period>
-                        <connector-ref>netty</connector-ref>
-                    </broadcast-group>
-                </broadcast-groups>
-                <discovery-groups>
-                    <discovery-group name="dg-group1">
-                        <group-address>231.7.7.7</group-address>
-                        <group-port>9876</group-port>
-                        <refresh-timeout>10000</refresh-timeout>
-                    </discovery-group>
-                </discovery-groups>
-                <cluster-connections>
-                    <cluster-connection name="my-cluster">
-                        <address>jms</address>
-                        <connector-ref>netty</connector-ref>
-                        <discovery-group-ref discovery-group-name="dg-group1"/>
-                    </cluster-connection>
-                </cluster-connections>
-            </hornetq-server>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:naming:1.2">
-            <remote-naming/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:remoting:1.1">
-            <connector name="remoting-connector" socket-binding="remoting" security-realm="ApplicationRealm"/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:resource-adapters:1.0"/>
-        <subsystem xmlns="urn:jboss:domain:sar:1.0"/>
-        <subsystem xmlns="urn:jboss:domain:security:1.2">
-            <security-domains>
-                <security-domain name="other" cache-type="default">
-                    <authentication>
-                        <login-module code="Remoting" flag="optional">
-                            <module-option name="password-stacking" value="useFirstPass"/>
-                        </login-module>
-                        <login-module code="RealmDirect" flag="required">
-                            <module-option name="password-stacking" value="useFirstPass"/>
-                        </login-module>
-                    </authentication>
-                </security-domain>
-                <security-domain name="jboss-web-policy" cache-type="default">
-                    <authorization>
-                        <policy-module code="Delegating" flag="required"/>
-                    </authorization>
-                </security-domain>
-                <security-domain name="jboss-ejb-policy" cache-type="default">
-                    <authorization>
-                        <policy-module code="Delegating" flag="required"/>
-                    </authorization>
-                </security-domain>
-            </security-domains>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:threads:1.1"/>
-        <subsystem xmlns="urn:jboss:domain:transactions:1.2">
-            <core-environment>
-                <process-id>
-                    <uuid/>
-                </process-id>
-            </core-environment>
-            <recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/>
-            <coordinator-environment default-timeout="300"/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:web:1.4" default-virtual-server="default-host" native="false">
-            <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/>
-            <virtual-server name="default-host" enable-welcome-root="true">
-                <alias name="localhost"/>
-                <alias name="example.com"/>
-            </virtual-server>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:webservices:1.2">
-            <modify-wsdl-address>true</modify-wsdl-address>
-            <wsdl-host>${jboss.bind.address:127.0.0.1}</wsdl-host>
-            <endpoint-config name="Standard-Endpoint-Config"/>
-            <endpoint-config name="Recording-Endpoint-Config">
-                <pre-handler-chain name="recording-handlers" protocol-bindings="##SOAP11_HTTP ##SOAP11_HTTP_MTOM ##SOAP12_HTTP ##SOAP12_HTTP_MTOM">
-                    <handler name="RecordingHandler" class="org.jboss.ws.common.invocation.RecordingServerHandler"/>
-                </pre-handler-chain>
-            </endpoint-config>
-            <client-config name="Standard-Client-Config"/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:weld:1.0"/>
-    </profile>
-    <interfaces>
-        <interface name="management">
-            <inet-address value="${jboss.bind.address.management:127.0.0.1}"/>
-        </interface>
-        <interface name="public">
-            <inet-address value="${jboss.bind.address:127.0.0.1}"/>
-        </interface>
-        <!-- TODO - only show this if the jacorb subsystem is added  -->
-        <interface name="unsecure">
-            <!--
-              ~  Used for IIOP sockets in the standard configuration.
-              ~                  To secure JacORB you need to setup SSL 
-              -->
-            <inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/>
-        </interface>
-    </interfaces>
-    <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
-        <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>
-        <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>
-        <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}"/>
-        <socket-binding name="ajp" port="8009"/>
-        <socket-binding name="http" port="8080"/>
-        <socket-binding name="https" port="8443"/>
-        <socket-binding name="jacorb" interface="unsecure" port="3528"/>
-        <socket-binding name="jacorb-ssl" interface="unsecure" port="3529"/>
-        <socket-binding name="messaging" port="5445"/>
-        <socket-binding name="messaging-backup" port="5545"/>
-        <socket-binding name="messaging-throughput" port="5455"/>
-        <socket-binding name="remoting" port="4447"/>
-        <socket-binding name="txn-recovery-environment" port="4712"/>
-        <socket-binding name="txn-status-manager" port="4713"/>
-        <outbound-socket-binding name="mail-smtp">
-            <remote-destination host="localhost" port="25"/>
-        </outbound-socket-binding>
-    </socket-binding-group>
-</server>

jboss-as-7.2.0.Final/docs/examples/configs/standalone-jts.xml

@@ -1,343 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-
-<server xmlns="urn:jboss:domain:1.4">
-    <extensions>
-        <extension module="org.jboss.as.clustering.infinispan"/>
-        <extension module="org.jboss.as.configadmin"/>
-        <extension module="org.jboss.as.connector"/>
-        <extension module="org.jboss.as.deployment-scanner"/>
-        <extension module="org.jboss.as.ee"/>
-        <extension module="org.jboss.as.ejb3"/>
-        <extension module="org.jboss.as.jacorb"/>
-        <extension module="org.jboss.as.jaxrs"/>
-        <extension module="org.jboss.as.jdr"/>
-        <extension module="org.jboss.as.jmx"/>
-        <extension module="org.jboss.as.jpa"/>
-        <extension module="org.jboss.as.jsf"/>
-        <extension module="org.jboss.as.logging"/>
-        <extension module="org.jboss.as.mail"/>
-        <extension module="org.jboss.as.naming"/>
-        <extension module="org.jboss.as.osgi"/>
-        <extension module="org.jboss.as.pojo"/>
-        <extension module="org.jboss.as.remoting"/>
-        <extension module="org.jboss.as.sar"/>
-        <extension module="org.jboss.as.security"/>
-        <extension module="org.jboss.as.threads"/>
-        <extension module="org.jboss.as.transactions"/>
-        <extension module="org.jboss.as.web"/>
-        <extension module="org.jboss.as.webservices"/>
-        <extension module="org.jboss.as.weld"/>
-    </extensions>
-    <management>
-        <security-realms>
-            <security-realm name="ManagementRealm">
-                <authentication>
-                    <local default-user="$local"/>
-                    <properties path="mgmt-users.properties" relative-to="jboss.server.config.dir"/>
-                </authentication>
-            </security-realm>
-            <security-realm name="ApplicationRealm">
-                <authentication>
-                    <local default-user="$local" allowed-users="*"/>
-                    <properties path="application-users.properties" relative-to="jboss.server.config.dir"/>
-                </authentication>
-                <authorization>
-                    <properties path="application-roles.properties" relative-to="jboss.server.config.dir"/>
-                </authorization>
-            </security-realm>
-        </security-realms>
-        <management-interfaces>
-            <native-interface security-realm="ManagementRealm">
-                <socket-binding native="management-native"/>
-            </native-interface>
-            <http-interface security-realm="ManagementRealm">
-                <socket-binding http="management-http"/>
-            </http-interface>
-        </management-interfaces>
-    </management>
-    <profile>
-        <subsystem xmlns="urn:jboss:domain:logging:1.2">
-            <console-handler name="CONSOLE">
-                <level name="INFO"/>
-                <formatter>
-                    <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
-                </formatter>
-            </console-handler>
-            <periodic-rotating-file-handler name="FILE" autoflush="true">
-                <formatter>
-                    <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
-                </formatter>
-                <file relative-to="jboss.server.log.dir" path="server.log"/>
-                <suffix value=".yyyy-MM-dd"/>
-                <append value="true"/>
-            </periodic-rotating-file-handler>
-            <logger category="com.arjuna">
-                <level name="WARN"/>
-            </logger>
-            <logger category="org.apache.tomcat.util.modeler">
-                <level name="WARN"/>
-            </logger>
-            <logger category="org.jboss.as.config">
-                <level name="DEBUG"/>
-            </logger>
-            <logger category="sun.rmi">
-                <level name="WARN"/>
-            </logger>
-            <logger category="jacorb">
-                <level name="WARN"/>
-            </logger>
-            <logger category="jacorb.config">
-                <level name="ERROR"/>
-            </logger>
-            <root-logger>
-                <level name="INFO"/>
-                <handlers>
-                    <handler name="CONSOLE"/>
-                    <handler name="FILE"/>
-                </handlers>
-            </root-logger>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:configadmin:1.0"/>
-        <subsystem xmlns="urn:jboss:domain:datasources:1.1">
-            <datasources>
-                <datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS" enabled="true" use-java-context="true">
-                    <connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1</connection-url>
-                    <driver>h2</driver>
-                    <security>
-                        <user-name>sa</user-name>
-                        <password>sa</password>
-                    </security>
-                </datasource>
-                <drivers>
-                    <driver name="h2" module="com.h2database.h2">
-                        <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
-                    </driver>
-                </drivers>
-            </datasources>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
-            <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000"/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:ee:1.1">
-            <spec-descriptor-property-replacement>false</spec-descriptor-property-replacement>
-            <jboss-descriptor-property-replacement>true</jboss-descriptor-property-replacement>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:ejb3:1.4">
-            <session-bean>
-                <stateless>
-                    <bean-instance-pool-ref pool-name="slsb-strict-max-pool"/>
-                </stateless>
-                <stateful default-access-timeout="5000" cache-ref="simple"/>
-                <singleton default-access-timeout="5000"/>
-            </session-bean>
-            <pools>
-                <bean-instance-pools>
-                    <strict-max-pool name="slsb-strict-max-pool" max-pool-size="20" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
-                    <strict-max-pool name="mdb-strict-max-pool" max-pool-size="20" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
-                </bean-instance-pools>
-            </pools>
-            <caches>
-                <cache name="simple" aliases="NoPassivationCache"/>
-                <cache name="passivating" passivation-store-ref="file" aliases="SimpleStatefulCache"/>
-            </caches>
-            <passivation-stores>
-                <file-passivation-store name="file"/>
-            </passivation-stores>
-            <async thread-pool-name="default"/>
-            <timer-service thread-pool-name="default">
-                <data-store path="timer-service-data" relative-to="jboss.server.data.dir"/>
-            </timer-service>
-            <remote connector-ref="remoting-connector" thread-pool-name="default"/>
-            <thread-pools>
-                <thread-pool name="default">
-                    <max-threads count="10"/>
-                    <keepalive-time time="100" unit="milliseconds"/>
-                </thread-pool>
-            </thread-pools>
-            <default-security-domain value="other"/>
-            <default-missing-method-permissions-deny-access value="true"/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:infinispan:1.4">
-            <cache-container name="web" aliases="standard-session-cache" default-cache="local-web" module="org.jboss.as.clustering.web.infinispan">
-                <local-cache name="local-web" batching="true">
-                    <file-store passivation="false" purge="false"/>
-                </local-cache>
-            </cache-container>
-            <cache-container name="hibernate" default-cache="local-query" module="org.jboss.as.jpa.hibernate:4">
-                <local-cache name="entity">
-                    <transaction mode="NON_XA"/>
-                    <eviction strategy="LRU" max-entries="10000"/>
-                    <expiration max-idle="100000"/>
-                </local-cache>
-                <local-cache name="local-query">
-                    <transaction mode="NONE"/>
-                    <eviction strategy="LRU" max-entries="10000"/>
-                    <expiration max-idle="100000"/>
-                </local-cache>
-                <local-cache name="timestamps">
-                    <transaction mode="NONE"/>
-                    <eviction strategy="NONE"/>
-                </local-cache>
-            </cache-container>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:jacorb:1.3">
-            <orb socket-binding="jacorb" ssl-socket-binding="jacorb-ssl">
-                <initializers transactions="spec" security="identity"/>
-            </orb>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:jaxrs:1.0"/>
-        <subsystem xmlns="urn:jboss:domain:jca:1.1">
-            <archive-validation enabled="true" fail-on-error="true" fail-on-warn="false"/>
-            <bean-validation enabled="true"/>
-            <default-workmanager>
-                <short-running-threads>
-                    <core-threads count="50"/>
-                    <queue-length count="50"/>
-                    <max-threads count="50"/>
-                    <keepalive-time time="10" unit="seconds"/>
-                </short-running-threads>
-                <long-running-threads>
-                    <core-threads count="50"/>
-                    <queue-length count="50"/>
-                    <max-threads count="50"/>
-                    <keepalive-time time="10" unit="seconds"/>
-                </long-running-threads>
-            </default-workmanager>
-            <cached-connection-manager/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:jdr:1.0"/>
-        <subsystem xmlns="urn:jboss:domain:jmx:1.2">
-            <expose-resolved-model/>
-            <expose-expression-model/>
-            <remoting-connector/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:jpa:1.1">
-            <jpa default-datasource="" default-extended-persistence-inheritance="DEEP"/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:jsf:1.0"/>
-        <subsystem xmlns="urn:jboss:domain:mail:1.0">
-            <mail-session jndi-name="java:jboss/mail/Default">
-                <smtp-server outbound-socket-binding-ref="mail-smtp"/>
-            </mail-session>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:naming:1.2">
-            <remote-naming/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:osgi:1.2" activation="lazy">
-            <properties>
-                <!-- Specifies the beginning start level of the framework -->
-                <property name="org.osgi.framework.startlevel.beginning">1</property>
-            </properties>
-            <capabilities>
-                <!-- modules registered with the OSGi layer on startup -->
-                <capability name="javax.jws.api"/>
-                <capability name="javax.persistence.api"/>
-                <capability name="javax.servlet.api"/>
-                <capability name="javax.transaction.api"/>
-                <capability name="javax.ws.rs.api"/>
-                <capability name="javax.xml.bind.api"/>
-                <capability name="javax.xml.ws.api"/>
-                <capability name="org.slf4j"/>
-                <!-- bundles started in startlevel 1 -->
-                <capability name="org.apache.felix.log" startlevel="1"/>
-                <capability name="org.jboss.osgi.logging" startlevel="1"/>
-                <capability name="org.apache.felix.configadmin" startlevel="1"/>
-                <capability name="org.jboss.as.osgi.configadmin" startlevel="1"/>
-                <capability name="org.jboss.as.osgi.http" startlevel="1"/>
-                <capability name="org.jboss.as.osgi.jpa" startlevel="1"/>
-            </capabilities>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:pojo:1.0"/>
-        <subsystem xmlns="urn:jboss:domain:remoting:1.1">
-            <connector name="remoting-connector" socket-binding="remoting" security-realm="ApplicationRealm"/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:resource-adapters:1.0"/>
-        <subsystem xmlns="urn:jboss:domain:sar:1.0"/>
-        <subsystem xmlns="urn:jboss:domain:security:1.2">
-            <security-domains>
-                <security-domain name="other" cache-type="default">
-                    <authentication>
-                        <login-module code="Remoting" flag="optional">
-                            <module-option name="password-stacking" value="useFirstPass"/>
-                        </login-module>
-                        <login-module code="RealmDirect" flag="required">
-                            <module-option name="password-stacking" value="useFirstPass"/>
-                        </login-module>
-                    </authentication>
-                </security-domain>
-                <security-domain name="jboss-web-policy" cache-type="default">
-                    <authorization>
-                        <policy-module code="Delegating" flag="required"/>
-                    </authorization>
-                </security-domain>
-                <security-domain name="jboss-ejb-policy" cache-type="default">
-                    <authorization>
-                        <policy-module code="Delegating" flag="required"/>
-                    </authorization>
-                </security-domain>
-            </security-domains>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:threads:1.1"/>
-        <subsystem xmlns="urn:jboss:domain:transactions:1.2">
-            <core-environment>
-                <process-id>
-                    <uuid/>
-                </process-id>
-            </core-environment>
-            <recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/>
-            <coordinator-environment default-timeout="300"/>
-            <jts/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:web:1.4" default-virtual-server="default-host" native="false">
-            <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/>
-            <virtual-server name="default-host" enable-welcome-root="true">
-                <alias name="localhost"/>
-                <alias name="example.com"/>
-            </virtual-server>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:webservices:1.2">
-            <modify-wsdl-address>true</modify-wsdl-address>
-            <wsdl-host>${jboss.bind.address:127.0.0.1}</wsdl-host>
-            <endpoint-config name="Standard-Endpoint-Config"/>
-            <endpoint-config name="Recording-Endpoint-Config">
-                <pre-handler-chain name="recording-handlers" protocol-bindings="##SOAP11_HTTP ##SOAP11_HTTP_MTOM ##SOAP12_HTTP ##SOAP12_HTTP_MTOM">
-                    <handler name="RecordingHandler" class="org.jboss.ws.common.invocation.RecordingServerHandler"/>
-                </pre-handler-chain>
-            </endpoint-config>
-            <client-config name="Standard-Client-Config"/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:weld:1.0"/>
-    </profile>
-    <interfaces>
-        <interface name="management">
-            <inet-address value="${jboss.bind.address.management:127.0.0.1}"/>
-        </interface>
-        <interface name="public">
-            <inet-address value="${jboss.bind.address:127.0.0.1}"/>
-        </interface>
-        <!-- TODO - only show this if the jacorb subsystem is added  -->
-        <interface name="unsecure">
-            <!--
-              ~  Used for IIOP sockets in the standard configuration.
-              ~                  To secure JacORB you need to setup SSL 
-              -->
-            <inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/>
-        </interface>
-    </interfaces>
-    <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
-        <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>
-        <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>
-        <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}"/>
-        <socket-binding name="ajp" port="8009"/>
-        <socket-binding name="http" port="8080"/>
-        <socket-binding name="https" port="8443"/>
-        <socket-binding name="jacorb" interface="unsecure" port="3528"/>
-        <socket-binding name="jacorb-ssl" interface="unsecure" port="3529"/>
-        <socket-binding name="remoting" port="4447"/>
-        <socket-binding name="txn-recovery-environment" port="4712"/>
-        <socket-binding name="txn-status-manager" port="4713"/>
-        <outbound-socket-binding name="mail-smtp">
-            <remote-destination host="localhost" port="25"/>
-        </outbound-socket-binding>
-    </socket-binding-group>
-</server>

jboss-as-7.2.0.Final/docs/examples/configs/standalone-minimalistic.xml

@@ -1,37 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-
-<server xmlns="urn:jboss:domain:1.3">
-    <management>
-        <security-realms>
-            <security-realm name="ManagementRealm">
-                <authentication>
-                    <local default-user="$local"/>
-                    <properties path="mgmt-users.properties" relative-to="jboss.server.config.dir"/>
-                </authentication>
-            </security-realm>
-        </security-realms>
-        <management-interfaces>
-            <native-interface security-realm="ManagementRealm">
-                <socket-binding native="management-native"/>
-            </native-interface>
-            <http-interface console-enabled="false" security-realm="ManagementRealm">
-                <socket-binding http="management-http"/>
-            </http-interface>
-        </management-interfaces>
-    </management>
-
-    <interfaces>
-        <interface name="management">
-            <inet-address value="${jboss.bind.address.management:127.0.0.1}"/>
-        </interface>
-        <!-- the default interface -->
-        <interface name="public">
-            <inet-address value="${jboss.bind.address:127.0.0.1}"/>
-        </interface>
-    </interfaces>
-
-    <socket-binding-group name="standard-sockets" default-interface="public">
-        <socket-binding name="management-native" interface="management" port="9999"/>
-        <socket-binding name="management-http" interface="management" port="9990"/>
-    </socket-binding-group>
-</server>

jboss-as-7.2.0.Final/docs/examples/configs/standalone-osgi-only.xml

@@ -1,109 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-
-<server xmlns="urn:jboss:domain:1.4">
-    <extensions>
-        <extension module="org.jboss.as.configadmin"/>
-        <extension module="org.jboss.as.deployment-scanner"/>
-        <extension module="org.jboss.as.ee"/>
-        <extension module="org.jboss.as.logging"/>
-        <extension module="org.jboss.as.naming"/>
-        <extension module="org.jboss.as.osgi"/>
-        <extension module="org.jboss.as.remoting"/>
-    </extensions>
-    <management>
-        <security-realms>
-            <security-realm name="ManagementRealm">
-                <authentication>
-                    <local default-user="$local"/>
-                    <properties path="mgmt-users.properties" relative-to="jboss.server.config.dir"/>
-                </authentication>
-            </security-realm>
-            <security-realm name="ApplicationRealm">
-                <authentication>
-                    <local default-user="$local" allowed-users="*"/>
-                    <properties path="application-users.properties" relative-to="jboss.server.config.dir"/>
-                </authentication>
-                <authorization>
-                    <properties path="application-roles.properties" relative-to="jboss.server.config.dir"/>
-                </authorization>
-            </security-realm>
-        </security-realms>
-        <management-interfaces>
-            <native-interface security-realm="ManagementRealm">
-                <socket-binding native="management-native"/>
-            </native-interface>
-            <http-interface security-realm="ManagementRealm">
-                <socket-binding http="management-http"/>
-            </http-interface>
-        </management-interfaces>
-    </management>
-    <profile>
-        <subsystem xmlns="urn:jboss:domain:logging:1.2">
-            <console-handler name="CONSOLE">
-                <level name="INFO"/>
-                <formatter>
-                    <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
-                </formatter>
-            </console-handler>
-            <periodic-rotating-file-handler name="FILE" autoflush="true">
-                <formatter>
-                    <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
-                </formatter>
-                <file relative-to="jboss.server.log.dir" path="server.log"/>
-                <suffix value=".yyyy-MM-dd"/>
-                <append value="false"/>
-            </periodic-rotating-file-handler>
-            <logger category="org.jboss.osgi">
-                <level name="DEBUG"/>
-            </logger>
-            <root-logger>
-                <level name="INFO"/>
-                <handlers>
-                    <handler name="CONSOLE"/>
-                    <handler name="FILE"/>
-                </handlers>
-            </root-logger>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:configadmin:1.0"/>
-        <subsystem xmlns="urn:jboss:domain:osgi:1.2" activation="eager">
-            <properties>
-                <!-- Specifies the beginning start level of the framework -->
-                <property name="org.osgi.framework.startlevel.beginning">1</property>
-            </properties>
-            <capabilities>
-                <!-- bundles started in startlevel 1 -->
-                <capability name="org.apache.felix.log" startlevel="1"/>
-                <capability name="org.jboss.osgi.logging" startlevel="1"/>
-                <capability name="org.apache.felix.configadmin" startlevel="1"/>
-                <capability name="org.jboss.as.osgi.configadmin" startlevel="1"/>
-            </capabilities>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
-            <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000"/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:ee:1.1">
-            <spec-descriptor-property-replacement>false</spec-descriptor-property-replacement>
-            <jboss-descriptor-property-replacement>true</jboss-descriptor-property-replacement>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:naming:1.2">
-            <remote-naming/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:remoting:1.1">
-            <connector name="remoting-connector" socket-binding="remoting" security-realm="ApplicationRealm"/>
-        </subsystem>
-    </profile>
-    <interfaces>
-        <interface name="management">
-            <inet-address value="${jboss.bind.address.management:127.0.0.1}"/>
-        </interface>
-        <interface name="public">
-            <inet-address value="${jboss.bind.address:127.0.0.1}"/>
-        </interface>
-    </interfaces>
-    <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
-        <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>
-        <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>
-        <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}"/>
-        <socket-binding name="remoting" port="4447"/>
-    </socket-binding-group>
-</server>

jboss-as-7.2.0.Final/docs/examples/configs/standalone-xts.xml

@@ -1,431 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-
-<server xmlns="urn:jboss:domain:1.4">
-    <extensions>
-        <extension module="org.jboss.as.clustering.infinispan"/>
-        <extension module="org.jboss.as.cmp"/>
-        <extension module="org.jboss.as.configadmin"/>
-        <extension module="org.jboss.as.connector"/>
-        <extension module="org.jboss.as.deployment-scanner"/>
-        <extension module="org.jboss.as.ee"/>
-        <extension module="org.jboss.as.ejb3"/>
-        <extension module="org.jboss.as.jacorb"/>
-        <extension module="org.jboss.as.jaxr"/>
-        <extension module="org.jboss.as.jaxrs"/>
-        <extension module="org.jboss.as.jdr"/>
-        <extension module="org.jboss.as.jmx"/>
-        <extension module="org.jboss.as.jpa"/>
-        <extension module="org.jboss.as.jsf"/>
-        <extension module="org.jboss.as.jsr77"/>
-        <extension module="org.jboss.as.logging"/>
-        <extension module="org.jboss.as.mail"/>
-        <extension module="org.jboss.as.messaging"/>
-        <extension module="org.jboss.as.naming"/>
-        <extension module="org.jboss.as.osgi"/>
-        <extension module="org.jboss.as.pojo"/>
-        <extension module="org.jboss.as.remoting"/>
-        <extension module="org.jboss.as.sar"/>
-        <extension module="org.jboss.as.security"/>
-        <extension module="org.jboss.as.threads"/>
-        <extension module="org.jboss.as.transactions"/>
-        <extension module="org.jboss.as.web"/>
-        <extension module="org.jboss.as.webservices"/>
-        <extension module="org.jboss.as.weld"/>
-        <extension module="org.jboss.as.xts"/>
-    </extensions>
-    <management>
-        <security-realms>
-            <security-realm name="ManagementRealm">
-                <authentication>
-                    <local default-user="$local"/>
-                    <properties path="mgmt-users.properties" relative-to="jboss.server.config.dir"/>
-                </authentication>
-            </security-realm>
-            <security-realm name="ApplicationRealm">
-                <authentication>
-                    <local default-user="$local" allowed-users="*"/>
-                    <properties path="application-users.properties" relative-to="jboss.server.config.dir"/>
-                </authentication>
-                <authorization>
-                    <properties path="application-roles.properties" relative-to="jboss.server.config.dir"/>
-                </authorization>
-            </security-realm>
-        </security-realms>
-        <management-interfaces>
-            <native-interface security-realm="ManagementRealm">
-                <socket-binding native="management-native"/>
-            </native-interface>
-            <http-interface security-realm="ManagementRealm">
-                <socket-binding http="management-http"/>
-            </http-interface>
-        </management-interfaces>
-    </management>
-    <profile>
-        <subsystem xmlns="urn:jboss:domain:logging:1.2">
-            <console-handler name="CONSOLE">
-                <level name="INFO"/>
-                <formatter>
-                    <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
-                </formatter>
-            </console-handler>
-            <periodic-rotating-file-handler name="FILE" autoflush="true">
-                <formatter>
-                    <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
-                </formatter>
-                <file relative-to="jboss.server.log.dir" path="server.log"/>
-                <suffix value=".yyyy-MM-dd"/>
-                <append value="true"/>
-            </periodic-rotating-file-handler>
-            <logger category="com.arjuna">
-                <level name="WARN"/>
-            </logger>
-            <logger category="org.apache.tomcat.util.modeler">
-                <level name="WARN"/>
-            </logger>
-            <logger category="org.jboss.as.config">
-                <level name="DEBUG"/>
-            </logger>
-            <logger category="sun.rmi">
-                <level name="WARN"/>
-            </logger>
-            <logger category="jacorb">
-                <level name="WARN"/>
-            </logger>
-            <logger category="jacorb.config">
-                <level name="ERROR"/>
-            </logger>
-            <root-logger>
-                <level name="INFO"/>
-                <handlers>
-                    <handler name="CONSOLE"/>
-                    <handler name="FILE"/>
-                </handlers>
-            </root-logger>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:cmp:1.0"/>
-        <subsystem xmlns="urn:jboss:domain:configadmin:1.0"/>
-        <subsystem xmlns="urn:jboss:domain:datasources:1.1">
-            <datasources>
-                <datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS" enabled="true" use-java-context="true">
-                    <connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1</connection-url>
-                    <driver>h2</driver>
-                    <security>
-                        <user-name>sa</user-name>
-                        <password>sa</password>
-                    </security>
-                </datasource>
-                <drivers>
-                    <driver name="h2" module="com.h2database.h2">
-                        <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
-                    </driver>
-                </drivers>
-            </datasources>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
-            <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000"/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:ee:1.1">
-            <spec-descriptor-property-replacement>false</spec-descriptor-property-replacement>
-            <jboss-descriptor-property-replacement>true</jboss-descriptor-property-replacement>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:ejb3:1.4">
-            <session-bean>
-                <stateless>
-                    <bean-instance-pool-ref pool-name="slsb-strict-max-pool"/>
-                </stateless>
-                <stateful default-access-timeout="5000" cache-ref="simple"/>
-                <singleton default-access-timeout="5000"/>
-            </session-bean>
-            <mdb>
-                <resource-adapter-ref resource-adapter-name="hornetq-ra"/>
-                <bean-instance-pool-ref pool-name="mdb-strict-max-pool"/>
-            </mdb>
-            <pools>
-                <bean-instance-pools>
-                    <strict-max-pool name="slsb-strict-max-pool" max-pool-size="20" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
-                    <strict-max-pool name="mdb-strict-max-pool" max-pool-size="20" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
-                </bean-instance-pools>
-            </pools>
-            <caches>
-                <cache name="simple" aliases="NoPassivationCache"/>
-                <cache name="passivating" passivation-store-ref="file" aliases="SimpleStatefulCache"/>
-            </caches>
-            <passivation-stores>
-                <file-passivation-store name="file"/>
-            </passivation-stores>
-            <async thread-pool-name="default"/>
-            <timer-service thread-pool-name="default">
-                <data-store path="timer-service-data" relative-to="jboss.server.data.dir"/>
-            </timer-service>
-            <remote connector-ref="remoting-connector" thread-pool-name="default"/>
-            <thread-pools>
-                <thread-pool name="default">
-                    <max-threads count="10"/>
-                    <keepalive-time time="100" unit="milliseconds"/>
-                </thread-pool>
-            </thread-pools>
-            <iiop enable-by-default="false" use-qualified-name="false"/>
-            <default-security-domain value="other"/>
-            <default-missing-method-permissions-deny-access value="true"/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:infinispan:1.4">
-            <cache-container name="web" aliases="standard-session-cache" default-cache="local-web" module="org.jboss.as.clustering.web.infinispan">
-                <local-cache name="local-web" batching="true">
-                    <file-store passivation="false" purge="false"/>
-                </local-cache>
-            </cache-container>
-            <cache-container name="hibernate" default-cache="local-query" module="org.jboss.as.jpa.hibernate:4">
-                <local-cache name="entity">
-                    <transaction mode="NON_XA"/>
-                    <eviction strategy="LRU" max-entries="10000"/>
-                    <expiration max-idle="100000"/>
-                </local-cache>
-                <local-cache name="local-query">
-                    <transaction mode="NONE"/>
-                    <eviction strategy="LRU" max-entries="10000"/>
-                    <expiration max-idle="100000"/>
-                </local-cache>
-                <local-cache name="timestamps">
-                    <transaction mode="NONE"/>
-                    <eviction strategy="NONE"/>
-                </local-cache>
-            </cache-container>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:jacorb:1.3">
-            <orb socket-binding="jacorb" ssl-socket-binding="jacorb-ssl">
-                <initializers transactions="spec" security="identity"/>
-            </orb>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:jaxr:1.1">
-            <connection-factory jndi-name="java:jboss/jaxr/ConnectionFactory"/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:jaxrs:1.0"/>
-        <subsystem xmlns="urn:jboss:domain:jca:1.1">
-            <archive-validation enabled="true" fail-on-error="true" fail-on-warn="false"/>
-            <bean-validation enabled="true"/>
-            <default-workmanager>
-                <short-running-threads>
-                    <core-threads count="50"/>
-                    <queue-length count="50"/>
-                    <max-threads count="50"/>
-                    <keepalive-time time="10" unit="seconds"/>
-                </short-running-threads>
-                <long-running-threads>
-                    <core-threads count="50"/>
-                    <queue-length count="50"/>
-                    <max-threads count="50"/>
-                    <keepalive-time time="10" unit="seconds"/>
-                </long-running-threads>
-            </default-workmanager>
-            <cached-connection-manager/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:jdr:1.0"/>
-        <subsystem xmlns="urn:jboss:domain:jmx:1.2">
-            <expose-resolved-model/>
-            <expose-expression-model/>
-            <remoting-connector/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:jpa:1.1">
-            <jpa default-datasource="" default-extended-persistence-inheritance="DEEP"/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:jsf:1.0"/>
-        <subsystem xmlns="urn:jboss:domain:jsr77:1.0"/>
-        <subsystem xmlns="urn:jboss:domain:mail:1.0">
-            <mail-session jndi-name="java:jboss/mail/Default">
-                <smtp-server outbound-socket-binding-ref="mail-smtp"/>
-            </mail-session>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:messaging:1.3">
-            <hornetq-server>
-                <persistence-enabled>true</persistence-enabled>
-                <journal-file-size>102400</journal-file-size>
-                <journal-min-files>2</journal-min-files>
-                <connectors>
-                    <netty-connector name="netty" socket-binding="messaging"/>
-                    <netty-connector name="netty-throughput" socket-binding="messaging-throughput">
-                        <param key="batch-delay" value="50"/>
-                    </netty-connector>
-                    <in-vm-connector name="in-vm" server-id="0"/>
-                </connectors>
-                <acceptors>
-                    <netty-acceptor name="netty" socket-binding="messaging"/>
-                    <netty-acceptor name="netty-throughput" socket-binding="messaging-throughput">
-                        <param key="batch-delay" value="50"/>
-                        <param key="direct-deliver" value="false"/>
-                    </netty-acceptor>
-                    <in-vm-acceptor name="in-vm" server-id="0"/>
-                </acceptors>
-                <security-settings>
-                    <security-setting match="#">
-                        <permission type="send" roles="guest"/>
-                        <permission type="consume" roles="guest"/>
-                        <permission type="createNonDurableQueue" roles="guest"/>
-                        <permission type="deleteNonDurableQueue" roles="guest"/>
-                    </security-setting>
-                </security-settings>
-                <address-settings>
-                    <!--default for catch all-->
-                    <address-setting match="#">
-                        <dead-letter-address>jms.queue.DLQ</dead-letter-address>
-                        <expiry-address>jms.queue.ExpiryQueue</expiry-address>
-                        <redelivery-delay>0</redelivery-delay>
-                        <max-size-bytes>10485760</max-size-bytes>
-                        <address-full-policy>BLOCK</address-full-policy>
-                        <message-counter-history-day-limit>10</message-counter-history-day-limit>
-                    </address-setting>
-                </address-settings>
-                <jms-connection-factories>
-                    <connection-factory name="InVmConnectionFactory">
-                        <connectors>
-                            <connector-ref connector-name="in-vm"/>
-                        </connectors>
-                        <entries>
-                            <entry name="java:/ConnectionFactory"/>
-                        </entries>
-                    </connection-factory>
-                    <connection-factory name="RemoteConnectionFactory">
-                        <connectors>
-                            <connector-ref connector-name="netty"/>
-                        </connectors>
-                        <entries>
-                            <entry name="java:jboss/exported/jms/RemoteConnectionFactory"/>
-                        </entries>
-                    </connection-factory>
-                    <pooled-connection-factory name="hornetq-ra">
-                        <transaction mode="xa"/>
-                        <connectors>
-                            <connector-ref connector-name="in-vm"/>
-                        </connectors>
-                        <entries>
-                            <entry name="java:/JmsXA"/>
-                        </entries>
-                    </pooled-connection-factory>
-                </jms-connection-factories>
-            </hornetq-server>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:naming:1.2">
-            <remote-naming/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:osgi:1.2" activation="lazy">
-            <properties>
-                <!-- Specifies the beginning start level of the framework -->
-                <property name="org.osgi.framework.startlevel.beginning">1</property>
-            </properties>
-            <capabilities>
-                <!-- modules registered with the OSGi layer on startup -->
-                <capability name="javax.jws.api"/>
-                <capability name="javax.persistence.api"/>
-                <capability name="javax.servlet.api"/>
-                <capability name="javax.transaction.api"/>
-                <capability name="javax.ws.rs.api"/>
-                <capability name="javax.xml.bind.api"/>
-                <capability name="javax.xml.ws.api"/>
-                <capability name="org.slf4j"/>
-                <!-- bundles started in startlevel 1 -->
-                <capability name="org.apache.felix.log" startlevel="1"/>
-                <capability name="org.jboss.osgi.logging" startlevel="1"/>
-                <capability name="org.apache.felix.configadmin" startlevel="1"/>
-                <capability name="org.jboss.as.osgi.configadmin" startlevel="1"/>
-                <capability name="org.jboss.as.osgi.http" startlevel="1"/>
-                <capability name="org.jboss.as.osgi.jpa" startlevel="1"/>
-            </capabilities>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:pojo:1.0"/>
-        <subsystem xmlns="urn:jboss:domain:remoting:1.1">
-            <connector name="remoting-connector" socket-binding="remoting" security-realm="ApplicationRealm"/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:resource-adapters:1.0"/>
-        <subsystem xmlns="urn:jboss:domain:sar:1.0"/>
-        <subsystem xmlns="urn:jboss:domain:security:1.2">
-            <security-domains>
-                <security-domain name="other" cache-type="default">
-                    <authentication>
-                        <login-module code="Remoting" flag="optional">
-                            <module-option name="password-stacking" value="useFirstPass"/>
-                        </login-module>
-                        <login-module code="RealmDirect" flag="required">
-                            <module-option name="password-stacking" value="useFirstPass"/>
-                        </login-module>
-                    </authentication>
-                </security-domain>
-                <security-domain name="jboss-web-policy" cache-type="default">
-                    <authorization>
-                        <policy-module code="Delegating" flag="required"/>
-                    </authorization>
-                </security-domain>
-                <security-domain name="jboss-ejb-policy" cache-type="default">
-                    <authorization>
-                        <policy-module code="Delegating" flag="required"/>
-                    </authorization>
-                </security-domain>
-            </security-domains>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:threads:1.1"/>
-        <subsystem xmlns="urn:jboss:domain:transactions:1.2">
-            <core-environment>
-                <process-id>
-                    <uuid/>
-                </process-id>
-            </core-environment>
-            <recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/>
-            <coordinator-environment default-timeout="300"/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:web:1.4" default-virtual-server="default-host" native="false">
-            <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/>
-            <virtual-server name="default-host" enable-welcome-root="true">
-                <alias name="localhost"/>
-                <alias name="example.com"/>
-            </virtual-server>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:webservices:1.2">
-            <modify-wsdl-address>true</modify-wsdl-address>
-            <wsdl-host>${jboss.bind.address:127.0.0.1}</wsdl-host>
-            <endpoint-config name="Standard-Endpoint-Config"/>
-            <endpoint-config name="Recording-Endpoint-Config">
-                <pre-handler-chain name="recording-handlers" protocol-bindings="##SOAP11_HTTP ##SOAP11_HTTP_MTOM ##SOAP12_HTTP ##SOAP12_HTTP_MTOM">
-                    <handler name="RecordingHandler" class="org.jboss.ws.common.invocation.RecordingServerHandler"/>
-                </pre-handler-chain>
-            </endpoint-config>
-            <client-config name="Standard-Client-Config"/>
-        </subsystem>
-        <subsystem xmlns="urn:jboss:domain:weld:1.0"/>
-        <subsystem xmlns="urn:jboss:domain:xts:1.0">
-            <xts-environment url="http://${jboss.bind.address:127.0.0.1}:8080/ws-c11/ActivationService"/>
-        </subsystem>
-    </profile>
-    <interfaces>
-        <interface name="management">
-            <inet-address value="${jboss.bind.address.management:127.0.0.1}"/>
-        </interface>
-        <interface name="public">
-            <inet-address value="${jboss.bind.address:127.0.0.1}"/>
-        </interface>
-        <!-- TODO - only show this if the jacorb subsystem is added  -->
-        <interface name="unsecure">
-            <!--
-              ~  Used for IIOP sockets in the standard configuration.
-              ~                  To secure JacORB you need to setup SSL 
-              -->
-            <inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/>
-        </interface>
-    </interfaces>
-    <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
-        <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>
-        <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>
-        <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}"/>
-        <socket-binding name="ajp" port="8009"/>
-        <socket-binding name="http" port="8080"/>
-        <socket-binding name="https" port="8443"/>
-        <socket-binding name="jacorb" interface="unsecure" port="3528"/>
-        <socket-binding name="jacorb-ssl" interface="unsecure" port="3529"/>
-        <socket-binding name="messaging" port="5445"/>
-        <socket-binding name="messaging-group" port="0" multicast-address="${jboss.messaging.group.address:231.7.7.7}" multicast-port="${jboss.messaging.group.port:9876}"/>
-        <socket-binding name="messaging-throughput" port="5455"/>
-        <socket-binding name="remoting" port="4447"/>
-        <socket-binding name="txn-recovery-environment" port="4712"/>
-        <socket-binding name="txn-status-manager" port="4713"/>
-        <outbound-socket-binding name="mail-smtp">
-            <remote-destination host="localhost" port="25"/>
-        </outbound-socket-binding>
-    </socket-binding-group>
-</server>

jboss-as-7.2.0.Final/docs/schema/application-client_6.xsd

@@ -1,311 +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/javaee"
-            xmlns:javaee="http://java.sun.com/xml/ns/javaee"
-            xmlns:xsd="http://www.w3.org/2001/XMLSchema"
-            elementFormDefault="qualified"
-            attributeFormDefault="unqualified"
-            version="6">
-  <xsd:annotation>
-    <xsd:documentation>
-
-      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
-
-      Copyright 2003-2009 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 6
-      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_6.xsd"
-      version="6">
-      ...
-      </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_6.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_6.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:element name="module-name"
-                   type="javaee:string"
-                   minOccurs="0"/>
-      <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:element name="data-source"
-                   type="javaee:data-sourceType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="version"
-                   type="javaee:dewey-versionType"
-                   fixed="6"
-                   use="required">
-      <xsd:annotation>
-        <xsd:documentation>
-
-          The required value for the version is 6.
-
-        </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>

jboss-as-7.2.0.Final/docs/schema/application_1_2.dtd

@@ -1,197 +0,0 @@
-<!--
-Copyright 1999 Sun Microsystems, Inc. 901 San Antonio Road,
-Palo Alto, CA  94303, U.S.A.  All rights reserved.
- 
-This product or document is protected by copyright and distributed
-under licenses restricting its use, copying, distribution, and
-decompilation.  No part of this product or documentation 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, JavaServer Pages, Java 
-Naming and Directory Interface, JDBC, JDK, JavaMail and Enterprise JavaBeans, 
-are trademarks or registered trademarks of Sun Microsystems, Inc in the U.S. 
-and other countries.
-
-All SPARC trademarks are used under license and are trademarks
-or registered trademarks of SPARC International, Inc.
-in the U.S. and other countries. Products bearing SPARC
-trademarks are based upon an architecture developed by Sun Microsystems, Inc. 
-
-PostScript is a registered trademark of Adobe Systems, Inc. 
-
- 
-Federal Acquisitions: Commercial Software - Government Users Subject to 
-Standard License Terms and Conditions.
-
-
- 
-DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
-CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY
-IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
-PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT
-TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY
-INVALID.
-
-_________________________________________________________________________
-Copyright 1999 Sun Microsystems, Inc., 
-901 San Antonio Road, Palo Alto, CA  94303, Etats-Unis. 
-Tous droits re'serve's.
- 
-
-Ce produit ou document est prote'ge' par un copyright et distribue' avec 
-des licences qui en restreignent l'utilisation, la copie, la distribution,
-et la de'compilation.  Aucune partie de ce produit ou de sa documentation
-associe'e ne peut e^tre reproduite sous aucune forme, par quelque moyen 
-que ce soit, sans l'autorisation pre'alable et e'crite de Sun et de ses 
-bailleurs de licence, s'il y en a.  
-
-Le logiciel de'tenu par des tiers, et qui comprend la technologie 
-relative aux polices de caracte`res, est prote'ge' par un copyright 
-et licencie' par des fournisseurs de Sun.
- 
-Sun, Sun Microsystems, le logo Sun, Solaris, Java, JavaServer Pages, Java 
-Naming and Directory Interface, JDBC, JDK, JavaMail, et Enterprise JavaBeans,  
-sont des marques de fabrique ou des marques de'pose'es de Sun 
-Microsystems, Inc. aux Etats-Unis et dans d'autres pays.
- 
-Toutes les marques SPARC sont utilise'es sous licence et sont
-des marques de fabrique ou des marques de'pose'es de SPARC
-International, Inc. aux Etats-Unis et  dans
-d'autres pays. Les produits portant les marques SPARC sont
-base's sur une architecture de'veloppe'e par Sun Microsystems, Inc.  
-
-Postcript est une marque enregistre'e d'Adobe Systems Inc. 
- 
-LA DOCUMENTATION EST FOURNIE "EN L'ETAT" ET TOUTES AUTRES CONDITIONS,
-DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES,
-DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT
-TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE
-A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFACON.
--->
-
-<!--
-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.
--->
-<!ELEMENT alt-dd (#PCDATA)>
-
-<!--
-The application element is the root element of a J2EE application deployment
-descriptor.
--->
-<!ELEMENT application (icon?, display-name, description?, module+,
-security-role*)>
-
-<!--
-The context-root element specifies the context root of a web application
--->
-<!ELEMENT context-root (#PCDATA)>
-
-<!--
-The description element provides a human readable description of the
-application. The description element should include any information that the
-application assembler wants to provide the deployer.
--->
-<!ELEMENT description (#PCDATA)>
-
-<!--
-The display-name element specifies an application name.
-The application name is assigned to the application by the application assembler
-and is used to identify the application to the deployer at deployment time.
--->
-<!ELEMENT display-name (#PCDATA)>
-
-<!--
-The ejb element specifies the URI of a ejb-jar, relative to the top level of the
-application package.
--->
-<!ELEMENT ejb (#PCDATA)>
-
-<!--
-The icon element contains a small-icon and large-icon element which specify the
-URIs for a small and a large GIF or JPEG icon image to represent the application
-in a GUI.
--->
-<!ELEMENT icon (small-icon?, large-icon?)>
-
-<!--
-The java element specifies the URI of a java application client module, relative
-to the top level of the application package.
--->
-<!ELEMENT java (#PCDATA)>
-
-<!--
-The large-icon element specifies the URI for a large GIF or JPEG icon image to
-represent the application in a GUI.
--->
-<!ELEMENT large-icon (#PCDATA)>
-
-<!--
-The module element represents a single J2EE module and contains an 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.
-The application deployment descriptor must have one module element for each J2EE
-module in the application package.
--->
-<!ELEMENT module ((ejb | java | web), alt-dd?)>
-
-<!--
-The role-name element contains the name of a security role.
--->
-<!ELEMENT role-name (#PCDATA)>
-
-<!--
-The security-role element contains the definition of a security role which is
-global to the application. The definition consists of a description of the
-security role, and the security role name. The descriptions at this level
-override those in the component level security-role definitions and must be the
-descriptions tool display to the deployer.
--->
-<!ELEMENT security-role (description?, role-name)>
-
-<!--
-The small-icon element specifies the URI for a small GIF or JPEG icon image to
-represent the application in a GUI.
--->
-<!ELEMENT small-icon (#PCDATA)>
-
-<!--
-The web element contains the web-uri and context-root of a web application
-module.
--->
-<!ELEMENT web (web-uri, context-root)>
-
-<!--
-The web-uri element specifies the URI of a web application file, relative to the
-top level of the application package.
--->
-<!ELEMENT web-uri (#PCDATA)>
-
-<!--
-The ID mechanism is to allow tools to easily make tool-specific references to
-the elements of the deployment descriptor.
- -->
-<!ATTLIST alt-dd id ID #IMPLIED>
-<!ATTLIST application id ID #IMPLIED>
-<!ATTLIST context-root id ID #IMPLIED>
-<!ATTLIST description id ID #IMPLIED>
-<!ATTLIST display-name id ID #IMPLIED>
-<!ATTLIST ejb id ID #IMPLIED>
-<!ATTLIST icon id ID #IMPLIED>
-<!ATTLIST java id ID #IMPLIED>
-<!ATTLIST large-icon id ID #IMPLIED>
-<!ATTLIST module id ID #IMPLIED>
-<!ATTLIST role-name id ID #IMPLIED>
-<!ATTLIST security-role id ID #IMPLIED>
-<!ATTLIST small-icon id ID #IMPLIED>
-<!ATTLIST web id ID #IMPLIED>
-<!ATTLIST web-uri id ID #IMPLIED>

jboss-as-7.2.0.Final/docs/schema/application_1_3.dtd

@@ -1,312 +0,0 @@
-<!--
-Copyright (c) 2000 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 embodied in the product that is 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 in other countries.
-
-This document and the product to which it pertains are distributed
-under licenses restricting their use, copying, distribution, and
-decompilation.  This document may be reproduced and distributed but may
-not be changed 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,  Java,  JavaServer Pages,  Java
-Naming and Directory Interface,  JDBC,  JDK,  JavaMail and  and
-Enterprise JavaBeans 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.
-
-DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
-CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
-WARRANTY OF MERCHANTABILITY, FITNESS FOR FOR A PARTICULAR PURPOSE OR
-NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
-DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
-
-
-_________________________________________________________________________
-
-Copyright (c) 2000 Sun Microsystems, Inc.,
-901 San Antonio Road,
-Palo Alto, California 94303, E'tats-Unis.
-Tous droits re'serve's.
-
-Sun Microsystems, Inc. a les droits de proprie'te' intellectuels
-relatants a` la technologie incorpore'e dans le produit qui est de'crit
-dans ce document. En particulier, et sans la limitation, ces droits de
-proprie'te' intellectuels peuvent inclure un ou plus des brevets
-ame'ricains e'nume're's a` http://www.sun.com/patents et un ou les
-brevets plus supple'mentaires ou les applications de brevet en attente
-dans les E'tats-Unis et dans les autres pays.
-
-Ce produit ou document est prote'ge' par un copyright et distribue'
-avec des licences qui en restreignent l'utilisation, la copie, la
-distribution, et la de'compilation.  Ce documention associe n peut
-e^tre reproduite et distribuer, par quelque moyen que ce soit, sans
-l'autorisation pre'alable et e'crite de Sun et de ses bailleurs de
-licence, le cas e'che'ant.
-
-Le logiciel de'tenu par des tiers, et qui comprend la technologie
-relative aux polices de caracte`res, est prote'ge' par un copyright et
-licencie' par des fournisseurs de Sun.
-
-Sun,  Sun Microsystems,  le logo Sun,  Java,  JavaServer Pages,  Java
-Naming and Directory Interface,  JDBC,  JDK,  JavaMail et  and
-Enterprise JavaBeans sont des marques de fabrique ou des marques
-de'pose'es de Sun Microsystems, Inc. aux E'tats-Unis et dans d'autres
-pays.
-
-LA DOCUMENTATION EST FOURNIE "EN L'E'TAT" ET TOUTES AUTRES CONDITIONS,
-DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT
-EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS
-NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A
-L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE
-CONTREFAC,ON.
--->
-
-<!--
-This is the XML DTD for the J2EE 1.3 application deployment
-descriptor.  All J2EE 1.3 application deployment descriptors
-must include a DOCTYPE of the following form:
-
-  <!DOCTYPE application PUBLIC
-	"-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
-	"http://java.sun.com/dtd/application_1_3.dtd">
-
--->
-
-<!--
-The following conventions apply to all J2EE deployment descriptor
-elements unless indicated otherwise.
-
-- In elements that contain PCDATA, leading and trailing whitespace
-  in the data may be ignored.
-
-- In elements whose value is an "enumerated type", the value is
-  case sensitive.
-
-- In elements that specify a pathname to a file within the same
-  JAR file, relative filenames (i.e., those not starting with "/")
-  are considered relative to the root of the JAR file's namespace.
-  Absolute filenames (i.e., those starting with "/") also specify
-  names in the root of the JAR file's namespace.  In general, relative
-  names are preferred.  The exception is .war files where absolute
-  names are preferred for consistency with the servlet API.
--->
-
-
-<!--
-The application element is the root element of a J2EE application
-deployment descriptor.
--->
-<!ELEMENT application (icon?, display-name, description?, module+,
-		security-role*)>
-
-<!--
-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.
-
-Used in: module
--->
-<!ELEMENT alt-dd (#PCDATA)>
-
-<!--
-The connector element specifies the URI of a resource adapter archive
-file, relative to the top level of the application package.
-
-Used in: module
--->
-<!ELEMENT connector (#PCDATA)>
-
-<!--
-The context-root element specifies the context root of a web
-application.
-
-Used in: web
--->
-<!ELEMENT context-root (#PCDATA)>
-
-<!--
-The description element is used to provide text describing the parent
-element.  The description element should include any information that
-the application ear file producer wants to provide to the consumer of
-the application ear file (i.e., to the Deployer). Typically, the tools
-used by the application ear file consumer will display the description
-when processing the parent element that contains the description.
-
-Used in: application, security-role
--->
-<!ELEMENT description (#PCDATA)>
-
-<!--
-The display-name element contains a short name that is intended to be
-displayed by tools.  The display name need not be unique.
-
-Used in: application
-
-Example:
-
-<display-name>Employee Self Service</display-name>
--->
-<!ELEMENT display-name (#PCDATA)>
-
-<!--
-The ejb element specifies the URI of an ejb-jar, relative to the top
-level of the application package.
-
-Used in: module
--->
-<!ELEMENT ejb (#PCDATA)>
-
-<!--
-The icon element contains small-icon and large-icon elements that
-specify the file names for small and a large GIF or JPEG icon images
-used to represent the parent element in a GUI tool.
-
-Used in: application
--->
-<!ELEMENT icon (small-icon?, large-icon?)>
-
-<!--
-The java element specifies the URI of a java application client module,
-relative to the top level of the application package.
-
-Used in: module
--->
-<!ELEMENT java (#PCDATA)>
-
-<!--
-The large-icon element contains the name of a file
-containing a large (32 x 32) icon image. The file
-name is a relative path within the application's
-ear file.
-
-The image may be either in the JPEG or GIF format.
-The icon can be used by tools.
-
-Used in: icon
-
-Example:
-
-<large-icon>employee-service-icon32x32.jpg</large-icon>
--->
-<!ELEMENT large-icon (#PCDATA)>
-
-<!--
-The module element represents 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.
-
-The application deployment descriptor must have one module element for
-each J2EE module in the application package.
-
-Used in: application
--->
-<!ELEMENT module ((connector | ejb | java | web), alt-dd?)>
-
-<!--
-The role-name element contains the name of a security role.
-
-The name must conform to the lexical rules for an NMTOKEN.
-
-Used in: security-role
--->
-<!ELEMENT role-name (#PCDATA)>
-
-<!--
-The security-role element contains the definition of a security
-role. The definition consists of an optional description of the
-security role, and the security role name.
-
-Used in: application
-
-Example:
-
-    <security-role>
-	<description>
-	    This role includes all employees who are authorized
-	    to access the employee service application.
-	</description>
-	<role-name>employee</role-name>
-    </security-role>
--->
-<!ELEMENT security-role (description?, role-name)>
-
-<!--
-The 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 application's
-ear file.
-
-The image may be either in the JPEG or GIF format.
-The icon can be used by tools.
-
-Used in: icon
-
-Example:
-
-<small-icon>employee-service-icon16x16.jpg</small-icon>
--->
-<!ELEMENT small-icon (#PCDATA)>
-
-<!--
-The web element contains the web-uri and context-root of a web
-application module.
-
-Used in: module
--->
-<!ELEMENT web (web-uri, context-root)>
-
-<!--
-The web-uri element specifies the URI of a web application file,
-relative to the top level of the application package.
-
-Used in: web
--->
-<!ELEMENT web-uri (#PCDATA)>
-
-<!--
-The ID mechanism is to allow tools that produce additional deployment
-information (i.e., information beyond the standard deployment
-descriptor information) to store the non-standard information in a
-separate file, and easily refer from these tool-specific files to the
-information in the standard deployment descriptor.
-
-Tools are not allowed to add the non-standard information into the
-standard deployment descriptor.
--->
-
-<!ATTLIST alt-dd id ID #IMPLIED>
-<!ATTLIST application id ID #IMPLIED>
-<!ATTLIST connector id ID #IMPLIED>
-<!ATTLIST context-root id ID #IMPLIED>
-<!ATTLIST description id ID #IMPLIED>
-<!ATTLIST display-name id ID #IMPLIED>
-<!ATTLIST ejb id ID #IMPLIED>
-<!ATTLIST icon id ID #IMPLIED>
-<!ATTLIST java id ID #IMPLIED>
-<!ATTLIST large-icon id ID #IMPLIED>
-<!ATTLIST module id ID #IMPLIED>
-<!ATTLIST role-name id ID #IMPLIED>
-<!ATTLIST security-role id ID #IMPLIED>
-<!ATTLIST small-icon id ID #IMPLIED>
-<!ATTLIST web id ID #IMPLIED>
-<!ATTLIST web-uri id ID #IMPLIED>

jboss-as-7.2.0.Final/docs/schema/application_1_4.xsd

@@ -1,314 +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.13 02/11/03
-    </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.  The deployment descriptor must be named
-	"META-INF/application.xml" in the application's ear file.
-	All application deployment descriptors must indicate
-	the application schema by using the J2EE namespace:
-
-	http://java.sun.com/xml/ns/j2ee
-
-	and indicate 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:group ref="j2ee:descriptionGroup"/>
-      <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: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:attribute name="id" type="xsd:ID"/>
-  </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:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </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:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-</xsd:schema>
-

jboss-as-7.2.0.Final/docs/schema/application_5.xsd

@@ -1,334 +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/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_5.xsds	1.17 08/05/05
-    </xsd:documentation>
-  </xsd:annotation>
-
-  <xsd:annotation>
-    <xsd:documentation>
-
-      Copyright 2003-2006 Sun Microsystems, Inc.
-      4150 Network Circle
-      Santa Clara, California 95054
-      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 5 deployment
-	descriptor.  The deployment descriptor must be named
-	"META-INF/application.xml" in the application's ear file.
-	All application deployment descriptors must indicate
-	the application 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 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_5.xsd"
-	      version="5">
-	      ...
-	    </application>
-
-	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_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" type="javaee:applicationType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The application element is the root element of a Java EE
-	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="javaee:module/javaee:web"/>
-      <xsd:field    xpath="javaee: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="javaee:security-role"/>
-      <xsd:field    xpath="javaee: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:group ref="javaee:descriptionGroup"/>
-      <xsd:element name="module"
-		   type="javaee:moduleType"
-		   maxOccurs="unbounded">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The application deployment descriptor must have one
-	    module element for each Java EE 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="javaee:security-roleType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="library-directory"
-		   type="javaee:pathType"
-		   minOccurs="0"
-		   maxOccurs="1">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The library-directory element specifies the pathname
-	    of a directory within the application package, relative
-	    to the top level of the application package.  All files
-	    named "*.jar" in this directory must be made available
-	    in the class path of all components included in this
-	    application package.  If this element isn't specified,
-	    the directory named "lib" is searched.  An empty element
-	    may be used to disable searching.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-    </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="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="moduleType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The moduleType defines a single Java EE 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="javaee: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="javaee: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="javaee: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="javaee:webType"/>
-      </xsd:choice>
-      <xsd:element name="alt-dd"
-		   type="javaee: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 Java EE 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:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </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="javaee: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="javaee:string">
-
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The context-root element specifies the context root
-	    of a web application.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-</xsd:schema>
-

jboss-as-7.2.0.Final/docs/schema/application_6.xsd

@@ -1,394 +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/javaee"
-            xmlns:javaee="http://java.sun.com/xml/ns/javaee"
-            xmlns:xsd="http://www.w3.org/2001/XMLSchema"
-            elementFormDefault="qualified"
-            attributeFormDefault="unqualified"
-            version="6">
-  <xsd:annotation>
-    <xsd:documentation>
-
-      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
-      
-      Copyright 2003-2009 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 6 deployment
-      descriptor.  The deployment descriptor must be named
-      "META-INF/application.xml" in the application's ear file.
-      All application deployment descriptors must indicate
-      the application 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 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_6.xsd"
-      version="6">
-      ...
-      </application>
-      
-      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_6.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_6.xsd"/>
-
-
-<!-- **************************************************** -->
-
-  <xsd:element name="application"
-               type="javaee:applicationType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The application element is the root element of a Java EE
-        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="javaee:module/javaee:web"/>
-      <xsd:field xpath="javaee: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="javaee:security-role"/>
-      <xsd:field xpath="javaee: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="application-name"
-                   type="javaee:string"
-                   minOccurs="0"/>
-      <xsd:group ref="javaee:descriptionGroup"/>
-      <xsd:element name="initialize-in-order"
-                   type="javaee:generic-booleanType"
-                   minOccurs="0"
-                   maxOccurs="1">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            If initialize-in-order is true, modules must be initialized
-            in the order they're listed in this deployment descriptor,
-            with the exception of application client modules, which can
-            be initialized in any order.
-            If initialize-in-order is not set or set to false, the order
-            of initialization is unspecified and may be product-dependent.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="module"
-                   type="javaee:moduleType"
-                   maxOccurs="unbounded">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The application deployment descriptor must have one
-            module element for each Java EE 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="javaee:security-roleType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="library-directory"
-                   type="javaee:pathType"
-                   minOccurs="0"
-                   maxOccurs="1">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The library-directory element specifies the pathname
-            of a directory within the application package, relative
-            to the top level of the application package.  All files
-            named "*.jar" in this directory must be made available
-            in the class path of all components included in this
-            application package.  If this element isn't specified,
-            the directory named "lib" is searched.  An empty element
-            may be used to disable searching.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="env-entry"
-                   type="javaee:env-entryType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="ejb-ref"
-                   type="javaee:ejb-refType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="ejb-local-ref"
-                   type="javaee:ejb-local-refType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:group ref="javaee:service-refGroup"/>
-      <xsd:element name="resource-ref"
-                   type="javaee:resource-refType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="resource-env-ref"
-                   type="javaee:resource-env-refType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="message-destination-ref"
-                   type="javaee:message-destination-refType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="persistence-context-ref"
-                   type="javaee:persistence-context-refType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="persistence-unit-ref"
-                   type="javaee:persistence-unit-refType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="message-destination"
-                   type="javaee:message-destinationType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="data-source"
-                   type="javaee:data-sourceType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="version"
-                   type="javaee:dewey-versionType"
-                   fixed="6"
-                   use="required">
-      <xsd:annotation>
-        <xsd:documentation>
-
-          The required value for the version is 6.
-          
-        </xsd:documentation>
-      </xsd:annotation>
-    </xsd:attribute>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="moduleType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The moduleType defines a single Java EE 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="javaee: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="javaee: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="javaee: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="javaee:webType"/>
-      </xsd:choice>
-      <xsd:element name="alt-dd"
-                   type="javaee: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 Java EE 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:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </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="javaee: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="javaee:string">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The context-root element specifies the context root
-            of a web application.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-</xsd:schema>

jboss-as-7.2.0.Final/docs/schema/ejb-jar_1_1.dtd

@@ -1,894 +0,0 @@
-<!--
-Copyright 1999 Sun Microsystems, Inc. 901 San Antonio Road,
-Palo Alto, CA  94303, U.S.A.  All rights reserved.
- 
-This product or document is protected by copyright and distributed
-under licenses restricting its use, copying, distribution, and
-decompilation.  No part of this product or documentation 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, JavaServer Pages, Java 
-Naming and Directory Interface, JDBC, JDK, JavaMail and Enterprise JavaBeans, 
-are trademarks or registered trademarks of Sun Microsystems, Inc in the U.S. 
-and other countries.
-
-All SPARC trademarks are used under license and are trademarks
-or registered trademarks of SPARC International, Inc.
-in the U.S. and other countries. Products bearing SPARC
-trademarks are based upon an architecture developed by Sun Microsystems, Inc. 
-
-PostScript is a registered trademark of Adobe Systems, Inc. 
-
- 
-Federal Acquisitions: Commercial Software - Government Users Subject to 
-Standard License Terms and Conditions.
-
-
- 
-DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
-CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY
-IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
-PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT
-TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY
-INVALID.
-
-_________________________________________________________________________
-Copyright 1999 Sun Microsystems, Inc., 
-901 San Antonio Road, Palo Alto, CA  94303, Etats-Unis. 
-Tous droits re'serve's.
- 
-
-Ce produit ou document est prote'ge' par un copyright et distribue' avec 
-des licences qui en restreignent l'utilisation, la copie, la distribution,
-et la de'compilation.  Aucune partie de ce produit ou de sa documentation
-associe'e ne peut e^tre reproduite sous aucune forme, par quelque moyen 
-que ce soit, sans l'autorisation pre'alable et e'crite de Sun et de ses 
-bailleurs de licence, s'il y en a.  
-
-Le logiciel de'tenu par des tiers, et qui comprend la technologie 
-relative aux polices de caracte`res, est prote'ge' par un copyright 
-et licencie' par des fournisseurs de Sun.
- 
-Sun, Sun Microsystems, le logo Sun, Solaris, Java, JavaServer Pages, Java 
-Naming and Directory Interface, JDBC, JDK, JavaMail, et Enterprise JavaBeans,  
-sont des marques de fabrique ou des marques de'pose'es de Sun 
-Microsystems, Inc. aux Etats-Unis et dans d'autres pays.
- 
-Toutes les marques SPARC sont utilise'es sous licence et sont
-des marques de fabrique ou des marques de'pose'es de SPARC
-International, Inc. aux Etats-Unis et  dans
-d'autres pays. Les produits portant les marques SPARC sont
-base's sur une architecture de'veloppe'e par Sun Microsystems, Inc.  
-
-Postcript est une marque enregistre'e d'Adobe Systems Inc. 
- 
-LA DOCUMENTATION EST FOURNIE "EN L'ETAT" ET TOUTES AUTRES CONDITIONS,
-DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES,
-DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT
-TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE
-A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFACON.
--->
-
-
-<!--
-This is the XML DTD for the EJB 1.1 deployment descriptor.
--->
-
-
-<!--
-The assembly-descriptor element contains application-assembly information.
-
-The application-assembly information consists of the following parts:
-the definition of security roles, the definition of method permissions,
-and the definition of transaction attributes for enterprise beans with
-container-managed transaction demarcation.
-
-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.
-
-Used in: ejb-jar
--->
-<!ELEMENT assembly-descriptor (security-role*, method-permission*,
-		container-transaction*)>
-
-<!--
-The cmp-field element describes a container-managed field. The field
-element includes an optional description of the field, and the name of
-the field.
-
-Used in: entity
--->
-<!ELEMENT cmp-field (description?, field-name)>
-
-<!--
-The container-transaction element specifies how the container must
-manage transaction scopes for the enterprise bean's method invocations.
-The element consists of an optional description, a list of method
-elements, and a transaction attribute.The transaction attribute is to
-be applied to all the specified methods.
-
-Used in: assembly-descriptor
--->
-<!ELEMENT container-transaction (description?, method+,
-		trans-attribute)>
-
-<!--
-The description element is used by the ejb-jar file producer to provide
-text describing the parent element.
-
-The description element should include any information that the ejb-jar
-file producer wants to provide to the consumer of the ejb-jar file
-(i.e. to the Deployer). Typically, the tools used by the ejb-jar file
-consumer will display the description when processing the parent
-element.
-
-Used in: cmp-field, container-transaction, ejb-jar, entity, env-entry,
-ejb-ref, method, method-permission, resource-ref, security-role,
-security-role-ref, and session.
--->
-<!ELEMENT description (#PCDATA)>
-
-<!--
-The display-name element contains a short name that is intended to be
-display by tools.
-
-Used in: ejb-jar, session, and entity
-
-Example:
-	<display-name>Employee Self Service</display-name>
--->
-<!ELEMENT display-name (#PCDATA)>
-
-<!--
-The ejb-class element contains the fully-qualified name of the
-enterprise bean's class.
-
-Used in: entity and session
-
-Example:
-		<ejb-class>com.wombat.empl.EmployeeServiceBean</ejb-class>
--->
-<!ELEMENT ejb-class (#PCDATA)>
-
-<!--
-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. The Deployer should make the ejb-client JAR
-file accessible to the client's class-loader.
-
-Used in: ejb-jar
-
-Example:
-	<ejb-client-jar>employee_service_client.jar</ejb-client-jar>
--->
-<!ELEMENT ejb-client-jar (#PCDATA)>
-
-<!--
-The ejb-jar element is the root element of the EJB deployment
-descriptor. It contains an optional description of the ejb-jar file,
-optional display name, optional small icon file name, optional large
-icon file name, mandatory structural information about all included
-enterprise beans, optional application-assembly descriptor, and an
-optional name of an ejb-client-jar file for the ejb-jar.
--->
-<!ELEMENT ejb-jar (description?, display-name?, small-icon?,
-		large-icon?, enterprise-beans, assembly-descriptor?,
-		ejb-client-jar?)>
-
-<!--
-The ejb-link element is used in the ejb-ref element to specify that an
-EJB reference is linked to another enterprise bean in the ejb-jar
-file.
-
-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.
-
-Used in: ejb-ref
-
-Example:
-		<ejb-link>EmployeeRecord</ejb-link>
--->
-<!ELEMENT ejb-link (#PCDATA)>
-
-<!--
-The ejb-name element specifies an enterprise bean's name. 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.
-
-The enterprise bean code does not depend on the name; therefore the
-name can be changed during the application-assembly process without
-breaking the enterprise bean's function.
-
-There is no architected relationship between the ejb-name in the
-deployment descriptor and the JNDI name that the Deployer will assign
-to the enterprise bean's home.
-
-The name must conform to the lexical rules for an NMTOKEN.
-
-Used in: entity, method, and session
-
-Example:
-		<ejb-name>EmployeeService</ejb-name>
--->
-<!ELEMENT ejb-name (#PCDATA)>
-
-<!--
-The ejb-ref element is used for the declaration of a reference to
-another enterprise bean's home. The declaration consists of an optional
-description; the EJB reference name used in the code of the referencing
-enterprise bean; the expected type of the referenced enterprise bean;
-the expected home and remote interfaces of the referenced enterprise
-bean; and an optional ejb-link information.
-
-The optional ejb-link element is used to specify the referenced
-enterprise bean. It is used typically in ejb-jar files that contain an
-assembled application.
-
-Used in: entity and session
--->
-<!ELEMENT ejb-ref (description?, ejb-ref-name, ejb-ref-type, home,
-		remote, ejb-link?)>
-
-<!--
-The ejb-ref-name element contains the name of an EJB reference. The EJB
-reference is an entry in the enterprise bean's environment.
-
-It is recommended that name is prefixed with "ejb/".
-
-Used in: ejb-ref
-
-Example:
-		<ejb-ref-name>ejb/Payroll</ejb-ref-name>
--->
-<!ELEMENT ejb-ref-name (#PCDATA)>
-
-<!--
-The ejb-ref-type element contains the expected type of the referenced
-enterprise bean.
-
-The ejb-ref-type element must be one of the following:
-		<ejb-ref-type>Entity</ejb-ref-type>
-		<ejb-ref-type>Session</ejb-ref-type>
-
-Used in: ejb-ref
--->
-<!ELEMENT ejb-ref-type (#PCDATA)>
-
-<!--
-The enterprise-beans element contains the declarations of one or more
-enterprise beans.
--->
-<!ELEMENT enterprise-beans (session | entity)+>
-
-<!--
-The entity element declares an entity bean. The declaration consists
-of: an optional description; optional display name; optional small icon
-file name; optional large icon file name; a name assigned to the
-enterprise bean in the deployment descriptor; the names of the entity
-bean's home and remote interfaces; 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 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 security role references;
-and an optional declaration of the bean's resource manager connection
-factory references.
-
-The optional primkey-field may be present in the descriptor if the
-entity's persistency-type is Container.
-
-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 persistency-type is Container, and none must not be present if
-the entity's persistence-type is Bean.
-
-Used in: enterprise-beans
--->
-<!ELEMENT entity (description?, display-name?, small-icon?,
-		large-icon?, ejb-name, home, remote, ejb-class,
-		persistence-type, prim-key-class, reentrant,
-		cmp-field*, primkey-field?, env-entry*,
-		ejb-ref*, security-role-ref*, resource-ref*)>
-
-<!--
-The env-entry element contains the declaration of an enterprise bean's
-environment entries. The declaration consists of an optional
-description, the name of the environment entry, and an optional value.
-
-Used in: entity and session
--->
-<!ELEMENT env-entry (description?, env-entry-name, env-entry-type,
-		env-entry-value?)>
-
-<!--
-The env-entry-name element contains the name of an enterprise bean's
-environment entry.
-
-Used in: env-entry
-
-Example:
-		<env-entry-name>minAmount</env-entry-name>
--->
-<!ELEMENT env-entry-name (#PCDATA)>
-
-<!--
-The env-entry-type element contains the fully-qualified Java type of
-the environment entry value that is expected by the enterprise bean's
-code.
-
-The following are the legal values of env-entry-type:
-java.lang.Boolean, java.lang.String, java.lang.Integer,
-java.lang.Double, java.lang.Byte, java.lang.Short, java.lang.Long, and
-java.lang.Float.
-
-Used in: env-entry
-
-Example:
-		<env-entry-type>java.lang.Boolean</env-entry-type>
--->
-<!ELEMENT env-entry-type (#PCDATA)>
-
-<!--
-The env-entry-value element contains the value of an enterprise bean's
-environment entry.
-
-Used in: env-entry
-
-Example:
-		<env-entry-value>100.00</env-entry-value>
--->
-<!ELEMENT env-entry-value (#PCDATA)>
-
-<!--
-The field-name element specifies the name of a container managed field.
-The name must be a public field of the enterprise bean class or one of
-its superclasses.
-
-Used in: cmp-field
-
-Example:
-		<field-name>firstName</field-Name>
--->
-<!ELEMENT field-name (#PCDATA)>
-
-<!--
-The home element contains the fully-qualified name of the enterprise
-bean's home interface.
-
-Used in: ejb-ref, entity, and session
-
-Example:
-		<home>com.aardvark.payroll.PayrollHome</home>
--->
-<!ELEMENT home (#PCDATA)>
-
-<!--
-The large-icon element contains the name of a file containing a large
-(32 x 32) icon image. The file name is relative path within the ejb-jar
-file.
-
-The image must be either in the JPEG or GIF format, and the file name
-must end with the suffix ".jpg" or ".gif" respectively.  The icon can
-be used by tools.
-
-Example:
-	<large-icon>employee-service-icon32x32.jpg</large-icon>
--->
-<!ELEMENT large-icon (#PCDATA)>
-
-<!--
-The method element is used to denote a method of an enterprise bean's
-home or remote interface, or a set of methods. The ejb-name element
-must be the name of one of the enterprise beans in declared in the
-deployment descriptor; the optional method-intf element allows to
-distinguish between a method with the same signature that is defined in
-both the home and remote interface; 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 the method element syntax:
-
-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 and remote 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[][]).
-
-
-Used in: method-permission and container-transaction
-
-Examples:
-
-    Style 1: The following method element refers to all the methods of
-		the EmployeeService bean's home and remote 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:
-
-    		<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.
-
-    		<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 defined in the home
-   interface and a method with the same name and signature that is
-   defined in the remote interface.
-
-	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 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>
-
--->
-<!ELEMENT method (description?, ejb-name, method-intf?, method-name,
-			method-params?)>
-
-<!--
-The method-intf element allows a method element to differentiate
-between the methods with the same name and signature that are defined
-in both the remote and home interfaces.
-
-The method-intf element must be one of the following:
-		<method-intf>Home</method-intf>
-		<method-intf>Remote</method-intf>
-
-Used in: method
--->
-<!ELEMENT method-intf (#PCDATA)>
-
-<!--
-The method-name element 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 remote and home
-interfaces.
-
-Used in: method
--->
-<!ELEMENT method-name (#PCDATA)>
-
-<!--
-The method-param element contains the fully-qualified Java type name of
-a method parameter.
-
-Used in: method-params
--->
-<!ELEMENT method-param (#PCDATA)>
-
-<!--
-The method-params element contains a list of the fully-qualified Java
-type names of the method parameters.
-
-Used in: method
--->
-<!ELEMENT method-params (method-param*)>
-
-<!--
-The method-permission element specifies that one or more security roles
-are allowed to invoke one or more enterprise bean methods. The
-method-permission element consists of an optional description, a list
-of security role names, and a list of method elements.
-
-The security roles used in the method-permission element must be
-defined in the security-role element of the deployment descriptor, and
-the methods must be methods defined in the enterprise bean's remote
-and/or home interfaces.
-
-Used in: assembly-descriptor
--->
-<!ELEMENT method-permission (description?, role-name+, method+)>
-
-<!--
-The persistence-type element specifies an entity bean's persistence
-management type.
-
-The persistence-type element must be one of the two following:
-		<persistence-type>Bean</persistence-type>
-		<persistence-type>Container</persistence-type>
-
-Used in: entity
--->
-<!ELEMENT persistence-type (#PCDATA)>
-
-<!--
-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.
-
-Used in: entity
-
-Examples:
-	<prim-key-class>java.lang.String</prim-key-class>
-	<prim-key-class>com.wombat.empl.EmployeeID</prim-key-class>
-	<prim-key-class>java.lang.Object</prim-key-class>
-
--->
-<!ELEMENT prim-key-class (#PCDATA)>
-
-<!--
-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.
-
-Used in: entity
-
-Example:
-	<primkey-field>EmployeeId</primkey-field>
--->
-<!ELEMENT primkey-field (#PCDATA)>
-
-<!--
-The reentrant element specifies whether an entity bean is reentrant or not.
-
-The reentrant element must be one of the two following:
-		<reentrant>True</reentrant>
-		<reentrant>False</reentrant>
-
-Used in: entity
--->
-<!ELEMENT reentrant (#PCDATA)>
-
-<!--
-The remote element contains the fully-qualified name of the enterprise
-bean's remote interface.
-
-Used in: ejb-ref, entity, and session
-
-Example:
-		<remote>com.wombat.empl.EmployeeService</remote>
--->
-<!ELEMENT remote (#PCDATA)>
-
-<!--
-The res-auth element specifies whether the enterprise bean code signs
-on programmatically to the resource manager, or whether the Container
-will sign on to the resource manager on behalf of the bean. In the
-latter case, the Container uses information that is supplied by the
-Deployer.
-
-The value of this element must be one of the two following:
-		<res-auth>Application</res-auth>
-		<res-auth>Container</res-auth>
--->
-<!ELEMENT res-auth (#PCDATA)>
-
-<!--
-The res-ref-name element specifies the name of a resource manager
-connection factory reference.
-
-Used in: resource-ref
--->
-<!ELEMENT res-ref-name (#PCDATA)>
-
-<!--
-The res-type element specifies the type of the data source. The type is
-specified by the Java interface (or class) expected to be implemented
-by the data source.
-
-Used in: resource-ref
--->
-<!ELEMENT res-type (#PCDATA)>
-
-<!--
-The resource-ref element contains a declaration of enterprise bean'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 enterprise bean code, and the type of authentication (bean or
-container).
-
-Used in: entity and session
-
-Example:
-		<resource-ref>
-			<res-ref-name>EmployeeAppDB</res-ref-name>
-			<res-type>javax.sql.DataSource</res-type>
-			<res-auth>Container</res-auth>
-		</resource-ref>
--->
-<!ELEMENT resource-ref (description?, res-ref-name, res-type,
-			res-auth)>
-
-<!--
-The role-link element is used to link a security role reference to a
-defined security role. The role-link element must contain the name of
-one of the security roles defined in the security-role elements.
-
-Used in: security-role-ref
--->
-<!ELEMENT role-link (#PCDATA)>
-
-<!--
-The role-name element contains the name of a security role.
-
-The name must conform to the lexical rules for an NMTOKEN.
-
-Used in: method-permission, security-role, and security-role-ref
--->
-<!ELEMENT role-name (#PCDATA)>
-
-<!--
-The security-role element contains the definition of a security role.
-The definition consists of an optional description of the security
-role, and the security role name.
-
-Used in: assembly-descriptor
-
-Example:
-		<security-role>
-			<description>
-				This role includes all employees who
-				are authorized to access the employee
-				service application.
-			</description>
-			<role-name>employee</role-name>
-		</security-role>
--->
-<!ELEMENT security-role (description?, role-name)>
-
-<!--
-The security-role-ref element contains the declaration of a security
-role reference in the enterprise bean's code. The declaration consists
-of an optional description, the security role name used in the code,
-and an optional link to a defined security role.
-
-The value of the role-name element must be the String used as the
-parameter to the EJBContext.isCallerInRole(String roleName) method.
-
-The value of the role-link element must be the name of one of the
-security roles defined in the security-role elements.
-
-Used in: entity and session
-
--->
-<!ELEMENT security-role-ref (description?, role-name, role-link?)>
-
-<!--
-The session-type element describes whether the session bean is a
-stateful session, or stateless session.
-
-The session-type element must be one of the two following:
-		<session-type>Stateful</session-type>
-		<session-type>Stateless</session-type>
--->
-<!ELEMENT session-type (#PCDATA)>
-
-<!--
-The session element declares an session bean. The declaration consists
-of: an optional description; optional display name; optional small icon
-file name; optional large icon file name; a name assigned to the
-enterprise bean in the deployment description; the names of the session
-bean's home and remote interfaces; 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 security role references;
-and an optional declaration of the bean's resource manager connection
-factory references.
-
-The elements that are optional are "optional" in the sense that they
-are omitted when if lists represented by them are empty.
-
-Used in: enterprise-beans
--->
-<!ELEMENT session (description?, display-name?, small-icon?,
-		large-icon?, ejb-name, home, remote, ejb-class,
-		session-type, transaction-type, env-entry*,
-		ejb-ref*, security-role-ref*, resource-ref*)>
-
-<!--
-The small-icon element contains the name of a file containing a small
-(16 x 16) icon image. The file name is relative path within the ejb-jar
-file.
-
-The image must be either in the JPEG or GIF format, and the file name
-must end with the suffix ".jpg" or ".gif" respectively.
-
-The icon can be used by tools.
-
-Example:
-	<small-icon>employee-service-icon16x16.jpg</small-icon>
--->
-<!ELEMENT small-icon (#PCDATA)>
-
-<!--
-The transaction-type element specifies an enterprise bean's transaction
-management type.
-
-The transaction-type element must be one of the two following:
-		<transaction-type>Bean</transaction-type>
-		<transaction-type>Container</transaction-type>
-
-Used in: session
--->
-<!ELEMENT transaction-type (#PCDATA)>
-
-<!--
-The trans-attribute element specifies how the container must manage the
-transaction boundaries when delegating a method invocation to an
-enterprise bean's business method.
-
-The value of trans-attribute must be one of the following:
-		<trans-attribute>NotSupported</trans-attribute>
-		<trans-attribute>Supports</trans-attribute>
-		<trans-attribute>Required</trans-attribute>
-		<trans-attribute>RequiresNew</trans-attribute>
-		<trans-attribute>Mandatory</trans-attribute>
-		<trans-attribute>Never</trans-attribute>
-
-Used in: container-transaction
--->
-<!ELEMENT trans-attribute (#PCDATA)>
-
-<!--
-The ID mechanism is to allow tools that produce additional deployment
-information (i.e information beyond the standard EJB deployment
-descriptor information) to store the non-standard information in a
-separate file, and easily refer from these tools-specific files to the
-information in the standard deployment descriptor.
-
-The EJB architecture does not allow the tools to add the non-standard
-information into the EJB deployment descriptor.
--->
-<!ATTLIST assembly-descriptor id ID #IMPLIED>
-<!ATTLIST cmp-field id ID #IMPLIED>
-<!ATTLIST container-transaction id ID #IMPLIED>
-<!ATTLIST description id ID #IMPLIED>
-<!ATTLIST display-name id ID #IMPLIED>
-<!ATTLIST ejb-class id ID #IMPLIED>
-<!ATTLIST ejb-client-jar id ID #IMPLIED>
-<!ATTLIST ejb-jar id ID #IMPLIED>
-<!ATTLIST ejb-link id ID #IMPLIED>
-<!ATTLIST ejb-name id ID #IMPLIED>
-<!ATTLIST ejb-ref id ID #IMPLIED>
-<!ATTLIST ejb-ref-name id ID #IMPLIED>
-<!ATTLIST ejb-ref-type id ID #IMPLIED>
-<!ATTLIST enterprise-beans id ID #IMPLIED>
-<!ATTLIST entity id ID #IMPLIED>
-<!ATTLIST env-entry id ID #IMPLIED>
-<!ATTLIST env-entry-name id ID #IMPLIED>
-<!ATTLIST env-entry-type id ID #IMPLIED>
-<!ATTLIST env-entry-value id ID #IMPLIED>
-<!ATTLIST field-name id ID #IMPLIED>
-<!ATTLIST home id ID #IMPLIED>
-<!ATTLIST large-icon id ID #IMPLIED>
-<!ATTLIST method id ID #IMPLIED>
-<!ATTLIST method-intf id ID #IMPLIED>
-<!ATTLIST method-name id ID #IMPLIED>
-<!ATTLIST method-param id ID #IMPLIED>
-<!ATTLIST method-params id ID #IMPLIED>
-<!ATTLIST method-permission id ID #IMPLIED>
-<!ATTLIST persistence-type id ID #IMPLIED>
-<!ATTLIST prim-key-class id ID #IMPLIED>
-<!ATTLIST primkey-field id ID #IMPLIED>
-<!ATTLIST reentrant id ID #IMPLIED>
-<!ATTLIST remote id ID #IMPLIED>
-<!ATTLIST res-auth id ID #IMPLIED>
-<!ATTLIST res-ref-name id ID #IMPLIED>
-<!ATTLIST res-type id ID #IMPLIED>
-<!ATTLIST resource-ref id ID #IMPLIED>
-<!ATTLIST role-link id ID #IMPLIED>
-<!ATTLIST role-name id ID #IMPLIED>
-<!ATTLIST security-role id ID #IMPLIED>
-<!ATTLIST security-role-ref id ID #IMPLIED>
-<!ATTLIST session-type id ID #IMPLIED>
-<!ATTLIST session id ID #IMPLIED>
-<!ATTLIST small-icon id ID #IMPLIED>
-<!ATTLIST transaction-type id ID #IMPLIED>
-<!ATTLIST trans-attribute id ID #IMPLIED>

jboss-as-7.2.0.Final/docs/schema/ejb-jar_2_0.dtd

@@ -1,1660 +0,0 @@
-<!--
-Copyright 2000-2001 Sun Microsystems, Inc. 901 San Antonio Road,
-Palo Alto, CA  94303, U.S.A.  All rights reserved.
-
-This product or document is protected by copyright and distributed
-under licenses restricting its use, copying, distribution, and
-decompilation.  No part of this product or documentation 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, JavaServer Pages, Java
-Naming and Directory Interface, JDBC, JDK, JavaMail and Enterprise JavaBeans,
-are trademarks or registered trademarks of Sun Microsystems, Inc in the U.S.
-and other countries.
-
-All SPARC trademarks are used under license and are trademarks
-or registered trademarks of SPARC International, Inc.
-in the U.S. and other countries. Products bearing SPARC
-trademarks are based upon an architecture developed by Sun Microsystems, Inc.
-
-PostScript is a registered trademark of Adobe Systems, Inc.
-
-Federal Acquisitions: Commercial Software - Government Users Subject to
-Standard License Terms and Conditions.
-
-DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
-CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY
-IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
-PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT
-TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY
-INVALID.
-
-_________________________________________________________________________
-
-Copyright 2000-2001 Sun Microsystems, Inc.,
-901 San Antonio Road, Palo Alto, CA  94303, Etats-Unis.
-Tous droits re'serve's.
-
-
-Ce produit ou document est prote'ge' par un copyright et distribue' avec
-des licences qui en restreignent l'utilisation, la copie, la distribution,
-et la de'compilation.  Aucune partie de ce produit ou de sa documentation
-associe'e ne peut e^tre reproduite sous aucune forme, par quelque moyen
-que ce soit, sans l'autorisation pre'alable et e'crite de Sun et de ses
-bailleurs de licence, s'il y en a.
-
-Le logiciel de'tenu par des tiers, et qui comprend la technologie
-relative aux polices de caracte`res, est prote'ge' par un copyright
-et licencie' par des fournisseurs de Sun.
-
-Sun, Sun Microsystems, le logo Sun, Solaris, Java, JavaServer Pages, Java
-Naming and Directory Interface, JDBC, JDK, JavaMail, et Enterprise JavaBeans,
-sont des marques de fabrique ou des marques de'pose'es de Sun
-Microsystems, Inc. aux Etats-Unis et dans d'autres pays.
-
-Toutes les marques SPARC sont utilise'es sous licence et sont
-des marques de fabrique ou des marques de'pose'es de SPARC
-International, Inc. aux Etats-Unis et  dans
-d'autres pays. Les produits portant les marques SPARC sont
-base's sur une architecture de'veloppe'e par Sun Microsystems, Inc.
-
-Postcript est une marque enregistre'e d'Adobe Systems Inc.
-
-LA DOCUMENTATION EST FOURNIE "EN L'ETAT" ET TOUTES AUTRES CONDITIONS,
-DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES,
-DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT
-TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE
-A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFACON.
--->
-
-<!--
-This is the XML DTD for the EJB 2.0 deployment descriptor.
-All EJB 2.0 deployment descriptors must include a DOCTYPE
-of the following form:
-
-  <!DOCTYPE ejb-jar PUBLIC
-	"-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN"
-	"http://java.sun.com/dtd/ejb-jar_2_0.dtd">
-
--->
-
-<!--
-The following conventions apply to all J2EE deployment descriptor
-elements unless indicated otherwise.
-
-- In elements that contain PCDATA, leading and trailing whitespace
-  in the data may be ignored.
-
-- In elements whose value is an "enumerated type", the value is
-  case sensitive.
-
-- In elements that specify a pathname to a file within the same
-  JAR file, relative filenames (i.e., those not starting with "/")
-  are considered relative to the root of the JAR file's namespace.
-  Absolute filenames (i.e., those starting with "/") also specify
-  names in the root of the JAR file's namespace.  In general, relative
-  names are preferred.  The exception is .war files where absolute
-  names are preferred for consistency with the servlet API.
--->
-
-
-<!--
-The ejb-jar element is the root element of the EJB deployment
-descriptor. It contains
-
-	- an optional description of the ejb-jar file
-	- an optional display name
-	- an optional small icon file name
-	- an optional 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.
--->
-<!ELEMENT ejb-jar (description?, display-name?, small-icon?,
-large-icon?, enterprise-beans, relationships?, assembly-descriptor?,
-ejb-client-jar?)>
-
-<!--
-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.
-
-Used in: entity
--->
-<!ELEMENT abstract-schema-name (#PCDATA)>
-
-<!--
-
-The acknowledge-mode element specifies whether JMS AUTO_ACKNOWLEDGE or
-DUPS_OK_ACKNOWLEDGE message acknowledgment semantics should be used
-for the onMessage message of a message-driven bean that uses bean
-managed transaction demarcation.
-
-The acknowledge-mode element must be one of the two following:
-
-	<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
-	<acknowledge-mode>Dups-ok-acknowledge</acknowledgemode>
-
-Used in: message-driven
--->
-<!ELEMENT acknowledge-mode (#PCDATA)>
-
-<!--
-The assembly-descriptor element contains 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 deployment.
-
-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.
-
-Used in: ejb-jar
--->
-<!ELEMENT assembly-descriptor (security-role*, method-permission*,
-container-transaction*, exclude-list?)>
-
-<!--
-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.
-
-Used in: ejb-relationship-role
--->
-<!ELEMENT cascade-delete EMPTY>
-
-<!--
-The cmp-field element describes a container-managed field. The
-field element includes an optional description of the field, and the
-name of the field.
-
-Used in: entity
--->
-<!ELEMENT cmp-field (description?, field-name)>
-
-<!--
-The cmp-version element specifies the version of an entity bean
-with container-managed persistence.
-
-The cmp-version element must be one of the two following:
-
-	<cmp-version>1.x</cmp-version>
-	<cmp-version>2.x</cmp-version>
-
-The default value of the cmp-version element is 2.x.
-
-Used in: entity
--->
-<!ELEMENT cmp-version (#PCDATA)>
-
-<!--
-
-The cmr-field element 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.
-
-Used in: ejb-relationship-role
--->
-<!ELEMENT cmr-field (description?, cmr-field-name, cmr-field-type?)>
-
-<!--
-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 consists of the name of the field specified by
-cmr-field-name in which the first letter is uppercased, prefixed by
-"get" or "set".
-
-Used in: cmr-field
--->
-<!ELEMENT cmr-field-name (#PCDATA)>
-
-<!--
-The cmr-field-type element specifies the class of a
-collection-valued logical relationship field in the entity bean
-class. The value of the cmr-field-type element must be either:
-java.util.Collection or java.util.Set.
-
-Used in: cmr-field
--->
-<!ELEMENT cmr-field-type (#PCDATA)>
-
-<!--
-The container-transaction element specifies how the container
-must manage transaction scopes for the enterprise bean's method
-invocations. The element consists of an optional description, a list
-of method elements, and a transaction attribute. The transaction
-attribute is to be applied to all the specified methods.
-
-Used in: assembly-descriptor
--->
-<!ELEMENT container-transaction (description?, method+, trans-attribute)>
-
-<!--
-The description element is used to provide text describing the parent
-element.  The description element should include any information that
-the enterprise bean ejb-jar file producer wants to provide to the consumer of
-the enterprise bean ejb-jar file (i.e., to the Deployer). Typically, the tools
-used by the enterprise bean ejb-jar file consumer will display the description
-when processing the parent element that contains the description.
-
-Used in: cmp-field, cmr-field, container-transaction, ejb-jar,
-ejb-local-ref, ejb-ref, ejb-relation, ejb-relationship-role, entity,
-env-entry, exclude-list, message-driven, method, method-permission,
-query, relationship-role-source, relationships, resource-env-ref,
-resource-ref, run-as, security-identity, security-role,
-security-role-ref, session
--->
-<!ELEMENT description (#PCDATA)>
-
-<!--
-The destination-type element specifies the type of the JMS
-destination. The type is specified by the Java interface expected to
-be implemented by the destination.
-
-The destination-type element must be one of the two following:
-
-<destination-type>javax.jms.Queue</destination-type>
-<destination-type>javax.jms.Topic</destination-type>
-
-Used in: message-driven-destination
--->
-<!ELEMENT destination-type (#PCDATA)>
-
-<!--
-The display-name element contains a short name that is intended to be
-displayed by tools.  The display name need not be unique.
-
-Used in: ejb-jar, entity, message-driven, session
-
-Example:
-
-<display-name>Employee Self Service</display-name>
--->
-<!ELEMENT display-name (#PCDATA)>
-
-<!--
-The ejb-class element contains the fully-qualified name of the
-enterprise bean's class.
-
-Used in: entity, message-driven, session
-
-Example:
-
-<ejb-class>com.wombat.empl.EmployeeServiceBean</ejb-class>
--->
-<!ELEMENT ejb-class (#PCDATA)>
-
-<!--
-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.
-
-Used in: ejb-jar
-
-Example:
-
-<ejb-client-jar>employee_service_client.jar</ejb-client-jar>
--->
-<!ELEMENT ejb-client-jar (#PCDATA)>
-
-<!--
-The ejb-link element is used in the ejb-ref or ejb-local-ref
-elements to specify that an EJB reference is linked to an
-enterprise bean.
-
-The 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 ejb-jar file
-containing the enterprise bean that is referencing the enterprise bean.
-This allows multiple enterprise beans with the same ejb-name to be
-uniquely identified.
-
-Used in: ejb-local-ref, ejb-ref
-
-Examples:
-
-	<ejb-link>EmployeeRecord</ejb-link>
-
-	<ejb-link>../products/product.jar#ProductEJB</ejb-link>
-
--->
-<!ELEMENT ejb-link (#PCDATA)>
-
-<!--
-The ejb-local-ref element is used for the declaration of a reference to
-an enterprise bean's local home. The declaration consists of:
-
-	- an optional description
-	- the EJB reference name used in the code of the enterprise bean
-	  that's referencing the enterprise bean
-	- the expected type of the referenced enterprise bean
-	- the expected local home and local interfaces of the referenced
-	  enterprise bean
-	- optional ejb-link information, used to specify the referenced
-	  enterprise bean
-
-Used in: entity, message-driven, session
--->
-<!ELEMENT ejb-local-ref (description?, ejb-ref-name, ejb-ref-type,
-		local-home, local, ejb-link?)>
-
-<!--
-The ejb-name element specifies an enterprise bean's name. 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 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 with cmp-version 2.x must conform to the
-lexical rules for an NMTOKEN. The name for an entity bean with
-cmp-version 2.x must not be a reserved literal in EJB QL.
-
-Used in: entity, message-driven, method, relationship-role-source,
-session
-
-Example:
-
-<ejb-name>EmployeeService</ejb-name>
--->
-<!ELEMENT ejb-name (#PCDATA)>
-
-<!--
-The ejb-ql element contains the EJB QL query string that defines
-a finder or select query. This element is defined within the scope of
-a query element whose contents specify the finder or the select method
-that uses the query. The content must be a valid EJB QL query string
-for the entity bean for which the query is specified.
-
-The ejb-ql element must be specified for all queries that are
-expressible in EJB QL.
-
-Used in: query
-
-Example:
-<query>
-    <query-method>
-        <method-name>ejbSelectPendingLineitems</method-name>
-        <method-params/>
-    </query-method>
-    <ejb-ql>SELECT ENTITY(l) FROM LineItems l WHERE l.shipped <> TRUE
-    </ejb-ql>
-</query>
-
--->
-<!ELEMENT ejb-ql (#PCDATA)>
-
-<!--
-The ejb-ref element is used for the declaration of a reference to
-an enterprise bean's home. The declaration consists of:
-
-	- an optional description
-	- the EJB reference name used in the code of
-	  the enterprise bean that's referencing the enterprise bean
-	- the expected type of the referenced enterprise bean
-	- the expected home and remote interfaces of the referenced
-	  enterprise bean
-	- optional ejb-link information, used to specify the referenced
-	  enterprise bean
-
-Used in: entity, message-driven, session
--->
-<!ELEMENT ejb-ref (description?, ejb-ref-name, ejb-ref-type,
-		home, remote, ejb-link?)>
-
-<!--
-The ejb-ref-name element contains the name of an EJB reference. The
-EJB reference is an entry in the enterprise bean's environment and is
-relative to the java:comp/env context.  The name must be unique
-within the enterprise bean.
-
-It is recommended that name is prefixed with "ejb/".
-
-Used in: ejb-local-ref, ejb-ref
-
-Example:
-
-<ejb-ref-name>ejb/Payroll</ejb-ref-name>
--->
-<!ELEMENT ejb-ref-name (#PCDATA)>
-
-<!--
-The ejb-ref-type element contains the expected type of the
-referenced enterprise bean.
-
-The ejb-ref-type element must be one of the following:
-
-	<ejb-ref-type>Entity</ejb-ref-type>
-	<ejb-ref-type>Session</ejb-ref-type>
-
-Used in: ejb-local-ref, ejb-ref
--->
-<!ELEMENT ejb-ref-type (#PCDATA)>
-
-<!--
-
-The ejb-relation element describes a relationship between two
-entity beans with container managed persistence.  An ejb-relation
-element 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.
-
-Used in: relationships
--->
-<!ELEMENT ejb-relation (description?, ejb-relation-name?, ejb-relationship-role,
-ejb-relationship-role)>
-
-<!--
-The ejb-relation-name element provides a unique name for a relationship.
-
-Used in: ejb-relation
--->
-<!ELEMENT ejb-relation-name (#PCDATA)>
-
-<!--
-The ejb-relationship-role element describes a role within a
-relationship. There are two roles in each relationship.
-
-The ejb-relationship-role element 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.
-
-Used in: ejb-relation
-
-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>
-...
--->
-<!ELEMENT ejb-relationship-role (description?, ejb-relationship-role-name?,
-multiplicity, cascade-delete?, relationship-role-source, cmr-field?)>
-
-<!--
-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.
-
-Used in: ejb-relationship-role
--->
-<!ELEMENT ejb-relationship-role-name (#PCDATA)>
-
-<!--
-The enterprise-beans element contains the declarations of one or more
-enterprise beans.
--->
-<!ELEMENT enterprise-beans (session | entity | message-driven)+>
-
-<!--
-The entity element declares an entity bean. The declaration
-consists of:
-
-	- an optional description
-	- an optional display name
-	- an optional small icon file name
-	- an optional large icon file name
-	- a unique name assigned to the enterprise bean
-	  in the deployment descriptor
-	- the names of the entity bean's home and component interfaces, if any
-	- the names of the entity bean's local home and local
-	  interface, 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 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 set of query declarations
-	  for finder and select methods for an entity
-	  bean with cmp-version 2.x.
-
-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 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.
-
-Used in: enterprise-beans
-
--->
-<!ELEMENT entity (description?, display-name?, small-icon?,
-		large-icon?, ejb-name, home?, remote?, local-home?,
-		local?, ejb-class, persistence-type, prim-key-class,
-		reentrant, cmp-version?, abstract-schema-name?,
-		cmp-field*, primkey-field?, env-entry*, ejb-ref*,
-		ejb-local-ref*, security-role-ref*, security-identity?,
-		resource-ref*, resource-env-ref*, query*)>
-
-<!--
-The env-entry element contains the declaration of an enterprise bean'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.
-
-Used in: entity, message-driven, session
--->
-<!ELEMENT env-entry (description?, env-entry-name, env-entry-type,
-		env-entry-value?)>
-
-<!--
-The env-entry-name element contains the name of an enterprise bean's
-environment entry.  The name is a JNDI name relative to the
-java:comp/env context.  The name must be unique within an enterprise bean.
-
-Used in: env-entry
-
-Example:
-
-<env-entry-name>minAmount</env-entry-name>
--->
-<!ELEMENT env-entry-name (#PCDATA)>
-
-<!--
-The env-entry-type element contains the fully-qualified Java type of
-the environment entry value that is expected by the enterprise bean's
-code.
-
-The following are the legal values of env-entry-type:
-
-	java.lang.Boolean
-	java.lang.Byte
-	java.lang.Character
-	java.lang.String
-	java.lang.Short
-	java.lang.Integer
-	java.lang.Long
-	java.lang.Float
-	java.lang.Double
-
-
-Used in: env-entry
-
-Example:
-
-<env-entry-type>java.lang.Boolean</env-entry-type>
--->
-<!ELEMENT env-entry-type (#PCDATA)>
-
-<!--
-The env-entry-value element contains the value of an enterprise bean'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.
-
-Used in: env-entry
-
-Example:
-
-<env-entry-value>100.00</env-entry-value>
--->
-<!ELEMENT env-entry-value (#PCDATA)>
-
-<!--
-The exclude list element defines a set of methods which the Assembler marks to
-be uncallable. It contains one or more methods.
-
-If the method permission relation contains methods that are in the
-exclude list, the Deployer must consider those methods to be
-uncallable.
-
-Used in: assembly-descriptor
--->
-<!ELEMENT exclude-list (description?, method+)>
-
-<!--
-The field-name element specifies the name of a container managed
-field. The name must be a public field of the enterprise bean class or
-one of its superclasses.
-
-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".
-
-Used in: cmp-field
-
-Example:
-
-
-	<field-name>firstName</field-Name>
-
--->
-<!ELEMENT field-name (#PCDATA)>
-
-<!--
-The home element contains the fully-qualified name of the enterprise
-bean's home interface.
-
-Used in: ejb-ref, entity, session
-
-Example:
-
-<home>com.aardvark.payroll.PayrollHome</home>
--->
-<!ELEMENT home (#PCDATA)>
-
-<!--
-The large-icon element contains the name of a file
-containing a large (32 x 32) icon image. The file
-name is a relative path within the enterprise bean's
-ejb-jar file.
-
-The image may be either in the JPEG or GIF format.
-The icon can be used by tools.
-
-Used in: ejb-jar, entity, message-driven, session
-
-Example:
-
-<large-icon>employee-service-icon32x32.jpg</large-icon>
--->
-<!ELEMENT large-icon (#PCDATA)>
-
-<!--
-
-The local element contains the fully-qualified name of the
-enterprise bean's local interface.
-
-Used in: ejb-local-ref, entity, session
-
--->
-<!ELEMENT local (#PCDATA)>
-
-<!--
-
-The local-home element contains the fully-qualified name of the
-enterprise bean's local home interface.
-
-Used in: ejb-local-ref, entity, session
--->
-<!ELEMENT local-home (#PCDATA)>
-
-<!--
-
-The message-driven element declares a message-driven bean. The
-declaration consists of:
-
-	- an optional description
-	- an optional display name
-	- an optional small icon file name
-	- an optional large icon file name
-	- a name assigned to the enterprise bean in
-	  the deployment descriptor
-	- the message-driven bean's implementation class
-	- the message-driven bean's transaction management type
-	- an optional declaration of the message-driven bean's
-	  message selector
-	- an optional declaration of the
-	  acknowledgment mode for the message-driven bean
-	  if bean-managed transaction demarcation is used
-	- an optional declaration of the
-	  intended destination type of the message-driven bean
-	- 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 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.
-
-Used in: enterprise-beans
--->
-<!ELEMENT message-driven (description?, display-name?, small-icon?,
-		large-icon?, ejb-name, ejb-class, transaction-type,
-		message-selector?, acknowledge-mode?,
-		message-driven-destination?, env-entry*, ejb-ref*,
-		ejb-local-ref*, security-identity?, resource-ref*,
-		resource-env-ref*)>
-
-<!--
-The message-driven-destination element provides advice to the Deployer
-as to whether a message-driven bean is intended for a Queue or a
-Topic. The declaration consists of: the type of the message-driven
-bean's intended destination and an optional declaration of whether a
-durable or non-durable subscription should be used if the
-destination-type is javax.jms.Topic.
-
-Used in: message-driven
--->
-<!ELEMENT message-driven-destination (destination-type,
-subscription-durability?)>
-
-<!--
-The message-selector element is used to specify the JMS message
-selector to be used in determining which messages a message-driven
-bean is to receive.
-
-Example:
-<message-selector>JMSType = `car' AND color = `blue' AND weight &gt; 2500
-</message-selector>
-
-Used in: message-driven
--->
-<!ELEMENT message-selector (#PCDATA)>
-
-<!--
-
-The method element is used to denote a method of an enterprise
-bean's home or component interface, or, in the case of a message-driven
-bean, the bean's onMessage method, or a set of 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 in both the home and component 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 the method element syntax:
-
-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 and component 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[][]).
-
-
-Used in: container-transaction, exclude-list, method-permission
-
-Examples:
-
-Style 1: The following method element refers to all the methods of
-the EmployeeService bean's home and component 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 and component 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 three 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>
-
--->
-<!ELEMENT method (description?, ejb-name, method-intf?, method-name,
-method-params?)>
-
-<!--
-
-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 component and home interfaces (e.g, in both an
-enterprise bean's remote and local interfaces; in both an enterprise bean's
-home and remote interfaces, etc.)
-
-The method-intf element must be one of the following:
-
-	<method-intf>Home</method-intf>
-	<method-intf>Remote</method-intf>
-	<method-intf>LocalHome</method-intf>
-	<method-intf>Local</method-intf>
-
-Used in: method, query-method
--->
-<!ELEMENT method-intf (#PCDATA)>
-
-<!--
-The method-name element 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 component and home
-interfaces.
-
-Used in: method, query-method
--->
-<!ELEMENT method-name (#PCDATA)>
-
-<!--
-The method-param element contains the fully-qualified Java type name
-of a method parameter.
-
-Used in: method-params
--->
-<!ELEMENT method-param (#PCDATA)>
-
-<!--
-The method-params element contains a list of the fully-qualified Java
-type names of the method parameters.
-
-Used in: method, query-method
--->
-<!ELEMENT method-params (method-param*)>
-
-<!--
-
-The method-permission element specifies that one or more security
-roles are allowed to invoke one or more enterprise bean methods. The
-method-permission element 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-permission element must be
-defined in the security-role element of the deployment descriptor, and
-the methods must be methods defined in the enterprise bean's component
-and/or home interfaces.
-
-
-Used in: assembly-descriptor
--->
-<!ELEMENT method-permission (description?, (role-name+|unchecked), method+)>
-
-<!--
-The multiplicity element describes the multiplicity of the role that
-participates in a relation.
-
-The multiplicity element must be one of the two following:
-
-	<multiplicity>One</multiplicity>
-	<multiplicity>Many</multiplicity>
-
-Used in: ejb-relationship-role
--->
-<!ELEMENT multiplicity (#PCDATA)>
-
-<!--
-The persistence-type element specifies an entity bean's persistence
-management type.
-
-The persistence-type element must be one of the two following:
-
-	<persistence-type>Bean</persistence-type>
-	<persistence-type>Container</persistence-type>
-
-Used in: entity
--->
-<!ELEMENT persistence-type (#PCDATA)>
-
-<!--
-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.
-
-Used in: entity
-
-Examples:
-
-	<prim-key-class>java.lang.String</prim-key-class>
-
-	<prim-key-class>com.wombat.empl.EmployeeID</prim-key-class>
-
-	<prim-key-class>java.lang.Object</prim-key-class>
-
--->
-<!ELEMENT prim-key-class (#PCDATA)>
-
-<!--
-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.
-
-Used in: entity
-
-Example:
-
-	<primkey-field>EmployeeId</primkey-field>
-
--->
-<!ELEMENT primkey-field (#PCDATA)>
-
-<!--
-The query element is used to specify 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 indicator which specifies how the abstract
-          schema type instance(s) must be mapped when results are
-          returned.
-    	- the EJB QL query string that defines the query.
-
-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
-when the query-method describes an ejbSelect query. The default value
-for the result-type-mapping element is "Local".
-
-
-Used in: entity
--->
-<!ELEMENT query (description?, query-method, result-type-mapping?, ejb-ql)>
-
-<!--
-The query-method element is used to specify 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.
-
-Used in: query
-
-Example:
-
-<query>
-    <description>Method finds large orders</description>
-    <query-method>
-        <method-name>findLargeOrders</method-name>
-        <method-params></method-params>
-    </query-method>
-    <ejb-ql>SELECT ENTITY(o) FROM Order o WHERE o.amount &gt; 1000</ejb-ql>
-</query>
-
--->
-<!ELEMENT query-method (method-name, method-intf?, method-params)>
-
-<!--
-The reentrant element specifies whether an entity bean is reentrant or
-not.
-
-The reentrant element must be one of the two following:
-
-	<reentrant>True</reentrant>
-	<reentrant>False</reentrant>
-
-Used in: entity
--->
-<!ELEMENT reentrant (#PCDATA)>
-
-<!--
-
-The relationship-role-source element designates the source of a role
-that participates in a relationship. A relationship-role-source
-element uniquely identifies an entity bean.
-
-Used in: ejb-relationship-role
--->
-<!ELEMENT relationship-role-source (description?, ejb-name)>
-
-<!--
-The relationships element describes the relationships in which
-entity beans with container managed persistence participate. The
-relationships element contains an optional description; and a list of
-ejb-relation elements, which specify the container managed
-relationships.
-
-
-Used in: ejb-jar
--->
-<!ELEMENT relationships (description?, ejb-relation+)>
-
-<!--
-The remote element contains the fully-qualified name of the enterprise
-bean's remote interface.
-
-Used in: ejb-ref, entity, session
-
-Example:
-
-<remote>com.wombat.empl.EmployeeService</remote>
--->
-<!ELEMENT remote (#PCDATA)>
-
-<!--
-The res-auth element specifies whether the enterprise bean code signs
-on programmatically to the resource manager, or whether the Container
-will sign on to the resource manager on behalf of the enterprise bean. In the
-latter case, the Container uses information that is supplied by the
-Deployer.
-
-The value of this element must be one of the two following:
-
-	<res-auth>Application</res-auth>
-	<res-auth>Container</res-auth>
-
-Used in: resource-ref
--->
-<!ELEMENT res-auth (#PCDATA)>
-
-<!--
-The res-ref-name element specifies the name of a resource manager
-connection factory reference.  The name is a JNDI name relative to the
-java:comp/env context.  The name must be unique within an enterprise bean.
-
-Used in: resource-ref
--->
-<!ELEMENT res-ref-name (#PCDATA)>
-
-<!--
-The res-sharing-scope element specifies whether connections obtained
-through the given resource manager connection factory reference can be
-shared. The value of this element, if specified, must be one of the
-two following:
-
-	<res-sharing-scope>Shareable</res-sharing-scope>
-	<res-sharing-scope>Unshareable</res-sharing-scope>
-
-The default value is Shareable.
-
-Used in: resource-ref
--->
-<!ELEMENT res-sharing-scope (#PCDATA)>
-
-<!--
-The res-type element specifies the type of the data source. The type
-is specified by the fully qualified Java language class or interface
-expected to be implemented by the data source.
-
-Used in: resource-ref
--->
-<!ELEMENT res-type (#PCDATA)>
-
-<!--
-The resource-env-ref element contains a declaration of an enterprise bean's
-reference to an administered object associated with a resource
-in the enterprise bean'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 enterprise bean code.
-
-Used in: entity, message-driven, session
-
-Example:
-
-<resource-env-ref>
-    <resource-env-ref-name>jms/StockQueue</resource-env-ref-name>
-    <resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
-</resource-env-ref>
--->
-<!ELEMENT resource-env-ref (description?, resource-env-ref-name,
-		resource-env-ref-type)>
-
-<!--
-The resource-env-ref-name element specifies the name of a resource
-environment reference; its value is the environment entry name used in
-the enterprise bean code.  The name is a JNDI name relative to the
-java:comp/env context and must be unique within an enterprise bean.
-
-Used in: resource-env-ref
--->
-<!ELEMENT resource-env-ref-name (#PCDATA)>
-
-<!--
-The resource-env-ref-type element specifies the type of a resource
-environment reference.  It is the fully qualified name of a Java
-language class or interface.
-
-Used in: resource-env-ref
--->
-<!ELEMENT resource-env-ref-type (#PCDATA)>
-
-<!--
-The resource-ref element contains a declaration of an enterprise bean'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 enterprise bean code, the type of authentication
-(Application or Container), and an optional specification of the
-shareability of connections obtained from the resource (Shareable or
-Unshareable).
-
-Used in: entity, message-driven, session
-
-Example:
-
-    <resource-ref>
-	<res-ref-name>jdbc/EmployeeAppDB</res-ref-name>
-	<res-type>javax.sql.DataSource</res-type>
-	<res-auth>Container</res-auth>
-	<res-sharing-scope>Shareable</res-sharing-scope>
-    </resource-ref>
--->
-<!ELEMENT resource-ref (description?, res-ref-name, res-type, res-auth,
-		res-sharing-scope?)>
-
-<!--
-
-The result-type-mapping element designates the mapping of the return
-value(s) of an select query.
-
-When the result type of a select query is an abstract schema type, the
-value of this element determines whether the select
-query returns remote or local entity objects.
-
-The result-type-mapping element must have one of the following:
-
-        <result-type-mapping>Local</result-type-mapping>
-        <result-type-mapping>Remote</result-type-mapping>
-
-Used in: query
--->
-<!ELEMENT result-type-mapping (#PCDATA)>
-
-<!--
-The role-link element is a reference to a defined security role. The
-role-link element must contain the name of one of the security roles
-defined in the security-role elements.
-
-Used in: security-role-ref
--->
-<!ELEMENT role-link (#PCDATA)>
-
-<!--
-The role-name element contains the name of a security role.
-
-The name must conform to the lexical rules for an NMTOKEN.
-
-Used in: method-permission, run-as, security-role, security-role-ref
--->
-<!ELEMENT role-name (#PCDATA)>
-
-<!--
-The run-as element specifies the run-as identity to be used for the
-execution of the enterprise bean. It contains an optional description, and
-the name of a security role.
-
-Used in: security-identity
--->
-<!ELEMENT run-as (description?, role-name)>
-
-<!--
-
-The security-identity element 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.
-
-Used in: entity, message-driven, session
--->
-<!ELEMENT security-identity (description?, (use-caller-identity|run-as))>
-
-<!--
-The security-role element contains the definition of a security
-role. The definition consists of an optional description of the
-security role, and the security role name.
-
-Used in: assembly-descriptor
-
-Example:
-
-    <security-role>
-	<description>
-	    This role includes all employees who are authorized
-	    to access the employee service application.
-	</description>
-	<role-name>employee</role-name>
-    </security-role>
--->
-<!ELEMENT security-role (description?, role-name)>
-
-<!--
-The security-role-ref element contains the declaration of a security
-role reference in the enterprise bean's code. The declaration consists
-of an optional description, the security role name used in the code,
-and an optional link to a security role. If the security role is not
-specified, the Deployer must choose an appropriate security role.
-
-The value of the role-name element must be the String used as the
-parameter to the EJBContext.isCallerInRole(String roleName) method
-or the HttpServletRequest.isUserInRole(String role) method.
-
-Used in: entity, session
-
--->
-<!ELEMENT security-role-ref (description?, role-name, role-link?)>
-
-<!--
-The session element declares an session bean. The declaration consists
-of:
-	- an optional description
-	- an optional display name
-	- an optional small icon file name
-	- an optional 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 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 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.
-
-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.
-
-Used in: enterprise-beans
--->
-<!ELEMENT session (description?, display-name?, small-icon?,
-large-icon?, ejb-name, home?, remote?, local-home? , local?,
-ejb-class, session-type, transaction-type, env-entry*, ejb-ref*,
-ejb-local-ref*, security-role-ref*, security-identity?, resource-ref*,
-resource-env-ref*)>
-
-<!--
-The session-type element describes whether the session bean is a
-stateful session or stateless session.
-
-The session-type element must be one of the two following:
-
-	<session-type>Stateful</session-type>
-	<session-type>Stateless</session-type>
--->
-<!ELEMENT session-type (#PCDATA)>
-
-<!--
-The small-icon element contains the name of a file
-containing a small (16 x 16) icon image. The file
-name is a relative path within the enterprise bean's
-ejb-jar file.
-
-The image may be either in the JPEG or GIF format.
-The icon can be used by tools.
-
-Used in: ejb-jar, entity, message-driven, session
-
-Example:
-
-<small-icon>employee-service-icon16x16.jpg</small-icon>
--->
-<!ELEMENT small-icon (#PCDATA)>
-
-<!--
-The subscription-durability element specifies whether a JMS topic
-subscription is intended to be durable or nondurable.
-
-The subscription-durability element must be one of the two following:
-
-	<subscription-durability>Durable</subscription-durability>
-	<subscription-durability>NonDurable</subscription-durability>
-
-Used in: message-driven-destination
--->
-<!ELEMENT subscription-durability (#PCDATA)>
-
-<!--
-The trans-attribute element specifies how the container must manage
-the transaction boundaries when delegating a method invocation to an
-enterprise bean's business method.
-
-The value of trans-attribute must be one of the following:
-
-
-	<trans-attribute>NotSupported</trans-attribute>
-	<trans-attribute>Supports</trans-attribute>
-	<trans-attribute>Required</trans-attribute>
-	<trans-attribute>RequiresNew</trans-attribute>
-	<trans-attribute>Mandatory</trans-attribute>
-	<trans-attribute>Never</trans-attribute>
-
-Used in: container-transaction
--->
-<!ELEMENT trans-attribute (#PCDATA)>
-
-<!--
-The transaction-type element specifies an enterprise bean's
-transaction management type.
-
-The transaction-type element must be one of the two following:
-
-	<transaction-type>Bean</transaction-type>
-	<transaction-type>Container</transaction-type>
-
-Used in: message-driven, session
--->
-<!ELEMENT transaction-type (#PCDATA)>
-
-<!--
-The unchecked element specifies that a method is not checked for authorization
-by the container prior to invocation of the method.
-
-Used in: method-permission
--->
-<!ELEMENT unchecked EMPTY>
-
-<!--
-
-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.
-
-Used in: security-identity
--->
-<!ELEMENT use-caller-identity EMPTY>
-
-<!--
-The ID mechanism is to allow tools that produce additional deployment
-information (i.e., information beyond the standard deployment
-descriptor information) to store the non-standard information in a
-separate file, and easily refer from these tool-specific files to the
-information in the standard deployment descriptor.
-
-Tools are not allowed to add the non-standard information into the
-standard deployment descriptor.
--->
-
-<!ATTLIST abstract-schema-name id ID #IMPLIED>
-<!ATTLIST acknowledge-mode id ID #IMPLIED>
-<!ATTLIST assembly-descriptor id ID #IMPLIED>
-<!ATTLIST cascade-delete id ID #IMPLIED>
-<!ATTLIST cmp-field id ID #IMPLIED>
-<!ATTLIST cmp-version id ID #IMPLIED>
-<!ATTLIST cmr-field id ID #IMPLIED>
-<!ATTLIST cmr-field-name id ID #IMPLIED>
-<!ATTLIST cmr-field-type id ID #IMPLIED>
-<!ATTLIST container-transaction id ID #IMPLIED>
-<!ATTLIST description id ID #IMPLIED>
-<!ATTLIST destination-type id ID #IMPLIED>
-<!ATTLIST display-name id ID #IMPLIED>
-<!ATTLIST ejb-class id ID #IMPLIED>
-<!ATTLIST ejb-client-jar id ID #IMPLIED>
-<!ATTLIST ejb-jar id ID #IMPLIED>
-<!ATTLIST ejb-link id ID #IMPLIED>
-<!ATTLIST ejb-local-ref id ID #IMPLIED>
-<!ATTLIST ejb-name id ID #IMPLIED>
-<!ATTLIST ejb-ql id ID #IMPLIED>
-<!ATTLIST ejb-ref id ID #IMPLIED>
-<!ATTLIST ejb-ref-name id ID #IMPLIED>
-<!ATTLIST ejb-ref-type id ID #IMPLIED>
-<!ATTLIST ejb-relation id ID #IMPLIED>
-<!ATTLIST ejb-relation-name id ID #IMPLIED>
-<!ATTLIST ejb-relationship-role id ID #IMPLIED>
-<!ATTLIST ejb-relationship-role-name id ID #IMPLIED>
-<!ATTLIST enterprise-beans id ID #IMPLIED>
-<!ATTLIST entity id ID #IMPLIED>
-<!ATTLIST env-entry id ID #IMPLIED>
-<!ATTLIST env-entry-name id ID #IMPLIED>
-<!ATTLIST env-entry-type id ID #IMPLIED>
-<!ATTLIST env-entry-value id ID #IMPLIED>
-<!ATTLIST exclude-list id ID #IMPLIED>
-<!ATTLIST field-name id ID #IMPLIED>
-<!ATTLIST home id ID #IMPLIED>
-<!ATTLIST large-icon id ID #IMPLIED>
-<!ATTLIST local id ID #IMPLIED>
-<!ATTLIST local-home id ID #IMPLIED>
-<!ATTLIST message-driven id ID #IMPLIED>
-<!ATTLIST message-driven-destination id ID #IMPLIED>
-<!ATTLIST message-selector id ID #IMPLIED>
-<!ATTLIST method id ID #IMPLIED>
-<!ATTLIST method-intf id ID #IMPLIED>
-<!ATTLIST method-name id ID #IMPLIED>
-<!ATTLIST method-param id ID #IMPLIED>
-<!ATTLIST method-params id ID #IMPLIED>
-<!ATTLIST method-permission id ID #IMPLIED>
-<!ATTLIST multiplicity id ID #IMPLIED>
-<!ATTLIST persistence-type id ID #IMPLIED>
-<!ATTLIST prim-key-class id ID #IMPLIED>
-<!ATTLIST primkey-field id ID #IMPLIED>
-<!ATTLIST query id ID #IMPLIED>
-<!ATTLIST query-method id ID #IMPLIED>
-<!ATTLIST reentrant id ID #IMPLIED>
-<!ATTLIST relationship-role-source id ID #IMPLIED>
-<!ATTLIST relationships id ID #IMPLIED>
-<!ATTLIST remote id ID #IMPLIED>
-<!ATTLIST res-auth id ID #IMPLIED>
-<!ATTLIST res-ref-name id ID #IMPLIED>
-<!ATTLIST res-sharing-scope id ID #IMPLIED>
-<!ATTLIST res-type id ID #IMPLIED>
-<!ATTLIST resource-env-ref id ID #IMPLIED>
-<!ATTLIST resource-env-ref-name id ID #IMPLIED>
-<!ATTLIST resource-env-ref-type id ID #IMPLIED>
-<!ATTLIST resource-ref id ID #IMPLIED>
-<!ATTLIST result-type-mapping id ID #IMPLIED>
-<!ATTLIST role-link id ID #IMPLIED>
-<!ATTLIST role-name id ID #IMPLIED>
-<!ATTLIST run-as id ID #IMPLIED>
-<!ATTLIST security-identity id ID #IMPLIED>
-<!ATTLIST security-role id ID #IMPLIED>
-<!ATTLIST security-role-ref id ID #IMPLIED>
-<!ATTLIST session id ID #IMPLIED>
-<!ATTLIST session-type id ID #IMPLIED>
-<!ATTLIST small-icon id ID #IMPLIED>
-<!ATTLIST subscription-durability id ID #IMPLIED>
-<!ATTLIST trans-attribute id ID #IMPLIED>
-<!ATTLIST transaction-type id ID #IMPLIED>
-<!ATTLIST unchecked id ID #IMPLIED>
-<!ATTLIST use-caller-identity id ID #IMPLIED>

jboss-as-7.2.0.Final/docs/schema/ejb-jar_2_1.xsd

@@ -1,2207 +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.23 08/01/03
-    </xsd:documentation>
-  </xsd:annotation>
-
-  <xsd:annotation>
-    <xsd:documentation>
-
-      Copyright 2003 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 EJB 2.1 deployment descriptor.
-	The deployment descriptor must be named "META-INF/ejb-jar.xml" in
-	the EJB's jar file.  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>
-
-  <xsd: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:assembly-descriptor/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="j2ee:xsdStringType">
-	<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="j2ee:xsdStringType">
-	<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:attribute name="id" type="xsd:ID"/>
-  </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:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </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:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </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:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="j2ee:string">
-	<xsd:enumeration value="1.x"/>
-	<xsd:enumeration value="2.x"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="j2ee:string">
-	<xsd:enumeration value="java.util.Collection"/>
-	<xsd:enumeration value="java.util.Set"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <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:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </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:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="ejb-classType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  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:simpleContent>
-      <xsd:restriction base="j2ee:fully-qualified-classType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <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:group ref="j2ee:descriptionGroup"/>
-      <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>
-	    <![CDATA[
-
-	      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: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:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="ejb-nameType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  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:simpleContent>
-      <xsd:restriction base="j2ee:xsdNMTOKENType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <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:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="ejb-relationship-roleType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  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:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </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:attribute name="id" type="xsd:ID"/>
-  </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.
-
-	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:group ref="j2ee:descriptionGroup"/>
-      <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:group ref="j2ee:jndiEnvironmentRefsGroup"/>
-      <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="query"
-		   type="j2ee:queryType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </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:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <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
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:group ref="j2ee:descriptionGroup"/>
-      <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:group ref="j2ee:jndiEnvironmentRefsGroup"/>
-      <xsd:element name="security-identity"
-		   type="j2ee:security-identityType"
-		   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <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:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="j2ee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <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:attribute name="id" type="xsd:ID"/>
-  </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:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="methodType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  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:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="j2ee:string">
-	<xsd:enumeration value="One"/>
-	<xsd:enumeration value="Many"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="j2ee:string">
-	<xsd:enumeration value="Bean"/>
-	<xsd:enumeration value="Container"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="query-methodType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  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 &gt; 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:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </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.
-
-	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="j2ee:xsdStringType"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </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:attribute name="id" type="xsd:ID"/>
-  </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:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="j2ee:string">
-	<xsd:enumeration value="Local"/>
-	<xsd:enumeration value="Remote"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <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:attribute name="id" type="xsd:ID"/>
-  </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
-
-	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:group ref="j2ee:descriptionGroup"/>
-      <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:group ref="j2ee:jndiEnvironmentRefsGroup"/>
-      <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:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="j2ee:string">
-	<xsd:enumeration value="Stateful"/>
-	<xsd:enumeration value="Stateless"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <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:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="j2ee:string">
-	<xsd:enumeration value="Bean"/>
-	<xsd:enumeration value="Container"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-</xsd:schema>
-

jboss-as-7.2.0.Final/docs/schema/ejb-jar_3_0.xsd

@@ -1,2705 +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/javaee"
-	    xmlns:javaee="http://java.sun.com/xml/ns/javaee"
-	    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
-	    elementFormDefault="qualified"
-	    attributeFormDefault="unqualified"
-	    version="3.0">
-  <xsd:annotation>
-    <xsd:documentation>
-      @(#)ejb-jar_3_0.xsds	1.51 02/23/06
-    </xsd:documentation>
-  </xsd:annotation>
-
-  <xsd:annotation>
-    <xsd:documentation>
-
-      Copyright 2003-2006 Sun Microsystems, Inc.
-      4150 Network Circle
-      Santa Clara, California 95054
-      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 EJB 3.0 deployment descriptor.
-	The deployment descriptor must be named "META-INF/ejb-jar.xml" in
-	the EJB's jar file.  All EJB deployment descriptors must indicate
-	the ejb-jar schema by using the Java EE namespace:
-
-	http://java.sun.com/xml/ns/javaee
-
-	and by indicating the version of the schema by
-	using the version element as shown below:
-
-	    <ejb-jar 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/ejb-jar_3_0.xsd"
-	      version="3.0">
-	      ...
-	    </ejb-jar>
-
-	The instance documents may indicate the published version of
-	the schema using the xsi:schemaLocation attribute for the
-	Java EE namespace with the following location:
-
-	http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.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="ejb-jar" type="javaee: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="javaee:enterprise-beans/*"/>
-      <xsd:field    xpath="javaee:ejb-name"/>
-    </xsd:key>
-
-    <xsd:keyref name="ejb-name-references"
-		refer="javaee: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=".//javaee:ejb-relationship-role/javaee:relationship-role-source"/>
-      <xsd:field
-	   xpath="javaee: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="javaee:assembly-descriptor/javaee:security-role"/>
-      <xsd:field    xpath="javaee:role-name"/>
-    </xsd:key>
-
-    <xsd:keyref name="role-name-references"
-		refer="javaee:role-name-key">
-      <xsd:annotation>
-	<xsd:documentation>
-
-	  The keyref indicates the references from
-	  security-role-ref to a specified role-name.
-
-	</xsd:documentation>
-      </xsd:annotation>
-      <xsd:selector xpath="javaee:enterprise-beans/*/javaee:security-role-ref"/>
-      <xsd:field    xpath="javaee: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="javaee:xsdStringType">
-	<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="javaee:xsdStringType">
-	<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:attribute name="id" type="xsd:ID"/>
-  </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="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="activation-config-property"
-		   type="javaee:activation-config-propertyType"
-		   maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="application-exceptionType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The application-exceptionType declares an application
-        exception. The declaration consists of:
-
-            - the exception class. When the container receives
-              an exception of this type, it is required to
-              forward this exception as an applcation exception
-              to the client regardless of whether it is a checked
-              or unchecked exception.
-            - an optional rollback element. If this element is
-              set to true, the container must rollback the current
-              transaction before forwarding the exception to the
-              client.  If not specified, it defaults to false.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="exception-class"
-		   type="javaee:fully-qualified-classType"/>
-      <xsd:element name="rollback"
-                   type="javaee:true-falseType"
-                   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="around-invokeType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The around-invoke type specifies a method on a
-        class to be called during the around invoke portion of an
-        ejb invocation.  Note that each class may have only one
-        around invoke method and that the method may not be
-        overloaded.
-
-        If the class element is missing then
-        the class defining the callback is assumed to be the
-        interceptor class or component class in scope at the
-        location in the descriptor in which the around invoke
-        definition appears.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="class"
-                   type="javaee:fully-qualified-classType"
-                   minOccurs="0"/>
-      <xsd:element name="method-name"
-                   type="javaee:java-identifierType"/>
-    </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, the definition
-        of interceptor bindings, a list of
-	methods to be excluded from being invoked, and a list of
-        exception types that should be treated as application exceptions.
-
-	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="javaee:security-roleType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="method-permission"
-		   type="javaee:method-permissionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="container-transaction"
-		   type="javaee:container-transactionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="interceptor-binding"
-                   type="javaee:interceptor-bindingType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="message-destination"
-		   type="javaee:message-destinationType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="exclude-list"
-		   type="javaee:exclude-listType"
-		   minOccurs="0"/>
-      <xsd:element name="application-exception"
-                   type="javaee:application-exceptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </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="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="field-name"
-		   type="javaee: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:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="javaee:string">
-	<xsd:enumeration value="1.x"/>
-	<xsd:enumeration value="2.x"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="javaee:string">
-	<xsd:enumeration value="java.util.Collection"/>
-	<xsd:enumeration value="java.util.Set"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <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="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="cmr-field-name"
-		   type="javaee: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="javaee:cmr-field-typeType"
-		   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </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="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="method"
-		   type="javaee:methodType"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="trans-attribute"
-		   type="javaee:trans-attributeType"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="ejb-classType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  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:simpleContent>
-      <xsd:restriction base="javaee:fully-qualified-classType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <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
-	    - structural information about all included
-	      enterprise beans that is not specified through
-              annotations
-            - structural information about interceptor classes
-	    - 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:group ref="javaee:descriptionGroup"/>
-      <xsd:element name="enterprise-beans"
-		   type="javaee:enterprise-beansType"
-                   minOccurs="0"/>
-      <xsd:element name="interceptors"
-		   type="javaee:interceptorsType"
-                   minOccurs="0"/>
-      <xsd:element name="relationships"
-		   type="javaee: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="javaee:ejb-relation"/>
-	  <xsd:field    xpath="javaee:ejb-relation-name"/>
-	</xsd:unique>
-      </xsd:element>
-      <xsd:element name="assembly-descriptor"
-		   type="javaee: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="javaee:pathType"
-		   minOccurs="0">
-	<xsd:annotation>
-	  <xsd:documentation>
-	    <![CDATA[
-
-	      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:sequence>
-    <xsd:attribute name="version"
-		   type="javaee:dewey-versionType"
-		   fixed="3.0"
-		   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: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:complexType name="ejb-nameType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  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:simpleContent>
-      <xsd:restriction base="javaee:xsdNMTOKENType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <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="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="ejb-relation-name"
-		   type="javaee: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="javaee:ejb-relationship-roleType"/>
-      <xsd:element name="ejb-relationship-role"
-		   type="javaee:ejb-relationship-roleType"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="ejb-relationship-roleType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  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="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="ejb-relationship-role-name"
-		   type="javaee: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="javaee:multiplicityType"/>
-      <xsd:element name="cascade-delete"
-		   type="javaee: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="javaee:relationship-role-sourceType"/>
-      <xsd:element name="cmr-field"
-		   type="javaee:cmr-fieldType"
-		   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </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="javaee: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="javaee:ejb-local-ref"/>
-	  <xsd:field    xpath="javaee: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="javaee:ejb-ref"/>
-	  <xsd:field    xpath="javaee: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="javaee:resource-env-ref"/>
-	  <xsd:field    xpath="javaee: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="javaee:message-destination-ref"/>
-	  <xsd:field    xpath="javaee: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="javaee:resource-ref"/>
-	  <xsd:field    xpath="javaee: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="javaee:env-entry"/>
-	  <xsd:field    xpath="javaee:env-entry-name"/>
-	</xsd:unique>
-      </xsd:element>
-
-      <xsd:element name="entity"
-		   type="javaee: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="javaee:ejb-local-ref"/>
-	  <xsd:field    xpath="javaee: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="javaee:ejb-ref"/>
-	  <xsd:field    xpath="javaee: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="javaee:resource-env-ref"/>
-	  <xsd:field    xpath="javaee: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="javaee:message-destination-ref"/>
-	  <xsd:field    xpath="javaee: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="javaee:resource-ref"/>
-	  <xsd:field    xpath="javaee: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="javaee:env-entry"/>
-	  <xsd:field    xpath="javaee:env-entry-name"/>
-	</xsd:unique>
-      </xsd:element>
-
-      <xsd:element name="message-driven"
-		   type="javaee: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="javaee:ejb-local-ref"/>
-	  <xsd:field    xpath="javaee: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="javaee:ejb-ref"/>
-	  <xsd:field    xpath="javaee: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="javaee:resource-env-ref"/>
-	  <xsd:field    xpath="javaee: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="javaee:message-destination-ref"/>
-	  <xsd:field    xpath="javaee: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="javaee:resource-ref"/>
-	  <xsd:field    xpath="javaee: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="javaee:env-entry"/>
-	  <xsd:field    xpath="javaee:env-entry-name"/>
-	</xsd:unique>
-      </xsd:element>
-
-    </xsd:choice>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </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
-            - an optional mapped-name element that can be used to provide
-              vendor-specific deployment information such as the physical
-              jndi-name of the entity bean's remote home interface. This
-              element is not required to be supported by all implementations.
-              Any use of this element is non-portable.
-	    - 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 optional entity bean's persistence management type. If
-              this element is not specified it is defaulted to Container.
-	    - 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.
-
-	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:group ref="javaee:descriptionGroup"/>
-      <xsd:element name="ejb-name"
-		   type="javaee:ejb-nameType"/>
-      <xsd:element name="mapped-name"
-		   type="javaee:xsdStringType"
-		   minOccurs="0"/>
-      <xsd:element name="home"
-		   type="javaee:homeType"
-		   minOccurs="0"/>
-      <xsd:element name="remote"
-		   type="javaee:remoteType"
-		   minOccurs="0"/>
-      <xsd:element name="local-home"
-		   type="javaee:local-homeType"
-		   minOccurs="0"/>
-      <xsd:element name="local"
-		   type="javaee:localType"
-		   minOccurs="0"/>
-      <xsd:element name="ejb-class"
-		   type="javaee:ejb-classType"/>
-      <xsd:element name="persistence-type"
-		   type="javaee:persistence-typeType"/>
-      <xsd:element name="prim-key-class"
-		   type="javaee: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="javaee: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="javaee:cmp-versionType"
-		   minOccurs="0"/>
-      <xsd:element name="abstract-schema-name"
-		   type="javaee: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="javaee:cmp-fieldType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="primkey-field"
-		   type="javaee: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:group ref="javaee:jndiEnvironmentRefsGroup"/>
-      <xsd:element name="security-role-ref"
-		   type="javaee:security-role-refType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-      <xsd:element name="security-identity"
-		   type="javaee:security-identityType"
-		   minOccurs="0"/>
-      <xsd:element name="query"
-		   type="javaee:queryType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </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="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="method"
-		   type="javaee:methodType"
-		   maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="init-methodType">
-    <xsd:sequence>
-      <xsd:element name="create-method"
-		   type="javaee:named-methodType"/>
-      <xsd:element name="bean-method"
-		   type="javaee:named-methodType"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="interceptor-bindingType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The interceptor-bindingType element describes the binding of
-        interceptor classes to beans within the ejb-jar.
-        It consists of :
-
-          - An optional description.
-          - The name of an ejb within the ejb-jar or the wildcard value "*",
-            which is used to define interceptors that are bound to all
-            beans in the ejb-jar.
-          - A list of interceptor classes that are bound to the contents of
-            the ejb-name element or a specification of the total ordering
-            over the interceptors defined for the given level and above.
-          - An optional exclude-default-interceptors element.  If set to true,
-            specifies that default interceptors are not to be applied to
-            a bean-class and/or business method.
-          - An optional exclude-class-interceptors element.  If set to true,
-            specifies that class interceptors are not to be applied to
-            a business method.
-          - An optional set of method elements for describing the name/params
-            of a method-level interceptor.
-
-         Interceptors bound to all classes using the wildcard syntax
-         "*" are default interceptors for the components in the ejb-jar.
-         In addition, interceptors may be bound at the level of the bean
-         class (class-level interceptors) or business methods (method-level
-         interceptors ).
-
-         The binding of interceptors to classes is additive.  If interceptors
-         are bound at the class-level and/or default-level as well as the
-         method-level, both class-level and/or default-level as well as
-         method-level will apply.
-
-         There are four possible styles of the interceptor element syntax :
-
-         1.
-         <interceptor-binding>
-           <ejb-name>*</ejb-name>
-           <interceptor-class>INTERCEPTOR</interceptor-class>
-         </interceptor-binding>
-
-         Specifying the ejb-name as the wildcard value "*" designates
-         default interceptors (interceptors that apply to all session and
-         message-driven beans contained in the ejb-jar).
-
-         2.
-         <interceptor-binding>
-           <ejb-name>EJBNAME</ejb-name>
-           <interceptor-class>INTERCEPTOR</interceptor-class>
-         </interceptor-binding>
-
-         This style is used to refer to interceptors associated with the
-         specified enterprise bean(class-level interceptors).
-
-         3.
-         <interceptor-binding>
-           <ejb-name>EJBNAME</ejb-name>
-           <interceptor-class>INTERCEPTOR</interceptor-class>
-           <method>
-             <method-name>METHOD</method-name>
-           </method>
-         </interceptor-binding>
-
-         This style is used to associate a method-level interceptor with
-         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.  Method-level
-         interceptors can only be associated with business methods of the
-         bean class.   Note that the wildcard value "*" cannot be used
-         to specify method-level interceptors.
-
-         4.
-         <interceptor-binding>
-           <ejb-name>EJBNAME</ejb-name>
-           <interceptor-class>INTERCEPTOR</interceptor-class>
-           <method>
-             <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>
-         </interceptor-binding>
-
-         This style is used to associate a method-level interceptor with
-         the specified method of the specified enterprise bean.  This
-         style is used to refer to a single method within a set of methods
-         with an overloaded name.  The values 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[][]).
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="ejb-name"
-		   type="javaee:string"/>
-      <xsd:choice>
-        <xsd:element name="interceptor-class"
-                     type="javaee:fully-qualified-classType"
-		     minOccurs="0"
-                     maxOccurs="unbounded"/>
-        <xsd:element name="interceptor-order"
-		     type="javaee:interceptor-orderType"
-		     minOccurs="1"/>
-      </xsd:choice>
-      <xsd:element name="exclude-default-interceptors"
-		   type="javaee:true-falseType"
-		   minOccurs="0"/>
-      <xsd:element name="exclude-class-interceptors"
-		   type="javaee:true-falseType"
-		   minOccurs="0"/>
-      <xsd:element name="method"
-		   type="javaee:named-methodType"
-                   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="interceptor-orderType">
-    <xsd:annotation>
-      <xsd:documentation>
-        The interceptor-orderType element describes a total ordering
-        of interceptor classes.
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-
-      <xsd:element name="interceptor-class"
-                   type="javaee:fully-qualified-classType"
-		   minOccurs="1"
-                   maxOccurs="unbounded"/>
-
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="interceptorType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The interceptorType element declares information about a single
-        interceptor class.  It consists of :
-
-            - An optional description.
-            - The fully-qualified name of the interceptor class.
-            - An optional list of around invoke methods declared on the
-              interceptor class and/or its super-classes.
-            - An optional list environment dependencies for the interceptor
-              class and/or its super-classes.
-            - An optional list of post-activate methods declared on the
-              interceptor class and/or its super-classes.
-            - An optional list of pre-passivate methods declared on the
-              interceptor class and/or its super-classes.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="interceptor-class"
-		   type="javaee:fully-qualified-classType"/>
-      <xsd:element name="around-invoke"
-                   type="javaee:around-invokeType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/>
-      <xsd:element name="post-activate"
-                   type="javaee:lifecycle-callbackType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="pre-passivate"
-                   type="javaee:lifecycle-callbackType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="interceptorsType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The interceptorsType element declares one or more interceptor
-        classes used by components within this ejb-jar.  The declaration
-        consists of :
-
-            - An optional description.
-            - One or more interceptor elements.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="interceptor"
-		   type="javaee:interceptorType"
-		   maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <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
-            - an optional mapped-name element that can be used to provide
-              vendor-specific deployment information such as the physical
-              jndi-name of destination from which this message-driven bean
-              should consume.  This element is not required to be supported
-              by all implementations.  Any use of this element is non-portable.
-	    - the message-driven bean's implementation class
-	    - an optional declaration of the bean's messaging
-	      type
-            - an optional declaration of the bean's timeout method.
-	    - the optional message-driven bean's transaction management
-              type. If it is not defined, it is defaulted to Container.
-	    - 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 list of the message-driven bean class and/or
-              superclass around-invoke methods.
-	    - 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
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:group ref="javaee:descriptionGroup"/>
-      <xsd:element name="ejb-name"
-		   type="javaee:ejb-nameType"/>
-      <xsd:element name="mapped-name"
-		   type="javaee:xsdStringType"
-		   minOccurs="0"/>
-      <xsd:element name="ejb-class"
-		   type="javaee:ejb-classType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-             The ejb-class element specifies the fully qualified name
-             of the bean class for this ejb.  It is required unless
-             there is a component-defining annotation for the same
-             ejb-name.
-
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="messaging-type"
-		   type="javaee:fully-qualified-classType"
-		   minOccurs="0">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The messaging-type element specifies the message
-	    listener interface of the message-driven bean.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="timeout-method"
-                   type="javaee:named-methodType"
-                   minOccurs="0"/>
-      <xsd:element name="transaction-type"
-		   type="javaee:transaction-typeType"
-                   minOccurs="0"/>
-      <xsd:element name="message-destination-type"
-		   type="javaee:message-destination-typeType"
-		   minOccurs="0"/>
-      <xsd:element name="message-destination-link"
-		   type="javaee:message-destination-linkType"
-		   minOccurs="0"/>
-      <xsd:element name="activation-config"
-		   type="javaee:activation-configType"
-		   minOccurs="0"/>
-      <xsd:element name="around-invoke"
-                   type="javaee:around-invokeType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/>
-      <xsd:element name="security-identity"
-		   type="javaee:security-identityType"
-		   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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 Local applies to
-        both local component interface and local business interface.
-        Similarly, Remote applies to both remote component interface
-        and the remote business interface.
-
-	The method-intf element must be one of the following:
-
-	    Home
-	    Remote
-	    LocalHome
-	    Local
-	    ServiceEndpoint
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-	<xsd:enumeration value="Home"/>
-	<xsd:enumeration value="Remote"/>
-	<xsd:enumeration value="LocalHome"/>
-	<xsd:enumeration value="Local"/>
-	<xsd:enumeration value="ServiceEndpoint"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="javaee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <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="javaee: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:attribute name="id" type="xsd:ID"/>
-  </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 business, home, component
-        and/or web service endpoint interfaces.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:choice>
-	<xsd:element name="role-name"
-		     type="javaee:role-nameType"
-		     maxOccurs="unbounded"/>
-	<xsd:element name="unchecked"
-		     type="javaee: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="javaee:methodType"
-		   maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="methodType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The methodType is used to denote a method of an enterprise
-	  bean's business, 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 business, home, component, and/or web service
-          endpoint nterfaces; 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 business, 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 business, 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 business, home, component,
-          and/or web service endpoint interfaces with the same name and
-	  signature. However, if the same method is a method of both the
-          local business interface, and the local component interface,
-          the same attribute applies to the method for both interfaces.
-          Likewise, if the same method is a method of both the remote
-          business interface and the remote component interface, the same
-          attribute applies to the method for both interfaces.
-
-	  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 three 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
-          and the remote business 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="javaee:descriptionType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-      <xsd:element name="ejb-name"
-		   type="javaee:ejb-nameType"/>
-      <xsd:element name="method-intf"
-		   type="javaee:method-intfType"
-		   minOccurs="0">
-      </xsd:element>
-      <xsd:element name="method-name"
-		   type="javaee:method-nameType"/>
-      <xsd:element name="method-params"
-		   type="javaee:method-paramsType"
-		   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="javaee:string">
-	<xsd:enumeration value="One"/>
-	<xsd:enumeration value="Many"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="named-methodType">
-    <xsd:sequence>
-      <xsd:element name="method-name"
-		   type="javaee:string"/>
-      <xsd:element name="method-params"
-		   type="javaee:method-paramsType"
-		   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="javaee:string">
-	<xsd:enumeration value="Bean"/>
-	<xsd:enumeration value="Container"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="query-methodType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  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 &gt; 1000
-	      </ejb-ql>
-	  </query>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="method-name"
-		   type="javaee:method-nameType"/>
-      <xsd:element name="method-params"
-		   type="javaee:method-paramsType"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </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.
-
-	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="javaee:descriptionType" minOccurs="0"/>
-      <xsd:element name="query-method"
-		   type="javaee:query-methodType"/>
-      <xsd:element name="result-type-mapping"
-		   type="javaee:result-type-mappingType"
-		   minOccurs="0"/>
-      <xsd:element name="ejb-ql"
-		   type="javaee:xsdStringType"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </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="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="ejb-name"
-		   type="javaee:ejb-nameType"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </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="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="ejb-relation"
-		   type="javaee: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=".//javaee:ejb-relationship-role-name"/>
-	  <xsd:field
-	       xpath="."/>
-	</xsd:unique>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="remove-methodType">
-    <xsd:sequence>
-      <xsd:element name="bean-method"
-		   type="javaee:named-methodType"/>
-      <xsd:element name="retain-if-exception"
-		   type="javaee:true-falseType"
-		   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="javaee:string">
-	<xsd:enumeration value="Local"/>
-	<xsd:enumeration value="Remote"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <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="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:choice>
-	<xsd:element name="use-caller-identity"
-		     type="javaee: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="javaee:run-asType"/>
-      </xsd:choice>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </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
-            - an optional mapped-name element that can be used to provide
-              vendor-specific deployment information such as the physical
-              jndi-name of the session bean's remote home/business interface.
-              This element is not required to be supported by all
-              implementations. Any use of this element is non-portable.
-            - the names of all the remote or local business interfaces,
-              if any
-	    - 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
-            - an optional declaration of the session bean's timeout method.
-	    - the optional session bean's transaction management type.
-              If it is not present, it is defaulted to Container.
-            - an optional list of the session bean class and/or
-              superclass around-invoke methods.
-	    - 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
-
-	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:group ref="javaee:descriptionGroup"/>
-      <xsd:element name="ejb-name"
-		   type="javaee:ejb-nameType"/>
-      <xsd:element name="mapped-name"
-		   type="javaee:xsdStringType"
-		   minOccurs="0"/>
-      <xsd:element name="home"
-		   type="javaee:homeType"
-		   minOccurs="0"/>
-      <xsd:element name="remote"
-		   type="javaee:remoteType"
-		   minOccurs="0"/>
-      <xsd:element name="local-home"
-		   type="javaee:local-homeType"
-		   minOccurs="0"/>
-      <xsd:element name="local"
-		   type="javaee:localType"
-		   minOccurs="0"/>
-      <xsd:element name="business-local"
-		   type="javaee:fully-qualified-classType"
-		   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="business-remote"
-		   type="javaee:fully-qualified-classType"
-		   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="service-endpoint"
-		   type="javaee: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="javaee:ejb-classType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-             The ejb-class element specifies the fully qualified name
-             of the bean class for this ejb.  It is required unless
-             there is a component-defining annotation for the same
-             ejb-name.
-
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="session-type"
-		   type="javaee:session-typeType"
-                   minOccurs="0"/>
-      <xsd:element name="timeout-method"
-                   type="javaee:named-methodType"
-                   minOccurs="0"/>
-      <xsd:element name="init-method"
-                   type="javaee:init-methodType"
-                   minOccurs="0"
-                   maxOccurs="unbounded">
-        <xsd:annotation>
-	  <xsd:documentation>
-
-	    The init-method element specifies the mappings for
-	    EJB 2.x style create methods for an EJB 3.0 bean.
-	    This element can only be specified for stateful
-            session beans.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="remove-method"
-                   type="javaee:remove-methodType"
-                   minOccurs="0"
-                   maxOccurs="unbounded">
-        <xsd:annotation>
-	  <xsd:documentation>
-
-	    The remove-method element specifies the mappings for
-	    EJB 2.x style remove methods for an EJB 3.0 bean.
-	    This element can only be specified for stateful
-            session beans.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="transaction-type"
-		   type="javaee:transaction-typeType"
-                   minOccurs="0"/>
-      <xsd:element name="around-invoke"
-                   type="javaee:around-invokeType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/>
-      <xsd:element name="post-activate"
-                   type="javaee:lifecycle-callbackType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="pre-passivate"
-                   type="javaee:lifecycle-callbackType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="security-role-ref"
-		   type="javaee:security-role-refType"
-		   minOccurs="0"
-		   maxOccurs="unbounded">
-      </xsd:element>
-      <xsd:element name="security-identity"
-		   type="javaee:security-identityType"
-		   minOccurs="0">
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="javaee:string">
-	<xsd:enumeration value="Stateful"/>
-	<xsd:enumeration value="Stateless"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="javaee: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:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="javaee:string">
-	<xsd:enumeration value="Bean"/>
-	<xsd:enumeration value="Container"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-</xsd:schema>
-

jboss-as-7.2.0.Final/docs/schema/ejb-jar_3_1.xsd

@@ -1,3260 +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/javaee"
-            xmlns:javaee="http://java.sun.com/xml/ns/javaee"
-            xmlns:xsd="http://www.w3.org/2001/XMLSchema"
-            elementFormDefault="qualified"
-            attributeFormDefault="unqualified"
-            version="3.1">
-  <xsd:annotation>
-    <xsd:documentation>
-
-      $Id$
-      
-    </xsd:documentation>
-  </xsd:annotation>
-
-  <xsd:annotation>
-    <xsd:documentation>
-
-      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
-      
-      Copyright 2003-2009 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.
-      
-      
-      Portions Copyrighted 2009 Red Hat
-      
-      Red Hat elects to include this software in this
-      distribution under the GPL Version 2 license.
-    </xsd:documentation>
-  </xsd:annotation>
-
-  <xsd:annotation>
-    <xsd:documentation>
-<![CDATA[[
-      This is the XML Schema for the EJB 3.1 deployment descriptor.
-      
-      All EJB deployment descriptors must indicate
-      the schema by using the Java EE namespace:
-      
-      http://java.sun.com/xml/ns/javaee
-      
-      and by indicating the version of the schema by
-      using the version element as shown below:
-      
-      <ejb-jar 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/ejb-jar_3_1.xsd"
-      version="3.1">
-      ...
-      </ejb-jar>
-      
-      The instance documents may indicate the published version of
-      the schema using the xsi:schemaLocation attribute for the
-      Java EE namespace with the following location:
-      
-      http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.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_6.xsd"/>
-
-
-<!-- **************************************************** -->
-
-  <xsd:element name="ejb-jar"
-               type="javaee: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 or
-          .war file.
-          
-        </xsd:documentation>
-      </xsd:annotation>
-      <xsd:selector xpath="javaee:enterprise-beans/*"/>
-      <xsd:field xpath="javaee:ejb-name"/>
-    </xsd:key>
-    <xsd:keyref name="ejb-name-references"
-                refer="javaee: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=".//javaee:ejb-relationship-role/javaee:relationship-role-source"/>
-      <xsd:field xpath="javaee: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="javaee:assembly-descriptor/javaee:security-role"/>
-      <xsd:field xpath="javaee:role-name"/>
-    </xsd:key>
-    <xsd:keyref name="role-name-references"
-                refer="javaee:role-name-key">
-      <xsd:annotation>
-        <xsd:documentation>
-
-          The keyref indicates the references from
-          security-role-ref to a specified role-name.
-          
-        </xsd:documentation>
-      </xsd:annotation>
-      <xsd:selector xpath="javaee:enterprise-beans/*/javaee:security-role-ref"/>
-      <xsd:field xpath="javaee:role-link"/>
-    </xsd:keyref>
-  </xsd:element>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="access-timeoutType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The access-timeoutType represents the maximum amount of
-        time (in a given time unit) that the container should wait for
-        a concurrency lock before throwing a timeout exception to the
-        client.
-        
-        A timeout value of 0 means concurrent access is not permitted.
-        
-        A timeout value of -1 means wait indefinitely to acquire a lock.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="timeout"
-                   type="javaee:xsdIntegerType"/>
-      <xsd:element name="unit"
-                   type="javaee:time-unit-typeType"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="async-methodType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The async-methodType element specifies that a session
-        bean method has asynchronous invocation semantics.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="method-name"
-                   type="javaee:string"/>
-      <xsd:element name="method-params"
-                   type="javaee:method-paramsType"
-                   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </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="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="activation-config-property"
-                   type="javaee:activation-config-propertyType"
-                   maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <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="javaee:xsdStringType">
-        <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="javaee:xsdStringType">
-        <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:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="around-invokeType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The around-invoke type specifies a method on a
-        class to be called during the around invoke portion of an 
-        ejb invocation.  Note that each class may have only one
-        around invoke method and that the method may not be
-        overloaded.
-        
-        If the class element is missing then
-        the class defining the callback is assumed to be the
-        interceptor class or component class in scope at the
-        location in the descriptor in which the around invoke
-        definition appears.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="class"
-                   type="javaee:fully-qualified-classType"
-                   minOccurs="0"/>
-      <xsd:element name="method-name"
-                   type="javaee:java-identifierType"/>
-    </xsd:sequence>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="around-timeoutType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The around-timeout type specifies a method on a
-        class to be called during the around-timeout portion of
-        a timer timeout callback.  Note that each class may have 
-        only one around-timeout method and that the method may not 
-        be overloaded.
-        
-        If the class element is missing then
-        the class defining the callback is assumed to be the
-        interceptor class or component class in scope at the
-        location in the descriptor in which the around-timeout
-        definition appears.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="class"
-                   type="javaee:fully-qualified-classType"
-                   minOccurs="0"/>
-      <xsd:element name="method-name"
-                   type="javaee:java-identifierType"/>
-    </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, the definition
-        of interceptor bindings, a list of
-        methods to be excluded from being invoked, and a list of
-        exception types that should be treated as application exceptions.
-        
-        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 or .war file producer.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="security-role"
-                   type="javaee:security-roleType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="method-permission"
-                   type="javaee:method-permissionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="container-transaction"
-                   type="javaee:container-transactionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="interceptor-binding"
-                   type="javaee:interceptor-bindingType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="message-destination"
-                   type="javaee:message-destinationType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="exclude-list"
-                   type="javaee:exclude-listType"
-                   minOccurs="0"/>
-      <xsd:element name="application-exception"
-                   type="javaee:application-exceptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </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="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="field-name"
-                   type="javaee: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:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="javaee:string">
-        <xsd:enumeration value="1.x"/>
-        <xsd:enumeration value="2.x"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <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="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="cmr-field-name"
-                   type="javaee: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="javaee:cmr-field-typeType"
-                   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="javaee:string">
-        <xsd:enumeration value="java.util.Collection"/>
-        <xsd:enumeration value="java.util.Set"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="concurrency-management-typeType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The concurrency-management-typeType specifies the way concurrency
-        is managed for a singleton or stateful session bean.  
-        
-        The concurrency management type must be one of the following:
-        
-        Bean
-        Container
-        
-        Bean managed concurrency can only be specified for a singleton bean.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-        <xsd:enumeration value="Bean"/>
-        <xsd:enumeration value="Container"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="concurrent-lock-typeType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The concurrent-lock-typeType specifies how the container must
-        manage concurrent access to a method of a Singleton bean 
-        with container-managed concurrency.
-        
-        The container managed concurrency lock type must be one 
-        of the following :
-        
-        Read
-        Write
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-        <xsd:enumeration value="Read"/>
-        <xsd:enumeration value="Write"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="concurrent-methodType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The concurrent-methodType specifies information about a method
-        of a bean with container managed concurrency.
-        
-        The optional lock element specifies the kind of concurrency 
-        lock asssociated with the method.
-        
-        The optional access-timeout element specifies the amount of
-        time (in a given time unit) the container should wait for a
-        concurrency lock before throwing an exception to the client.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="method"
-                   type="javaee:named-methodType"/>
-      <xsd:element name="lock"
-                   type="javaee:concurrent-lock-typeType"
-                   minOccurs="0"/>
-      <xsd:element name="access-timeout"
-                   type="javaee:access-timeoutType"
-                   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </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="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="method"
-                   type="javaee:methodType"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="trans-attribute"
-                   type="javaee:trans-attributeType"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="depends-onType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The depends-onType is used to express initialization 
-        ordering dependencies between Singleton components.
-        The depends-onType specifies the names of one or more
-        Singleton beans in the same application as the referring
-        Singleton, each of which must be initialized before
-        the referring bean.  
-        
-        Each dependent bean is expressed using ejb-link syntax.
-        The order in which dependent beans are initialized at 
-        runtime is not guaranteed to match the order in which
-        they are listed.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="ejb-name"
-                   type="javaee:ejb-linkType"
-                   minOccurs="1"
-                   maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="ejb-classType">
-    <xsd:annotation>
-      <xsd:documentation>
-<![CDATA[[
-        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:simpleContent>
-      <xsd:restriction base="javaee:fully-qualified-classType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <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
-        - an optional module name. Only applicable to
-        stand-alone ejb-jars or ejb-jars packaged in an ear.
-        Ignored if specified for an ejb-jar.xml within a .war.
-        In that case, standard .war module-name rules apply.
-        - structural information about all included
-        enterprise beans that is not specified through
-        annotations
-        - structural information about interceptor classes
-        - 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="module-name"
-                   type="javaee:string"
-                   minOccurs="0"/>
-      <xsd:group ref="javaee:descriptionGroup"/>
-      <xsd:element name="enterprise-beans"
-                   type="javaee:enterprise-beansType"
-                   minOccurs="0"/>
-      <xsd:element name="interceptors"
-                   type="javaee:interceptorsType"
-                   minOccurs="0"/>
-      <xsd:element name="relationships"
-                   type="javaee: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="javaee:ejb-relation"/>
-          <xsd:field xpath="javaee:ejb-relation-name"/>
-        </xsd:unique>
-      </xsd:element>
-      <xsd:element name="assembly-descriptor"
-                   type="javaee:assembly-descriptorType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Providing an assembly-descriptor in the deployment
-            descriptor is optional for the ejb-jar or .war file
-            producer.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="ejb-client-jar"
-                   type="javaee:pathType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-<![CDATA[[
-            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:sequence>
-    <xsd:attribute name="version"
-                   type="javaee:dewey-versionType"
-                   fixed="3.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: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:complexType name="ejb-nameType">
-    <xsd:annotation>
-      <xsd:documentation>
-<![CDATA[[
-        The ejb-nameType specifies an enterprise bean's name. It is
-        used by ejb-name elements. This name is assigned by the
-        file producer to name the enterprise bean in the
-        ejb-jar or .war file's deployment descriptor. The name must be
-        unique among the names of the enterprise beans in the same
-        ejb-jar or .war 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:simpleContent>
-      <xsd:restriction base="javaee:xsdNMTOKENType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <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="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="ejb-relation-name"
-                   type="javaee: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="javaee:ejb-relationship-roleType"/>
-      <xsd:element name="ejb-relationship-role"
-                   type="javaee:ejb-relationship-roleType"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="ejb-relationship-roleType">
-    <xsd:annotation>
-      <xsd:documentation>
-<![CDATA[[
-        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="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="ejb-relationship-role-name"
-                   type="javaee: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="javaee:multiplicityType"/>
-      <xsd:element name="cascade-delete"
-                   type="javaee: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="javaee:relationship-role-sourceType"/>
-      <xsd:element name="cmr-field"
-                   type="javaee:cmr-fieldType"
-                   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </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="javaee: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="javaee:ejb-local-ref"/>
-          <xsd:field xpath="javaee: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="javaee:ejb-ref"/>
-          <xsd:field xpath="javaee: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="javaee:resource-env-ref"/>
-          <xsd:field xpath="javaee: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="javaee:message-destination-ref"/>
-          <xsd:field xpath="javaee: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="javaee:resource-ref"/>
-          <xsd:field xpath="javaee: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="javaee:env-entry"/>
-          <xsd:field xpath="javaee:env-entry-name"/>
-        </xsd:unique>
-      </xsd:element>
-      <xsd:element name="entity"
-                   type="javaee: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="javaee:ejb-local-ref"/>
-          <xsd:field xpath="javaee: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="javaee:ejb-ref"/>
-          <xsd:field xpath="javaee: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="javaee:resource-env-ref"/>
-          <xsd:field xpath="javaee: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="javaee:message-destination-ref"/>
-          <xsd:field xpath="javaee: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="javaee:resource-ref"/>
-          <xsd:field xpath="javaee: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="javaee:env-entry"/>
-          <xsd:field xpath="javaee:env-entry-name"/>
-        </xsd:unique>
-      </xsd:element>
-      <xsd:element name="message-driven"
-                   type="javaee: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="javaee:ejb-local-ref"/>
-          <xsd:field xpath="javaee: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="javaee:ejb-ref"/>
-          <xsd:field xpath="javaee: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="javaee:resource-env-ref"/>
-          <xsd:field xpath="javaee: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="javaee:message-destination-ref"/>
-          <xsd:field xpath="javaee: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="javaee:resource-ref"/>
-          <xsd:field xpath="javaee: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="javaee:env-entry"/>
-          <xsd:field xpath="javaee:env-entry-name"/>
-        </xsd:unique>
-      </xsd:element>
-    </xsd:choice>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </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
-        - an optional mapped-name element that can be used to provide
-        vendor-specific deployment information such as the physical
-        jndi-name of the entity bean's remote home interface. This 
-        element is not required to be supported by all implementations.
-        Any use of this element is non-portable.
-        - 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 optional entity bean's persistence management type. If 
-        this element is not specified it is defaulted to Container.
-        - 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.
-        
-        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:group ref="javaee:descriptionGroup"/>
-      <xsd:element name="ejb-name"
-                   type="javaee:ejb-nameType"/>
-      <xsd:element name="mapped-name"
-                   type="javaee:xsdStringType"
-                   minOccurs="0"/>
-      <xsd:element name="home"
-                   type="javaee:homeType"
-                   minOccurs="0"/>
-      <xsd:element name="remote"
-                   type="javaee:remoteType"
-                   minOccurs="0"/>
-      <xsd:element name="local-home"
-                   type="javaee:local-homeType"
-                   minOccurs="0"/>
-      <xsd:element name="local"
-                   type="javaee:localType"
-                   minOccurs="0"/>
-      <xsd:element name="ejb-class"
-                   type="javaee:ejb-classType"/>
-      <xsd:element name="persistence-type"
-                   type="javaee:persistence-typeType"/>
-      <xsd:element name="prim-key-class"
-                   type="javaee: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="javaee: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="javaee:cmp-versionType"
-                   minOccurs="0"/>
-      <xsd:element name="abstract-schema-name"
-                   type="javaee: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="javaee:cmp-fieldType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="primkey-field"
-                   type="javaee: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:group ref="javaee:jndiEnvironmentRefsGroup"/>
-      <xsd:element name="security-role-ref"
-                   type="javaee:security-role-refType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="security-identity"
-                   type="javaee:security-identityType"
-                   minOccurs="0"/>
-      <xsd:element name="query"
-                   type="javaee:queryType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </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="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="method"
-                   type="javaee:methodType"
-                   maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="application-exceptionType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The application-exceptionType declares an application
-        exception. The declaration consists of:
-        
-        - the exception class. When the container receives
-        an exception of this type, it is required to 
-        forward this exception as an applcation exception 
-        to the client regardless of whether it is a checked
-        or unchecked exception.
-        - an optional rollback element. If this element is 
-        set to true, the container must rollback the current 
-        transaction before forwarding the exception to the
-        client.  If not specified, it defaults to false.
-        - an optional inherited element. If this element is 
-        set to true, subclasses of the exception class type
-        are also automatically considered application 
-        exceptions (unless overriden at a lower level).
-        If set to false, only the exception class type is
-        considered an application-exception, not its
-        exception subclasses. If not specified, this
-        value defaults to true.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="exception-class"
-                   type="javaee:fully-qualified-classType"/>
-      <xsd:element name="rollback"
-                   type="javaee:true-falseType"
-                   minOccurs="0"/>
-      <xsd:element name="inherited"
-                   type="javaee:true-falseType"
-                   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="interceptorsType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The interceptorsType element declares one or more interceptor
-        classes used by components within this ejb-jar or .war.  The declaration
-        consists of :
-        
-        - An optional description.
-        - One or more interceptor elements.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-                   type="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="interceptor"
-                   type="javaee:interceptorType"
-                   maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="interceptorType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The interceptorType element declares information about a single
-        interceptor class.  It consists of :
-        
-        - An optional description.
-        - The fully-qualified name of the interceptor class.
-        - An optional list of around invoke methods declared on the
-        interceptor class and/or its super-classes.
-        - An optional list of around timeout methods declared on the
-        interceptor class and/or its super-classes.
-        - An optional list environment dependencies for the interceptor
-        class and/or its super-classes.
-        - An optional list of post-activate methods declared on the
-        interceptor class and/or its super-classes.
-        - An optional list of pre-passivate methods declared on the
-        interceptor class and/or its super-classes.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-                   type="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="interceptor-class"
-                   type="javaee:fully-qualified-classType"/>
-      <xsd:element name="around-invoke"
-                   type="javaee:around-invokeType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="around-timeout"
-                   type="javaee:around-timeoutType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/>
-      <xsd:element name="post-activate"
-                   type="javaee:lifecycle-callbackType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="pre-passivate"
-                   type="javaee:lifecycle-callbackType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="interceptor-bindingType">
-    <xsd:annotation>
-      <xsd:documentation>
-<![CDATA[[
-        The interceptor-bindingType element describes the binding of
-        interceptor classes to beans within the ejb-jar or .war.
-        It consists of :
-        
-        - An optional description.
-        - The name of an ejb within the module or the wildcard value "*",
-        which is used to define interceptors that are bound to all
-        beans in the ejb-jar or .war.
-        - A list of interceptor classes that are bound to the contents of
-        the ejb-name element or a specification of the total ordering
-        over the interceptors defined for the given level and above.
-        - An optional exclude-default-interceptors element.  If set to true,
-        specifies that default interceptors are not to be applied to 
-        a bean-class and/or business method.
-        - An optional exclude-class-interceptors element.  If set to true,
-        specifies that class interceptors are not to be applied to 
-        a business method.
-        - An optional set of method elements for describing the name/params
-        of a method-level interceptor.
-        
-        Interceptors bound to all classes using the wildcard syntax
-        "*" are default interceptors for the components in the ejb-jar or .war. 
-        In addition, interceptors may be bound at the level of the bean
-        class (class-level interceptors) or business methods (method-level
-        interceptors ).
-        
-        The binding of interceptors to classes is additive.  If interceptors
-        are bound at the class-level and/or default-level as well as the
-        method-level, both class-level and/or default-level as well as
-        method-level will apply. 
-        
-        There are four possible styles of the interceptor element syntax :
-        
-        1.
-        <interceptor-binding>
-        <ejb-name>*</ejb-name>
-        <interceptor-class>INTERCEPTOR</interceptor-class>
-        </interceptor-binding>
-        
-        Specifying the ejb-name as the wildcard value "*" designates
-        default interceptors (interceptors that apply to all session and
-        message-driven beans contained in the ejb-jar or .war).
-        
-        2. 
-        <interceptor-binding>
-        <ejb-name>EJBNAME</ejb-name>
-        <interceptor-class>INTERCEPTOR</interceptor-class>
-        </interceptor-binding>
-        
-        This style is used to refer to interceptors associated with the
-        specified enterprise bean(class-level interceptors).
-        
-        3. 
-        <interceptor-binding>
-        <ejb-name>EJBNAME</ejb-name>
-        <interceptor-class>INTERCEPTOR</interceptor-class>
-        <method>
-        <method-name>METHOD</method-name>
-        </method>
-        </interceptor-binding>
-        
-        This style is used to associate a method-level interceptor with 
-        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.  Method-level
-        interceptors can only be associated with business methods of the
-        bean class.   Note that the wildcard value "*" cannot be used
-        to specify method-level interceptors.
-        
-        4. 
-        <interceptor-binding>
-        <ejb-name>EJBNAME</ejb-name>
-        <interceptor-class>INTERCEPTOR</interceptor-class>
-        <method>
-        <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>
-        </interceptor-binding>
-        
-        This style is used to associate a method-level interceptor with 
-        the specified method of the specified enterprise bean.  This 
-        style is used to refer to a single method within a set of methods
-        with an overloaded name.  The values 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[][]).
-        
-]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-                   type="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="ejb-name"
-                   type="javaee:string"/>
-      <xsd:choice>
-        <xsd:element name="interceptor-class"
-                     type="javaee:fully-qualified-classType"
-                     minOccurs="0"
-                     maxOccurs="unbounded"/>
-        <xsd:element name="interceptor-order"
-                     type="javaee:interceptor-orderType"
-                     minOccurs="1"/>
-      </xsd:choice>
-      <xsd:element name="exclude-default-interceptors"
-                   type="javaee:true-falseType"
-                   minOccurs="0"/>
-      <xsd:element name="exclude-class-interceptors"
-                   type="javaee:true-falseType"
-                   minOccurs="0"/>
-      <xsd:element name="method"
-                   type="javaee:named-methodType"
-                   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="interceptor-orderType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The interceptor-orderType element describes a total ordering
-        of interceptor classes.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="interceptor-class"
-                   type="javaee:fully-qualified-classType"
-                   minOccurs="1"
-                   maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="named-methodType">
-    <xsd:sequence>
-      <xsd:element name="method-name"
-                   type="javaee:string"/>
-      <xsd:element name="method-params"
-                   type="javaee:method-paramsType"
-                   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="init-methodType">
-    <xsd:sequence>
-      <xsd:element name="create-method"
-                   type="javaee:named-methodType"/>
-      <xsd:element name="bean-method"
-                   type="javaee:named-methodType"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="remove-methodType">
-    <xsd:sequence>
-      <xsd:element name="bean-method"
-                   type="javaee:named-methodType"/>
-      <xsd:element name="retain-if-exception"
-                   type="javaee:true-falseType"
-                   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <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
-        - an optional mapped-name element that can be used to provide
-        vendor-specific deployment information such as the physical
-        jndi-name of destination from which this message-driven bean
-        should consume.  This element is not required to be supported 
-        by all implementations.  Any use of this element is non-portable.
-        - the message-driven bean's implementation class
-        - an optional declaration of the bean's messaging 
-        type 
-        - an optional declaration of the bean's timeout method for
-        handling programmatically created timers
-        - an optional declaration of timers to be automatically created at
-        deployment time
-        - the optional message-driven bean's transaction management 
-        type. If it is not defined, it is defaulted to Container.
-        - 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 list of the message-driven bean class and/or
-        superclass around-invoke methods.
-        - an optional list of the message-driven bean class and/or
-        superclass around-timeout methods.
-        - 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
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:group ref="javaee:descriptionGroup"/>
-      <xsd:element name="ejb-name"
-                   type="javaee:ejb-nameType"/>
-      <xsd:element name="mapped-name"
-                   type="javaee:xsdStringType"
-                   minOccurs="0"/>
-      <xsd:element name="ejb-class"
-                   type="javaee:ejb-classType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The ejb-class element specifies the fully qualified name
-            of the bean class for this ejb.  It is required unless
-            there is a component-defining annotation for the same
-            ejb-name.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="messaging-type"
-                   type="javaee:fully-qualified-classType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The messaging-type element specifies the message
-            listener interface of the message-driven bean. 
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="timeout-method"
-                   type="javaee:named-methodType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The timeout-method element specifies the method that
-            will receive callbacks for programmatically
-            created timers.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="timer"
-                   type="javaee:timerType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="transaction-type"
-                   type="javaee:transaction-typeType"
-                   minOccurs="0"/>
-      <xsd:element name="message-destination-type"
-                   type="javaee:message-destination-typeType"
-                   minOccurs="0"/>
-      <xsd:element name="message-destination-link"
-                   type="javaee:message-destination-linkType"
-                   minOccurs="0"/>
-      <xsd:element name="activation-config"
-                   type="javaee:activation-configType"
-                   minOccurs="0"/>
-      <xsd:element name="around-invoke"
-                   type="javaee:around-invokeType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="around-timeout"
-                   type="javaee:around-timeoutType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/>
-      <xsd:element name="security-role-ref"
-                   type="javaee:security-role-refType"
-                   minOccurs="0"
-                   maxOccurs="unbounded">
-      </xsd:element>
-      <xsd:element name="security-identity"
-                   type="javaee:security-identityType"
-                   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="methodType">
-    <xsd:annotation>
-      <xsd:documentation>
-<![CDATA[[
-        The methodType is used to denote a method of an enterprise
-        bean's business, 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 business, home, component, and/or web service 
-        endpoint nterfaces; 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 business, 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 business, 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 business, home, component,
-        and/or web service endpoint interfaces with the same name and
-        signature. However, if the same method is a method of both the
-        local business interface, and the local component interface, 
-        the same attribute applies to the method for both interfaces.
-        Likewise, if the same method is a method of both the remote 
-        business interface and the remote component interface, the same
-        attribute applies to the method for both interfaces.
-        
-        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 three 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
-        and the remote business 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="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="ejb-name"
-                   type="javaee:ejb-nameType"/>
-      <xsd:element name="method-intf"
-                   type="javaee:method-intfType"
-                   minOccurs="0">
-      </xsd:element>
-      <xsd:element name="method-name"
-                   type="javaee:method-nameType"/>
-      <xsd:element name="method-params"
-                   type="javaee:method-paramsType"
-                   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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. 
-        
-        Local applies to the local component interface, local business 
-        interfaces, and the no-interface view. 
-        
-        Remote applies to both remote component interface and the remote 
-        business interfaces.  
-        
-        ServiceEndpoint refers to methods exposed through a web service
-        endpoint.
-        
-        Timer refers to the bean's timeout callback methods.
-        
-        MessageEndpoint refers to the methods of a message-driven bean's
-        message-listener interface.
-        
-        The method-intf element must be one of the following:
-        
-        Home
-        Remote
-        LocalHome
-        Local
-        ServiceEndpoint
-        Timer
-        MessageEndpoint
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-        <xsd:enumeration value="Home"/>
-        <xsd:enumeration value="Remote"/>
-        <xsd:enumeration value="LocalHome"/>
-        <xsd:enumeration value="Local"/>
-        <xsd:enumeration value="ServiceEndpoint"/>
-        <xsd:enumeration value="Timer"/>
-        <xsd:enumeration value="MessageEndpoint"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="javaee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <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="javaee: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:attribute name="id"
-                   type="xsd:ID"/>
-  </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 business, home, component 
-        and/or web service endpoint interfaces.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-                   type="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:choice>
-        <xsd:element name="role-name"
-                     type="javaee:role-nameType"
-                     maxOccurs="unbounded"/>
-        <xsd:element name="unchecked"
-                     type="javaee: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="javaee:methodType"
-                   maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="javaee:string">
-        <xsd:enumeration value="One"/>
-        <xsd:enumeration value="Many"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="javaee:string">
-        <xsd:enumeration value="Bean"/>
-        <xsd:enumeration value="Container"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </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.
-        
-        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="javaee:descriptionType"
-                   minOccurs="0"/>
-      <xsd:element name="query-method"
-                   type="javaee:query-methodType"/>
-      <xsd:element name="result-type-mapping"
-                   type="javaee:result-type-mappingType"
-                   minOccurs="0"/>
-      <xsd:element name="ejb-ql"
-                   type="javaee:xsdStringType"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="query-methodType">
-    <xsd:annotation>
-      <xsd:documentation>
-<![CDATA[[
-        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 &gt; 1000
-        </ejb-ql>
-        </query>
-        
-]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="method-name"
-                   type="javaee:method-nameType"/>
-      <xsd:element name="method-params"
-                   type="javaee:method-paramsType"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </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="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="ejb-name"
-                   type="javaee:ejb-nameType"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </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="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="ejb-relation"
-                   type="javaee: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=".//javaee:ejb-relationship-role-name"/>
-          <xsd:field xpath="."/>
-        </xsd:unique>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="javaee:string">
-        <xsd:enumeration value="Local"/>
-        <xsd:enumeration value="Remote"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <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="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:choice>
-        <xsd:element name="use-caller-identity"
-                     type="javaee: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="javaee:run-asType"/>
-      </xsd:choice>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </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
-        - an optional mapped-name element that can be used to provide
-        vendor-specific deployment information such as the physical
-        jndi-name of the session bean's remote home/business interface. 
-        This element is not required to be supported by all 
-        implementations. Any use of this element is non-portable.
-        - the names of all the remote or local business interfaces, 
-        if any
-        - 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
-        - an optional declaration that this bean exposes a
-        no-interface view
-        - 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
-        - an optional declaration of a stateful session bean's timeout value
-        - an optional declaration of the session bean's timeout method for
-        handling programmatically created timers
-        - an optional declaration of timers to be automatically created at
-        deployment time
-        - an optional declaration that a Singleton bean has eager
-        initialization
-        - an optional declaration of a Singleton/Stateful bean's concurrency 
-        management type
-        - an optional declaration of the method locking metadata
-        for a Singleton with container managed concurrency
-        - an optional declaration of the other Singleton beans in the
-        application that must be initialized before this bean
-        - an optional declaration of the session bean's asynchronous 
-        methods
-        - the optional session bean's transaction management type. 
-        If it is not present, it is defaulted to Container.
-        - an optional declaration of a stateful session bean's 
-        afterBegin, beforeCompletion, and/or afterCompletion methods
-        - an optional list of the session bean class and/or
-        superclass around-invoke methods.
-        - an optional list of the session bean class and/or
-        superclass around-timeout methods.
-        - 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
-        
-        The elements that are optional are "optional" in the sense
-        that they are omitted when if lists represented by them are
-        empty.
-        
-        The service-endpoint element may only be specified if the
-        bean is a stateless session bean.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:group ref="javaee:descriptionGroup"/>
-      <xsd:element name="ejb-name"
-                   type="javaee:ejb-nameType"/>
-      <xsd:element name="mapped-name"
-                   type="javaee:xsdStringType"
-                   minOccurs="0"/>
-      <xsd:element name="home"
-                   type="javaee:homeType"
-                   minOccurs="0"/>
-      <xsd:element name="remote"
-                   type="javaee:remoteType"
-                   minOccurs="0"/>
-      <xsd:element name="local-home"
-                   type="javaee:local-homeType"
-                   minOccurs="0"/>
-      <xsd:element name="local"
-                   type="javaee:localType"
-                   minOccurs="0"/>
-      <xsd:element name="business-local"
-                   type="javaee:fully-qualified-classType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="business-remote"
-                   type="javaee:fully-qualified-classType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="local-bean"
-                   type="javaee:emptyType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The local-bean element declares that this
-            session bean exposes a no-interface Local client view.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="service-endpoint"
-                   type="javaee: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="javaee:ejb-classType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The ejb-class element specifies the fully qualified name
-            of the bean class for this ejb.  It is required unless
-            there is a component-defining annotation for the same
-            ejb-name.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="session-type"
-                   type="javaee:session-typeType"
-                   minOccurs="0"/>
-      <xsd:element name="stateful-timeout"
-                   type="javaee:stateful-timeoutType"
-                   minOccurs="0"/>
-      <xsd:element name="timeout-method"
-                   type="javaee:named-methodType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The timeout-method element specifies the method that
-            will receive callbacks for programmatically
-            created timers.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="timer"
-                   type="javaee:timerType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="init-on-startup"
-                   type="javaee:true-falseType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The init-on-startup element specifies that a Singleton
-            bean has eager initialization.
-            This element can only be specified for singleton session
-            beans.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="concurrency-management-type"
-                   type="javaee:concurrency-management-typeType"
-                   minOccurs="0"/>
-      <xsd:element name="concurrent-method"
-                   type="javaee:concurrent-methodType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="depends-on"
-                   type="javaee:depends-onType"
-                   minOccurs="0"/>
-      <xsd:element name="init-method"
-                   type="javaee:init-methodType"
-                   minOccurs="0"
-                   maxOccurs="unbounded">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The init-method element specifies the mappings for
-            EJB 2.x style create methods for an EJB 3.x bean.
-            This element can only be specified for stateful 
-            session beans. 
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="remove-method"
-                   type="javaee:remove-methodType"
-                   minOccurs="0"
-                   maxOccurs="unbounded">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The remove-method element specifies the mappings for
-            EJB 2.x style remove methods for an EJB 3.x bean.
-            This element can only be specified for stateful 
-            session beans. 
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="async-method"
-                   type="javaee:async-methodType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="transaction-type"
-                   type="javaee:transaction-typeType"
-                   minOccurs="0"/>
-      <xsd:element name="after-begin-method"
-                   type="javaee:named-methodType"
-                   minOccurs="0"/>
-      <xsd:element name="before-completion-method"
-                   type="javaee:named-methodType"
-                   minOccurs="0"/>
-      <xsd:element name="after-completion-method"
-                   type="javaee:named-methodType"
-                   minOccurs="0"/>
-      <xsd:element name="around-invoke"
-                   type="javaee:around-invokeType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="around-timeout"
-                   type="javaee:around-timeoutType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/>
-      <xsd:element name="post-activate"
-                   type="javaee:lifecycle-callbackType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="pre-passivate"
-                   type="javaee:lifecycle-callbackType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="security-role-ref"
-                   type="javaee:security-role-refType"
-                   minOccurs="0"
-                   maxOccurs="unbounded">
-      </xsd:element>
-      <xsd:element name="security-identity"
-                   type="javaee:security-identityType"
-                   minOccurs="0">
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="session-typeType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The session-typeType describes whether the session bean is a
-        singleton, stateful or stateless session. It is used by
-        session-type elements.
-        
-        The value must be one of the three following:
-        
-        Singleton
-        Stateful
-        Stateless
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-        <xsd:enumeration value="Singleton"/>
-        <xsd:enumeration value="Stateful"/>
-        <xsd:enumeration value="Stateless"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="stateful-timeoutType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The stateful-timeoutType represents the amount of time
-        a stateful session bean can be idle(not receive any client
-        invocations) before it is eligible for removal by the container.
-        
-        A timeout value of 0 means the bean is immediately eligible for removal.
-        
-        A timeout value of -1 means the bean will never be removed due to timeout.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="timeout"
-                   type="javaee:xsdIntegerType"/>
-      <xsd:element name="unit"
-                   type="javaee:time-unit-typeType"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="time-unit-typeType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The time-unit-typeType represents a time duration at a given
-        unit of granularity.  
-        
-        The time unit type must be one of the following :
-        
-        Days
-        Hours
-        Minutes
-        Seconds
-        Milliseconds
-        Microseconds
-        Nanoseconds
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-        <xsd:enumeration value="Days"/>
-        <xsd:enumeration value="Hours"/>
-        <xsd:enumeration value="Minutes"/>
-        <xsd:enumeration value="Seconds"/>
-        <xsd:enumeration value="Milliseconds"/>
-        <xsd:enumeration value="Microseconds"/>
-        <xsd:enumeration value="Nanoseconds"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="timer-scheduleType">
-    <xsd:sequence>
-      <xsd:element name="second"
-                   type="javaee:string"
-                   minOccurs="0"/>
-      <xsd:element name="minute"
-                   type="javaee:string"
-                   minOccurs="0"/>
-      <xsd:element name="hour"
-                   type="javaee:string"
-                   minOccurs="0"/>
-      <xsd:element name="day-of-month"
-                   type="javaee:string"
-                   minOccurs="0"/>
-      <xsd:element name="month"
-                   type="javaee:string"
-                   minOccurs="0"/>
-      <xsd:element name="day-of-week"
-                   type="javaee:string"
-                   minOccurs="0"/>
-      <xsd:element name="year"
-                   type="javaee:string"
-                   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="timerType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The timerType specifies an enterprise bean timer.  Each
-        timer is automatically created by the container upon
-        deployment.  Timer callbacks occur based on the 
-        schedule attributes.  All callbacks are made to the
-        timeout-method associated with the timer.  
-        
-        A timer can have an optional start and/or end date. If
-        a start date is specified, it takes precedence over the
-        associated timer schedule such that any matching
-        expirations prior to the start time will not occur.
-        Likewise, no matching expirations will occur after any
-        end date.   Start/End dates are specified using the
-        XML Schema dateTime type, which follows the ISO-8601
-        standard for date(and optional time-within-the-day) 
-        representation.
-        
-        An optional flag can be used to control whether
-        this timer has persistent(true) delivery semantics or
-        non-persistent(false) delivery semantics.  If not specified,
-        the value defaults to persistent(true).
-        
-        A time zone can optionally be associated with a timer.
-        If specified, the timer's schedule is evaluated in the context
-        of that time zone, regardless of the default time zone in which
-        the container is executing.   Time zones are specified as an
-        ID string.  The set of required time zone IDs is defined by
-        the Zone Name(TZ) column of the public domain zoneinfo database.
-        
-        An optional info string can be assigned to the timer and 
-        retrieved at runtime through the Timer.getInfo() method.
-        
-        The timerType can only be specified on stateless session
-        beans, singleton session beans, and message-driven beans.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-                   type="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="schedule"
-                   type="javaee:timer-scheduleType"/>
-      <xsd:element name="start"
-                   type="xsd:dateTime"
-                   minOccurs="0"/>
-      <xsd:element name="end"
-                   type="xsd:dateTime"
-                   minOccurs="0"/>
-      <xsd:element name="timeout-method"
-                   type="javaee:named-methodType"/>
-      <xsd:element name="persistent"
-                   type="javaee:true-falseType"
-                   minOccurs="0"/>
-      <xsd:element name="timezone"
-                   type="javaee:string"
-                   minOccurs="0"/>
-      <xsd:element name="info"
-                   type="javaee:string"
-                   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="javaee: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:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType 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:simpleContent>
-      <xsd:restriction base="javaee:string">
-        <xsd:enumeration value="Bean"/>
-        <xsd:enumeration value="Container"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-</xsd:schema>

jboss-as-7.2.0.Final/docs/schema/j2ee_1_4.xsd

@@ -1,1607 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xsd:schema
-     targetNamespace="http://java.sun.com/xml/ns/j2ee"
-     xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
-     xmlns:xsd="http://www.w3.org/2001/XMLSchema"
-     elementFormDefault="qualified"
-     attributeFormDefault="unqualified"
-     version="1.4">
-  <xsd:annotation>
-    <xsd:documentation>
-      @(#)j2ee_1_4.xsds	1.43 03/09/16
-    </xsd:documentation>
-  </xsd:annotation>
-
-  <xsd:annotation>
-    <xsd:documentation>
-
-      Copyright 2003 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:include schemaLocation=
-	"http://www.ibm.com/webservices/xsd/j2ee_web_services_client_1_1.xsd"/>
-
-
-<!-- **************************************************** -->
-
-  <xsd:group name="descriptionGroup">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This group keeps the usage of the contained description related
-	elements consistent across J2EE deployment descriptors.
-
-	All elements may occur multiple times with different languages,
-	to support localization of the content.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="j2ee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="display-name"
-		   type="j2ee:display-nameType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="icon"
-		   type="j2ee:iconType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-    </xsd:sequence>
-  </xsd:group>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="descriptionType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The description type is used by a description element to
-	provide text describing the parent element.  The elements
-	that use this type should include any information that the
-	Deployment Component's Deployment File file producer wants
-	to provide to the consumer of the Deployment Component's
-	Deployment File (i.e., to the Deployer). Typically, the
-	tools used by such a Deployment File consumer will display
-	the description when processing the parent element that
-	contains the description.
-
-	The lang attribute defines the language that the
-	description is provided in. The default value is "en" (English).
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="j2ee:xsdStringType">
-	<xsd:attribute ref="xml:lang"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:simpleType name="dewey-versionType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This type defines a dewey decimal which is used
-	to describe versions of documents.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:restriction base="xsd:decimal">
-      <xsd:whiteSpace value="collapse"/>
-    </xsd:restriction>
-
-  </xsd:simpleType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="display-nameType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The display-name type contains a short name that is intended
-	  to be displayed by tools. It is used by display-name
-	  elements.  The display name need not be unique.
-
-	  Example:
-
-	  ...
-	     <display-name xml:lang="en">Employee Self Service</display-name>
-
-	  The value of the xml:lang attribute is "en" (English) by default.
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="j2ee:string">
-	<xsd:attribute ref="xml:lang"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="ejb-linkType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The ejb-linkType is used by ejb-link
-	  elements in the ejb-ref or ejb-local-ref elements to specify
-	  that an EJB reference is linked to enterprise bean.
-
-	  The value of the ejb-link element must be the ejb-name of an
-	  enterprise bean in the same ejb-jar file or in another ejb-jar
-	  file in the same J2EE application unit.
-
-	  Alternatively, the name in the ejb-link element may be
-	  composed of a path name specifying the ejb-jar containing the
-	  referenced enterprise bean with the ejb-name of the target
-	  bean appended and separated from the path name by "#".  The
-	  path name is relative to the Deployment File containing
-	  Deployment Component that is referencing the enterprise
-	  bean.  This allows multiple enterprise beans with the same
-	  ejb-name to be uniquely identified.
-
-	  Examples:
-
-	      <ejb-link>EmployeeRecord</ejb-link>
-
-	      <ejb-link>../products/product.jar#ProductEJB</ejb-link>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="ejb-local-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The ejb-local-refType is used by ejb-local-ref elements for
-	the declaration of a reference to an enterprise bean's local
-	home. The declaration consists of:
-
-	    - an optional description
-	    - the EJB reference name used in the code of the Deployment
-	      Component that's referencing the enterprise bean
-	    - the expected type of the referenced enterprise bean
-	    - the expected local home and local interfaces of the
-	      referenced enterprise bean
-	    - optional ejb-link information, used to specify the
-	      referenced enterprise bean
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="j2ee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="ejb-ref-name"
-		   type="j2ee:ejb-ref-nameType"/>
-      <xsd:element name="ejb-ref-type"
-		   type="j2ee:ejb-ref-typeType"/>
-      <xsd:element name="local-home"
-		   type="j2ee:local-homeType"/>
-      <xsd:element name="local"
-		   type="j2ee:localType"/>
-      <xsd:element name="ejb-link"
-		   type="j2ee:ejb-linkType"
-		   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="ejb-ref-nameType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The ejb-ref-name element contains the name of an EJB
-	  reference. The EJB reference is an entry in the
-	  Deployment Component's environment and is relative to the
-	  java:comp/env context.  The name must be unique within the
-	  Deployment Component.
-
-	  It is recommended that name is prefixed with "ejb/".
-
-	  Example:
-
-	  <ejb-ref-name>ejb/Payroll</ejb-ref-name>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:jndi-nameType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="ejb-ref-typeType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The ejb-ref-typeType contains the expected type of the
-	referenced enterprise bean.
-
-	The ejb-ref-type designates a value
-	that must be one of the following:
-
-	    Entity
-	    Session
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:string">
-	<xsd:enumeration value="Entity"/>
-	<xsd:enumeration value="Session"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="ejb-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The ejb-refType is used by ejb-ref elements for the
-	declaration of a reference to an enterprise bean's home. The
-	declaration consists of:
-
-	    - an optional description
-	    - the EJB reference name used in the code of
-	      the Deployment Component that's referencing the enterprise
-	      bean
-	    - the expected type of the referenced enterprise bean
-	    - the expected home and remote interfaces of the referenced
-	      enterprise bean
-	    - optional ejb-link information, used to specify the
-	      referenced enterprise bean
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="j2ee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="ejb-ref-name"
-		   type="j2ee:ejb-ref-nameType"/>
-      <xsd:element name="ejb-ref-type"
-		   type="j2ee:ejb-ref-typeType"/>
-
-      <xsd:element name="home"
-		   type="j2ee:homeType"/>
-      <xsd:element name="remote"
-		   type="j2ee:remoteType"/>
-      <xsd:element name="ejb-link"
-		   type="j2ee:ejb-linkType"
-		   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="emptyType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This type is used to designate an empty
-	element when used.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="env-entry-type-valuesType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  This type contains the fully-qualified Java type of the
-	  environment entry value that is expected by the
-	  application's code.
-
-	  The following are the legal values of env-entry-type-valuesType:
-
-	      java.lang.Boolean
-	      java.lang.Byte
-	      java.lang.Character
-	      java.lang.String
-	      java.lang.Short
-	      java.lang.Integer
-	      java.lang.Long
-	      java.lang.Float
-	      java.lang.Double
-
-	  Example:
-
-	  <env-entry-type>java.lang.Boolean</env-entry-type>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:string">
-	<xsd:enumeration value="java.lang.Boolean"/>
-	<xsd:enumeration value="java.lang.Byte"/>
-	<xsd:enumeration value="java.lang.Character"/>
-	<xsd:enumeration value="java.lang.String"/>
-	<xsd:enumeration value="java.lang.Short"/>
-	<xsd:enumeration value="java.lang.Integer"/>
-	<xsd:enumeration value="java.lang.Long"/>
-	<xsd:enumeration value="java.lang.Float"/>
-	<xsd:enumeration value="java.lang.Double"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="env-entryType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The env-entryType is used to declare an application's
-	environment entry. The declaration consists of an optional
-	description, the name of the environment entry, and an
-	optional value.  If a value is not specified, one must be
-	supplied during deployment.
-
-	It is used by env-entry elements.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="j2ee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="env-entry-name"
-		   type="j2ee:jndi-nameType">
-	<xsd:annotation>
-	  <xsd:documentation>
-	    <![CDATA[
-
-	      The env-entry-name element contains the name of a
-	      Deployment Component's environment entry.  The name
-	      is a JNDI name relative to the java:comp/env
-	      context.  The name must be unique within a
-	      Deployment Component. The uniqueness
-	      constraints must be defined within the declared
-	      context.
-
-	      Example:
-
-	      <env-entry-name>minAmount</env-entry-name>
-
-	      ]]>
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="env-entry-type"
-		   type="j2ee:env-entry-type-valuesType"/>
-
-      <xsd:element name="env-entry-value"
-		   type="j2ee:xsdStringType"
-		   minOccurs="0">
-	<xsd:annotation>
-	  <xsd:documentation>
-	    <![CDATA[
-
-	      The env-entry-value designates the value of a
-	      Deployment Component's environment entry. The value
-	      must be a String that is valid for the
-	      constructor of the specified type that takes a
-	      single String parameter, or for java.lang.Character,
-	      a single character.
-
-	      Example:
-
-	      <env-entry-value>100.00</env-entry-value>
-
-	      ]]>
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="fully-qualified-classType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The elements that use this type designate the name of a
-	Java class or interface.  The name is in the form of a
-	"binary name", as defined in the JLS.  This is the form
-	of name used in Class.forName().  Tools that need the
-	canonical name (the name used in source code) will need
-	to convert this binary name to the canonical name.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="generic-booleanType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This type defines four different values which can designate
-	boolean values. This includes values yes and no which are
-	not designated by xsd:boolean
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:string">
-	<xsd:enumeration value="true"/>
-	<xsd:enumeration value="false"/>
-	<xsd:enumeration value="yes"/>
-	<xsd:enumeration value="no"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="homeType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The homeType defines the fully-qualified name of
-	  an enterprise bean's home interface.
-
-	  Example:
-
-	      <home>com.aardvark.payroll.PayrollHome</home>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:fully-qualified-classType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="iconType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The icon type contains small-icon and large-icon elements
-	that specify the file names for small and large GIF or
-	JPEG icon images used to represent the parent element in a
-	GUI tool.
-
-	The xml:lang attribute defines the language that the
-	icon file names are provided in. Its value is "en" (English)
-	by default.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="small-icon" type="j2ee:pathType"
-		   minOccurs="0">
-	<xsd:annotation>
-	  <xsd:documentation>
-	    <![CDATA[
-
-	      The small-icon element contains the name of a file
-	      containing a small (16 x 16) icon image. The file
-	      name is a relative path within the Deployment
-	      Component's Deployment File.
-
-	      The image may be either in the JPEG or GIF format.
-	      The icon can be used by tools.
-
-	      Example:
-
-	      <small-icon>employee-service-icon16x16.jpg</small-icon>
-
-	      ]]>
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="large-icon" type="j2ee:pathType"
-		   minOccurs="0">
-	<xsd:annotation>
-	  <xsd:documentation>
-	    <![CDATA[
-
-	      The large-icon element contains the name of a file
-	      containing a large
-	      (32 x 32) icon image. The file name is a relative
-	      path within the Deployment Component's Deployment
-	      File.
-
-	      The image may be either in the JPEG or GIF format.
-	      The icon can be used by tools.
-
-	      Example:
-
-	      <large-icon>employee-service-icon32x32.jpg</large-icon>
-
-	      ]]>
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-    </xsd:sequence>
-
-    <xsd:attribute ref="xml:lang"/>
-    <xsd:attribute name="id" type="xsd:ID"/>
-
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="java-identifierType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The java-identifierType defines a Java identifier.
-	The users of this type should further verify that
-	the content does not contain Java reserved keywords.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:string">
-	<xsd:pattern value="($|_|\p{L})(\p{L}|\p{Nd}|_|$)*"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="java-typeType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This is a generic type that designates a Java primitive
-	type or a fully qualified name of a Java interface/type,
-	or an array of such types.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:string">
-	<xsd:pattern value="[^\p{Z}]*"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="jndi-nameType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The jndi-nameType type designates a JNDI name in the
-	Deployment Component's environment and is relative to the
-	java:comp/env context.  A JNDI name must be unique within the
-	Deployment Component.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:group name="jndiEnvironmentRefsGroup">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This group keeps the usage of the contained JNDI environment
-	reference elements consistent across J2EE deployment descriptors.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="env-entry"
-		   type="j2ee:env-entryType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-      <xsd:element name="ejb-ref"
-		   type="j2ee:ejb-refType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-      <xsd:element name="ejb-local-ref"
-		   type="j2ee:ejb-local-refType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-      <xsd:group ref="j2ee:service-refGroup"/>
-      <xsd:element name="resource-ref"
-		   type="j2ee:resource-refType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-      <xsd:element name="resource-env-ref"
-		   type="j2ee:resource-env-refType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-      <xsd:element name="message-destination-ref"
-		   type="j2ee:message-destination-refType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-    </xsd:sequence>
-  </xsd:group>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="listenerType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The listenerType indicates the deployment properties for a web
-	application listener bean.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:group ref="j2ee:descriptionGroup"/>
-      <xsd:element name="listener-class"
-		   type="j2ee:fully-qualified-classType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The listener-class element declares a class in the
-	    application must be registered as a web
-	    application listener bean. The value is the fully
-	    qualified classname of the listener class.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="local-homeType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The local-homeType defines the fully-qualified
-	name of an enterprise bean's local home interface.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:fully-qualified-classType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="localType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The localType defines the fully-qualified name of an
-	enterprise bean's local interface.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:fully-qualified-classType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="message-destination-linkType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The message-destination-linkType is used to link a message
-	destination reference or message-driven bean to a message
-	destination.
-
-	The Assembler sets the value to reflect the flow of messages
-	between producers and consumers in the application.
-
-	The value must be the message-destination-name of a message
-	destination in the same Deployment File or in another
-	Deployment File in the same J2EE application unit.
-
-	Alternatively, the value may be composed of a path name
-	specifying a Deployment File containing the referenced
-	message destination with the message-destination-name of the
-	destination appended and separated from the path name by
-	"#". The path name is relative to the Deployment File
-	containing Deployment Component that is referencing the
-	message destination.  This allows multiple message
-	destinations with the same name to be uniquely identified.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="message-destination-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The message-destination-ref element contains a declaration
-	  of Deployment Component's reference to a message destination
-	  associated with a resource in Deployment Component's
-	  environment. It consists of:
-
-		  - an optional description
-		  - the message destination reference name
-		  - the message destination type
-		  - a specification as to whether the
-		    destination is used for
-		    consuming or producing messages, or both
-		  - a link to the message destination
-
-	  Examples:
-
-	  <message-destination-ref>
-		  <message-destination-ref-name>jms/StockQueue
-		  </message-destination-ref-name>
-		  <message-destination-type>javax.jms.Queue
-		  </message-destination-type>
-		  <message-destination-usage>Consumes
-		  </message-destination-usage>
-		  <message-destination-link>CorporateStocks
-		  </message-destination-link>
-	  </message-destination-ref>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="j2ee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="message-destination-ref-name"
-		   type="j2ee:jndi-nameType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The message-destination-ref-name element specifies
-	    the name of a message destination reference; its
-	    value is the environment entry name used in
-	    Deployment Component code.  The name is a JNDI name
-	    relative to the java:comp/env context and must be
-	    unique within an ejb-jar (for enterprise beans) or a
-	    Deployment File (for others).
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="message-destination-type"
-		   type="j2ee:message-destination-typeType"/>
-      <xsd:element name="message-destination-usage"
-		   type="j2ee:message-destination-usageType"/>
-      <xsd:element name="message-destination-link"
-		   type="j2ee:message-destination-linkType"
-		   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="message-destination-typeType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The message-destination-typeType specifies the type of
-	  the destination. The type is specified by the Java interface
-	  expected to be implemented by the destination.
-
-	  Example:
-
-	    <message-destination-type>javax.jms.Queue
-	    </message-destination-type>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:fully-qualified-classType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="message-destination-usageType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The message-destination-usageType specifies the use of the
-	message destination indicated by the reference.  The value
-	indicates whether messages are consumed from the message
-	destination, produced for the destination, or both.  The
-	Assembler makes use of this information in linking producers
-	of a destination with its consumers.
-
-	The value of the message-destination-usage element must be
-	one of the following:
-	    Consumes
-	    Produces
-	    ConsumesProduces
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:string">
-	<xsd:enumeration value="Consumes"/>
-	<xsd:enumeration value="Produces"/>
-	<xsd:enumeration value="ConsumesProduces"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="message-destinationType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The message-destinationType specifies a message
-	  destination. The logical destination described by this
-	  element is mapped to a physical destination by the Deployer.
-
-	  The message destination element contains:
-
-		  - an optional description
-		  - an optional display-name
-		  - an optional icon
-		  - a message destination name which must be unique
-		    among message destination names within the same
-		    Deployment File.
-
-	  Example:
-
-	  <message-destination>
-		  <message-destination-name>CorporateStocks
-		  </message-destination-name>
-	  </message-destination>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:group ref="j2ee:descriptionGroup"/>
-      <xsd:element name="message-destination-name"
-		   type="j2ee:string">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The message-destination-name element specifies a
-	    name for a message destination.  This name must be
-	    unique among the names of message destinations
-	    within the Deployment File.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="param-valueType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This type is a general type that can be used to declare
-	parameter/value lists.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="j2ee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="param-name"
-		   type="j2ee:string">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The param-name element contains the name of a
-	    parameter.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="param-value"
-		   type="j2ee:xsdStringType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The param-value element contains the value of a
-	    parameter.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="pathType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The elements that use this type designate either a relative
-	path or an absolute path starting with a "/".
-
-	In elements that specify a pathname to a file within the
-	same Deployment File, relative filenames (i.e., those not
-	starting with "/") are considered relative to the root of
-	the Deployment File's namespace.  Absolute filenames (i.e.,
-	those starting with "/") also specify names in the root of
-	the Deployment File's namespace.  In general, relative names
-	are preferred.  The exception is .war files where absolute
-	names are preferred for consistency with the Servlet API.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="remoteType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The remote element contains the fully-qualified name
-	  of the enterprise bean's remote interface.
-
-	  Example:
-
-	      <remote>com.wombat.empl.EmployeeService</remote>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:fully-qualified-classType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="res-authType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The res-authType specifies whether the Deployment Component
-	code signs on programmatically to the resource manager, or
-	whether the Container will sign on to the resource manager
-	on behalf of the Deployment Component. In the latter case,
-	the Container uses information that is supplied by the
-	Deployer.
-
-	The value must be one of the two following:
-
-	    Application
-	    Container
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:string">
-	<xsd:enumeration value="Application"/>
-	<xsd:enumeration value="Container"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="res-sharing-scopeType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The res-sharing-scope type specifies whether connections
-	obtained through the given resource manager connection
-	factory reference can be shared. The value, if specified,
-	must be one of the two following:
-
-	    Shareable
-	    Unshareable
-
-	The default value is Shareable.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:string">
-	<xsd:enumeration value="Shareable"/>
-	<xsd:enumeration value="Unshareable"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="resource-env-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The resource-env-refType is used to define
-	  resource-env-type elements.  It contains a declaration of a
-	  Deployment Component's reference to an administered object
-	  associated with a resource in the Deployment Component's
-	  environment.  It consists of an optional description, the
-	  resource environment reference name, and an indication of
-	  the resource environment reference type expected by the
-	  Deployment Component code.
-
-	  Example:
-
-	  <resource-env-ref>
-	      <resource-env-ref-name>jms/StockQueue
-	      </resource-env-ref-name>
-	      <resource-env-ref-type>javax.jms.Queue
-	      </resource-env-ref-type>
-	  </resource-env-ref>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="j2ee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="resource-env-ref-name"
-		   type="j2ee:jndi-nameType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The resource-env-ref-name element specifies the name
-	    of a resource environment reference; its value is
-	    the environment entry name used in
-	    the Deployment Component code.  The name is a JNDI
-	    name relative to the java:comp/env context and must
-	    be unique within a Deployment Component.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="resource-env-ref-type"
-		   type="j2ee:fully-qualified-classType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The resource-env-ref-type element specifies the type
-	    of a resource environment reference.  It is the
-	    fully qualified name of a Java language class or
-	    interface.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="resource-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The resource-refType contains a declaration of a
-	  Deployment Component's reference to an external resource. It
-	  consists of an optional description, the resource manager
-	  connection factory reference name, the indication of the
-	  resource manager connection factory type expected by the
-	  Deployment Component code, the type of authentication
-	  (Application or Container), and an optional specification of
-	  the shareability of connections obtained from the resource
-	  (Shareable or Unshareable).
-
-	  Example:
-
-	  <resource-ref>
-	      <res-ref-name>jdbc/EmployeeAppDB</res-ref-name>
-	      <res-type>javax.sql.DataSource</res-type>
-	      <res-auth>Container</res-auth>
-	      <res-sharing-scope>Shareable</res-sharing-scope>
-	  </resource-ref>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="j2ee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="res-ref-name"
-		   type="j2ee:jndi-nameType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The res-ref-name element specifies the name of a
-	    resource manager connection factory reference.
-	    The name is a JNDI name relative to the
-	    java:comp/env context.
-	    The name must be unique within a Deployment File.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="res-type"
-		   type="j2ee:fully-qualified-classType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The res-type element specifies the type of the data
-	    source. The type is specified by the fully qualified
-	    Java language class or interface
-	    expected to be implemented by the data source.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="res-auth"
-		   type="j2ee:res-authType"/>
-
-      <xsd:element name="res-sharing-scope"
-		   type="j2ee:res-sharing-scopeType"
-		   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="role-nameType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The role-nameType designates the name of a security role.
-
-	The name must conform to the lexical rules for a token.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="run-asType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The run-asType specifies the run-as identity to be
-	used for the execution of a component. It contains an
-	optional description, and the name of a security role.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="j2ee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="role-name"
-		   type="j2ee:role-nameType"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="security-role-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The security-role-refType contains the declaration of a
-	security role reference in a component's or a
-	Deployment Component's code. The declaration consists of an
-	optional description, the security role name used in the
-	code, and an optional link to a security role. If the
-	security role is not specified, the Deployer must choose an
-	appropriate security role.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="j2ee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="role-name"
-		   type="j2ee:role-nameType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The value of the role-name element must be the String used
-	    as the parameter to the
-	    EJBContext.isCallerInRole(String roleName) method or the
-	    HttpServletRequest.isUserInRole(String role) method.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="role-link"
-		   type="j2ee:role-nameType"
-		   minOccurs="0">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The role-link element is a reference to a defined
-	    security role. The role-link element must contain
-	    the name of one of the security roles defined in the
-	    security-role elements.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="security-roleType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The security-roleType contains the definition of a security
-	  role. The definition consists of an optional description of the
-	  security role, and the security role name.
-
-	  Example:
-
-	      <security-role>
-	      <description>
-		  This role includes all employees who are authorized
-		  to access the employee service application.
-	      </description>
-	      <role-name>employee</role-name>
-	      </security-role>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="j2ee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="role-name"
-		   type="j2ee:role-nameType"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="string">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This is a special string datatype that is defined by J2EE as
-	a base type for defining collapsed strings. When schemas
-	require trailing/leading space elimination as well as
-	collapsing the existing whitespace, this base type may be
-	used.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:token">
-	<xsd:attribute name="id" type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="true-falseType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This simple type designates a boolean with only two
-	permissible values
-
-	- true
-	- false
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:xsdBooleanType">
-	<xsd:pattern value="(true|false)"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="url-patternType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The url-patternType contains the url pattern of the mapping.
-	It must follow the rules specified in Section 11.2 of the
-	Servlet API Specification. This pattern is assumed to be in
-	URL-decoded form and must not contain CR(#xD) or LF(#xA).
-	If it contains those characters, the container must inform
-	the developer with a descriptive error message.
-	The container must preserve all characters including whitespaces.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="xsdAnyURIType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This type adds an "id" attribute to xsd:anyURI.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:anyURI">
-	<xsd:attribute name="id" type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="xsdBooleanType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This type adds an "id" attribute to xsd:boolean.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:boolean">
-	<xsd:attribute name="id" type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="xsdIntegerType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This type adds an "id" attribute to xsd:integer.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:integer">
-	<xsd:attribute name="id" type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="xsdNMTOKENType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This type adds an "id" attribute to xsd:NMTOKEN.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:NMTOKEN">
-	<xsd:attribute name="id" type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="xsdNonNegativeIntegerType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This type adds an "id" attribute to xsd:nonNegativeInteger.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:nonNegativeInteger">
-	<xsd:attribute name="id" type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="xsdPositiveIntegerType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This type adds an "id" attribute to xsd:positiveInteger.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:positiveInteger">
-	<xsd:attribute name="id" type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="xsdQNameType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This type adds an "id" attribute to xsd:QName.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:QName">
-	<xsd:attribute name="id" type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="xsdStringType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This type adds an "id" attribute to xsd:string.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:string">
-	<xsd:attribute name="id" type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-</xsd:schema>
-

jboss-as-7.2.0.Final/docs/schema/j2ee_jaxrpc_mapping_1_1.xsd

@@ -1,885 +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.1">
-  <xsd:annotation>
-    <xsd:documentation>
-      @(#)j2ee_jaxrpc_mapping_1_1.xsds	1.11 09/03/03
-
-      Based on j2ee_jaxrpc_mapping_1_0.dtd, Last updated: 09/19/2002 10:26
-    </xsd:documentation>
-  </xsd:annotation>
-
-  <xsd:annotation>
-    <xsd:documentation>
-
-      Copyright 2003 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>
-
-      (C) Copyright International Business Machines Corporation 2002
-
-    </xsd:documentation>
-  </xsd:annotation>
-
-  <xsd:annotation>
-    <xsd:documentation>
-      <![CDATA[
-
-	The element describes the Java mapping to a known WSDL document.
-
-	It contains the mapping between package names and XML namespaces,
-	WSDL root types and Java artifacts, and the set of mappings for
-	services.
-
-	All java-wsdl-mapping deployment descriptors must indicate 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:
-
-	    <java-wsdl-mapping 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://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd"
-	      version="1.1">
-	      ...
-	    </java-wsdl-mapping>
-
-	The instance documents may indicate the published version of
-	the schema using the xsi:schemaLocation attribute for J2EE
-	namespace with the following location:
-
-	http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_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>
-
-  <xsd:include schemaLocation="j2ee_1_4.xsd"/>
-
-
-<!-- **************************************************** -->
-
-
-  <xsd:element name="java-wsdl-mapping" type="j2ee:java-wsdl-mappingType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This is the root of the java-wsdl-mapping deployment descriptor.
-
-      </xsd:documentation>
-    </xsd:annotation>
-  </xsd:element>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="constructor-parameter-orderType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The constructor-parameter-order element defines the order
-	that complexType element values are applied to a Java
-	exception constructor. Element names are specified for each
-	parameter of the constructor, including element names of
-	inherited types if necessary.
-
-	Used in: exception-mapping
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="element-name"
-		   type="j2ee:string"
-		   minOccurs="1" maxOccurs="unbounded">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The element-name element defines the name of a complexType
-	    element name attribute value.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="exception-mappingType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The exception-mapping element defines the mapping between the
-	service specific exception types and wsdl faults and
-	SOAP headerfaults.
-
-	This element should be interpreted with respect to the
-	mapping between a method and an operation which provides the
-	mapping context.
-
-	Used in: service-endpoint-method-mapping
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="exception-type"
-		   type="j2ee:fully-qualified-classType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The exception-type element defines Java type of the exception.
-	    It may be a service specific exception.
-
-	    It must be a fully qualified class name.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="wsdl-message"
-		   type="j2ee:wsdl-messageType"/>
-      <xsd:element name="wsdl-message-part-name"
-		   type="j2ee:wsdl-message-part-nameType"
-		   minOccurs="0" maxOccurs="1">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-            The wsdl-message-part-name element is required only
-            when the message referenced by the wsdl-message element
-            has more than one part.
-
-            This only occurs when multiple headerfaults use the
-            same message.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="constructor-parameter-order"
-		   type="j2ee:constructor-parameter-orderType"
-		   minOccurs="0" maxOccurs="1"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="java-wsdl-mappingType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The element describes the Java mapping to a known WSDL document.
-
-	It contains the mapping between package names and XML namespaces,
-	WSDL root types and Java artifacts, and the set of mappings for
-	services.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="package-mapping"
-		   type="j2ee:package-mappingType"
-		   minOccurs="1" maxOccurs="unbounded"/>
-      <xsd:element name="java-xml-type-mapping"
-		   type="j2ee:java-xml-type-mappingType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-      <xsd:element name="exception-mapping"
-		   type="j2ee:exception-mappingType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-      <xsd:sequence minOccurs="0" maxOccurs="unbounded">
-        <xsd:element name="service-interface-mapping"
-		     type="j2ee:service-interface-mappingType"
-		     minOccurs="0" maxOccurs="1"/>
-        <xsd:element name="service-endpoint-interface-mapping"
-		     type="j2ee:service-endpoint-interface-mappingType"
-		     minOccurs="1" maxOccurs="unbounded"/>
-      </xsd:sequence>
-    </xsd:sequence>
-
-    <xsd:attribute name="version"
-		   type="j2ee:dewey-versionType"
-		   fixed="1.1"
-		   use="required">
-      <xsd:annotation>
-	<xsd:documentation>
-
-	  The required value for the version is 1.1.
-
-	</xsd:documentation>
-      </xsd:annotation>
-    </xsd:attribute>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="java-xml-type-mappingType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The java-xml-type-mapping element contains a java-type that is the
-	fully qualified name of the Java class, primitive type, or array
-	type, QName of the XML root type or anonymous type, the WSDL type
-	scope the QName applies to and the set of variable mappings for
-	each public variable within the Java class.
-
-	Used in: java-wsdl-mapping
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="java-type"
-		   type="j2ee:java-typeType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The java-type element is the fully qualified class name of
-	    a Java class, primitive, or array type.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <choice>
-        <xsd:element name="root-type-qname"
-		   type="j2ee:xsdQNameType">
-	  <xsd:annotation>
-	    <xsd:documentation>
-
-	      The root-type-qname identifies the WSDL QName of an XML type.
-
-	    </xsd:documentation>
-	  </xsd:annotation>
-        </xsd:element>
-        <xsd:element name="anonymous-type-qname"
-		   type="j2ee:string">
-	  <xsd:annotation>
-	    <xsd:documentation>
-
-	      The anonymous-type-qname identifies the WSDL QName of an
-	      anonymous XML type.
-
-	    </xsd:documentation>
-	  </xsd:annotation>
-        </xsd:element>
-      </choice>
-      <xsd:element name="qname-scope"
-		   type="j2ee:qname-scopeType"/>
-      <xsd:element name="variable-mapping"
-		   type="j2ee:variable-mappingType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="method-param-parts-mappingType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The method-param-parts-mapping element defines the mapping between a
-	Java method parameters and a wsdl-message.
-
-	Used in: service-endpoint-method-mapping
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="param-position"
-		   type="j2ee:xsdNonNegativeIntegerType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The param-position element defines the position of a
-	    parameter within a Java method.  It must be an integer
-	    starting from 0.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="param-type"
-		   type="j2ee:java-typeType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The param-type element defines the fully qualified
-	    class name of a Java class, primitive, or array type.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="wsdl-message-mapping"
-		   type="j2ee:wsdl-message-mappingType"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="package-mappingType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The package-mapping indicates the mapping between java-package-name
-	and XML namespace in the WSDL document.
-
-	Used in: java-wsdl-mapping
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="package-type"
-		   type="j2ee:fully-qualified-classType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The package-type indicates the Java package name. It must be a fully
-	    qualified package name, even though the XML schema type is
-	    fully-qualified-classType.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="namespaceURI"
-		   type="j2ee:xsdAnyURIType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The namespaceURI element indicates a URI.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="parameter-modeType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The parameter-mode element defines the mode of the parameter.
-	It can have only three values, IN, OUT, INOUT.
-
-	Used in: java-xml-type-mapping
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:string">
-	<xsd:enumeration value="IN"/>
-	<xsd:enumeration value="OUT"/>
-	<xsd:enumeration value="INOUT"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="port-mappingType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The port-mapping defines the mapping of the WSDL port name attribute
-	to the Java name used to generate the Generated Service Interface
-	method get{java-name}.
-
-	Used in: service-interface-mapping
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="port-name"
-		   type="j2ee:string">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The port-mapping defines the mapping of the WSDL port name
-	    attribute to the Java name used to generate the Generated
-	    Service Interface method get{java-name}.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="java-port-name"
-		   type="j2ee:string">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The java-port-name element is the string to use as the port
-	    name in Java.  It is used in generating the Generated
-	    Service Interface method get{java-port-name}.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="qname-scopeType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The qname-scope elements scopes the reference of a QName to the WSDL
-	element type it applies to. The value of qname-scope may be
-	simpleType, complexType, or element.
-
-	Used in: java-xml-type-mapping
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:string">
-	<xsd:enumeration value="simpleType"/>
-	<xsd:enumeration value="complexType"/>
-	<xsd:enumeration value="element"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="service-endpoint-interface-mappingType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The service-endpoint-interface-mapping defines a tuple
-	to specify Service Endpoint Interfaces to
-	WSDL port types and WSDL bindings.
-
-	An interface may be mapped to a port-type and binding multiple
-	times. This happens rarely.
-
-	Used in: java-wsdl-mapping
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="service-endpoint-interface"
-		   type="j2ee:fully-qualified-classType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The service-endpoint-interface element defines the Java
-	    type for the endpoint interface. The name must be a fully
-	    qualified class name.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="wsdl-port-type"
-		   type="j2ee:xsdQNameType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The wsdl-port-type element defines the wsdl port type
-	    by a QNAME which uniquely identifies  the port type.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="wsdl-binding"
-		   type="j2ee:xsdQNameType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The wsdl-binding element defines the wsdl binding
-	    by a QNAME which uniquely identifies  the binding.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="service-endpoint-method-mapping"
-		   type="j2ee:service-endpoint-method-mappingType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="service-endpoint-method-mappingType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The service-endpoint-method-mapping element defines the mapping of
-	Java methods to operations (which are not uniquely qualified by
-	qnames).
-
-	The wsdl-operation should be interpreted with respect to the
-	portType and binding in which this definition is embedded within.
-	See the definitions for service-endpoint-interface-mapping and
-	service-interface-mapping to acquire the proper context.  The
-	wrapped-element indicator should only be specified when a WSDL
-	message wraps an element type.  The wsdl-return-value-mapping is
-	not specified for one-way operations.
-
-	Used in: service-endpoint-interface-mapping
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="java-method-name"
-		   type="j2ee:string">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The java-method-name element defines the name of a Java method
-	    within an interface.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="wsdl-operation"
-		   type="j2ee:string">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The wsdl-operation element defines an operation within a WSDL
-	    document.  It must be interpreted with respect to a port type.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="wrapped-element"
-		   type="j2ee:emptyType"
-		   minOccurs="0"
-		   maxOccurs="1">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The wrapped-element element is defined when a WSDL message
-	    with a single part is used to wrap an element type and the
-	    element's name matches the operation name.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="method-param-parts-mapping"
-		   type="j2ee:method-param-parts-mappingType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="wsdl-return-value-mapping"
-		   type="j2ee:wsdl-return-value-mappingType"
-		   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="service-interface-mappingType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The service-interface-mapping element defines how a Java type for
-	the service interface maps to a WSDL service.
-
-	Used in: java-wsdl-mapping
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="service-interface"
-		   type="j2ee:fully-qualified-classType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The service-interface element defines the Java type for the service.
-	    For static services, it is javax.xml.rpc.Service interface. For
-	    generated service, it would be the generated interface name.
-
-	    The name must be a fully qualified class name.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="wsdl-service-name"
-		   type="j2ee:xsdQNameType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The wsdl-service-name element defines the wsdl service name
-	    by a QNAME which uniquely identifies  the service.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="port-mapping"
-		   type="j2ee:port-mappingType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="variable-mappingType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The variable-mapping element defines the correlation between a
-	Java class data member or JavaBeans property to an XML element
-	or attribute name of an XML root type. If the data-member
-	element is present, the Java variable name is a public data
-	member.  If data-member	is not present, the Java variable name
-	is a JavaBeans property.
-
-	Used in: java-xml-type-mapping
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="java-variable-name"
-		   type="j2ee:string">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The java-variable-name defines the name of a public data member or
-	    JavaBeans property within a Java class.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="data-member"
-		   type="j2ee:emptyType"
-		   minOccurs="0" maxOccurs="1">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The data-member element is a boolean indicator that a Java
-	    variable is a public data member and not a JavaBeans property.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:choice>
-        <xsd:element name="xml-attribute-name"
-		     type="j2ee:string">
-	  <xsd:annotation>
-	    <xsd:documentation>
-
-	      The xml-attribute-name element defines name attribute value
-	      of a WSDL attribute element within a root type.  The value
-	      of an xml-attribute-name element must match the value of
-	      the ref attribute if mapping an attribute reference.
-
-	    </xsd:documentation>
-	  </xsd:annotation>
-        </xsd:element>
-        <xsd:element name="xml-element-name"
-		     type="j2ee:string">
-	  <xsd:annotation>
-	    <xsd:documentation>
-
-	      The xml-element-name element defines name attribute value of
-	      a WSDL element within a root type.  The value of an
-	      xml-element-name element must match the value of the ref
-	      attribute if mapping an element reference.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-        </xsd:element>
-        <xsd:element name="xml-wildcard"
-		     type="j2ee:emptyType">
-	  <xsd:annotation>
-	    <xsd:documentation>
-
-	      The xml-wildcard element associates the variable-mapping with
-	      an xsd:any element within a root type.
-
-	    </xsd:documentation>
-	  </xsd:annotation>
-        </xsd:element>
-      </xsd:choice>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="wsdl-message-mappingType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The wsdl-message-mapping element defines the mapping to a
-	specific message and its part. Together they define uniquely
-	the mapping for a specific parameter. Parts within a message
-	context are uniquely identified with their names.
-
-	The parameter-mode is defined by the mapping to indicate
-	whether the mapping will be IN, OUT, or INOUT..  The presence
-	of the soap-header element indicates that the parameter is
-	mapped to a soap header only.  When absent, it means that the
-	wsdl-message is mapped to a Java parameter. The soap headers
-	are interpreted in the order they are provided in the mapping.
-
-	Used in: method-param-parts-mapping
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="wsdl-message"
-		   type="j2ee:wsdl-messageType"/>
-      <xsd:element name="wsdl-message-part-name"
-		   type="j2ee:wsdl-message-part-nameType"/>
-      <xsd:element name="parameter-mode"
-		   type="j2ee:parameter-modeType"/>
-      <xsd:element name="soap-header"
-		   type="j2ee:emptyType"
-		   minOccurs="0" maxOccurs="1">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The soap-header element is a boolean element indicating that
-	    a parameter is mapped to a SOAP header.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="wsdl-message-part-nameType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	Interpretation of the wsdl-message-part-name element depends on
-	whether or not wrapped-element has been defined in the
-	service-endpoint-method-mapping.  If wrapped-element is not
-	specified, wsdl-message-part-name defines a WSDL message part. It
-	should always be interpreted with respect to a wsdl-message
-	element. If wrapped-element is specified, wsdl-message-part-name
-	refers to an element name of the element type.
-
-	Used in: wsdl-message-mapping, wsdl-return-value-mapping
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="wsdl-messageType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The wsdl-message element defines a WSDL message by a QNAME.
-
-	Used in: wsdl-message-mapping, wsdl-return-value-mapping,
-	exception-mapping
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:xsdQNameType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="wsdl-return-value-mappingType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The wsdl-return-value-mapping  element defines the mapping for the
-	method's return value. It defines the mapping to a specific message
-	and its part.  Together they define uniquely the mapping for a
-	specific parameter. Parts within a message context are uniquely
-	identified with their names. The wsdl-message-part-name is not
-	specified if there is no return value or OUT parameters.
-
-	Used in: service-endpoint-method-mapping
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="method-return-value"
-		   type="j2ee:fully-qualified-classType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The method-return-value  element defines a fully qualified
-	    class name or void type for the method's return value
-	    type.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="wsdl-message"
-		   type="j2ee:wsdl-messageType"/>
-      <xsd:element name="wsdl-message-part-name"
-		   type="j2ee:wsdl-message-part-nameType"
-		   minOccurs="0"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-</xsd:schema>
-

jboss-as-7.2.0.Final/docs/schema/j2ee_web_services_1_1.xsd

@@ -1,490 +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.1">
-  <xsd:annotation>
-    <xsd:documentation>
-      @(#)j2ee_web_services_1_1.xsds	1.11 02/11/03
-    </xsd:documentation>
-  </xsd:annotation>
-
-  <xsd:annotation>
-    <xsd:documentation>
-
-      Copyright 2003 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>
-
-      (C) Copyright International Business Machines Corporation 2002
-
-    </xsd:documentation>
-  </xsd:annotation>
-
-  <xsd:annotation>
-    <xsd:documentation>
-      <![CDATA[
-
-	The webservices element is the root element for the web services
-	deployment descriptor.  It specifies the set of web service
-	descriptions that are to be deployed into the J2EE Application
-	Server and the dependencies they have on container resources and
-	services.  The deployment descriptor must be named
-	"META-INF/webservices.xml" in the web services' jar file.
-
-	Used in: webservices.xml
-
-	All webservices deployment descriptors must indicate the
-	webservices 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:
-
-	    <webservices 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://www.ibm.com/webservices/xsd/j2ee_web_services_1_1.xsd"
-	      version="1.1">
-	      ...
-	    </webservices>
-
-	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://www.ibm.com/webservices/xsd/j2ee_web_services_1_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>
-
-  <xsd:include schemaLocation="j2ee_1_4.xsd"/>
-
-
-  <!-- **************************************************** -->
-
-
-  <xsd:element name="webservices" type="j2ee:webservicesType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The webservices element is the root element for the web services
-	deployment descriptor.  It specifies the set of web service
-	descriptions that are to be deployed into the J2EE Application Server
-	and the dependencies they have on container resources and services.
-
-	Used in: webservices.xml
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:key name="webservice-description-name-key">
-      <xsd:annotation>
-        <xsd:documentation>
-
-	  The webservice-description-name identifies the collection of
-	  port-components associated with a WSDL file and JAX-RPC mapping. The
-	  name must be unique within the deployment descriptor.
-
-        </xsd:documentation>
-      </xsd:annotation>
-      <xsd:selector xpath="j2ee:webservice-description"/>
-      <xsd:field xpath="j2ee:webservice-description-name"/>
-    </xsd:key>
-  </xsd:element>
-
-  <!-- **************************************************** -->
-
-  <xsd:complexType name="port-componentType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The port-component element associates a WSDL port with a web service
-	interface and implementation.  It defines the name of the port as a
-	component, optional description, optional display name, optional iconic
-	representations, WSDL port QName, Service Endpoint Interface, Service
-	Implementation Bean.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="description"
-        type="j2ee:descriptionType"
-        minOccurs="0" maxOccurs="1"/>
-      <xsd:element name="display-name"
-        type="j2ee:display-nameType"
-        minOccurs="0" maxOccurs="1"/>
-      <xsd:element name="icon"
-        type="j2ee:iconType"
-        minOccurs="0" maxOccurs="1"/>
-      <xsd:element name="port-component-name"
-        type="j2ee:string">
-        <xsd:annotation>
-          <xsd:documentation>
-            <![CDATA[
-
-	      The port-component-name element specifies a port component's
-	      name.  This name is assigned by the module producer to name
-	      the service implementation bean in the module's deployment
-	      descriptor. The name must be unique among the port component
-	      names defined in the same module.
-
-	      Used in: port-component
-
-	      Example:
-		      <port-component-name>EmployeeService
-		      </port-component-name>
-
-              ]]>
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="wsdl-port"
-        type="j2ee:xsdQNameType">
-        <xsd:annotation>
-          <xsd:documentation>
-
-	    Defines the name space and local name part of the WSDL port QName.
-
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="service-endpoint-interface"
-        type="j2ee:fully-qualified-classType">
-        <xsd:annotation>
-          <xsd:documentation>
-            <![CDATA[
-
-	      The service-endpoint-interface element contains the
-	      fully-qualified name of the port component's Service Endpoint
-	      Interface.
-
-	      Used in: port-component
-
-	      Example:
-		      <remote>com.wombat.empl.EmployeeService</remote>
-
-              ]]>
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="service-impl-bean"
-        type="j2ee:service-impl-beanType"/>
-
-      <xsd:element name="handler"
-        type="j2ee:port-component_handlerType"
-        minOccurs="0" maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-  <!-- **************************************************** -->
-
-  <xsd:complexType name="port-component_handlerType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	Declares the handler for a port-component. Handlers can access the
-	init-param name/value pairs using the HandlerInfo interface.
-
-	Used in: port-component
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:group ref="j2ee:descriptionGroup"/>
-      <xsd:element name="handler-name"
-        type="j2ee:string">
-        <xsd:annotation>
-          <xsd:documentation>
-
-	    Defines the name of the handler. The name must be unique within the
-	    module.
-
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="handler-class"
-        type="j2ee:fully-qualified-classType">
-        <xsd:annotation>
-          <xsd:documentation>
-
-	    Defines a fully qualified class name for the handler implementation.
-
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="init-param"
-        type="j2ee:param-valueType"
-        minOccurs="0" maxOccurs="unbounded"/>
-
-      <xsd:element name="soap-header"
-        type="j2ee:xsdQNameType"
-        minOccurs="0" maxOccurs="unbounded">
-        <xsd:annotation>
-          <xsd:documentation>
-
-	    Defines the QName of a SOAP header that will be processed by the
-	    handler.
-
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="soap-role"
-        type="j2ee:string"
-        minOccurs="0" maxOccurs="unbounded">
-        <xsd:annotation>
-          <xsd:documentation>
-
-	    The soap-role element contains a SOAP actor definition that the
-	    Handler will play as a role.
-
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-  <!-- **************************************************** -->
-
-  <xsd:complexType name="service-impl-beanType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The service-impl-bean element defines the web service implementation.
-	A service implementation can be an EJB bean class or JAX-RPC web
-	component.  Existing EJB implementations are exposed as a web service
-	using an ejb-link.
-
-	Used in: port-component
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:choice>
-      <xsd:element name="ejb-link"
-        type="j2ee:ejb-linkType"/>
-      <xsd:element name="servlet-link"
-        type="j2ee:servlet-linkType"/>
-    </xsd:choice>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-  <!-- **************************************************** -->
-
-  <xsd:complexType name="servlet-linkType">
-    <xsd:annotation>
-      <xsd:documentation>
-        <![CDATA[
-
-	  The servlet-link element is used in the service-impl-bean element
-	  to specify that a Service Implementation Bean is defined as a
-	  JAX-RPC Service Endpoint.
-
-	  The value of the servlet-link element must be the servlet-name of
-	  a JAX-RPC Service Endpoint in the same WAR file.
-
-	  Used in: service-impl-bean
-
-	  Example:
-		  <servlet-link>StockQuoteService</servlet-link>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="j2ee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-  <!-- **************************************************** -->
-
-  <xsd:complexType name="webservice-descriptionType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The webservice-description element defines a WSDL document file
-	and the set of Port components associated with the WSDL ports
-	defined in the WSDL document.  There may be multiple
-	webservice-descriptions defined within a module.
-
-	All WSDL file ports must have a corresponding port-component element
-	defined.
-
-	Used in: webservices
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="description"
-        type="j2ee:descriptionType"
-        minOccurs="0" maxOccurs="1"/>
-      <xsd:element name="display-name"
-        type="j2ee:display-nameType"
-        minOccurs="0" maxOccurs="1"/>
-      <xsd:element name="icon"
-        type="j2ee:iconType"
-        minOccurs="0" maxOccurs="1"/>
-      <xsd:element name="webservice-description-name"
-        type="j2ee:string">
-        <xsd:annotation>
-          <xsd:documentation>
-
-	    The webservice-description-name identifies the collection of
-	    port-components associated with a WSDL file and JAX-RPC
-	    mapping. The name must be unique within the deployment descriptor.
-
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="wsdl-file"
-        type="j2ee:pathType">
-        <xsd:annotation>
-          <xsd:documentation>
-
-	    The wsdl-file element contains the name of a WSDL file in the
-	    module.  The file name is a relative path within the module.
-
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="jaxrpc-mapping-file"
-        type="j2ee:pathType">
-        <xsd:annotation>
-          <xsd:documentation>
-
-	    The jaxrpc-mapping-file element contains the name of a file that
-	    describes the JAX-RPC mapping between the Java interaces used by
-	    the application and the WSDL description in the wsdl-file.  The
-	    file name is a relative path within the module.
-
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="port-component"
-        type="j2ee:port-componentType"
-        minOccurs="1" maxOccurs="unbounded">
-        <xsd:key name="port-component_handler-name-key">
-          <xsd:annotation>
-            <xsd:documentation>
-
-	      Defines the name of the handler. The name must be unique
-	      within the module.
-
-            </xsd:documentation>
-          </xsd:annotation>
-          <xsd:selector xpath="j2ee:handler"/>
-          <xsd:field xpath="j2ee:handler-name"/>
-        </xsd:key>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-  <!-- **************************************************** -->
-
-  <xsd:complexType name="webservicesType">
-    <xsd:sequence>
-      <xsd:group ref="j2ee:descriptionGroup"/>
-      <xsd:element name="webservice-description"
-        type="j2ee:webservice-descriptionType"
-        minOccurs="1" maxOccurs="unbounded">
-        <xsd:key name="port-component-name-key">
-          <xsd:annotation>
-            <xsd:documentation>
-              <![CDATA[
-
-		The port-component-name element specifies a port
-		component's name.  This name is assigned by the module
-		producer to name the service implementation bean in the
-		module's deployment descriptor. The name must be unique
-		among the port component names defined in the same module.
-
-		Used in: port-component
-
-		Example:
-			<port-component-name>EmployeeService
-			</port-component-name>
-
-          ]]>
-            </xsd:documentation>
-          </xsd:annotation>
-          <xsd:selector xpath="j2ee:port-component"/>
-          <xsd:field xpath="j2ee:port-component-name"/>
-        </xsd:key>
-      </xsd:element>
-    </xsd:sequence>
-
-    <xsd:attribute name="version"
-      type="j2ee:dewey-versionType"
-      fixed="1.1"
-      use="required">
-      <xsd:annotation>
-        <xsd:documentation>
-
-	  The required value for the version is 1.1.
-
-        </xsd:documentation>
-      </xsd:annotation>
-    </xsd:attribute>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-</xsd:schema>
-

jboss-as-7.2.0.Final/docs/schema/j2ee_web_services_client_1_1.xsd

@@ -1,344 +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.1">
-  <xsd:annotation>
-    <xsd:documentation>
-      @(#)j2ee_web_services_client_1_1.xsds	1.10 02/11/03
-    </xsd:documentation>
-  </xsd:annotation>
-
-  <xsd:annotation>
-    <xsd:documentation>
-
-      Copyright 2003 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>
-
-      (C) Copyright International Business Machines Corporation 2002
-
-    </xsd:documentation>
-  </xsd:annotation>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="port-component-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The port-component-ref element declares a client dependency
-	on the container for resolving a Service Endpoint Interface
-	to a WSDL port. It optionally associates the Service Endpoint
-	Interface with a particular port-component. This is only used
-	by the container for a Service.getPort(Class) method call.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="service-endpoint-interface"
-		   type="j2ee:fully-qualified-classType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The service-endpoint-interface element defines a fully qualified
-	    Java class that represents the Service Endpoint Interface of a
-	    WSDL port.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="port-component-link"
-		   type="j2ee:string"
-		   minOccurs="0" maxOccurs="1">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The port-component-link element links a port-component-ref
-	    to a specific port-component required to be made available
-	    by a service reference.
-
-	    The value of a port-component-link must be the
-	    port-component-name of a port-component in the same module
-	    or another module in the same application unit. The syntax
-	    for specification follows the syntax defined for ejb-link
-	    in the EJB 2.0 specification.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:group name="service-refGroup">
-    <xsd:sequence>
-      <xsd:element name="service-ref"
-		   type="j2ee:service-refType"
-		   minOccurs="0" maxOccurs="unbounded">
-	<xsd:key name="service-ref_handler-name-key">
-	  <xsd:annotation>
-	    <xsd:documentation>
-
-	      Defines the name of the handler. The name must be unique
-	      within the module.
-
-	    </xsd:documentation>
-	  </xsd:annotation>
-	  <xsd:selector xpath="j2ee:handler"/>
-	  <xsd:field xpath="j2ee:handler-name"/>
-	</xsd:key>
-      </xsd:element>
-    </xsd:sequence>
-  </xsd:group>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="service-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The service-ref element declares a reference to a Web
-	service. It contains optional description, display name and
-	icons, a declaration of the required Service interface,
-	an optional WSDL document location, an optional set
-	of JAX-RPC mappings, an optional QName for the service element,
-	an optional set of Service Endpoint Interfaces to be resolved
-	by the container to a WSDL port, and an optional set of handlers.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:group ref="j2ee:descriptionGroup"/>
-      <xsd:element name="service-ref-name"
-		   type="j2ee:jndi-nameType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The service-ref-name element declares logical name that the
-	    components in the module use to look up the Web service. It
-	    is recommended that all service reference names start with
-	    "service/".
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="service-interface"
-		   type="j2ee:fully-qualified-classType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The service-interface element declares the fully qualified class
-	    name of the JAX-RPC Service interface the client depends on.
-	    In most cases the value will be javax.xml.rpc.Service.  A JAX-RPC
-	    generated Service Interface class may also be specified.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="wsdl-file"
-		   type="j2ee:xsdAnyURIType"
-		   minOccurs="0" maxOccurs="1">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The wsdl-file element contains the URI location of a WSDL
-	    file. The location is relative to the root of the module.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="jaxrpc-mapping-file"
-		   type="j2ee:pathType"
-		   minOccurs="0" maxOccurs="1">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The jaxrpc-mapping-file element contains the name of a file that
-	    describes the JAX-RPC mapping between the Java interaces used by
-	    the application and the WSDL description in the wsdl-file.  The
-	    file name is a relative path within the module file.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="service-qname"
-		   type="j2ee:xsdQNameType"
-		   minOccurs="0" maxOccurs="1">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The service-qname element declares the specific WSDL service
-	    element that is being refered to.  It is not specified if no
-	    wsdl-file is declared.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="port-component-ref"
-		   type="j2ee:port-component-refType"
-		   minOccurs="0" maxOccurs="unbounded">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The port-component-ref element declares a client dependency
-	    on the container for resolving a Service Endpoint Interface
-	    to a WSDL port. It optionally associates the Service Endpoint
-	    Interface with a particular port-component. This is only used
-	    by the container for a Service.getPort(Class) method call.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="handler"
-		   type="j2ee:service-ref_handlerType"
-		   minOccurs="0" maxOccurs="unbounded">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    Declares the handler for a port-component. Handlers can
-	    access the init-param name/value pairs using the
-	    HandlerInfo interface. If port-name is not specified, the
-	    handler is assumed to be associated with all ports of the
-	    service.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="service-ref_handlerType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	Declares the handler for a port-component. Handlers can access the
-	init-param name/value pairs using the HandlerInfo interface. If
-	port-name is not specified, the handler is assumed to be associated
-	with all ports of the service.
-
-	Used in: service-ref
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:group ref="j2ee:descriptionGroup"/>
-      <xsd:element name="handler-name"
-		   type="j2ee:string">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    Defines the name of the handler. The name must be unique
-	    within the module.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="handler-class"
-		   type="j2ee:fully-qualified-classType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    Defines a fully qualified class name for the handler
-	    implementation.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="init-param"
-		   type="j2ee:param-valueType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-
-      <xsd:element name="soap-header"
-		   type="j2ee:xsdQNameType"
-		   minOccurs="0" maxOccurs="unbounded">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    Defines the QName of a SOAP header that will be processed
-	    by the handler.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="soap-role"
-		   type="j2ee:string"
-		   minOccurs="0" maxOccurs="unbounded">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The soap-role element contains a SOAP actor definition that
-	    the Handler will play as a role.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="port-name"
-		   type="j2ee:string"
-		   minOccurs="0" maxOccurs="unbounded">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The port-name element defines the WSDL port-name that a
-	    handler should be associated with.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-</xsd:schema>
-

jboss-as-7.2.0.Final/docs/schema/java-properties_1_0.xsd

@@ -1,58 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!-- $Id: java-properties_1_0.xsd 33892 2005-07-25 02:47:23Z starksm $
--->
-<xs:schema version="1.0"
-   targetNamespace="urn:jboss:java-properties"
-   xmlns:java="urn:jboss:custom-object-binding"
-   xmlns:xs="http://www.w3.org/2001/XMLSchema"
-   xmlns:jbxb="http://www.jboss.org/xml/ns/jbxb"
-   attributeFormDefault="unqualified"
-   elementFormDefault="qualified"
-   >
-   <xs:annotation>
-      <xs:documentation>A JBossXB schema for specifying how a java.util.Properties
-         object is unmarshalled.
-      </xs:documentation>
-   </xs:annotation>
-   <xs:element name="properties">
-      <xs:annotation>
-         <xs:appinfo>
-            <jbxb:class impl="java.util.Properties"/>
-         </xs:appinfo>
-      </xs:annotation>
-      <xs:complexType>
-         <xs:sequence>
-            <xs:element name="property" maxOccurs="unbounded">
-               <xs:annotation>
-                  <xs:appinfo>
-                     <jbxb:putMethod name="setProperty" keyType="java.lang.String" valueType="java.lang.String"/>
-                  </xs:appinfo>
-               </xs:annotation>
-               <xs:complexType id="propertyType">
-                  <xs:annotation>
-                     <xs:appinfo>
-                        <jbxb:mapEntry/>
-                     </xs:appinfo>
-                  </xs:annotation>
-                  <xs:sequence>
-                     <xs:element name="key" type="xs:string">
-                        <xs:annotation>
-                           <xs:appinfo>
-                              <jbxb:mapEntryKey/>
-                           </xs:appinfo>
-                        </xs:annotation>
-                     </xs:element>
-                     <xs:element name="value" type="xs:string">
-                        <xs:annotation>
-                           <xs:appinfo>
-                              <jbxb:mapEntryValue/>
-                           </xs:appinfo>
-                        </xs:annotation>
-                     </xs:element>
-                  </xs:sequence>
-               </xs:complexType>
-            </xs:element>
-         </xs:sequence>
-      </xs:complexType>
-   </xs:element>
-</xs:schema>

jboss-as-7.2.0.Final/docs/schema/javaee_5.xsd

@@ -1,2095 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xsd:schema
-     targetNamespace="http://java.sun.com/xml/ns/javaee"
-     xmlns:javaee="http://java.sun.com/xml/ns/javaee"
-     xmlns:xsd="http://www.w3.org/2001/XMLSchema"
-     elementFormDefault="qualified"
-     attributeFormDefault="unqualified"
-     version="5">
-  <xsd:annotation>
-    <xsd:documentation>
-      @(#)javaee_5.xsds	1.65 06/02/17
-    </xsd:documentation>
-  </xsd:annotation>
-
-  <xsd:annotation>
-    <xsd:documentation>
-
-      Copyright 2003-2006 Sun Microsystems, Inc.
-      4150 Network Circle
-      Santa Clara, California 95054
-      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:include schemaLocation="javaee_web_services_client_1_2.xsd"/>
-
-
-<!-- **************************************************** -->
-
-  <xsd:group name="descriptionGroup">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This group keeps the usage of the contained description related
-	elements consistent across Java EE deployment descriptors.
-
-	All elements may occur multiple times with different languages,
-	to support localization of the content.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="display-name"
-		   type="javaee:display-nameType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="icon"
-		   type="javaee:iconType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-    </xsd:sequence>
-  </xsd:group>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="descriptionType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The description type is used by a description element to
-	provide text describing the parent element.  The elements
-	that use this type should include any information that the
-	Deployment Component's Deployment File file producer wants
-	to provide to the consumer of the Deployment Component's
-	Deployment File (i.e., to the Deployer). Typically, the
-	tools used by such a Deployment File consumer will display
-	the description when processing the parent element that
-	contains the description.
-
-	The lang attribute defines the language that the
-	description is provided in. The default value is "en" (English).
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="javaee:xsdStringType">
-	<xsd:attribute ref="xml:lang"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:simpleType name="dewey-versionType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This type defines a dewey decimal that is used
-	to describe versions of documents.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:restriction base="xsd:token">
-      <xsd:pattern value="\.?[0-9]+(\.[0-9]+)*"/>
-    </xsd:restriction>
-  </xsd:simpleType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="display-nameType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The display-name type contains a short name that is intended
-	  to be displayed by tools. It is used by display-name
-	  elements.  The display name need not be unique.
-
-	  Example:
-
-	  ...
-	     <display-name xml:lang="en">
-	       Employee Self Service
-	     </display-name>
-
-	  The value of the xml:lang attribute is "en" (English) by default.
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="javaee:string">
-	<xsd:attribute ref="xml:lang"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="ejb-linkType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The ejb-linkType is used by ejb-link
-	  elements in the ejb-ref or ejb-local-ref elements to specify
-	  that an EJB reference is linked to enterprise bean.
-
-	  The value of the ejb-link element must be the ejb-name of an
-	  enterprise bean in the same ejb-jar file or in another ejb-jar
-	  file in the same Java EE application unit.
-
-	  Alternatively, the name in the ejb-link element may be
-	  composed of a path name specifying the ejb-jar containing the
-	  referenced enterprise bean with the ejb-name of the target
-	  bean appended and separated from the path name by "#".  The
-	  path name is relative to the Deployment File containing
-	  Deployment Component that is referencing the enterprise
-	  bean.  This allows multiple enterprise beans with the same
-	  ejb-name to be uniquely identified.
-
-	  Examples:
-
-	      <ejb-link>EmployeeRecord</ejb-link>
-
-	      <ejb-link>../products/product.jar#ProductEJB</ejb-link>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="ejb-local-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The ejb-local-refType is used by ejb-local-ref elements for
-	the declaration of a reference to an enterprise bean's local
-	home or to the local business interface of a 3.0 bean.
-        The declaration consists of:
-
-	    - an optional description
-	    - the EJB reference name used in the code of the Deployment
-	      Component that's referencing the enterprise bean.
-	    - the optional expected type of the referenced enterprise bean
-	    - the optional expected local interface of the referenced
-              enterprise bean or the local business interface of the
-              referenced enterprise bean.
-	    - the optional expected local home interface of the referenced
-              enterprise bean. Not applicable if this ejb-local-ref refers
-              to the local business interface of a 3.0 bean.
-	    - optional ejb-link information, used to specify the
-	      referenced enterprise bean
-            - optional elements to define injection of the named enterprise
-              bean into a component field or property.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="ejb-ref-name"
-		   type="javaee:ejb-ref-nameType"/>
-      <xsd:element name="ejb-ref-type"
-		   type="javaee:ejb-ref-typeType"
-                   minOccurs="0"/>
-      <xsd:element name="local-home"
-		   type="javaee:local-homeType"
-                   minOccurs="0"/>
-      <xsd:element name="local"
-		   type="javaee:localType"
-                   minOccurs="0"/>
-      <xsd:element name="ejb-link"
-		   type="javaee:ejb-linkType"
-		   minOccurs="0"/>
-      <xsd:group ref="javaee:resourceGroup"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="ejb-ref-nameType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The ejb-ref-name element contains the name of an EJB
-	  reference. The EJB reference is an entry in the
-	  Deployment Component's environment and is relative to the
-	  java:comp/env context.  The name must be unique within the
-	  Deployment Component.
-
-	  It is recommended that name is prefixed with "ejb/".
-
-	  Example:
-
-	  <ejb-ref-name>ejb/Payroll</ejb-ref-name>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:jndi-nameType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="ejb-ref-typeType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The ejb-ref-typeType contains the expected type of the
-	referenced enterprise bean.
-
-	The ejb-ref-type designates a value
-	that must be one of the following:
-
-	    Entity
-	    Session
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-	<xsd:enumeration value="Entity"/>
-	<xsd:enumeration value="Session"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="ejb-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The ejb-refType is used by ejb-ref elements for the
-	declaration of a reference to an enterprise bean's home or
-        to the remote business interface of a 3.0 bean.
-	The declaration consists of:
-
-	    - an optional description
-	    - the EJB reference name used in the code of
-	      the Deployment Component that's referencing the enterprise
-	      bean.
-	    - the optional expected type of the referenced enterprise bean
-            - the optional remote interface of the referenced enterprise bean
-              or the remote business interface of the referenced enterprise
-              bean
-	    - the optional expected home interface of the referenced
-              enterprise bean.  Not applicable if this ejb-ref
-              refers to the remote business interface of a 3.0 bean.
-	    - optional ejb-link information, used to specify the
-	      referenced enterprise bean
-            - optional elements to define injection of the named enterprise
-              bean into a component field or property
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="ejb-ref-name"
-		   type="javaee:ejb-ref-nameType"/>
-      <xsd:element name="ejb-ref-type"
-		   type="javaee:ejb-ref-typeType"
-		   minOccurs="0"/>
-      <xsd:element name="home"
-		   type="javaee:homeType"
-		   minOccurs="0"/>
-      <xsd:element name="remote"
-		   type="javaee:remoteType"
-                   minOccurs="0"/>
-      <xsd:element name="ejb-link"
-		   type="javaee:ejb-linkType"
-		   minOccurs="0"/>
-      <xsd:group ref="javaee:resourceGroup"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="emptyType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This type is used to designate an empty
-	element when used.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="env-entry-type-valuesType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  This type contains the fully-qualified Java type of the
-	  environment entry value that is expected by the
-	  application's code.
-
-	  The following are the legal values of env-entry-type-valuesType:
-
-	      java.lang.Boolean
-	      java.lang.Byte
-	      java.lang.Character
-	      java.lang.String
-	      java.lang.Short
-	      java.lang.Integer
-	      java.lang.Long
-	      java.lang.Float
-	      java.lang.Double
-
-	  Example:
-
-	  <env-entry-type>java.lang.Boolean</env-entry-type>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-	<xsd:enumeration value="java.lang.Boolean"/>
-	<xsd:enumeration value="java.lang.Byte"/>
-	<xsd:enumeration value="java.lang.Character"/>
-	<xsd:enumeration value="java.lang.String"/>
-	<xsd:enumeration value="java.lang.Short"/>
-	<xsd:enumeration value="java.lang.Integer"/>
-	<xsd:enumeration value="java.lang.Long"/>
-	<xsd:enumeration value="java.lang.Float"/>
-	<xsd:enumeration value="java.lang.Double"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="env-entryType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The env-entryType is used to declare an application's
-	environment entry. The declaration consists of an optional
-	description, the name of the environment entry, a type
-	(optional if the value is injected, otherwise required), and
-	an optional value.
-
-	It also includes optional elements to define injection of
-	the named resource into fields or JavaBeans properties.
-
-	If a value is not specified and injection is requested,
-	no injection will occur and no entry of the specified name
-	will be created.  This allows an initial value to be
-	specified in the source code without being incorrectly
-	changed when no override has been specified.
-
-	If a value is not specified and no injection is requested,
-	a value must be supplied during deployment.
-
-	This type is used by env-entry elements.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="env-entry-name"
-		   type="javaee:jndi-nameType">
-	<xsd:annotation>
-	  <xsd:documentation>
-	    <![CDATA[
-
-	      The env-entry-name element contains the name of a
-	      Deployment Component's environment entry.  The name
-	      is a JNDI name relative to the java:comp/env
-	      context.  The name must be unique within a
-	      Deployment Component. The uniqueness
-	      constraints must be defined within the declared
-	      context.
-
-	      Example:
-
-	      <env-entry-name>minAmount</env-entry-name>
-
-	      ]]>
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="env-entry-type"
-		   type="javaee:env-entry-type-valuesType"
-		   minOccurs="0">
-	<xsd:annotation>
-	  <xsd:documentation>
-	    <![CDATA[
-
-	      The env-entry-type element contains the Java language
-	      type of the environment entry.  If an injection target
-	      is specified for the environment entry, the type may
-	      be omitted, or must match the type of the injection
-	      target.  If no injection target is specified, the type
-	      is required.
-
-	      Example:
-
-	      <env-entry-type>java.lang.Integer</env-entry-type>
-
-	      ]]>
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="env-entry-value"
-		   type="javaee:xsdStringType"
-		   minOccurs="0">
-	<xsd:annotation>
-	  <xsd:documentation>
-	    <![CDATA[
-
-	      The env-entry-value designates the value of a
-	      Deployment Component's environment entry. The value
-	      must be a String that is valid for the
-	      constructor of the specified type that takes a
-	      single String parameter, or for java.lang.Character,
-	      a single character.
-
-	      Example:
-
-	      <env-entry-value>100.00</env-entry-value>
-
-	      ]]>
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:group ref="javaee:resourceGroup"/>
-
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="fully-qualified-classType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The elements that use this type designate the name of a
-	Java class or interface.  The name is in the form of a
-	"binary name", as defined in the JLS.  This is the form
-	of name used in Class.forName().  Tools that need the
-	canonical name (the name used in source code) will need
-	to convert this binary name to the canonical name.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="generic-booleanType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This type defines four different values which can designate
-	boolean values. This includes values yes and no which are
-	not designated by xsd:boolean
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-	<xsd:enumeration value="true"/>
-	<xsd:enumeration value="false"/>
-	<xsd:enumeration value="yes"/>
-	<xsd:enumeration value="no"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="homeType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The homeType defines the fully-qualified name of
-	  an enterprise bean's home interface.
-
-	  Example:
-
-	      <home>com.aardvark.payroll.PayrollHome</home>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:fully-qualified-classType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="iconType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The icon type contains small-icon and large-icon elements
-	that specify the file names for small and large GIF, JPEG,
-	or PNG icon images used to represent the parent element in a
-	GUI tool.
-
-	The xml:lang attribute defines the language that the
-	icon file names are provided in. Its value is "en" (English)
-	by default.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="small-icon" type="javaee:pathType"
-		   minOccurs="0">
-	<xsd:annotation>
-	  <xsd:documentation>
-	    <![CDATA[
-
-	      The small-icon element contains the name of a file
-	      containing a small (16 x 16) icon image. The file
-	      name is a relative path within the Deployment
-	      Component's Deployment File.
-
-	      The image may be in the GIF, JPEG, or PNG format.
-	      The icon can be used by tools.
-
-	      Example:
-
-	      <small-icon>employee-service-icon16x16.jpg</small-icon>
-
-	      ]]>
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="large-icon" type="javaee:pathType"
-		   minOccurs="0">
-	<xsd:annotation>
-	  <xsd:documentation>
-	    <![CDATA[
-
-	      The large-icon element contains the name of a file
-	      containing a large
-	      (32 x 32) icon image. The file name is a relative
-	      path within the Deployment Component's Deployment
-	      File.
-
-	      The image may be in the GIF, JPEG, or PNG format.
-	      The icon can be used by tools.
-
-	      Example:
-
-	      <large-icon>employee-service-icon32x32.jpg</large-icon>
-
-	      ]]>
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-    </xsd:sequence>
-
-    <xsd:attribute ref="xml:lang"/>
-    <xsd:attribute name="id" type="xsd:ID"/>
-
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="injection-targetType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	An injection target specifies a class and a name within
-	that class into which a resource should be injected.
-
-	The injection target class specifies the fully qualified
-	class name that is the target of the injection.  The
-	Java EE specifications describe which classes can be an
-	injection target.
-
-	The injection target name specifies the target within
-	the specified class.  The target is first looked for as a
-	JavaBeans property name.  If not found, the target is
-	looked for as a field name.
-
-	The specified resource will be injected into the target
-	during initialization of the class by either calling the
-	set method for the target property or by setting a value
-	into the named field.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="injection-target-class"
-		   type="javaee:fully-qualified-classType"/>
-      <xsd:element name="injection-target-name"
-		   type="javaee:java-identifierType"/>
-    </xsd:sequence>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="java-identifierType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The java-identifierType defines a Java identifier.
-	The users of this type should further verify that
-	the content does not contain Java reserved keywords.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-	<xsd:pattern value="($|_|\p{L})(\p{L}|\p{Nd}|_|$)*"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="java-typeType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This is a generic type that designates a Java primitive
-	type or a fully qualified name of a Java interface/type,
-	or an array of such types.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-	<xsd:pattern value="[^\p{Z}]*"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="jndi-nameType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The jndi-nameType type designates a JNDI name in the
-	Deployment Component's environment and is relative to the
-	java:comp/env context.  A JNDI name must be unique within the
-	Deployment Component.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:group name="jndiEnvironmentRefsGroup">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This group keeps the usage of the contained JNDI environment
-	reference elements consistent across Java EE deployment descriptors.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="env-entry"
-		   type="javaee:env-entryType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-      <xsd:element name="ejb-ref"
-		   type="javaee:ejb-refType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-      <xsd:element name="ejb-local-ref"
-		   type="javaee:ejb-local-refType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-      <xsd:group ref="javaee:service-refGroup"/>
-      <xsd:element name="resource-ref"
-		   type="javaee:resource-refType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-      <xsd:element name="resource-env-ref"
-		   type="javaee:resource-env-refType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-      <xsd:element name="message-destination-ref"
-		   type="javaee:message-destination-refType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-      <xsd:element name="persistence-context-ref"
-		   type="javaee:persistence-context-refType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-      <xsd:element name="persistence-unit-ref"
-		   type="javaee:persistence-unit-refType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-      <xsd:element name="post-construct"
-		   type="javaee:lifecycle-callbackType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-      <xsd:element name="pre-destroy"
-		   type="javaee:lifecycle-callbackType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-    </xsd:sequence>
-  </xsd:group>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="lifecycle-callbackType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The lifecycle-callback type specifies a method on a
-	class to be called when a lifecycle event occurs.
-	Note that each class may have only one lifecycle callback
-        method for any given event and that the method may not
-	be overloaded.
-
-        If the lifefycle-callback-class element is missing then
-        the class defining the callback is assumed to be the
-        component class in scope at the place in the descriptor
-        in which the callback definition appears.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="lifecycle-callback-class"
-		   type="javaee:fully-qualified-classType"
-                   minOccurs="0"/>
-      <xsd:element name="lifecycle-callback-method"
-		   type="javaee:java-identifierType"/>
-    </xsd:sequence>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="listenerType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The listenerType indicates the deployment properties for a web
-	application listener bean.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:group ref="javaee:descriptionGroup"/>
-      <xsd:element name="listener-class"
-		   type="javaee:fully-qualified-classType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The listener-class element declares a class in the
-	    application must be registered as a web
-	    application listener bean. The value is the fully
-	    qualified classname of the listener class.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="local-homeType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The local-homeType defines the fully-qualified
-	name of an enterprise bean's local home interface.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:fully-qualified-classType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="localType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The localType defines the fully-qualified name of an
-	enterprise bean's local interface.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:fully-qualified-classType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="message-destination-linkType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The message-destination-linkType is used to link a message
-	destination reference or message-driven bean to a message
-	destination.
-
-	The Assembler sets the value to reflect the flow of messages
-	between producers and consumers in the application.
-
-	The value must be the message-destination-name of a message
-	destination in the same Deployment File or in another
-	Deployment File in the same Java EE application unit.
-
-	Alternatively, the value may be composed of a path name
-	specifying a Deployment File containing the referenced
-	message destination with the message-destination-name of the
-	destination appended and separated from the path name by
-	"#". The path name is relative to the Deployment File
-	containing Deployment Component that is referencing the
-	message destination.  This allows multiple message
-	destinations with the same name to be uniquely identified.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="message-destination-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The message-destination-ref element contains a declaration
-	  of Deployment Component's reference to a message destination
-	  associated with a resource in Deployment Component's
-	  environment. It consists of:
-
-		  - an optional description
-		  - the message destination reference name
-		  - an optional message destination type
-		  - an optional specification as to whether
-		    the destination is used for
-		    consuming or producing messages, or both.
-		    if not specified, "both" is assumed.
-		  - an optional link to the message destination
-		  - optional injection targets
-
-	  The message destination type must be supplied unless an
-	  injection target is specified, in which case the type
-	  of the target is used.  If both are specified, the type
-	  must be assignment compatible with the type of the injection
-	  target.
-
-	  Examples:
-
-	  <message-destination-ref>
-		  <message-destination-ref-name>jms/StockQueue
-		  </message-destination-ref-name>
-		  <message-destination-type>javax.jms.Queue
-		  </message-destination-type>
-		  <message-destination-usage>Consumes
-		  </message-destination-usage>
-		  <message-destination-link>CorporateStocks
-		  </message-destination-link>
-	  </message-destination-ref>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="message-destination-ref-name"
-		   type="javaee:jndi-nameType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The message-destination-ref-name element specifies
-	    the name of a message destination reference; its
-	    value is the environment entry name used in
-	    Deployment Component code.  The name is a JNDI name
-	    relative to the java:comp/env context and must be
-	    unique within an ejb-jar (for enterprise beans) or a
-	    Deployment File (for others).
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="message-destination-type"
-		   type="javaee:message-destination-typeType"
-		   minOccurs="0"/>
-      <xsd:element name="message-destination-usage"
-		   type="javaee:message-destination-usageType"
-		   minOccurs="0"/>
-      <xsd:element name="message-destination-link"
-		   type="javaee:message-destination-linkType"
-		   minOccurs="0"/>
-
-      <xsd:group ref="javaee:resourceGroup"/>
-
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="message-destination-typeType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The message-destination-typeType specifies the type of
-	  the destination. The type is specified by the Java interface
-	  expected to be implemented by the destination.
-
-	  Example:
-
-	    <message-destination-type>javax.jms.Queue
-	    </message-destination-type>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:fully-qualified-classType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="message-destination-usageType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The message-destination-usageType specifies the use of the
-	message destination indicated by the reference.  The value
-	indicates whether messages are consumed from the message
-	destination, produced for the destination, or both.  The
-	Assembler makes use of this information in linking producers
-	of a destination with its consumers.
-
-	The value of the message-destination-usage element must be
-	one of the following:
-	    Consumes
-	    Produces
-	    ConsumesProduces
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-	<xsd:enumeration value="Consumes"/>
-	<xsd:enumeration value="Produces"/>
-	<xsd:enumeration value="ConsumesProduces"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="message-destinationType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The message-destinationType specifies a message
-	  destination. The logical destination described by this
-	  element is mapped to a physical destination by the Deployer.
-
-	  The message destination element contains:
-
-		  - an optional description
-		  - an optional display-name
-		  - an optional icon
-		  - a message destination name which must be unique
-		    among message destination names within the same
-		    Deployment File.
-		  - an optional mapped name
-
-	  Example:
-
-	  <message-destination>
-		  <message-destination-name>CorporateStocks
-		  </message-destination-name>
-	  </message-destination>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:group ref="javaee:descriptionGroup"/>
-      <xsd:element name="message-destination-name"
-		   type="javaee:string">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The message-destination-name element specifies a
-	    name for a message destination.  This name must be
-	    unique among the names of message destinations
-	    within the Deployment File.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="mapped-name"
-		   type="javaee:xsdStringType"
-		   minOccurs="0">
-	<xsd:annotation>
-	  <xsd:documentation>
-	    <![CDATA[
-
-	      A product specific name that this message destination
-	      should be mapped to.  Each message-destination-ref
-	      element that references this message destination will
-	      define a name in the namespace of the referencing
-	      component.  (It's a name in the JNDI java:comp/env
-	      namespace.)  Many application servers provide a way to
-	      map these local names to names of resources known to the
-	      application server.  This mapped name is often a global
-	      JNDI name, but may be a name of any form.  Each of the
-	      local names should be mapped to this same global name.
-
-	      Application servers are not required to support any
-	      particular form or type of mapped name, nor the ability
-	      to use mapped names.  The mapped name is
-	      product-dependent and often installation-dependent.  No
-	      use of a mapped name is portable.
-
-	      ]]>
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="param-valueType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This type is a general type that can be used to declare
-	parameter/value lists.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="param-name"
-		   type="javaee:string">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The param-name element contains the name of a
-	    parameter.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="param-value"
-		   type="javaee:xsdStringType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The param-value element contains the value of a
-	    parameter.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="pathType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The elements that use this type designate either a relative
-	path or an absolute path starting with a "/".
-
-	In elements that specify a pathname to a file within the
-	same Deployment File, relative filenames (i.e., those not
-	starting with "/") are considered relative to the root of
-	the Deployment File's namespace.  Absolute filenames (i.e.,
-	those starting with "/") also specify names in the root of
-	the Deployment File's namespace.  In general, relative names
-	are preferred.  The exception is .war files where absolute
-	names are preferred for consistency with the Servlet API.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="persistence-context-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The persistence-context-ref element contains a declaration
-	  of Deployment Component's reference to a persistence context
-	  associated within a Deployment Component's
-	  environment. It consists of:
-
-		  - an optional description
-		  - the persistence context reference name
-		  - an optional persistence unit name.  If not specified,
-                    the default persistence unit is assumed.
-		  - an optional specification as to whether
-		    the persistence context type is Transaction or
-		    Extended.  If not specified, Transaction is assumed.
-                  - an optional list of persistence properties
-		  - optional injection targets
-
-	  Examples:
-
-            <persistence-context-ref>
-              <persistence-context-ref-name>myPersistenceContext
-              </persistence-context-ref-name>
-            </persistence-context-ref>
-
-            <persistence-context-ref>
-              <persistence-context-ref-name>myPersistenceContext
-                </persistence-context-ref-name>
-              <persistence-unit-name>PersistenceUnit1
-                </persistence-unit-name>
-              <persistence-context-type>Extended</persistence-context-type>
-            </persistence-context-ref>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="persistence-context-ref-name"
-		   type="javaee:jndi-nameType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The persistence-context-ref-name element specifies
-	    the name of a persistence context reference; its
-	    value is the environment entry name used in
-	    Deployment Component code.  The name is a JNDI name
-	    relative to the java:comp/env context.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="persistence-unit-name"
-		   type="javaee:string"
-		   minOccurs="0">
-        <xsd:annotation>
-	  <xsd:documentation>
-
-            The Application Assembler(or BeanProvider) may use the
-            following syntax to avoid the need to rename persistence
-            units to have unique names within a Java EE application.
-
-            The Application Assembler specifies the pathname of the
-            root of the persistence.xml file for the referenced
-            persistence unit and appends the name of the persistence
-            unit separated from the pathname by #. The pathname is
-            relative to the referencing application component jar file.
-            In this manner, multiple persistence units with the same
-            persistence unit name may be uniquely identified when the
-            Application Assembler cannot change persistence unit names.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="persistence-context-type"
-		   type="javaee:persistence-context-typeType"
-		   minOccurs="0"/>
-
-      <xsd:element name="persistence-property"
-		   type="javaee:propertyType"
-		   minOccurs="0"
-		   maxOccurs="unbounded">
-        <xsd:annotation>
-	  <xsd:documentation>
-
-            Used to specify properties for the container or persistence
-            provider.  Vendor-specific properties may be included in
-            the set of properties.  Properties that are not recognized
-            by a vendor must be ignored.  Entries that make use of the
-            namespace javax.persistence and its subnamespaces must not
-            be used for vendor-specific properties.  The namespace
-            javax.persistence is reserved for use by the specification.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:group ref="javaee:resourceGroup"/>
-
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="persistence-context-typeType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The persistence-context-typeType specifies the transactional
-	nature of a persistence context reference.
-
-	The value of the persistence-context-type element must be
-	one of the following:
-	    Transaction
-            Extended
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-	<xsd:enumeration value="Transaction"/>
-	<xsd:enumeration value="Extended"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="persistence-unit-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The persistence-unit-ref element contains a declaration
-	  of Deployment Component's reference to a persistence unit
-	  associated within a Deployment Component's
-	  environment. It consists of:
-
-		  - an optional description
-		  - the persistence unit reference name
-		  - an optional persistence unit name.  If not specified,
-                    the default persistence unit is assumed.
-		  - optional injection targets
-
-	  Examples:
-
-            <persistence-unit-ref>
-              <persistence-unit-ref-name>myPersistenceUnit
-              </persistence-unit-ref-name>
-            </persistence-unit-ref>
-
-            <persistence-unit-ref>
-              <persistence-unit-ref-name>myPersistenceUnit
-                </persistence-unit-ref-name>
-              <persistence-unit-name>PersistenceUnit1
-                </persistence-unit-name>
-            </persistence-unit-ref>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="persistence-unit-ref-name"
-		   type="javaee:jndi-nameType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The persistence-unit-ref-name element specifies
-	    the name of a persistence unit reference; its
-	    value is the environment entry name used in
-	    Deployment Component code.  The name is a JNDI name
-	    relative to the java:comp/env context.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="persistence-unit-name"
-		   type="javaee:string"
-		   minOccurs="0">
-        <xsd:annotation>
-	  <xsd:documentation>
-
-            The Application Assembler(or BeanProvider) may use the
-            following syntax to avoid the need to rename persistence
-            units to have unique names within a Java EE application.
-
-            The Application Assembler specifies the pathname of the
-            root of the persistence.xml file for the referenced
-            persistence unit and appends the name of the persistence
-            unit separated from the pathname by #. The pathname is
-            relative to the referencing application component jar file.
-            In this manner, multiple persistence units with the same
-            persistence unit name may be uniquely identified when the
-            Application Assembler cannot change persistence unit names.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:group ref="javaee:resourceGroup"/>
-
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="propertyType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	Specifies a name/value pair.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="name"
-		   type="javaee:xsdStringType">
-      </xsd:element>
-      <xsd:element name="value"
-		   type="javaee:xsdStringType">
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="remoteType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The remote element contains the fully-qualified name
-	  of the enterprise bean's remote interface.
-
-	  Example:
-
-	      <remote>com.wombat.empl.EmployeeService</remote>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:fully-qualified-classType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="res-authType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The res-authType specifies whether the Deployment Component
-	code signs on programmatically to the resource manager, or
-	whether the Container will sign on to the resource manager
-	on behalf of the Deployment Component. In the latter case,
-	the Container uses information that is supplied by the
-	Deployer.
-
-	The value must be one of the two following:
-
-	    Application
-	    Container
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-	<xsd:enumeration value="Application"/>
-	<xsd:enumeration value="Container"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="res-sharing-scopeType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The res-sharing-scope type specifies whether connections
-	obtained through the given resource manager connection
-	factory reference can be shared. The value, if specified,
-	must be one of the two following:
-
-	    Shareable
-	    Unshareable
-
-	The default value is Shareable.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-	<xsd:enumeration value="Shareable"/>
-	<xsd:enumeration value="Unshareable"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="resource-env-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The resource-env-refType is used to define
-	  resource-env-type elements.  It contains a declaration of a
-	  Deployment Component's reference to an administered object
-	  associated with a resource in the Deployment Component's
-	  environment.  It consists of an optional description, the
-	  resource environment reference name, and an optional
-	  indication of the resource environment reference type
-	  expected by the Deployment Component code.
-
-	  It also includes optional elements to define injection of
-	  the named resource into fields or JavaBeans properties.
-
-	  The resource environment type must be supplied unless an
-	  injection target is specified, in which case the type
-	  of the target is used.  If both are specified, the type
-	  must be assignment compatible with the type of the injection
-	  target.
-
-	  Example:
-
-	  <resource-env-ref>
-	      <resource-env-ref-name>jms/StockQueue
-	      </resource-env-ref-name>
-	      <resource-env-ref-type>javax.jms.Queue
-	      </resource-env-ref-type>
-	  </resource-env-ref>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="resource-env-ref-name"
-		   type="javaee:jndi-nameType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The resource-env-ref-name element specifies the name
-	    of a resource environment reference; its value is
-	    the environment entry name used in
-	    the Deployment Component code.  The name is a JNDI
-	    name relative to the java:comp/env context and must
-	    be unique within a Deployment Component.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="resource-env-ref-type"
-		   type="javaee:fully-qualified-classType"
-		   minOccurs="0">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The resource-env-ref-type element specifies the type
-	    of a resource environment reference.  It is the
-	    fully qualified name of a Java language class or
-	    interface.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:group ref="javaee:resourceGroup"/>
-
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="resource-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The resource-refType contains a declaration of a
-	  Deployment Component's reference to an external resource. It
-	  consists of an optional description, the resource manager
-	  connection factory reference name, an optional indication of
-	  the resource manager connection factory type expected by the
-	  Deployment Component code, an optional type of authentication
-	  (Application or Container), and an optional specification of
-	  the shareability of connections obtained from the resource
-	  (Shareable or Unshareable).
-
-	  It also includes optional elements to define injection of
-	  the named resource into fields or JavaBeans properties.
-
-	  The connection factory type must be supplied unless an
-	  injection target is specified, in which case the type
-	  of the target is used.  If both are specified, the type
-	  must be assignment compatible with the type of the injection
-	  target.
-
-	  Example:
-
-	  <resource-ref>
-	      <res-ref-name>jdbc/EmployeeAppDB</res-ref-name>
-	      <res-type>javax.sql.DataSource</res-type>
-	      <res-auth>Container</res-auth>
-	      <res-sharing-scope>Shareable</res-sharing-scope>
-	  </resource-ref>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="res-ref-name"
-		   type="javaee:jndi-nameType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The res-ref-name element specifies the name of a
-	    resource manager connection factory reference.
-	    The name is a JNDI name relative to the
-	    java:comp/env context.
-	    The name must be unique within a Deployment File.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="res-type"
-		   type="javaee:fully-qualified-classType"
-		   minOccurs="0">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The res-type element specifies the type of the data
-	    source. The type is specified by the fully qualified
-	    Java language class or interface
-	    expected to be implemented by the data source.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="res-auth"
-		   type="javaee:res-authType"
-		   minOccurs="0"/>
-
-      <xsd:element name="res-sharing-scope"
-		   type="javaee:res-sharing-scopeType"
-		   minOccurs="0"/>
-
-      <xsd:group ref="javaee:resourceGroup"/>
-
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:group name="resourceGroup">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This group collects elements that are common to all the
-	JNDI resource elements.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="mapped-name"
-		   type="javaee:xsdStringType"
-		   minOccurs="0">
-	<xsd:annotation>
-	  <xsd:documentation>
-	    <![CDATA[
-
-	      A product specific name that this resource should be
-	      mapped to.  The name of this resource, as defined by the
-	      resource's name element or defaulted, is a name that is
-	      local to the application component using the resource.
-	      (It's a name in the JNDI java:comp/env namespace.)  Many
-	      application servers provide a way to map these local
-	      names to names of resources known to the application
-	      server.  This mapped name is often a global JNDI name,
-	      but may be a name of any form.
-
-	      Application servers are not required to support any
-	      particular form or type of mapped name, nor the ability
-	      to use mapped names.  The mapped name is
-	      product-dependent and often installation-dependent.  No
-	      use of a mapped name is portable.
-
-	      ]]>
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="injection-target"
-		   type="javaee:injection-targetType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-    </xsd:sequence>
-  </xsd:group>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="role-nameType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The role-nameType designates the name of a security role.
-
-	The name must conform to the lexical rules for a token.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="run-asType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The run-asType specifies the run-as identity to be
-	used for the execution of a component. It contains an
-	optional description, and the name of a security role.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="role-name"
-		   type="javaee:role-nameType"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="security-role-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The security-role-refType contains the declaration of a
-	security role reference in a component's or a
-	Deployment Component's code. The declaration consists of an
-	optional description, the security role name used in the
-	code, and an optional link to a security role. If the
-	security role is not specified, the Deployer must choose an
-	appropriate security role.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="role-name"
-		   type="javaee:role-nameType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The value of the role-name element must be the String used
-	    as the parameter to the
-	    EJBContext.isCallerInRole(String roleName) method or the
-	    HttpServletRequest.isUserInRole(String role) method.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="role-link"
-		   type="javaee:role-nameType"
-		   minOccurs="0">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The role-link element is a reference to a defined
-	    security role. The role-link element must contain
-	    the name of one of the security roles defined in the
-	    security-role elements.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="security-roleType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The security-roleType contains the definition of a security
-	  role. The definition consists of an optional description of
-	  the security role, and the security role name.
-
-	  Example:
-
-	      <security-role>
-	      <description>
-		  This role includes all employees who are authorized
-		  to access the employee service application.
-	      </description>
-	      <role-name>employee</role-name>
-	      </security-role>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="javaee:descriptionType"
-		   minOccurs="0"
-		   maxOccurs="unbounded"/>
-      <xsd:element name="role-name"
-		   type="javaee:role-nameType"/>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="string">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This is a special string datatype that is defined by Java EE as
-	a base type for defining collapsed strings. When schemas
-	require trailing/leading space elimination as well as
-	collapsing the existing whitespace, this base type may be
-	used.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:token">
-	<xsd:attribute name="id" type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="true-falseType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This simple type designates a boolean with only two
-	permissible values
-
-	- true
-	- false
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:xsdBooleanType">
-	<xsd:pattern value="(true|false)"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="url-patternType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The url-patternType contains the url pattern of the mapping.
-	It must follow the rules specified in Section 11.2 of the
-	Servlet API Specification. This pattern is assumed to be in
-	URL-decoded form and must not contain CR(#xD) or LF(#xA).
-	If it contains those characters, the container must inform
-	the developer with a descriptive error message.
-	The container must preserve all characters including whitespaces.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="xsdAnyURIType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This type adds an "id" attribute to xsd:anyURI.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:anyURI">
-	<xsd:attribute name="id" type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="xsdBooleanType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This type adds an "id" attribute to xsd:boolean.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:boolean">
-	<xsd:attribute name="id" type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="xsdIntegerType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This type adds an "id" attribute to xsd:integer.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:integer">
-	<xsd:attribute name="id" type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="xsdNMTOKENType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This type adds an "id" attribute to xsd:NMTOKEN.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:NMTOKEN">
-	<xsd:attribute name="id" type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="xsdNonNegativeIntegerType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This type adds an "id" attribute to xsd:nonNegativeInteger.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:nonNegativeInteger">
-	<xsd:attribute name="id" type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="xsdPositiveIntegerType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This type adds an "id" attribute to xsd:positiveInteger.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:positiveInteger">
-	<xsd:attribute name="id" type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="xsdQNameType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This type adds an "id" attribute to xsd:QName.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:QName">
-	<xsd:attribute name="id" type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="xsdStringType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	This type adds an "id" attribute to xsd:string.
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:string">
-	<xsd:attribute name="id" type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-</xsd:schema>
-

jboss-as-7.2.0.Final/docs/schema/javaee_6.xsd

@@ -1,2431 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xsd:schema targetNamespace="http://java.sun.com/xml/ns/javaee"
-            xmlns:javaee="http://java.sun.com/xml/ns/javaee"
-            xmlns:xsd="http://www.w3.org/2001/XMLSchema"
-            elementFormDefault="qualified"
-            attributeFormDefault="unqualified"
-            version="6">
-  <xsd:annotation>
-    <xsd:documentation>
-
-      $Id$
-      
-    </xsd:documentation>
-  </xsd:annotation>
-
-  <xsd:annotation>
-    <xsd:documentation>
-
-      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
-      
-      Copyright 2003-2009 Sun Microsystems, Inc. All rights reserved.
-      
-      The contents of this file are subject to the terms of either the
-      GNU General Public License Version 2 only ("GPL") or the Common
-      Development and Distribution License("CDDL") (collectively, the
-      "License").  You may not use this file except in compliance with
-      the License. You can obtain a copy of the License at
-      https://glassfish.dev.java.net/public/CDDL+GPL.html or
-      glassfish/bootstrap/legal/LICENSE.txt.  See the License for the
-      specific language governing permissions and limitations under the
-      License.
-      
-      When distributing the software, include this License Header
-      Notice in each file and include the License file at
-      glassfish/bootstrap/legal/LICENSE.txt.  Sun designates this
-      particular file as subject to the "Classpath" exception as
-      provided by Sun in the GPL Version 2 section of the License file
-      that accompanied this code.  If applicable, add the following
-      below the License Header, with the fields enclosed by brackets []
-      replaced by your own identifying information:
-      "Portions Copyrighted [year] [name of copyright owner]"
-      
-      Contributor(s):
-      
-      If you wish your version of this file to be governed by only the
-      CDDL or only the GPL Version 2, indicate your decision by adding
-      "[Contributor] elects to include this software in this
-      distribution under the [CDDL or GPL Version 2] license."  If you
-      don't indicate a single choice of license, a recipient has the
-      option to distribute your version of this file under either the
-      CDDL, the GPL Version 2 or to extend the choice of license to its
-      licensees as provided above.  However, if you add GPL Version 2
-      code and therefore, elected the GPL Version 2 license, then the
-      option applies only if the new code is made subject to such
-      option by the copyright holder.
-      
-    </xsd:documentation>
-  </xsd:annotation>
-
-  <xsd:annotation>
-    <xsd:documentation>
-
-      The following definitions that appear in the common
-      shareable schema(s) of Java EE deployment descriptors should be
-      interpreted with respect to the context they are included:
-      
-      Deployment Component may indicate one of the following:
-      java ee application;
-      application client;
-      web application;
-      enterprise bean;
-      resource adapter; 
-      
-      Deployment File may indicate one of the following:
-      ear file;
-      war file;
-      jar file;
-      rar file;
-      
-    </xsd:documentation>
-  </xsd:annotation>
-
-  <xsd:import namespace="http://www.w3.org/XML/1998/namespace"
-              schemaLocation="http://www.w3.org/2001/xml.xsd"/>
-
-  <xsd:include schemaLocation="javaee_web_services_client_1_3.xsd"/>
-
-  <xsd:group name="descriptionGroup">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        This group keeps the usage of the contained description related
-        elements consistent across Java EE deployment descriptors.
-        
-        All elements may occur multiple times with different languages,
-        to support localization of the content.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-                   type="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="display-name"
-                   type="javaee:display-nameType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="icon"
-                   type="javaee:iconType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-    </xsd:sequence>
-  </xsd:group>
-
-  <xsd:group name="jndiEnvironmentRefsGroup">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        This group keeps the usage of the contained JNDI environment
-        reference elements consistent across Java EE deployment descriptors.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="env-entry"
-                   type="javaee:env-entryType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="ejb-ref"
-                   type="javaee:ejb-refType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="ejb-local-ref"
-                   type="javaee:ejb-local-refType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:group ref="javaee:service-refGroup"/>
-      <xsd:element name="resource-ref"
-                   type="javaee:resource-refType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="resource-env-ref"
-                   type="javaee:resource-env-refType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="message-destination-ref"
-                   type="javaee:message-destination-refType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="persistence-context-ref"
-                   type="javaee:persistence-context-refType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="persistence-unit-ref"
-                   type="javaee:persistence-unit-refType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="post-construct"
-                   type="javaee:lifecycle-callbackType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="pre-destroy"
-                   type="javaee:lifecycle-callbackType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="data-source"
-                   type="javaee:data-sourceType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-    </xsd:sequence>
-  </xsd:group>
-
-  <xsd:group name="resourceGroup">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        This group collects elements that are common to most
-        JNDI resource elements.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:group ref="javaee:resourceBaseGroup"/>
-      <xsd:element name="lookup-name"
-                   type="javaee:xsdStringType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The JNDI name to be looked up to resolve a resource reference.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-  </xsd:group>
-
-  <xsd:group name="resourceBaseGroup">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        This group collects elements that are common to all the
-        JNDI resource elements. It does not include the lookup-name
-        element, that is only applicable to some resource elements.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="mapped-name"
-                   type="javaee:xsdStringType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            A product specific name that this resource should be
-            mapped to.  The name of this resource, as defined by the
-            resource's name element or defaulted, is a name that is
-            local to the application component using the resource.
-            (It's a name in the JNDI java:comp/env namespace.)  Many
-            application servers provide a way to map these local
-            names to names of resources known to the application
-            server.  This mapped name is often a global JNDI name,
-            but may be a name of any form.
-            
-            Application servers are not required to support any
-            particular form or type of mapped name, nor the ability
-            to use mapped names.  The mapped name is
-            product-dependent and often installation-dependent.  No
-            use of a mapped name is portable.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="injection-target"
-                   type="javaee:injection-targetType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-    </xsd:sequence>
-  </xsd:group>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="data-sourceType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        Configuration of a DataSource.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-                   type="javaee:descriptionType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Description of this DataSource.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="name"
-                   type="javaee:jndi-nameType">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The name element specifies the JNDI name of the
-            data source being defined.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="class-name"
-                   type="javaee:fully-qualified-classType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            DataSource, XADataSource or ConnectionPoolDataSource
-            implementation class.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="server-name"
-                   type="javaee:string"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Database server name.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="port-number"
-                   type="javaee:xsdIntegerType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Port number where a server is listening for requests.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="database-name"
-                   type="javaee:string"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Name of a database on a server.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="url"
-                   type="javaee:jdbc-urlType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-            <![CDATA[[
-            A JDBC URL. If the <code>url</code> property is specified
-            along with other standard <code>DataSource</code> properties
-            such as <code>serverName</code>, <code>databaseName</code>
-            and <code>portNumber</code>, the more specific properties will
-            take precedence and <code>url</code> will be ignored.
-            
-            ]]>
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="user"
-                   type="javaee:string"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            User name to use for connection authentication.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="password"
-                   type="javaee:string"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Password to use for connection authentication.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="property"
-                   type="javaee:propertyType"
-                   minOccurs="0"
-                   maxOccurs="unbounded">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            JDBC DataSource property.  This may be a vendor-specific
-            property or a less commonly used DataSource property.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="login-timeout"
-                   type="javaee:xsdIntegerType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Sets the maximum time in seconds that this data source
-            will wait while attempting to connect to a database.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="transactional"
-                   type="javaee:xsdBooleanType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Set to false if connections should not participate in
-            transactions.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="isolation-level"
-                   type="javaee:isolation-levelType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Isolation level for connections.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="initial-pool-size"
-                   type="javaee:xsdIntegerType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Number of connections that should be created when a
-            connection pool is initialized.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="max-pool-size"
-                   type="javaee:xsdIntegerType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Maximum number of connections that should be concurrently
-            allocated for a connection pool.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="min-pool-size"
-                   type="javaee:xsdIntegerType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Minimum number of connections that should be concurrently
-            allocated for a connection pool.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="max-idle-time"
-                   type="javaee:xsdIntegerType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The number of seconds that a physical connection should
-            remain unused in the pool before the connection is
-            closed for a connection pool.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="max-statements"
-                   type="javaee:xsdIntegerType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The total number of statements that a connection pool
-            should keep open.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </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="javaee:xsdStringType">
-        <xsd:attribute ref="xml:lang"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-  <xsd:simpleType name="dewey-versionType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        This type defines a dewey decimal that is used
-        to describe versions of documents. 
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:restriction base="xsd:token">
-      <xsd:pattern value="\.?[0-9]+(\.[0-9]+)*"/>
-    </xsd:restriction>
-  </xsd:simpleType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="display-nameType">
-    <xsd:annotation>
-      <xsd:documentation>
-        <![CDATA[[
-        The display-name type contains a short name that is intended
-        to be displayed by tools. It is used by display-name
-        elements.  The display name need not be unique.
-        
-        Example: 
-        
-        ...
-        <display-name xml:lang="en">
-        Employee Self Service
-        </display-name>
-        
-        The value of the xml:lang attribute is "en" (English) by default. 
-        
-        ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="javaee:string">
-        <xsd:attribute ref="xml:lang"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="ejb-linkType">
-    <xsd:annotation>
-      <xsd:documentation>
-        <![CDATA[[
-        The ejb-linkType is used by ejb-link
-        elements in the ejb-ref or ejb-local-ref elements to specify
-        that an EJB reference is linked to enterprise bean.
-        
-        The value of the ejb-link element must be the ejb-name of an
-        enterprise bean in the same ejb-jar file or in another ejb-jar
-        file in the same Java EE application unit. 
-        
-        Alternatively, the name in the ejb-link element may be
-        composed of a path name specifying the ejb-jar containing the
-        referenced enterprise bean with the ejb-name of the target
-        bean appended and separated from the path name by "#".  The
-        path name is relative to the Deployment File containing
-        Deployment Component that is referencing the enterprise
-        bean.  This allows multiple enterprise beans with the same
-        ejb-name to be uniquely identified.
-        
-        Examples:
-        
-        <ejb-link>EmployeeRecord</ejb-link>
-        
-        <ejb-link>../products/product.jar#ProductEJB</ejb-link>
-        
-        ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="ejb-local-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The ejb-local-refType is used by ejb-local-ref elements for
-        the declaration of a reference to an enterprise bean's local
-        home or to the local business interface of a 3.0 bean.
-        The declaration consists of:
-        
-        - an optional description
-        - the EJB reference name used in the code of the Deployment 
-        Component that's referencing the enterprise bean.
-        - the optional expected type of the referenced enterprise bean
-        - the optional expected local interface of the referenced 
-        enterprise bean or the local business interface of the 
-        referenced enterprise bean.
-        - the optional expected local home interface of the referenced 
-        enterprise bean. Not applicable if this ejb-local-ref refers
-        to the local business interface of a 3.0 bean.
-        - optional ejb-link information, used to specify the 
-        referenced enterprise bean
-        - optional elements to define injection of the named enterprise  
-        bean into a component field or property.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-                   type="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="ejb-ref-name"
-                   type="javaee:ejb-ref-nameType"/>
-      <xsd:element name="ejb-ref-type"
-                   type="javaee:ejb-ref-typeType"
-                   minOccurs="0"/>
-      <xsd:element name="local-home"
-                   type="javaee:local-homeType"
-                   minOccurs="0"/>
-      <xsd:element name="local"
-                   type="javaee:localType"
-                   minOccurs="0"/>
-      <xsd:element name="ejb-link"
-                   type="javaee:ejb-linkType"
-                   minOccurs="0"/>
-      <xsd:group ref="javaee:resourceGroup"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="ejb-ref-nameType">
-    <xsd:annotation>
-      <xsd:documentation>
-        <![CDATA[[
-        The ejb-ref-name element contains the name of an EJB
-        reference. The EJB reference is an entry in the
-        Deployment Component's environment and is relative to the
-        java:comp/env context.  The name must be unique within the
-        Deployment Component.
-        
-        It is recommended that name is prefixed with "ejb/".
-        
-        Example:
-        
-        <ejb-ref-name>ejb/Payroll</ejb-ref-name>
-        
-        ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:jndi-nameType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="ejb-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The ejb-refType is used by ejb-ref elements for the
-        declaration of a reference to an enterprise bean's home or
-        to the remote business interface of a 3.0 bean.  
-        The declaration consists of:
-        
-        - an optional description
-        - the EJB reference name used in the code of
-        the Deployment Component that's referencing the enterprise
-        bean. 
-        - the optional expected type of the referenced enterprise bean
-        - the optional remote interface of the referenced enterprise bean
-        or the remote business interface of the referenced enterprise 
-        bean
-        - the optional expected home interface of the referenced 
-        enterprise bean.  Not applicable if this ejb-ref
-        refers to the remote business interface of a 3.0 bean.
-        - optional ejb-link information, used to specify the
-        referenced enterprise bean
-        - optional elements to define injection of the named enterprise
-        bean into a component field or property
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-                   type="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="ejb-ref-name"
-                   type="javaee:ejb-ref-nameType"/>
-      <xsd:element name="ejb-ref-type"
-                   type="javaee:ejb-ref-typeType"
-                   minOccurs="0"/>
-      <xsd:element name="home"
-                   type="javaee:homeType"
-                   minOccurs="0"/>
-      <xsd:element name="remote"
-                   type="javaee:remoteType"
-                   minOccurs="0"/>
-      <xsd:element name="ejb-link"
-                   type="javaee:ejb-linkType"
-                   minOccurs="0"/>
-      <xsd:group ref="javaee:resourceGroup"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="ejb-ref-typeType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The ejb-ref-typeType contains the expected type of the
-        referenced enterprise bean.
-        
-        The ejb-ref-type designates a value
-        that must be one of the following:
-        
-        Entity
-        Session
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-        <xsd:enumeration value="Entity"/>
-        <xsd:enumeration value="Session"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="emptyType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        This type is used to designate an empty
-        element when used. 
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="env-entryType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The env-entryType is used to declare an application's
-        environment entry. The declaration consists of an optional
-        description, the name of the environment entry, a type
-        (optional if the value is injected, otherwise required), and
-        an optional value.
-        
-        It also includes optional elements to define injection of
-        the named resource into fields or JavaBeans properties.
-        
-        If a value is not specified and injection is requested,
-        no injection will occur and no entry of the specified name
-        will be created.  This allows an initial value to be
-        specified in the source code without being incorrectly
-        changed when no override has been specified.
-        
-        If a value is not specified and no injection is requested,
-        a value must be supplied during deployment. 
-        
-        This type is used by env-entry elements.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-                   type="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="env-entry-name"
-                   type="javaee:jndi-nameType">
-        <xsd:annotation>
-          <xsd:documentation>
-            <![CDATA[[
-            The env-entry-name element contains the name of a
-            Deployment Component's environment entry.  The name
-            is a JNDI name relative to the java:comp/env
-            context.  The name must be unique within a 
-            Deployment Component. The uniqueness
-            constraints must be defined within the declared
-            context.
-            
-            Example:
-            
-            <env-entry-name>minAmount</env-entry-name>
-            
-            ]]>
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="env-entry-type"
-                   type="javaee:env-entry-type-valuesType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-            <![CDATA[[
-            The env-entry-type element contains the Java language
-            type of the environment entry.  If an injection target
-            is specified for the environment entry, the type may
-            be omitted, or must match the type of the injection
-            target.  If no injection target is specified, the type
-            is required.
-            
-            Example:
-            
-            <env-entry-type>java.lang.Integer</env-entry-type>
-            
-            ]]>
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="env-entry-value"
-                   type="javaee:xsdStringType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-            <![CDATA[[
-            The env-entry-value designates the value of a
-            Deployment Component's environment entry. The value
-            must be a String that is valid for the
-            constructor of the specified type that takes a
-            single String parameter, or for java.lang.Character,
-            a single character.
-            
-            Example:
-            
-            <env-entry-value>100.00</env-entry-value>
-            
-            ]]>
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:group ref="javaee:resourceGroup"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="env-entry-type-valuesType">
-    <xsd:annotation>
-      <xsd:documentation>
-        <![CDATA[[
-        This type contains the fully-qualified Java type of the
-        environment entry value that is expected by the
-        application's code.
-        
-        The following are the legal values of env-entry-type-valuesType:
-        
-        java.lang.Boolean
-        java.lang.Byte
-        java.lang.Character
-        java.lang.String
-        java.lang.Short
-        java.lang.Integer
-        java.lang.Long
-        java.lang.Float
-        java.lang.Double
-        		  java.lang.Class
-        		  any enumeration type (i.e. a subclass of java.lang.Enum)
-        
-        Examples:
-        
-        <env-entry-type>java.lang.Boolean</env-entry-type>
-        <env-entry-type>java.lang.Class</env-entry-type>
-        <env-entry-type>com.example.Color</env-entry-type>
-        
-        ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:fully-qualified-classType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="fully-qualified-classType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The elements that use this type designate the name of a
-        Java class or interface.  The name is in the form of a
-        "binary name", as defined in the JLS.  This is the form
-        of name used in Class.forName().  Tools that need the
-        canonical name (the name used in source code) will need
-        to convert this binary name to the canonical name.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="generic-booleanType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        This type defines four different values which can designate
-        boolean values. This includes values yes and no which are 
-        not designated by xsd:boolean
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-        <xsd:enumeration value="true"/>
-        <xsd:enumeration value="false"/>
-        <xsd:enumeration value="yes"/>
-        <xsd:enumeration value="no"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="iconType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The icon type contains small-icon and large-icon elements
-        that specify the file names for small and large GIF, JPEG,
-        or PNG icon images used to represent the parent element in a
-        GUI tool. 
-        
-        The xml:lang attribute defines the language that the
-        icon file names are provided in. Its value is "en" (English)
-        by default. 
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="small-icon"
-                   type="javaee:pathType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-            <![CDATA[[
-            The small-icon element contains the name of a file
-            containing a small (16 x 16) icon image. The file
-            name is a relative path within the Deployment
-            Component's Deployment File.
-            
-            The image may be in the GIF, JPEG, or PNG format.
-            The icon can be used by tools.
-            
-            Example:
-            
-            <small-icon>employee-service-icon16x16.jpg</small-icon>
-            
-            ]]>
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="large-icon"
-                   type="javaee:pathType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-            <![CDATA[[
-            The large-icon element contains the name of a file
-            containing a large
-            (32 x 32) icon image. The file name is a relative 
-            path within the Deployment Component's Deployment
-            File.
-            
-            The image may be in the GIF, JPEG, or PNG format.
-            The icon can be used by tools.
-            
-            Example:
-            
-            <large-icon>employee-service-icon32x32.jpg</large-icon>
-            
-            ]]>
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute ref="xml:lang"/>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="injection-targetType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        An injection target specifies a class and a name within
-        that class into which a resource should be injected.
-        
-        The injection target class specifies the fully qualified
-        class name that is the target of the injection.  The
-        Java EE specifications describe which classes can be an
-        injection target.
-        
-        The injection target name specifies the target within
-        the specified class.  The target is first looked for as a
-        JavaBeans property name.  If not found, the target is
-        looked for as a field name.
-        
-        The specified resource will be injected into the target
-        during initialization of the class by either calling the
-        set method for the target property or by setting a value
-        into the named field.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="injection-target-class"
-                   type="javaee:fully-qualified-classType"/>
-      <xsd:element name="injection-target-name"
-                   type="javaee:java-identifierType"/>
-    </xsd:sequence>
-  </xsd:complexType>
-
-  <xsd:simpleType name="isolation-levelType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        	The following transaction isolation levels are allowed
-        	(see documentation for the java.sql.Connection interface):
-        TRANSACTION_READ_UNCOMMITTED
-        TRANSACTION_READ_COMMITTED
-        TRANSACTION_REPEATABLE_READ
-        TRANSACTION_SERIALIZABLE
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:restriction base="xsd:string">
-      <xsd:enumeration value="TRANSACTION_READ_UNCOMMITTED"/>
-      <xsd:enumeration value="TRANSACTION_READ_COMMITTED"/>
-      <xsd:enumeration value="TRANSACTION_REPEATABLE_READ"/>
-      <xsd:enumeration value="TRANSACTION_SERIALIZABLE"/>
-    </xsd:restriction>
-  </xsd:simpleType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="java-identifierType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The java-identifierType defines a Java identifier.
-        The users of this type should further verify that 
-        the content does not contain Java reserved keywords.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-        <xsd:pattern value="($|_|\p{L})(\p{L}|\p{Nd}|_|$)*"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="java-typeType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        This is a generic type that designates a Java primitive
-        type or a fully qualified name of a Java interface/type,
-        or an array of such types.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-        <xsd:pattern value="[^\p{Z}]*"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="jdbc-urlType">
-    <xsd:annotation>
-      <xsd:documentation>
-        <![CDATA[[
-        The jdbc-urlType contains the url pattern of the mapping.
-        It must follow the rules specified in Section 9.3 of the
-        JDBC Specification where the format is:
-        
-        jdbc:<subprotocol>:<subname>
-        
-        Example:
-        
-        <url>jdbc:mysql://localhost:3307/testdb</url>
-        
-        ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-        <xsd:pattern value="jdbc:(.*):(.*)"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="jndi-nameType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The jndi-nameType type designates a JNDI name in the
-        Deployment Component's environment and is relative to the
-        java:comp/env context.  A JNDI name must be unique within the
-        Deployment Component.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="homeType">
-    <xsd:annotation>
-      <xsd:documentation>
-        <![CDATA[[
-        The homeType defines the fully-qualified name of
-        an enterprise bean's home interface. 
-        
-        Example:
-        
-        <home>com.aardvark.payroll.PayrollHome</home>
-        
-        ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:fully-qualified-classType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="lifecycle-callbackType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The lifecycle-callback type specifies a method on a
-        class to be called when a lifecycle event occurs.
-        Note that each class may have only one lifecycle callback
-        method for any given event and that the method may not
-        be overloaded.
-        
-        If the lifefycle-callback-class element is missing then
-        the class defining the callback is assumed to be the
-        component class in scope at the place in the descriptor
-        in which the callback definition appears.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="lifecycle-callback-class"
-                   type="javaee:fully-qualified-classType"
-                   minOccurs="0"/>
-      <xsd:element name="lifecycle-callback-method"
-                   type="javaee:java-identifierType"/>
-    </xsd:sequence>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="listenerType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The listenerType indicates the deployment properties for a web
-        application listener bean.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:group ref="javaee:descriptionGroup"/>
-      <xsd:element name="listener-class"
-                   type="javaee:fully-qualified-classType">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The listener-class element declares a class in the
-            application must be registered as a web
-            application listener bean. The value is the fully
-            qualified classname of the listener class.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="localType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The localType defines the fully-qualified name of an
-        enterprise bean's local interface.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:fully-qualified-classType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="local-homeType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The local-homeType defines the fully-qualified
-        name of an enterprise bean's local home interface.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:fully-qualified-classType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="param-valueType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        This type is a general type that can be used to declare
-        parameter/value lists.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-                   type="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="param-name"
-                   type="javaee:string">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The param-name element contains the name of a
-            parameter.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="param-value"
-                   type="javaee:xsdStringType">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The param-value element contains the value of a
-            parameter.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="pathType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The elements that use this type designate either a relative
-        path or an absolute path starting with a "/".
-        
-        In elements that specify a pathname to a file within the
-        same Deployment File, relative filenames (i.e., those not
-        starting with "/") are considered relative to the root of
-        the Deployment File's namespace.  Absolute filenames (i.e.,
-        those starting with "/") also specify names in the root of
-        the Deployment File's namespace.  In general, relative names
-        are preferred.  The exception is .war files where absolute
-        names are preferred for consistency with the Servlet API.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="persistence-context-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-        <![CDATA[[
-        The persistence-context-ref element contains a declaration
-        of Deployment Component's reference to a persistence context
-        associated within a Deployment Component's
-        environment. It consists of:
-        
-        - an optional description
-        - the persistence context reference name
-        - an optional persistence unit name.  If not specified,
-        the default persistence unit is assumed.
-        - an optional specification as to whether
-        the persistence context type is Transaction or
-        Extended.  If not specified, Transaction is assumed.
-        - an optional list of persistence properties
-        - optional injection targets
-        
-        Examples:
-        
-        <persistence-context-ref>
-        <persistence-context-ref-name>myPersistenceContext
-        </persistence-context-ref-name>
-        </persistence-context-ref>
-        
-        <persistence-context-ref>
-        <persistence-context-ref-name>myPersistenceContext
-        </persistence-context-ref-name>
-        <persistence-unit-name>PersistenceUnit1
-        </persistence-unit-name>
-        <persistence-context-type>Extended</persistence-context-type>
-        </persistence-context-ref>
-        
-        ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-                   type="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="persistence-context-ref-name"
-                   type="javaee:jndi-nameType">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The persistence-context-ref-name element specifies
-            the name of a persistence context reference; its
-            value is the environment entry name used in
-            Deployment Component code.  The name is a JNDI name
-            relative to the java:comp/env context.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="persistence-unit-name"
-                   type="javaee:string"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The Application Assembler(or BeanProvider) may use the
-            following syntax to avoid the need to rename persistence
-            units to have unique names within a Java EE application.
-            
-            The Application Assembler specifies the pathname of the
-            root of the persistence.xml file for the referenced
-            persistence unit and appends the name of the persistence
-            unit separated from the pathname by #. The pathname is
-            relative to the referencing application component jar file. 
-            In this manner, multiple persistence units with the same
-            persistence unit name may be uniquely identified when the 
-            Application Assembler cannot change persistence unit names.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="persistence-context-type"
-                   type="javaee:persistence-context-typeType"
-                   minOccurs="0"/>
-      <xsd:element name="persistence-property"
-                   type="javaee:propertyType"
-                   minOccurs="0"
-                   maxOccurs="unbounded">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Used to specify properties for the container or persistence
-            provider.  Vendor-specific properties may be included in
-            the set of properties.  Properties that are not recognized
-            by a vendor must be ignored.  Entries that make use of the 
-            namespace javax.persistence and its subnamespaces must not
-            be used for vendor-specific properties.  The namespace
-            javax.persistence is reserved for use by the specification.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:group ref="javaee:resourceBaseGroup"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="persistence-context-typeType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The persistence-context-typeType specifies the transactional
-        nature of a persistence context reference.  
-        
-        The value of the persistence-context-type element must be
-        one of the following:
-        Transaction
-        Extended
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-        <xsd:enumeration value="Transaction"/>
-        <xsd:enumeration value="Extended"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="propertyType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        Specifies a name/value pair.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="name"
-                   type="javaee:xsdStringType">
-      </xsd:element>
-      <xsd:element name="value"
-                   type="javaee:xsdStringType">
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="persistence-unit-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-        <![CDATA[[
-        The persistence-unit-ref element contains a declaration
-        of Deployment Component's reference to a persistence unit
-        associated within a Deployment Component's
-        environment. It consists of:
-        
-        - an optional description
-        - the persistence unit reference name
-        - an optional persistence unit name.  If not specified,
-        the default persistence unit is assumed.
-        - optional injection targets
-        
-        Examples:
-        
-        <persistence-unit-ref>
-        <persistence-unit-ref-name>myPersistenceUnit
-        </persistence-unit-ref-name>
-        </persistence-unit-ref>
-        
-        <persistence-unit-ref>
-        <persistence-unit-ref-name>myPersistenceUnit
-        </persistence-unit-ref-name>
-        <persistence-unit-name>PersistenceUnit1
-        </persistence-unit-name>
-        </persistence-unit-ref>
-        
-        ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-                   type="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="persistence-unit-ref-name"
-                   type="javaee:jndi-nameType">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The persistence-unit-ref-name element specifies
-            the name of a persistence unit reference; its
-            value is the environment entry name used in
-            Deployment Component code.  The name is a JNDI name
-            relative to the java:comp/env context.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="persistence-unit-name"
-                   type="javaee:string"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The Application Assembler(or BeanProvider) may use the
-            following syntax to avoid the need to rename persistence
-            units to have unique names within a Java EE application.
-            
-            The Application Assembler specifies the pathname of the
-            root of the persistence.xml file for the referenced
-            persistence unit and appends the name of the persistence
-            unit separated from the pathname by #. The pathname is
-            relative to the referencing application component jar file. 
-            In this manner, multiple persistence units with the same
-            persistence unit name may be uniquely identified when the 
-            Application Assembler cannot change persistence unit names.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:group ref="javaee:resourceBaseGroup"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="remoteType">
-    <xsd:annotation>
-      <xsd:documentation>
-        <![CDATA[[
-        The remote element contains the fully-qualified name
-        of the enterprise bean's remote interface.
-        
-        Example:
-        
-        <remote>com.wombat.empl.EmployeeService</remote>
-        
-        ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:fully-qualified-classType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="resource-env-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-        <![CDATA[[
-        The resource-env-refType is used to define
-        resource-env-ref elements.  It contains a declaration of a
-        Deployment Component's reference to an administered object
-        associated with a resource in the Deployment Component's
-        environment.  It consists of an optional description, the
-        resource environment reference name, and an optional
-        indication of the resource environment reference type
-        expected by the Deployment Component code.
-        
-        It also includes optional elements to define injection of
-        the named resource into fields or JavaBeans properties.
-        
-        The resource environment type must be supplied unless an
-        injection target is specified, in which case the type
-        of the target is used.  If both are specified, the type
-        must be assignment compatible with the type of the injection
-        target.
-        
-        Example:
-        
-        <resource-env-ref>
-        <resource-env-ref-name>jms/StockQueue
-        </resource-env-ref-name>
-        <resource-env-ref-type>javax.jms.Queue
-        </resource-env-ref-type>
-        </resource-env-ref>
-        
-        ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-                   type="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="resource-env-ref-name"
-                   type="javaee:jndi-nameType">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The resource-env-ref-name element specifies the name
-            of a resource environment reference; its value is
-            the environment entry name used in
-            the Deployment Component code.  The name is a JNDI 
-            name relative to the java:comp/env context and must 
-            be unique within a Deployment Component.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="resource-env-ref-type"
-                   type="javaee:fully-qualified-classType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The resource-env-ref-type element specifies the type
-            of a resource environment reference.  It is the
-            fully qualified name of a Java language class or
-            interface.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:group ref="javaee:resourceGroup"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="resource-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-        <![CDATA[[
-        The resource-refType contains a declaration of a
-        Deployment Component's reference to an external resource. It
-        consists of an optional description, the resource manager
-        connection factory reference name, an optional indication of
-        the resource manager connection factory type expected by the
-        Deployment Component code, an optional type of authentication
-        (Application or Container), and an optional specification of
-        the shareability of connections obtained from the resource
-        (Shareable or Unshareable).
-        
-        It also includes optional elements to define injection of
-        the named resource into fields or JavaBeans properties.
-        
-        The connection factory type must be supplied unless an
-        injection target is specified, in which case the type
-        of the target is used.  If both are specified, the type
-        must be assignment compatible with the type of the injection
-        target.
-        
-        Example:
-        
-        <resource-ref>
-        <res-ref-name>jdbc/EmployeeAppDB</res-ref-name>
-        <res-type>javax.sql.DataSource</res-type>
-        <res-auth>Container</res-auth>
-        <res-sharing-scope>Shareable</res-sharing-scope>
-        </resource-ref>
-        
-        ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-                   type="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="res-ref-name"
-                   type="javaee:jndi-nameType">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The res-ref-name element specifies the name of a
-            resource manager connection factory reference.
-            The name is a JNDI name relative to the
-            java:comp/env context.  
-            The name must be unique within a Deployment File. 
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="res-type"
-                   type="javaee:fully-qualified-classType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The res-type element specifies the type of the data
-            source. The type is specified by the fully qualified
-            Java language class or interface
-            expected to be implemented by the data source.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="res-auth"
-                   type="javaee:res-authType"
-                   minOccurs="0"/>
-      <xsd:element name="res-sharing-scope"
-                   type="javaee:res-sharing-scopeType"
-                   minOccurs="0"/>
-      <xsd:group ref="javaee:resourceGroup"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="res-authType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The res-authType specifies whether the Deployment Component
-        code signs on programmatically to the resource manager, or
-        whether the Container will sign on to the resource manager
-        on behalf of the Deployment Component. In the latter case,
-        the Container uses information that is supplied by the
-        Deployer.
-        
-        The value must be one of the two following:
-        
-        Application
-        Container
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-        <xsd:enumeration value="Application"/>
-        <xsd:enumeration value="Container"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="res-sharing-scopeType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The res-sharing-scope type specifies whether connections
-        obtained through the given resource manager connection
-        factory reference can be shared. The value, if specified,
-        must be one of the two following:
-        
-        Shareable
-        Unshareable
-        
-        The default value is Shareable.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-        <xsd:enumeration value="Shareable"/>
-        <xsd:enumeration value="Unshareable"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="run-asType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The run-asType specifies the run-as identity to be
-        used for the execution of a component. It contains an 
-        optional description, and the name of a security role.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-                   type="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="role-name"
-                   type="javaee:role-nameType"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="role-nameType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The role-nameType designates the name of a security role.
-        
-        The name must conform to the lexical rules for a token.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="security-roleType">
-    <xsd:annotation>
-      <xsd:documentation>
-        <![CDATA[[
-        The security-roleType contains the definition of a security
-        role. The definition consists of an optional description of
-        the security role, and the security role name.
-        
-        Example:
-        
-        <security-role>
-        <description>
-        This role includes all employees who are authorized
-        to access the employee service application.
-        </description>
-        <role-name>employee</role-name>
-        </security-role>
-        
-        ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-                   type="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="role-name"
-                   type="javaee:role-nameType"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="security-role-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The security-role-refType contains the declaration of a
-        security role reference in a component's or a
-        Deployment Component's code. The declaration consists of an
-        optional description, the security role name used in the
-        code, and an optional link to a security role. If the
-        security role is not specified, the Deployer must choose an
-        appropriate security role.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-                   type="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="role-name"
-                   type="javaee:role-nameType">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The value of the role-name element must be the String used
-            as the parameter to the 
-            EJBContext.isCallerInRole(String roleName) method or the
-            HttpServletRequest.isUserInRole(String role) method.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="role-link"
-                   type="javaee:role-nameType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The role-link element is a reference to a defined
-            security role. The role-link element must contain
-            the name of one of the security roles defined in the
-            security-role elements.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="xsdQNameType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        This type adds an "id" attribute to xsd:QName.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:QName">
-        <xsd:attribute name="id"
-                       type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="xsdBooleanType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        This type adds an "id" attribute to xsd:boolean.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:boolean">
-        <xsd:attribute name="id"
-                       type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="xsdNMTOKENType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        This type adds an "id" attribute to xsd:NMTOKEN.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:NMTOKEN">
-        <xsd:attribute name="id"
-                       type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="xsdAnyURIType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        This type adds an "id" attribute to xsd:anyURI.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:anyURI">
-        <xsd:attribute name="id"
-                       type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="xsdIntegerType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        This type adds an "id" attribute to xsd:integer.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:integer">
-        <xsd:attribute name="id"
-                       type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="xsdPositiveIntegerType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        This type adds an "id" attribute to xsd:positiveInteger.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:positiveInteger">
-        <xsd:attribute name="id"
-                       type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="xsdNonNegativeIntegerType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        This type adds an "id" attribute to xsd:nonNegativeInteger.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:nonNegativeInteger">
-        <xsd:attribute name="id"
-                       type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="xsdStringType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        This type adds an "id" attribute to xsd:string.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:string">
-        <xsd:attribute name="id"
-                       type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="string">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        This is a special string datatype that is defined by Java EE as
-        a base type for defining collapsed strings. When schemas
-        require trailing/leading space elimination as well as
-        collapsing the existing whitespace, this base type may be
-        used.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:token">
-        <xsd:attribute name="id"
-                       type="xsd:ID"/>
-      </xsd:extension>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="true-falseType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        This simple type designates a boolean with only two
-        permissible values
-        
-        - true
-        - false
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:xsdBooleanType">
-        <xsd:pattern value="(true|false)"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="url-patternType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The url-patternType contains the url pattern of the mapping.
-        It must follow the rules specified in Section 11.2 of the
-        Servlet API Specification. This pattern is assumed to be in
-        URL-decoded form and must not contain CR(#xD) or LF(#xA).
-        If it contains those characters, the container must inform
-        the developer with a descriptive error message.
-        The container must preserve all characters including whitespaces.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:extension base="xsd:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="message-destinationType">
-    <xsd:annotation>
-      <xsd:documentation>
-        <![CDATA[[
-        The message-destinationType specifies a message
-        destination. The logical destination described by this
-        element is mapped to a physical destination by the Deployer.
-        
-        The message destination element contains: 
-        
-        - an optional description
-        - an optional display-name
-        - an optional icon
-        - a message destination name which must be unique
-        among message destination names within the same 
-        Deployment File. 
-        - an optional mapped name
-        - an optional lookup name
-        
-        Example: 
-        
-        <message-destination>
-        <message-destination-name>CorporateStocks
-        </message-destination-name>
-        </message-destination>
-        
-        ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:group ref="javaee:descriptionGroup"/>
-      <xsd:element name="message-destination-name"
-                   type="javaee:string">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The message-destination-name element specifies a
-            name for a message destination.  This name must be
-            unique among the names of message destinations
-            within the Deployment File.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="mapped-name"
-                   type="javaee:xsdStringType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            A product specific name that this message destination
-            should be mapped to.  Each message-destination-ref
-            element that references this message destination will
-            define a name in the namespace of the referencing
-            component or in one of the other predefined namespaces. 
-            Many application servers provide a way to map these
-            local names to names of resources known to the
-            application server.  This mapped name is often a global
-            JNDI name, but may be a name of any form.  Each of the
-            local names should be mapped to this same global name.
-            
-            Application servers are not required to support any
-            particular form or type of mapped name, nor the ability
-            to use mapped names.  The mapped name is
-            product-dependent and often installation-dependent.  No
-            use of a mapped name is portable.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="lookup-name"
-                   type="javaee:xsdStringType"
-                   minOccurs="0">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The JNDI name to be looked up to resolve the message destination.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="message-destination-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-        <![CDATA[[
-        The message-destination-ref element contains a declaration
-        of Deployment Component's reference to a message destination
-        associated with a resource in Deployment Component's
-        environment. It consists of:
-        
-        - an optional description
-        - the message destination reference name
-        - an optional message destination type
-        - an optional specification as to whether
-        the destination is used for 
-        consuming or producing messages, or both.
-        if not specified, "both" is assumed.
-        - an optional link to the message destination
-        - optional injection targets
-        
-        The message destination type must be supplied unless an
-        injection target is specified, in which case the type
-        of the target is used.  If both are specified, the type
-        must be assignment compatible with the type of the injection
-        target.
-        
-        Examples:
-        
-        <message-destination-ref>
-        <message-destination-ref-name>jms/StockQueue
-        </message-destination-ref-name>
-        <message-destination-type>javax.jms.Queue
-        </message-destination-type>
-        <message-destination-usage>Consumes
-        </message-destination-usage>
-        <message-destination-link>CorporateStocks
-        </message-destination-link>
-        </message-destination-ref>
-        
-        ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-                   type="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-      <xsd:element name="message-destination-ref-name"
-                   type="javaee:jndi-nameType">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The message-destination-ref-name element specifies
-            the name of a message destination reference; its
-            value is the environment entry name used in
-            Deployment Component code.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="message-destination-type"
-                   type="javaee:message-destination-typeType"
-                   minOccurs="0"/>
-      <xsd:element name="message-destination-usage"
-                   type="javaee:message-destination-usageType"
-                   minOccurs="0"/>
-      <xsd:element name="message-destination-link"
-                   type="javaee:message-destination-linkType"
-                   minOccurs="0"/>
-      <xsd:group ref="javaee:resourceGroup"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="message-destination-usageType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The message-destination-usageType specifies the use of the
-        message destination indicated by the reference.  The value
-        indicates whether messages are consumed from the message
-        destination, produced for the destination, or both.  The
-        Assembler makes use of this information in linking producers
-        of a destination with its consumers.
-        
-        The value of the message-destination-usage element must be
-        one of the following:
-        Consumes
-        Produces
-        ConsumesProduces
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-        <xsd:enumeration value="Consumes"/>
-        <xsd:enumeration value="Produces"/>
-        <xsd:enumeration value="ConsumesProduces"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="message-destination-typeType">
-    <xsd:annotation>
-      <xsd:documentation>
-        <![CDATA[[
-        The message-destination-typeType specifies the type of
-        the destination. The type is specified by the Java interface
-        expected to be implemented by the destination.
-        
-        Example: 
-        
-        <message-destination-type>javax.jms.Queue
-        </message-destination-type>
-        
-        ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:fully-qualified-classType"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="message-destination-linkType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The message-destination-linkType is used to link a message
-        destination reference or message-driven bean to a message
-        destination.
-        
-        The Assembler sets the value to reflect the flow of messages
-        between producers and consumers in the application.
-        
-        The value must be the message-destination-name of a message
-        destination in the same Deployment File or in another
-        Deployment File in the same Java EE application unit.
-        
-        Alternatively, the value may be composed of a path name
-        specifying a Deployment File containing the referenced
-        message destination with the message-destination-name of the
-        destination appended and separated from the path name by
-        "#". The path name is relative to the Deployment File
-        containing Deployment Component that is referencing the
-        message destination.  This allows multiple message
-        destinations with the same name to be uniquely identified.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-</xsd:schema>
-

jboss-as-7.2.0.Final/docs/schema/javaee_web_services_1_2.xsd

@@ -1,747 +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/javaee"
-	    xmlns:javaee="http://java.sun.com/xml/ns/javaee"
-	    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
-	    elementFormDefault="qualified"
-	    attributeFormDefault="unqualified"
-	    version="1.2">
-  <xsd:annotation>
-    <xsd:documentation>
-      @(#)javaee_web_services_1_2.xsds	1.18 02/13/06
-    </xsd:documentation>
-  </xsd:annotation>
-
-  <xsd:annotation>
-    <xsd:documentation>
-
-      Copyright 2003-2006 Sun Microsystems, Inc.
-      4150 Network Circle
-      Santa Clara, California 95054
-      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>
-
-      (C) Copyright International Business Machines Corporation 2002
-
-    </xsd:documentation>
-  </xsd:annotation>
-
-  <xsd:annotation>
-    <xsd:documentation>
-      <![CDATA[
-
-	The webservices element is the root element for the web services
-	deployment descriptor.  It specifies the set of web service
-	descriptions that are to be deployed into the Java EE Application
-	Server and the dependencies they have on container resources and
-	services.  The deployment descriptor must be named
-	"META-INF/webservices.xml" in the web services' jar file.
-
-	Used in: webservices.xml
-
-	All webservices deployment descriptors must indicate the
-	webservices schema by using the Java EE namespace:
-
-	http://java.sun.com/xml/ns/javaee
-
-	and by indicating the version of the schema by using the version
-	element as shown below:
-
-	    <webservices 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/javaee_web_services_1_2.xsd"
-	      version="1.2">
-	      ...
-	    </webservices>
-
-	The instance documents may indicate the published version of the
-	schema using the xsi:schemaLocation attribute for the Java EE
-	namespace with the following location:
-
-	http://java.sun.com/xml/ns/javaee/javaee_web_services_1_2.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="webservices" type="javaee:webservicesType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The webservices element is the root element for the web services
-	deployment descriptor.  It specifies the set of web service
-	descriptions that are to be deployed into the Java EE Application Server
-	and the dependencies they have on container resources and services.
-
-	Used in: webservices.xml
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:key name="webservice-description-name-key">
-      <xsd:annotation>
-	<xsd:documentation>
-
-	  The webservice-description-name identifies the collection of
-	  port-components associated with a WSDL file and JAX-RPC mapping. The
-	  name must be unique within the deployment descriptor.
-
-	</xsd:documentation>
-      </xsd:annotation>
-      <xsd:selector xpath="javaee:webservice-description"/>
-      <xsd:field xpath="javaee:webservice-description-name"/>
-    </xsd:key>
-  </xsd:element>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="handler-chainType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-      The handler-chain element defines the handlerchain.
-      Handlerchain can be defined such that the handlers in the
-      handlerchain operate,all ports of a service, on a specific
-      port or on a list of protocol-bindings. The choice of elements
-      service-name-pattern, port-name-pattern and protocol-bindings
-      are used to specify whether the handlers in handler-chain are
-      for a service, port or protocol binding. If none of these
-      choices are specified with the handler-chain element then the
-      handlers specified in the handler-chain will be applied on
-      everything.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-
-      <xsd:choice minOccurs="0" maxOccurs="1">
-         <xsd:element name="service-name-pattern"
-		      type="javaee:qname-pattern" />
-         <xsd:element name="port-name-pattern"
-		      type="javaee:qname-pattern" />
-         <xsd:element name="protocol-bindings"
-		      type="javaee:protocol-bindingListType"/>
-      </xsd:choice>
-
-      <xsd:element name="handler"
-                   type="javaee:port-component_handlerType"
-		   minOccurs="1" maxOccurs="unbounded"/>
-    </xsd:sequence>
-
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="handler-chainsType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-      The handler-chains element defines the handlerchains associated
-      with this service or service endpoint.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="handler-chain"
-                   type="javaee:handler-chainType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-    </xsd:sequence>
-
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="port-componentType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The port-component element associates a WSDL port with a web service
-	interface and implementation.  It defines the name of the port as a
-	component, optional description, optional display name, optional iconic
-	representations, WSDL port QName, Service Endpoint Interface, Service
-	Implementation Bean.
-
-	This element also associates a WSDL service with a JAX-WS Provider
-	implementation.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="javaee:descriptionType"
-		   minOccurs="0" maxOccurs="1"/>
-      <xsd:element name="display-name"
-		   type="javaee:display-nameType"
-		   minOccurs="0" maxOccurs="1"/>
-      <xsd:element name="icon"
-		   type="javaee:iconType"
-		   minOccurs="0" maxOccurs="1"/>
-      <xsd:element name="port-component-name"
-		   type="javaee:string">
-	<xsd:annotation>
-	  <xsd:documentation>
-	    <![CDATA[
-
-	      The port-component-name element specifies a port component's
-	      name.  This name is assigned by the module producer to name
-	      the service implementation bean in the module's deployment
-	      descriptor. The name must be unique among the port component
-	      names defined in the same module.
-
-	      Used in: port-component
-
-	      Example:
-		      <port-component-name>EmployeeService
-		      </port-component-name>
-
-	      ]]>
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="wsdl-service"
-		   type="javaee:xsdQNameType"
-		   minOccurs="0" maxOccurs="1">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    Defines the name space and local name part of the WSDL
-	    service QName. This is required to be specified for
-	    port components that are JAX-WS Provider implementations.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="wsdl-port"
-		   type="javaee:xsdQNameType"
-		   minOccurs="0" maxOccurs="1">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    Defines the name space and local name part of the WSDL
-	    port QName. This is not required to be specified for port
-	    components that are JAX-WS Provider implementations
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="enable-mtom"
-                   type="javaee:true-falseType"
-		   minOccurs="0" maxOccurs="1">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Used to enable or disable SOAP MTOM/XOP mechanism for an
-            endpoint implementation.
-
-	    Not to be specified for JAX-RPC runtime
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="protocol-binding"
-                   type="javaee:protocol-bindingType"
-		   minOccurs="0" maxOccurs="1">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Used to specify the protocol binding used by the port-component.
-	    If this element is not specified, then the default binding is
-            used (SOAP 1.1 over HTTP)
-
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="service-endpoint-interface"
-		   type="javaee:fully-qualified-classType"
-		   minOccurs="0" maxOccurs="1">
-	<xsd:annotation>
-	  <xsd:documentation>
-	    <![CDATA[
-
-	      The service-endpoint-interface element contains the
-	      fully-qualified name of the port component's Service Endpoint
-	      Interface.
-
-	      Used in: port-component
-
-	      Example:
-		      <remote>com.wombat.empl.EmployeeService</remote>
-
-	      This may not be specified in case there is no Service
-	      Enpoint Interface as is the case with directly using an
-	      implementation class with the @WebService annotation.
-
-	      When the port component is a Provider implementation
-	      this is not specified.
-
-	      ]]>
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="service-impl-bean"
-		   type="javaee:service-impl-beanType"/>
-
-      <xsd:choice>
-	<xsd:element name="handler"
-		     type="javaee:port-component_handlerType"
-		     minOccurs="0" maxOccurs="unbounded">
-	  <xsd:annotation>
-	    <xsd:documentation>
-		 To be used with JAX-RPC based runtime only.
-	    </xsd:documentation>
-	  </xsd:annotation>
-	</xsd:element>
-	<xsd:element name="handler-chains"
-		     type="javaee:handler-chainsType"
-		     minOccurs="0" maxOccurs="1">
-	  <xsd:annotation>
-	    <xsd:documentation>
-		 To be used with JAX-WS based runtime only.
-	    </xsd:documentation>
-	  </xsd:annotation>
-	</xsd:element>
-      </xsd:choice>
-
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="port-component_handlerType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	Declares the handler for a port-component. Handlers can access the
-	init-param name/value pairs using the HandlerInfo interface.
-
-	Used in: port-component
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:group ref="javaee:descriptionGroup"/>
-      <xsd:element name="handler-name"
-		   type="javaee:string">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    Defines the name of the handler. The name must be unique within the
-	    module.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="handler-class"
-		   type="javaee:fully-qualified-classType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    Defines a fully qualified class name for the handler implementation.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="init-param"
-		   type="javaee:param-valueType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-
-      <xsd:element name="soap-header"
-		   type="javaee:xsdQNameType"
-		   minOccurs="0" maxOccurs="unbounded">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    Defines the QName of a SOAP header that will be processed by the
-	    handler.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="soap-role"
-		   type="javaee:string"
-		   minOccurs="0" maxOccurs="unbounded">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The soap-role element contains a SOAP actor definition that the
-	    Handler will play as a role.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:simpleType name="protocol-URIAliasType">
-     <xsd:annotation>
-        <xsd:documentation>
-	   Defines the type that is used for specifying tokens that
-	   start with ## which are used to alias existing standard
-	   protocol bindings and support aliases for new standard
-	   binding URIs that are introduced in future specifications.
-
-	   The following tokens alias the standard protocol binding
-	   URIs:
-
-	   ##SOAP11_HTTP = "http://schemas.xmlsoap.org/wsdl/soap/http"
-	   ##SOAP11_HTTP_MTOM =
-                 "http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true"
-           ##SOAP12_HTTP = "http://www.w3.org/2003/05/soap/bindings/HTTP/"
-           ##SOAP12_HTTP_MTOM =
-		 "http://www.w3.org/2003/05/soap/bindings/HTTP/?mtom=true"
-           ##XML_HTTP = "http://www.w3.org/2004/08/wsdl/http"
-
-        </xsd:documentation>
-     </xsd:annotation>
-     <xsd:restriction base="xsd:token">
-        <xsd:pattern value="##.+"/>
-     </xsd:restriction>
-  </xsd:simpleType>
-
-<!-- **************************************************** -->
-
-  <xsd:simpleType name="protocol-bindingListType">
-     <xsd:annotation>
-        <xsd:documentation>
-	   Defines the type used for specifying a list of
-	   protocol-bindingType(s). For e.g.
-
-	    ##SOAP11_HTTP ##SOAP12_HTTP ##XML_HTTP
-
-        </xsd:documentation>
-     </xsd:annotation>
-     <xsd:list itemType="javaee:protocol-bindingType"/>
-  </xsd:simpleType>
-
-<!-- **************************************************** -->
-
-  <xsd:simpleType name="protocol-bindingType">
-     <xsd:annotation>
-        <xsd:documentation>
-	   Defines the type used for specifying the URI for the
-	   protocol binding used by the port-component.  For
-	   portability one could use one of the following tokens that
-	   alias the standard binding types:
-
-	    ##SOAP11_HTTP
-	    ##SOAP11_HTTP_MTOM
-	    ##SOAP12_HTTP
-	    ##SOAP12_HTTP_MTOM
-	    ##XML_HTTP
-
-	   Other specifications could define tokens that start with ##
-	   to alias new standard binding URIs that are introduced.
-
-        </xsd:documentation>
-     </xsd:annotation>
-     <xsd:union memberTypes="xsd:anyURI javaee:protocol-URIAliasType"/>
-  </xsd:simpleType>
-
-<!-- **************************************************** -->
-
-  <xsd:simpleType name="qname-pattern">
-     <xsd:annotation>
-        <xsd:documentation>
-	     This is used to specify the QName pattern in the
-	     attribute service-name-pattern and port-name-pattern in
-	     the handler-chain element
-
-	     For example, the various forms acceptable here for
-	     service-name-pattern attribute in handler-chain element
-	     are :
-
-	     Exact Name: service-name-pattern="ns1:EchoService"
-
-		 In this case, handlers specified in this
-		 handler-chain element will apply to all ports with
-		 this exact service name. The namespace prefix must
-		 have been declared in a namespace declaration
-		 attribute in either the start-tag of the element
-		 where the prefix is used or in an an ancestor
-		 element (i.e. an element in whose content the
-		 prefixed markup occurs)
-
-	     Pattern : service-name-pattern="ns1:EchoService*"
-
-		 In this case, handlers specified in this
-		 handler-chain element will apply to all ports whose
-		 Service names are like EchoService1, EchoServiceFoo
-		 etc. The namespace prefix must have been declared in
-		 a namespace declaration attribute in either the
-		 start-tag of the element where the prefix is used or
-		 in an an ancestor element (i.e. an element in whose
-		 content the prefixed markup occurs)
-
-	     Wild Card : service-name-pattern="*"
-
-		In this case, handlers specified in this handler-chain
-		element will apply to ports of all service names.
-
-	    The same can be applied to port-name attribute in
-	    handler-chain element.
-
-        </xsd:documentation>
-     </xsd:annotation>
-
-     <xsd:restriction base="xsd:token">
-        <xsd:pattern value="\*|([\i-[:]][\c-[:]]*:)?[\i-[:]][\c-[:]]*\*?"/>
-     </xsd:restriction>
-
-  </xsd:simpleType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="service-impl-beanType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The service-impl-bean element defines the web service implementation.
-	A service implementation can be an EJB bean class or JAX-RPC web
-	component.  Existing EJB implementations are exposed as a web service
-	using an ejb-link.
-
-	Used in: port-component
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:choice>
-      <xsd:element name="ejb-link"
-		   type="javaee:ejb-linkType"/>
-      <xsd:element name="servlet-link"
-		   type="javaee:servlet-linkType"/>
-    </xsd:choice>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="servlet-linkType">
-    <xsd:annotation>
-      <xsd:documentation>
-	<![CDATA[
-
-	  The servlet-link element is used in the service-impl-bean element
-	  to specify that a Service Implementation Bean is defined as a
-	  JAX-RPC Service Endpoint.
-
-	  The value of the servlet-link element must be the servlet-name of
-	  a JAX-RPC Service Endpoint in the same WAR file.
-
-	  Used in: service-impl-bean
-
-	  Example:
-		  <servlet-link>StockQuoteService</servlet-link>
-
-	  ]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="webservice-descriptionType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The webservice-description element defines a WSDL document file
-	and the set of Port components associated with the WSDL ports
-	defined in the WSDL document.  There may be multiple
-	webservice-descriptions defined within a module.
-
-	All WSDL file ports must have a corresponding port-component element
-	defined.
-
-	Used in: webservices
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="description"
-		   type="javaee:descriptionType"
-		   minOccurs="0" maxOccurs="1"/>
-      <xsd:element name="display-name"
-		   type="javaee:display-nameType"
-		   minOccurs="0" maxOccurs="1"/>
-      <xsd:element name="icon"
-		   type="javaee:iconType"
-		   minOccurs="0" maxOccurs="1"/>
-      <xsd:element name="webservice-description-name"
-		   type="javaee:string">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The webservice-description-name identifies the collection of
-	    port-components associated with a WSDL file and JAX-RPC
-	    mapping. The name must be unique within the deployment descriptor.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="wsdl-file"
-		   type="javaee:pathType"
-		   minOccurs="0" maxOccurs="1">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The wsdl-file element contains the name of a WSDL file in the
-	    module.  The file name is a relative path within the module.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="jaxrpc-mapping-file"
-		   type="javaee:pathType"
-		   minOccurs="0" maxOccurs="1">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The jaxrpc-mapping-file element contains the name of a file that
-	    describes the JAX-RPC mapping between the Java interaces used by
-	    the application and the WSDL description in the wsdl-file.  The
-	    file name is a relative path within the module.
-
-	    This is not required when JAX-WS based runtime is used.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="port-component"
-		   type="javaee:port-componentType"
-		   minOccurs="1" maxOccurs="unbounded">
-	<xsd:key name="port-component_handler-name-key">
-	  <xsd:annotation>
-	    <xsd:documentation>
-
-	      Defines the name of the handler. The name must be unique
-	      within the module.
-
-	    </xsd:documentation>
-	  </xsd:annotation>
-	  <xsd:selector xpath="javaee:handler"/>
-	  <xsd:field xpath="javaee:handler-name"/>
-	</xsd:key>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="webservicesType">
-    <xsd:sequence>
-      <xsd:group ref="javaee:descriptionGroup"/>
-      <xsd:element name="webservice-description"
-		   type="javaee:webservice-descriptionType"
-		   minOccurs="1" maxOccurs="unbounded">
-	<xsd:key name="port-component-name-key">
-	  <xsd:annotation>
-	    <xsd:documentation>
-	      <![CDATA[
-
-		The port-component-name element specifies a port
-		component's name.  This name is assigned by the module
-		producer to name the service implementation bean in the
-		module's deployment descriptor. The name must be unique
-		among the port component names defined in the same module.
-
-		Used in: port-component
-
-		Example:
-			<port-component-name>EmployeeService
-			</port-component-name>
-
-		]]>
-	    </xsd:documentation>
-	  </xsd:annotation>
-	  <xsd:selector xpath="javaee:port-component"/>
-	  <xsd:field xpath="javaee:port-component-name"/>
-	</xsd:key>
-      </xsd:element>
-    </xsd:sequence>
-
-    <xsd:attribute name="version"
-		   type="javaee:dewey-versionType"
-		   fixed="1.2"
-		   use="required">
-      <xsd:annotation>
-	<xsd:documentation>
-
-	  The required value for the version is 1.2.
-
-	</xsd:documentation>
-      </xsd:annotation>
-    </xsd:attribute>
-
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-</xsd:schema>
-

jboss-as-7.2.0.Final/docs/schema/javaee_web_services_1_3.xsd

@@ -1,580 +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/javaee"
-            xmlns:javaee="http://java.sun.com/xml/ns/javaee"
-            xmlns:xsd="http://www.w3.org/2001/XMLSchema"
-            elementFormDefault="qualified"
-            attributeFormDefault="unqualified"
-            version="1.3">
-  <xsd:annotation>
-    <xsd:documentation>
-
-      $Id$
-      
-    </xsd:documentation>
-  </xsd:annotation>
-
-  <xsd:annotation>
-    <xsd:documentation>
-
-      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
-      
-      Copyright 2003-2009 Sun Microsystems, Inc. All rights reserved.
-      
-      The contents of this file are subject to the terms of either the
-      GNU General Public License Version 2 only ("GPL") or the Common
-      Development and Distribution License("CDDL") (collectively, the
-      "License").  You may not use this file except in compliance with
-      the License. You can obtain a copy of the License at
-      https://glassfish.dev.java.net/public/CDDL+GPL.html or
-      glassfish/bootstrap/legal/LICENSE.txt.  See the License for the
-      specific language governing permissions and limitations under the
-      License.
-      
-      When distributing the software, include this License Header
-      Notice in each file and include the License file at
-      glassfish/bootstrap/legal/LICENSE.txt.  Sun designates this
-      particular file as subject to the "Classpath" exception as
-      provided by Sun in the GPL Version 2 section of the License file
-      that accompanied this code.  If applicable, add the following
-      below the License Header, with the fields enclosed by brackets []
-      replaced by your own identifying information:
-      "Portions Copyrighted [year] [name of copyright owner]"
-      
-      Contributor(s):
-      
-      If you wish your version of this file to be governed by only the
-      CDDL or only the GPL Version 2, indicate your decision by adding
-      "[Contributor] elects to include this software in this
-      distribution under the [CDDL or GPL Version 2] license."  If you
-      don't indicate a single choice of license, a recipient has the
-      option to distribute your version of this file under either the
-      CDDL, the GPL Version 2 or to extend the choice of license to its
-      licensees as provided above.  However, if you add GPL Version 2
-      code and therefore, elected the GPL Version 2 license, then the
-      option applies only if the new code is made subject to such
-      option by the copyright holder.
-      
-    </xsd:documentation>
-  </xsd:annotation>
-
-  <xsd:annotation>
-    <xsd:documentation>
-
-      (C) Copyright International Business Machines Corporation 2002
-      
-    </xsd:documentation>
-  </xsd:annotation>
-
-  <xsd:annotation>
-    <xsd:documentation>
-<![CDATA[[
-      The webservices element is the root element for the web services
-      deployment descriptor.  It specifies the set of web service
-      descriptions that are to be deployed into the Java EE Application
-      Server and the dependencies they have on container resources and
-      services.  The deployment descriptor must be named
-      "META-INF/webservices.xml" in the web services' jar file.
-      
-      Used in: webservices.xml
-      
-      All webservices deployment descriptors must indicate the
-      webservices schema by using the Java EE namespace:
-      
-      http://java.sun.com/xml/ns/javaee
-      
-      and by indicating the version of the schema by using the version
-      element as shown below:
-      
-      <webservices 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/javaee_web_services_1_3.xsd"
-      version="1.3">
-      ...
-      </webservices>
-      
-      The instance documents may indicate the published version of the
-      schema using the xsi:schemaLocation attribute for the Java EE
-      namespace with the following location:
-      
-      http://java.sun.com/xml/ns/javaee/javaee_web_services_1_3.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_6.xsd"/>
-
-
-<!-- **************************************************** -->
-
-  <xsd:element name="webservices"
-               type="javaee:webservicesType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The webservices element is the root element for the web services
-        deployment descriptor.  It specifies the set of web service
-        descriptions that are to be deployed into the Java EE Application Server
-        and the dependencies they have on container resources and services.
-        
-        Used in: webservices.xml
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:key name="webservice-description-name-key">
-      <xsd:annotation>
-        <xsd:documentation>
-
-          The webservice-description-name identifies the collection of
-          port-components associated with a WSDL file and JAX-RPC mapping. The
-          name must be unique within the deployment descriptor.
-          
-        </xsd:documentation>
-      </xsd:annotation>
-      <xsd:selector xpath="javaee:webservice-description"/>
-      <xsd:field xpath="javaee:webservice-description-name"/>
-    </xsd:key>
-  </xsd:element>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="port-componentType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The port-component element associates a WSDL port with a web service
-        interface and implementation.  It defines the name of the port as a
-        component, optional description, optional display name, optional iconic
-        representations, WSDL port QName, Service Endpoint Interface, Service
-        Implementation Bean.
-        
-        This element also associates a WSDL service with a JAX-WS Provider
-        implementation.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-                   type="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="1"/>
-      <xsd:element name="display-name"
-                   type="javaee:display-nameType"
-                   minOccurs="0"
-                   maxOccurs="1"/>
-      <xsd:element name="icon"
-                   type="javaee:iconType"
-                   minOccurs="0"
-                   maxOccurs="1"/>
-      <xsd:element name="port-component-name"
-                   type="javaee:string">
-        <xsd:annotation>
-          <xsd:documentation>
-<![CDATA[[
-            The port-component-name element specifies a port component's
-            name.  This name is assigned by the module producer to name
-            the service implementation bean in the module's deployment
-            descriptor. The name must be unique among the port component
-            names defined in the same module.
-            
-            Used in: port-component
-            
-            Example:
-            	      <port-component-name>EmployeeService
-            	      </port-component-name>
-            
-]]>
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="wsdl-service"
-                   type="javaee:xsdQNameType"
-                   minOccurs="0"
-                   maxOccurs="1">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Defines the name space and local name part of the WSDL
-            service QName. This is required to be specified for
-            port components that are JAX-WS Provider implementations.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="wsdl-port"
-                   type="javaee:xsdQNameType"
-                   minOccurs="0"
-                   maxOccurs="1">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Defines the name space and local name part of the WSDL
-            port QName. This is not required to be specified for port
-            components that are JAX-WS Provider implementations
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="enable-mtom"
-                   type="javaee:true-falseType"
-                   minOccurs="0"
-                   maxOccurs="1">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Used to enable or disable SOAP MTOM/XOP mechanism for an
-            endpoint implementation.
-            
-            Not to be specified for JAX-RPC runtime
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="mtom-threshold"
-                   type="javaee:xsdNonNegativeIntegerType"
-                   minOccurs="0"
-                   maxOccurs="1">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            When MTOM is enabled, binary data above this size in bytes
-            will be XOP encoded or sent as attachment. Default value is 0.
-            
-            Not to be specified for JAX-RPC runtime
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="addressing"
-                   type="javaee:addressingType"
-                   minOccurs="0"
-                   maxOccurs="1">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            This specifies the WS-Addressing requirements for a JAX-WS
-            web service. It corresponds to javax.xml.ws.soap.Addressing
-            annotation or its feature javax.xml.ws.soap.AddressingFeature.
-            
-            See the addressingType for more information.
-            
-            Not to be specified for JAX-RPC runtime
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="respect-binding"
-                   type="javaee:respect-bindingType"
-                   minOccurs="0"
-                   maxOccurs="1">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Corresponds to the javax.xml.ws.RespectBinding annotation
-            or its corresponding javax.xml.ws.RespectBindingFeature web
-            service feature. This is used to control whether a JAX-WS
-            implementation must respect/honor the contents of the
-            wsdl:binding in the WSDL that is associated with the service.
-            
-            Not to be specified for JAX-RPC runtime
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="protocol-binding"
-                   type="javaee:protocol-bindingType"
-                   minOccurs="0"
-                   maxOccurs="1">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Used to specify the protocol binding used by the port-component.
-            If this element is not specified, then the default binding is
-            used (SOAP 1.1 over HTTP)
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="service-endpoint-interface"
-                   type="javaee:fully-qualified-classType"
-                   minOccurs="0"
-                   maxOccurs="1">
-        <xsd:annotation>
-          <xsd:documentation>
-<![CDATA[[
-            The service-endpoint-interface element contains the
-            fully-qualified name of the port component's Service Endpoint
-            Interface.
-            
-            Used in: port-component
-            
-            Example:
-            	      <remote>com.wombat.empl.EmployeeService</remote>
-            
-            This may not be specified in case there is no Service
-            Enpoint Interface as is the case with directly using an
-            implementation class with the @WebService annotation.
-            
-            When the port component is a Provider implementation
-            this is not specified.
-            
-]]>
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="service-impl-bean"
-                   type="javaee:service-impl-beanType"/>
-      <xsd:choice>
-        <xsd:element name="handler"
-                     type="javaee:handlerType"
-                     minOccurs="0"
-                     maxOccurs="unbounded">
-          <xsd:annotation>
-            <xsd:documentation>
-
-              	 To be used with JAX-RPC based runtime only.
-              
-            </xsd:documentation>
-          </xsd:annotation>
-        </xsd:element>
-        <xsd:element name="handler-chains"
-                     type="javaee:handler-chainsType"
-                     minOccurs="0"
-                     maxOccurs="1">
-          <xsd:annotation>
-            <xsd:documentation>
-
-              	 To be used with JAX-WS based runtime only.
-              
-            </xsd:documentation>
-          </xsd:annotation>
-        </xsd:element>
-      </xsd:choice>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="service-impl-beanType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The service-impl-bean element defines the web service implementation.
-        A service implementation can be an EJB bean class or JAX-RPC web
-        component.  Existing EJB implementations are exposed as a web service
-        using an ejb-link.
-        
-        Used in: port-component
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:choice>
-      <xsd:element name="ejb-link"
-                   type="javaee:ejb-linkType"/>
-      <xsd:element name="servlet-link"
-                   type="javaee:servlet-linkType"/>
-    </xsd:choice>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="servlet-linkType">
-    <xsd:annotation>
-      <xsd:documentation>
-<![CDATA[[
-        The servlet-link element is used in the service-impl-bean element
-        to specify that a Service Implementation Bean is defined as a
-        JAX-RPC Service Endpoint.
-        
-        The value of the servlet-link element must be the servlet-name of
-        a JAX-RPC Service Endpoint in the same WAR file.
-        
-        Used in: service-impl-bean
-        
-        Example:
-        	  <servlet-link>StockQuoteService</servlet-link>
-        
-]]>
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string"/>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="webservice-descriptionType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The webservice-description element defines a WSDL document file
-        and the set of Port components associated with the WSDL ports
-        defined in the WSDL document.  There may be multiple
-        webservice-descriptions defined within a module.
-        
-        All WSDL file ports must have a corresponding port-component element
-        defined.
-        
-        Used in: webservices
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="description"
-                   type="javaee:descriptionType"
-                   minOccurs="0"
-                   maxOccurs="1"/>
-      <xsd:element name="display-name"
-                   type="javaee:display-nameType"
-                   minOccurs="0"
-                   maxOccurs="1"/>
-      <xsd:element name="icon"
-                   type="javaee:iconType"
-                   minOccurs="0"
-                   maxOccurs="1"/>
-      <xsd:element name="webservice-description-name"
-                   type="javaee:string">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The webservice-description-name identifies the collection of
-            port-components associated with a WSDL file and JAX-RPC
-            mapping. The name must be unique within the deployment descriptor.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="wsdl-file"
-                   type="javaee:pathType"
-                   minOccurs="0"
-                   maxOccurs="1">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The wsdl-file element contains the name of a WSDL file in the
-            module.  The file name is a relative path within the module.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="jaxrpc-mapping-file"
-                   type="javaee:pathType"
-                   minOccurs="0"
-                   maxOccurs="1">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The jaxrpc-mapping-file element contains the name of a file that
-            describes the JAX-RPC mapping between the Java interaces used by
-            the application and the WSDL description in the wsdl-file.  The
-            file name is a relative path within the module.
-            
-            This is not required when JAX-WS based runtime is used.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="port-component"
-                   type="javaee:port-componentType"
-                   minOccurs="1"
-                   maxOccurs="unbounded">
-        <xsd:key name="port-component_handler-name-key">
-          <xsd:annotation>
-            <xsd:documentation>
-
-              Defines the name of the handler. The name must be unique
-              within the module.
-              
-            </xsd:documentation>
-          </xsd:annotation>
-          <xsd:selector xpath="javaee:handler"/>
-          <xsd:field xpath="javaee:handler-name"/>
-        </xsd:key>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="webservicesType">
-    <xsd:sequence>
-      <xsd:group ref="javaee:descriptionGroup"/>
-      <xsd:element name="webservice-description"
-                   type="javaee:webservice-descriptionType"
-                   minOccurs="1"
-                   maxOccurs="unbounded">
-        <xsd:key name="port-component-name-key">
-          <xsd:annotation>
-            <xsd:documentation>
-<![CDATA[[
-              	The port-component-name element specifies a port
-              	component's name.  This name is assigned by the module
-              	producer to name the service implementation bean in the
-              	module's deployment descriptor. The name must be unique
-              	among the port component names defined in the same module.
-              
-              	Used in: port-component
-              
-              	Example:
-              		<port-component-name>EmployeeService
-              		</port-component-name>
-              
-              	
-              
-]]>
-            </xsd:documentation>
-          </xsd:annotation>
-          <xsd:selector xpath="javaee:port-component"/>
-          <xsd:field xpath="javaee:port-component-name"/>
-        </xsd:key>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="version"
-                   type="javaee:dewey-versionType"
-                   fixed="1.3"
-                   use="required">
-      <xsd:annotation>
-        <xsd:documentation>
-
-          The required value for the version is 1.3.
-          
-        </xsd:documentation>
-      </xsd:annotation>
-    </xsd:attribute>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-</xsd:schema>

jboss-as-7.2.0.Final/docs/schema/javaee_web_services_client_1_2.xsd

@@ -1,578 +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/javaee"
-	    xmlns:javaee="http://java.sun.com/xml/ns/javaee"
-	    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
-	    elementFormDefault="qualified"
-	    attributeFormDefault="unqualified"
-	    version="1.2">
-  <xsd:annotation>
-    <xsd:documentation>
-      @(#)javaee_web_services_client_1_2.xsds	1.19 02/13/06
-    </xsd:documentation>
-  </xsd:annotation>
-
-  <xsd:annotation>
-    <xsd:documentation>
-
-      Copyright 2003-2006 Sun Microsystems, Inc.
-      4150 Network Circle
-      Santa Clara, California 95054
-      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>
-
-      (C) Copyright International Business Machines Corporation 2002
-
-    </xsd:documentation>
-  </xsd:annotation>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="port-component-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The port-component-ref element declares a client dependency
-	on the container for resolving a Service Endpoint Interface
-	to a WSDL port. It optionally associates the Service Endpoint
-	Interface with a particular port-component. This is only used
-	by the container for a Service.getPort(Class) method call.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="service-endpoint-interface"
-		   type="javaee:fully-qualified-classType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The service-endpoint-interface element defines a fully qualified
-	    Java class that represents the Service Endpoint Interface of a
-	    WSDL port.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="enable-mtom"
-                   type="javaee:true-falseType"
-		   minOccurs="0" maxOccurs="1">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Used to enable or disable SOAP MTOM/XOP mechanism on the client
-	    side for a port-component.
-
-	    Not to be specified for JAX-RPC runtime
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="port-component-link"
-		   type="javaee:string"
-		   minOccurs="0" maxOccurs="1">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The port-component-link element links a port-component-ref
-	    to a specific port-component required to be made available
-	    by a service reference.
-
-	    The value of a port-component-link must be the
-	    port-component-name of a port-component in the same module
-	    or another module in the same application unit. The syntax
-	    for specification follows the syntax defined for ejb-link
-	    in the EJB 2.0 specification.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:group name="service-refGroup">
-    <xsd:sequence>
-      <xsd:element name="service-ref"
-		   type="javaee:service-refType"
-		   minOccurs="0" maxOccurs="unbounded">
-	<xsd:key name="service-ref_handler-name-key">
-	  <xsd:annotation>
-	    <xsd:documentation>
-
-	      Defines the name of the handler. The name must be unique
-	      within the module.
-
-	    </xsd:documentation>
-	  </xsd:annotation>
-	  <xsd:selector xpath="javaee:handler"/>
-	  <xsd:field xpath="javaee:handler-name"/>
-	</xsd:key>
-      </xsd:element>
-    </xsd:sequence>
-  </xsd:group>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="service-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	The service-ref element declares a reference to a Web
-	service. It contains optional description, display name and
-	icons, a declaration of the required Service interface,
-	an optional WSDL document location, an optional set
-	of JAX-RPC mappings, an optional QName for the service element,
-	an optional set of Service Endpoint Interfaces to be resolved
-	by the container to a WSDL port, and an optional set of handlers.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:group ref="javaee:descriptionGroup"/>
-      <xsd:element name="service-ref-name"
-		   type="javaee:jndi-nameType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The service-ref-name element declares logical name that the
-	    components in the module use to look up the Web service. It
-	    is recommended that all service reference names start with
-	    "service/".
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="service-interface"
-		   type="javaee:fully-qualified-classType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The service-interface element declares the fully qualified class
-	    name of the JAX-RPC Service interface the client depends on.
-	    In most cases the value will be javax.xml.rpc.Service.  A JAX-RPC
-	    generated Service Interface class may also be specified.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="service-ref-type"
-		   type="javaee:fully-qualified-classType"
-		   minOccurs="0" maxOccurs="1">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The service-ref-type element declares the type of the service-ref
-	    element that is injected or returned when a JNDI lookup is done.
-	    This must be either a fully qualified name of Service class or
-	    the fully qualified name of service endpoint interface class.
-	    This is only used with JAX-WS runtime where the corresponding
-	    @WebServiceRef annotation can be used to denote both a Service
-	    or a Port.
-
-	    If this is not specified, then the type of service-ref element
-	    that is injected or returned when a JNDI lookup is done is
-	    always a Service interface/class.
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="wsdl-file"
-		   type="javaee:xsdAnyURIType"
-		   minOccurs="0" maxOccurs="1">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The wsdl-file element contains the URI location of a WSDL
-	    file. The location is relative to the root of the module.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="jaxrpc-mapping-file"
-		   type="javaee:pathType"
-		   minOccurs="0" maxOccurs="1">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The jaxrpc-mapping-file element contains the name of a file that
-	    describes the JAX-RPC mapping between the Java interaces used by
-	    the application and the WSDL description in the wsdl-file.  The
-	    file name is a relative path within the module file.
-
-	    This is not required when JAX-WS based runtime is used.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="service-qname"
-		   type="javaee:xsdQNameType"
-		   minOccurs="0" maxOccurs="1">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The service-qname element declares the specific WSDL service
-	    element that is being refered to.  It is not specified if no
-	    wsdl-file is declared.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="port-component-ref"
-		   type="javaee:port-component-refType"
-		   minOccurs="0" maxOccurs="unbounded">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The port-component-ref element declares a client dependency
-	    on the container for resolving a Service Endpoint Interface
-	    to a WSDL port. It optionally associates the Service Endpoint
-	    Interface with a particular port-component. This is only used
-	    by the container for a Service.getPort(Class) method call.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:choice>
-	  <xsd:element name="handler"
-		       type="javaee:service-ref_handlerType"
-		       minOccurs="0" maxOccurs="unbounded">
-	    <xsd:annotation>
-	      <xsd:documentation>
-
-		Declares the handler for a port-component. Handlers can
-		access the init-param name/value pairs using the
-		HandlerInfo interface. If port-name is not specified, the
-		handler is assumed to be associated with all ports of the
-		service.
-
-		To be used with JAX-RPC based runtime only.
-
-	      </xsd:documentation>
-	    </xsd:annotation>
-	  </xsd:element>
-	  <xsd:element name="handler-chains"
-		       type="javaee:service-ref_handler-chainsType"
-		       minOccurs="0" maxOccurs="1">
-	    <xsd:annotation>
-	      <xsd:documentation>
-		 To be used with JAX-WS based runtime only.
-	      </xsd:documentation>
-	    </xsd:annotation>
-	  </xsd:element>
-      </xsd:choice>
-
-      <xsd:group ref="javaee:resourceGroup"/>
-
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="service-ref_handler-chainType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-      The handler-chain element defines the handlerchain.
-      Handlerchain can be defined such that the handlers in the
-      handlerchain operate,all ports of a service, on a specific
-      port or on a list of protocol-bindings. The choice of elements
-      service-name-pattern, port-name-pattern and protocol-bindings
-      are used to specify whether the handlers in handler-chain are
-      for a service, port or protocol binding. If none of these
-      choices are specified with the handler-chain element then the
-      handlers specified in the handler-chain will be applied on
-      everything.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-
-      <xsd:choice minOccurs="0" maxOccurs="1">
-         <xsd:element name="service-name-pattern"
-		      type="javaee:service-ref_qname-pattern" />
-         <xsd:element name="port-name-pattern"
-	              type="javaee:service-ref_qname-pattern" />
-         <xsd:element name="protocol-bindings"
-	              type="javaee:service-ref_protocol-bindingListType"/>
-      </xsd:choice>
-
-      <xsd:element name="handler"
-                   type="javaee:service-ref_handlerType"
-		   minOccurs="1" maxOccurs="unbounded"/>
-    </xsd:sequence>
-
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="service-ref_handler-chainsType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-      The handler-chains element defines the handlerchains associated with this
-      service or service endpoint.
-
-      </xsd:documentation>
-    </xsd:annotation>
-
-    <xsd:sequence>
-      <xsd:element name="handler-chain"
-                   type="javaee:service-ref_handler-chainType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-    </xsd:sequence>
-
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="service-ref_handlerType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-	Declares the handler for a port-component. Handlers can access the
-	init-param name/value pairs using the HandlerInfo interface. If
-	port-name is not specified, the handler is assumed to be associated
-	with all ports of the service.
-
-	Used in: service-ref
-
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:group ref="javaee:descriptionGroup"/>
-      <xsd:element name="handler-name"
-		   type="javaee:string">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    Defines the name of the handler. The name must be unique
-	    within the module.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="handler-class"
-		   type="javaee:fully-qualified-classType">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    Defines a fully qualified class name for the handler
-	    implementation.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-      <xsd:element name="init-param"
-		   type="javaee:param-valueType"
-		   minOccurs="0" maxOccurs="unbounded"/>
-
-      <xsd:element name="soap-header"
-		   type="javaee:xsdQNameType"
-		   minOccurs="0" maxOccurs="unbounded">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    Defines the QName of a SOAP header that will be processed
-	    by the handler.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="soap-role"
-		   type="javaee:string"
-		   minOccurs="0" maxOccurs="unbounded">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The soap-role element contains a SOAP actor definition that
-	    the Handler will play as a role.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-
-      <xsd:element name="port-name"
-		   type="javaee:string"
-		   minOccurs="0" maxOccurs="unbounded">
-	<xsd:annotation>
-	  <xsd:documentation>
-
-	    The port-name element defines the WSDL port-name that a
-	    handler should be associated with.
-
-	  </xsd:documentation>
-	</xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id" type="xsd:ID"/>
-  </xsd:complexType>
-
-<!-- **************************************************** -->
-
-  <xsd:simpleType name="service-ref_protocol-URIAliasType">
-     <xsd:annotation>
-        <xsd:documentation>
-	   Defines the type that is used for specifying tokens that
-	   start with ## which are used to alias existing standard
-	   protocol bindings and support aliases for new standard
-	   binding URIs that are introduced in future specifications.
-
-	   The following tokens alias the standard protocol binding
-	   URIs:
-
-	   ##SOAP11_HTTP = "http://schemas.xmlsoap.org/wsdl/soap/http"
-	   ##SOAP11_HTTP_MTOM =
-                 "http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true"
-           ##SOAP12_HTTP = "http://www.w3.org/2003/05/soap/bindings/HTTP/"
-           ##SOAP12_HTTP_MTOM =
-                 "http://www.w3.org/2003/05/soap/bindings/HTTP/?mtom=true"
-           ##XML_HTTP = "http://www.w3.org/2004/08/wsdl/http"
-
-        </xsd:documentation>
-     </xsd:annotation>
-     <xsd:restriction base="xsd:token">
-        <xsd:pattern value="##.+"/>
-     </xsd:restriction>
-  </xsd:simpleType>
-
-<!-- **************************************************** -->
-
-  <xsd:simpleType name="service-ref_protocol-bindingListType">
-     <xsd:annotation>
-        <xsd:documentation>
-	   Defines the type used for specifying a list of
-	   protocol-bindingType(s). For e.g.
-
-	    ##SOAP11_HTTP ##SOAP12_HTTP ##XML_HTTP
-
-        </xsd:documentation>
-     </xsd:annotation>
-     <xsd:list itemType="javaee:service-ref_protocol-bindingType"/>
-  </xsd:simpleType>
-
-<!-- **************************************************** -->
-
-  <xsd:simpleType name="service-ref_protocol-bindingType">
-     <xsd:annotation>
-        <xsd:documentation>
-	   Defines the type used for specifying the URI for the
-	   protocol binding used by the port-component.  For
-	   portability one could use one of the following tokens that
-	   alias the standard binding types:
-
-	    ##SOAP11_HTTP
-	    ##SOAP11_HTTP_MTOM
-            ##SOAP12_HTTP
-            ##SOAP12_HTTP_MTOM
-            ##XML_HTTP
-
-	   Other specifications could define tokens that start with ##
-	   to alias new standard binding URIs that are introduced.
-
-        </xsd:documentation>
-     </xsd:annotation>
-     <xsd:union memberTypes="xsd:anyURI javaee:service-ref_protocol-URIAliasType"/>
-  </xsd:simpleType>
-
-<!-- **************************************************** -->
-
-  <xsd:simpleType name="service-ref_qname-pattern">
-     <xsd:annotation>
-        <xsd:documentation>
-	     This is used to specify the QName pattern in the
-	     attribute service-name-pattern and port-name-pattern in
-	     the handler-chain element
-
-	     For example, the various forms acceptable here for
-	     service-name-pattern attribute in handler-chain element
-	     are :
-
-	     Exact Name: service-name-pattern="ns1:EchoService"
-
-		 In this case, handlers specified in this
-		 handler-chain element will apply to all ports with
-		 this exact service name. The namespace prefix must
-		 have been declared in a namespace declaration
-		 attribute in either the start-tag of the element
-		 where the prefix is used or in an an ancestor
-		 element (i.e. an element in whose content the
-		 prefixed markup occurs)
-
-	     Pattern : service-name-pattern="ns1:EchoService*"
-
-		 In this case, handlers specified in this
-		 handler-chain element will apply to all ports whose
-		 Service names are like EchoService1, EchoServiceFoo
-		 etc. The namespace prefix must have been declared in
-		 a namespace declaration attribute in either the
-		 start-tag of the element where the prefix is used or
-		 in an an ancestor element (i.e. an element in whose
-		 content the prefixed markup occurs)
-
-	     Wild Card : service-name-pattern="*"
-
-		In this case, handlers specified in this handler-chain
-		element will apply to ports of all service names.
-
-	    The same can be applied to port-name attribute in
-	    handler-chain element.
-
-        </xsd:documentation>
-     </xsd:annotation>
-
-     <xsd:restriction base="xsd:token">
-        <xsd:pattern value="\*|([\i-[:]][\c-[:]]*:)?[\i-[:]][\c-[:]]*\*?"/>
-     </xsd:restriction>
-
-  </xsd:simpleType>
-
-</xsd:schema>
-

jboss-as-7.2.0.Final/docs/schema/javaee_web_services_client_1_3.xsd

@@ -1,745 +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/javaee"
-            xmlns:javaee="http://java.sun.com/xml/ns/javaee"
-            xmlns:xsd="http://www.w3.org/2001/XMLSchema"
-            elementFormDefault="qualified"
-            attributeFormDefault="unqualified"
-            version="1.3">
-  <xsd:annotation>
-    <xsd:documentation>
-
-      $Id$
-      
-    </xsd:documentation>
-  </xsd:annotation>
-
-  <xsd:annotation>
-    <xsd:documentation>
-
-      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
-      
-      Copyright 2003-2009 Sun Microsystems, Inc. All rights reserved.
-      
-      The contents of this file are subject to the terms of either the
-      GNU General Public License Version 2 only ("GPL") or the Common
-      Development and Distribution License("CDDL") (collectively, the
-      "License").  You may not use this file except in compliance with
-      the License. You can obtain a copy of the License at
-      https://glassfish.dev.java.net/public/CDDL+GPL.html or
-      glassfish/bootstrap/legal/LICENSE.txt.  See the License for the
-      specific language governing permissions and limitations under the
-      License.
-      
-      When distributing the software, include this License Header
-      Notice in each file and include the License file at
-      glassfish/bootstrap/legal/LICENSE.txt.  Sun designates this
-      particular file as subject to the "Classpath" exception as
-      provided by Sun in the GPL Version 2 section of the License file
-      that accompanied this code.  If applicable, add the following
-      below the License Header, with the fields enclosed by brackets []
-      replaced by your own identifying information:
-      "Portions Copyrighted [year] [name of copyright owner]"
-      
-      Contributor(s):
-      
-      If you wish your version of this file to be governed by only the
-      CDDL or only the GPL Version 2, indicate your decision by adding
-      "[Contributor] elects to include this software in this
-      distribution under the [CDDL or GPL Version 2] license."  If you
-      don't indicate a single choice of license, a recipient has the
-      option to distribute your version of this file under either the
-      CDDL, the GPL Version 2 or to extend the choice of license to its
-      licensees as provided above.  However, if you add GPL Version 2
-      code and therefore, elected the GPL Version 2 license, then the
-      option applies only if the new code is made subject to such
-      option by the copyright holder.
-      
-    </xsd:documentation>
-  </xsd:annotation>
-
-  <xsd:annotation>
-    <xsd:documentation>
-
-      (C) Copyright International Business Machines Corporation 2002
-      
-    </xsd:documentation>
-  </xsd:annotation>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="service-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The service-ref element declares a reference to a Web
-        service. It contains optional description, display name and
-        icons, a declaration of the required Service interface,
-        an optional WSDL document location, an optional set
-        of JAX-RPC mappings, an optional QName for the service element,
-        an optional set of Service Endpoint Interfaces to be resolved 
-        by the container to a WSDL port, and an optional set of handlers.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:group ref="javaee:descriptionGroup"/>
-      <xsd:element name="service-ref-name"
-                   type="javaee:jndi-nameType">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The service-ref-name element declares logical name that the
-            components in the module use to look up the Web service. It 
-            is recommended that all service reference names start with 
-            "service/".
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="service-interface"
-                   type="javaee:fully-qualified-classType">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The service-interface element declares the fully qualified class
-            name of the JAX-RPC Service interface the client depends on. 
-            In most cases the value will be javax.xml.rpc.Service.  A JAX-RPC
-            generated Service Interface class may also be specified.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="service-ref-type"
-                   type="javaee:fully-qualified-classType"
-                   minOccurs="0"
-                   maxOccurs="1">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The service-ref-type element declares the type of the service-ref 
-            element that is injected or returned when a JNDI lookup is done.
-            This must be either a fully qualified name of Service class or 
-            the fully qualified name of service endpoint interface class. 
-            This is only used with JAX-WS runtime where the corresponding 
-            @WebServiceRef annotation can be used to denote both a Service
-            or a Port.
-            
-            If this is not specified, then the type of service-ref element 
-            that is injected or returned when a JNDI lookup is done is 
-            always a Service interface/class.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="wsdl-file"
-                   type="javaee:xsdAnyURIType"
-                   minOccurs="0"
-                   maxOccurs="1">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The wsdl-file element contains the URI location of a WSDL
-            file. The location is relative to the root of the module.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="jaxrpc-mapping-file"
-                   type="javaee:pathType"
-                   minOccurs="0"
-                   maxOccurs="1">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The jaxrpc-mapping-file element contains the name of a file that
-            describes the JAX-RPC mapping between the Java interaces used by
-            the application and the WSDL description in the wsdl-file.  The 
-            file name is a relative path within the module file.
-            
-            This is not required when JAX-WS based runtime is used.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="service-qname"
-                   type="javaee:xsdQNameType"
-                   minOccurs="0"
-                   maxOccurs="1">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The service-qname element declares the specific WSDL service
-            element that is being refered to.  It is not specified if no
-            wsdl-file is declared.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="port-component-ref"
-                   type="javaee:port-component-refType"
-                   minOccurs="0"
-                   maxOccurs="unbounded">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The port-component-ref element declares a client dependency
-            on the container for resolving a Service Endpoint Interface
-            to a WSDL port. It optionally associates the Service Endpoint
-            Interface with a particular port-component. This is only used
-            by the container for a Service.getPort(Class) method call.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:choice>
-        <xsd:element name="handler"
-                     type="javaee:handlerType"
-                     minOccurs="0"
-                     maxOccurs="unbounded">
-          <xsd:annotation>
-            <xsd:documentation>
-
-              	Declares the handler for a port-component. Handlers can
-              	access the init-param name/value pairs using the
-              	HandlerInfo interface. If port-name is not specified, the
-              	handler is assumed to be associated with all ports of the
-              	service.
-              
-              	To be used with JAX-RPC based runtime only.
-              
-            </xsd:documentation>
-          </xsd:annotation>
-        </xsd:element>
-        <xsd:element name="handler-chains"
-                     type="javaee:handler-chainsType"
-                     minOccurs="0"
-                     maxOccurs="1">
-          <xsd:annotation>
-            <xsd:documentation>
-
-              	 To be used with JAX-WS based runtime only.
-              
-            </xsd:documentation>
-          </xsd:annotation>
-        </xsd:element>
-      </xsd:choice>
-      <xsd:group ref="javaee:resourceGroup"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="port-component-refType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The port-component-ref element declares a client dependency
-        on the container for resolving a Service Endpoint Interface
-        to a WSDL port. It optionally associates the Service Endpoint
-        Interface with a particular port-component. This is only used
-        by the container for a Service.getPort(Class) method call.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="service-endpoint-interface"
-                   type="javaee:fully-qualified-classType">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The service-endpoint-interface element defines a fully qualified
-            Java class that represents the Service Endpoint Interface of a
-            WSDL port.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="enable-mtom"
-                   type="javaee:true-falseType"
-                   minOccurs="0"
-                   maxOccurs="1">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Used to enable or disable SOAP MTOM/XOP mechanism on the client
-            side for a port-component. 
-            
-            Not to be specified for JAX-RPC runtime
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="mtom-threshold"
-                   type="javaee:xsdNonNegativeIntegerType"
-                   minOccurs="0"
-                   maxOccurs="1">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            When MTOM is enabled, binary data above this size in bytes
-            should be XOP encoded or sent as attachment. Default value is 0.
-            
-            Not to be specified for JAX-RPC runtime
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="addressing"
-                   type="javaee:addressingType"
-                   minOccurs="0"
-                   maxOccurs="1">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            This specifies the WS-Addressing requirements for a JAX-WS
-            web service. It corresponds to javax.xml.ws.soap.Addressing
-            annotation or its feature javax.xml.ws.soap.AddressingFeature.
-            
-            See the addressingType for more information.
-            
-            Not to be specified for JAX-RPC runtime
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="respect-binding"
-                   type="javaee:respect-bindingType"
-                   minOccurs="0"
-                   maxOccurs="1">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Corresponds to the javax.xml.ws.RespectBinding annotation
-            or its corresponding javax.xml.ws.RespectBindingFeature web
-            service feature. This is used to control whether a JAX-WS
-            implementation must respect/honor the contents of the
-            wsdl:binding in the WSDL that is associated with the service.
-            
-            Not to be specified for JAX-RPC runtime
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="port-component-link"
-                   type="javaee:string"
-                   minOccurs="0"
-                   maxOccurs="1">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The port-component-link element links a port-component-ref
-            to a specific port-component required to be made available
-            by a service reference.
-            
-            The value of a port-component-link must be the
-            port-component-name of a port-component in the same module
-            or another module in the same application unit. The syntax
-            for specification follows the syntax defined for ejb-link
-            in the EJB 2.0 specification.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="handler-chainsType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The handler-chains element defines the handlerchains associated with this
-        service or service endpoint.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="handler-chain"
-                   type="javaee:handler-chainType"
-                   minOccurs="0"
-                   maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="handler-chainType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        The handler-chain element defines the handlerchain. 
-        Handlerchain can be defined such that the handlers in the
-        handlerchain operate,all ports of a service, on a specific
-        port or on a list of protocol-bindings. The choice of elements
-        service-name-pattern, port-name-pattern and protocol-bindings
-        are used to specify whether the handlers in handler-chain are
-        for a service, port or protocol binding. If none of these 
-        choices are specified with the handler-chain element then the
-        handlers specified in the handler-chain will be applied on 
-        everything.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:choice minOccurs="0"
-                  maxOccurs="1">
-        <xsd:element name="service-name-pattern"
-                     type="javaee:qname-pattern"/>
-        <xsd:element name="port-name-pattern"
-                     type="javaee:qname-pattern"/>
-        <xsd:element name="protocol-bindings"
-                     type="javaee:protocol-bindingListType"/>
-      </xsd:choice>
-      <xsd:element name="handler"
-                   type="javaee:handlerType"
-                   minOccurs="1"
-                   maxOccurs="unbounded"/>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-  <xsd:simpleType name="protocol-bindingListType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        Defines the type used for specifying a list of
-        protocol-bindingType(s). For e.g.
-        
-        ##SOAP11_HTTP ##SOAP12_HTTP ##XML_HTTP
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:list itemType="javaee:protocol-bindingType"/>
-  </xsd:simpleType>
-
-  <xsd:simpleType name="protocol-bindingType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        Defines the type used for specifying the URI for the
-        protocol binding used by the port-component.  For
-        portability one could use one of the following tokens that
-        alias the standard binding types: 
-        
-        ##SOAP11_HTTP
-        ##SOAP11_HTTP_MTOM
-        ##SOAP12_HTTP
-        ##SOAP12_HTTP_MTOM
-        ##XML_HTTP
-        
-        Other specifications could define tokens that start with ##
-        to alias new standard binding URIs that are introduced.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:union memberTypes="xsd:anyURI javaee:protocol-URIAliasType"/>
-  </xsd:simpleType>
-
-  <xsd:simpleType name="protocol-URIAliasType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        Defines the type that is used for specifying tokens that
-        start with ## which are used to alias existing standard
-        protocol bindings and support aliases for new standard
-        binding URIs that are introduced in future specifications.
-        
-        The following tokens alias the standard protocol binding
-        URIs:
-        
-        ##SOAP11_HTTP = "http://schemas.xmlsoap.org/wsdl/soap/http"
-        ##SOAP11_HTTP_MTOM = 
-        "http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true"
-        ##SOAP12_HTTP = "http://www.w3.org/2003/05/soap/bindings/HTTP/"
-        ##SOAP12_HTTP_MTOM = 
-        "http://www.w3.org/2003/05/soap/bindings/HTTP/?mtom=true"
-        ##XML_HTTP = "http://www.w3.org/2004/08/wsdl/http"
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:restriction base="xsd:token">
-      <xsd:pattern value="##.+"/>
-    </xsd:restriction>
-  </xsd:simpleType>
-
-  <xsd:simpleType name="qname-pattern">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        This is used to specify the QName pattern in the
-        attribute service-name-pattern and port-name-pattern in
-        the handler-chain element
-        
-        For example, the various forms acceptable here for
-        service-name-pattern attribute in handler-chain element
-        are :
-        
-        Exact Name: service-name-pattern="ns1:EchoService"
-        
-        	 In this case, handlers specified in this
-        	 handler-chain element will apply to all ports with
-        	 this exact service name. The namespace prefix must
-        	 have been declared in a namespace declaration
-        	 attribute in either the start-tag of the element
-        	 where the prefix is used or in an an ancestor 
-        	 element (i.e. an element in whose content the 
-        	 prefixed markup occurs)
-        	 
-        
-        Pattern : service-name-pattern="ns1:EchoService*"
-        
-        	 In this case, handlers specified in this
-        	 handler-chain element will apply to all ports whose
-        	 Service names are like EchoService1, EchoServiceFoo
-        	 etc. The namespace prefix must have been declared in
-        	 a namespace declaration attribute in either the
-        	 start-tag of the element where the prefix is used or
-        	 in an an ancestor element (i.e. an element in whose 
-        	 content the prefixed markup occurs)
-        
-        Wild Card : service-name-pattern="*"
-        
-        	In this case, handlers specified in this handler-chain
-        	element will apply to ports of all service names.
-        
-        The same can be applied to port-name attribute in
-        handler-chain element.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:restriction base="xsd:token">
-      <xsd:pattern value="\*|([\i-[:]][\c-[:]]*:)?[\i-[:]][\c-[:]]*\*?"/>
-    </xsd:restriction>
-  </xsd:simpleType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="addressingType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        This specifies the WS-Addressing requirements for a JAX-WS web service.
-        It corresponds to javax.xml.ws.soap.Addressing annotation or its
-        feature javax.xml.ws.soap.AddressingFeature.
-        
-        If the "enabled" element is "true", WS-Addressing is enabled.
-        It means that the endpoint supports WS-Addressing but does not require
-        its use. The default value for "enabled" is "true".
-        
-        If the WS-Addressing is enabled and the "required" element is "true",
-        it means that the endpoint requires WS-Addressing. The default value
-        for "required" is "false".
-        
-        If WS-Addressing is enabled, the "responses" element determines
-        if an endpoint requires the use of only anonymous responses,
-        or only non-anonymous responses, or all. The value of the "responses"
-        element must be one of the following:
-        
-        ANONYMOUS
-        NON_ANONYMOUS
-        ALL
-        
-        The default value for the "responses" is ALL.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="enabled"
-                   type="javaee:true-falseType"
-                   minOccurs="0"
-                   maxOccurs="1"/>
-      <xsd:element name="required"
-                   type="javaee:true-falseType"
-                   minOccurs="0"
-                   maxOccurs="1"/>
-      <xsd:element name="responses"
-                   type="javaee:addressing-responsesType"
-                   minOccurs="0"
-                   maxOccurs="1"/>
-    </xsd:sequence>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="addressing-responsesType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        If WS-Addressing is enabled, this type determines if an endpoint
-        requires the use of only anonymous responses, or only non-anonymous
-        responses, or all.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:simpleContent>
-      <xsd:restriction base="javaee:string">
-        <xsd:enumeration value="ANONYMOUS"/>
-        <xsd:enumeration value="NON_ANONYMOUS"/>
-        <xsd:enumeration value="ALL"/>
-      </xsd:restriction>
-    </xsd:simpleContent>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="respect-bindingType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        Corresponds to the javax.xml.ws.RespectBinding annotation
-        or its corresponding javax.xml.ws.RespectBindingFeature web
-        service feature. This is used to control whether a JAX-WS
-        implementation must respect/honor the contents of the
-        wsdl:binding in the WSDL that is associated with the service.
-        
-        If the "enabled" element is "true", wsdl:binding in the
-        associated WSDL, if any, must be respected/honored.
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:element name="enabled"
-                   type="javaee:true-falseType"
-                   minOccurs="0"
-                   maxOccurs="1"/>
-    </xsd:sequence>
-  </xsd:complexType>
-
-
-<!-- **************************************************** -->
-
-  <xsd:complexType name="handlerType">
-    <xsd:annotation>
-      <xsd:documentation>
-
-        Declares the handler for a port-component, service-ref. Handlers can
-        access the init-param name/value pairs using the HandlerInfo interface.
-        
-        Used in: port-component, service-ref
-        
-      </xsd:documentation>
-    </xsd:annotation>
-    <xsd:sequence>
-      <xsd:group ref="javaee:descriptionGroup"/>
-      <xsd:element name="handler-name"
-                   type="javaee:string">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Defines the name of the handler. The name must be unique within the
-            module.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="handler-class"
-                   type="javaee:fully-qualified-classType">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Defines a fully qualified class name for the handler implementation.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="init-param"
-                   type="javaee:param-valueType"
-                   minOccurs="0"
-                   maxOccurs="unbounded">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Not to be specified for JAX-WS runtime
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="soap-header"
-                   type="javaee:xsdQNameType"
-                   minOccurs="0"
-                   maxOccurs="unbounded">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            Defines the QName of a SOAP header that will be processed by the
-            handler.
-            
-            Not to be specified for JAX-WS runtime
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="soap-role"
-                   type="javaee:string"
-                   minOccurs="0"
-                   maxOccurs="unbounded">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The soap-role element contains a SOAP actor definition that the
-            Handler will play as a role.
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-      <xsd:element name="port-name"
-                   type="javaee:string"
-                   minOccurs="0"
-                   maxOccurs="unbounded">
-        <xsd:annotation>
-          <xsd:documentation>
-
-            The port-name element defines the WSDL port-name that a
-            handler should be associated with. If port-name is not
-            specified, the handler is assumed to be associated with
-            all ports of the service.
-            
-            Not to be specified for JAX-WS runtime
-            
-          </xsd:documentation>
-        </xsd:annotation>
-      </xsd:element>
-    </xsd:sequence>
-    <xsd:attribute name="id"
-                   type="xsd:ID"/>
-  </xsd:complexType>
-
-  <xsd:group name="service-refGroup">
-    <xsd:sequence>
-      <xsd:element name="service-ref"
-                   type="javaee:service-refType"
-                   minOccurs="0"
-                   maxOccurs="unbounded">
-        <xsd:key name="service-ref_handler-name-key">
-          <xsd:annotation>
-            <xsd:documentation>
-
-              Defines the name of the handler. The name must be unique
-              within the module.
-              
-            </xsd:documentation>
-          </xsd:annotation>
-          <xsd:selector xpath="javaee:handler"/>
-          <xsd:field xpath="javaee:handler-name"/>
-        </xsd:key>
-      </xsd:element>
-    </xsd:sequence>
-  </xsd:group>
-
-</xsd:schema>

jboss-as-7.2.0.Final/docs/schema/jboss-app_3_0.dtd

@@ -1,41 +0,0 @@
-<?xml version='1.0' encoding='UTF-8' ?>
-
-<!-- The JBoss specific elements for ears.
-$Id: jboss-app_3_0.dtd 20476 2004-04-17 13:29:24Z tdiesler $
-
-DOCTYPE jboss-app
-    PUBLIC "-//JBoss//DTD J2EE Application 1.3//EN"
-    "http://www.jboss.org/j2ee/dtd/jboss-app_3_0.dtd"
--->
-
-<!-- The jboss-app element is the root element.
--->
-<!ELEMENT jboss-app (loader-repository?, module*)>
-
-<!-- The loader-repository specifies the name of the UnifiedLoaderRepository
-   MBean to use for the ear to provide ear level scoping of classes deployed
-   in the ear. It is a unique JMX ObjectName string.
-
-   Example:
-   <loader-repository>jboss.test:loader=cts-cmp2v1-sar.ear</loader-repository>
--->
-<!ELEMENT loader-repository (#PCDATA)>
-<!-- The loaderRepositoryClass attribute gives the classname loader-repository
-implementation.
--->
-<!ATTLIST loader-repository loaderRepositoryClass CDATA #IMPLIED>
-
-<!-- The module element is used to specify a jboss specific module archive.
--->
-<!ELEMENT module (service)>
-
-<!-- The service element specifies a service archive (SAR) to deploy.
-
-Example:
-   <module>
-      <service>external.sar</service>
-   </module>
--->
-<!ELEMENT service (#PCDATA)>
-
-

jboss-as-7.2.0.Final/docs/schema/jboss-app_3_2.dtd

@@ -1,76 +0,0 @@
-<?xml version='1.0' encoding='UTF-8' ?>
-
-<!-- The JBoss 3.2.x specific elements for ears.
-$Id: jboss-app_3_2.dtd 22964 2004-08-14 00:35:40Z starksm $
-
-DOCTYPE jboss-app
-    PUBLIC "-//JBoss//DTD J2EE Application 1.3V2//EN"
-    "http://www.jboss.org/j2ee/dtd/jboss-app_3_2.dtd"
--->
-
-<!-- The jboss-app element is the root element.
--->
-<!ELEMENT jboss-app (loader-repository?, jmx-name?, module*)>
-
-<!-- The loader-repository specifies the name of the UnifiedLoaderRepository
-   MBean to use for the ear to provide ear level scoping of classes deployed
-   in the ear. It is a unique JMX ObjectName string. It may also specify
-   an arbitrary configuration by including a loader-repository-config element.
-
-Examples:
-   <loader-repository>jboss.test:loader=cts-cmp2v1-sar.ear</loader-repository>
-
-   <loader-repository loaderRepositoryClass='dot.com.LoaderRepository'>
-      dot.com:loader=unique-archive-name
-      <loader-repository-config configParserClass='dot.com.LoaderParser'>
-         java2ParentDelegaton=true
-      </loader-repository-config>
-   </loader-repository>
--->
-<!ELEMENT loader-repository (#PCDATA | loader-repository-config)*>
-<!-- The loaderRepositoryClass attribute gives the classname of the
-org.jboss.mx.loading.LoaderRepository implementation.
--->
-<!ATTLIST loader-repository loaderRepositoryClass CDATA #IMPLIED>
-
-<!-- The loader-repository-config element specifies any arbitrary configuration
-fragment for use in configuring the loader-repository instance. The actual
-content of this element is specific to the loaderRepositoryClass and the
-code parsing the element.
--->
-<!ELEMENT loader-repository-config (#PCDATA)>
-<!-- The configParserClass attribute gives the classname of the
-org.jboss.mx.loading.LoaderRepositoryFactory.LoaderRepositoryConfigParser
-implementation to use to parse the loader-repository-config content.
--->
-<!ATTLIST loader-repository-config configParserClass CDATA #IMPLIED>
-
-<!-- The jmx-name element allows one to specify the JMX ObjectName to use
-for the MBean associated with the ejb-jar module. This must be a unique
-name and valid JMX ObjectName string.
-
-  Used in: jboss-app
--->
-<!ELEMENT jmx-name (#PCDATA)>
-
-<!-- The module element is used to specify a jboss specific module archive.
--->
-<!ELEMENT module (service | har)>
-
-<!-- The service element specifies a service archive (SAR) to deploy.
-
-Example:
-   <module>
-      <service>external.sar</service>
-   </module>
--->
-<!ELEMENT service (#PCDATA)>
-
-<!-- The har element specifies a Hibernate archive (HAR) to deploy.
-
-Example:
-   <module>
-      <har>myapp.har</har>
-   </module>
--->
-<!ELEMENT har (#PCDATA)>

jboss-as-7.2.0.Final/docs/schema/jboss-app_4_0.dtd

@@ -1,145 +0,0 @@
-<?xml version='1.0' encoding='UTF-8' ?>
-
-<!-- The JBoss 4.x specific elements for ears.
-$Id: jboss-app_4_0.dtd 60563 2007-02-15 11:11:32Z dimitris@jboss.org $
-
-DOCTYPE jboss-app
-    PUBLIC "-//JBoss//DTD J2EE Application 1.4//EN"
-    "http://www.jboss.org/j2ee/dtd/jboss-app_4_0.dtd"
--->
-
-<!-- The jboss-app element is the root element.
--->
-<!ELEMENT jboss-app (module-order?,security-domain?, unauthenticated-principal?,
- loader-repository?, jmx-name?, module*, security-role*)>
-
-<!--
- The value of the module-order could be implicit or strict
- <module-order>strict</module-order>
- 	or 
- <module-order>implicit</module-order>
- The strict value indicates that the deployments of the modules will 
- be done in the order that would be specified in the application.xml 
- and jboss-app.xml file . 
- The implicit value indicates the deployment would follow the order 
- which would be specified in the DeploymentSorter.
- The default order will be implicit to support backward compatibility
---> 
-<!ELEMENT module-order (#PCDATA)>
-
-<!--
-  The security-domain element specifies the JNDI name of the security
-  manager that implements the EJBSecurityManager and RealmMapping for
-  the domain. When specified at the jboss level it specifies the security
-  domain for all j2ee components in the deployment unit.
-  One can override the global security-domain at the container
-  level using the security-domain element at the container-configuration
-  level.
-
-  Used in: jboss-app
--->
-<!ELEMENT security-domain (#PCDATA)>
-
-<!--
-  The unauthenticated-principal element specifies the name of the principal
-  that will be returned by the EJBContext.getCallerPrincipal() method if there
-  is no authenticated user. This Principal has no roles or privaledges to call
-  any other beans.
--->
-<!ELEMENT unauthenticated-principal (#PCDATA)>
-
-<!-- The loader-repository specifies the name of the UnifiedLoaderRepository
-   MBean to use for the ear to provide ear level scoping of classes deployed
-   in the ear. It is a unique JMX ObjectName string. It may also specify
-   an arbitrary configuration by including a loader-repository-config element.
-
-Examples:
-   <loader-repository>jboss.test:loader=cts-cmp2v1-sar.ear</loader-repository>
-
-   <loader-repository loaderRepositoryClass='dot.com.LoaderRepository'>
-      dot.com:loader=unique-archive-name
-      <loader-repository-config configParserClass='dot.com.LoaderParser'>
-         java2ParentDelegaton=true
-      </loader-repository-config>
-   </loader-repository>
--->
-<!ELEMENT loader-repository (#PCDATA | loader-repository-config)*>
-<!-- The loaderRepositoryClass attribute gives the classname of the
-org.jboss.mx.loading.LoaderRepository implementation.
--->
-<!ATTLIST loader-repository loaderRepositoryClass CDATA #IMPLIED>
-
-<!-- The loader-repository-config element specifies any arbitrary configuration
-fragment for use in configuring the loader-repository instance. The actual
-content of this element is specific to the loaderRepositoryClass and the
-code parsing the element.
--->
-<!ELEMENT loader-repository-config (#PCDATA)>
-<!-- The configParserClass attribute gives the classname of the
-org.jboss.mx.loading.LoaderRepositoryFactory.LoaderRepositoryConfigParser
-implementation to use to parse the loader-repository-config content.
--->
-<!ATTLIST loader-repository-config configParserClass CDATA #IMPLIED>
-
-<!-- The jmx-name element allows one to specify the JMX ObjectName to use
-for the MBean associated with the ejb-jar module. This must be a unique
-name and valid JMX ObjectName string.
-
-   Used in: jboss-app
--->
-<!ELEMENT jmx-name (#PCDATA)>
-
-<!-- The module element is used to specify a jboss specific module archive.
--->
-<!ELEMENT module (service | har)>
-<!-- Allow the module to have a unique id -->
-<!ATTLIST module id ID #IMPLIED>
-
-<!-- The service element specifies a service archive (SAR) to deploy.
-
-Example:
-   <module>
-      <service>external.sar</service>
-   </module>
--->
-<!ELEMENT service (#PCDATA)>
-
-<!-- The har element specifies a Hibernate archive (HAR) to deploy.
-
-Example:
-   <module>
-      <har>myapp.har</har>
-   </module>
--->
-<!ELEMENT har (#PCDATA)>
-
-<!--
-  The security-role element contains the definition of a security role.
-  The definition consists of an the security role name and principal name element(s).
-
-Used in: jboss-app
-
-Example:
-		<security-role>
-      <role-name>Manager</role-name>
-      <principal-name>j2ee</principal-name>
-      <principal-name>javajoe</principal-name>
-		</security-role>
--->
-<!ELEMENT security-role (role-name, principal-name+)>
-
-<!--
-  The role-name element is the name of the role.
-
-  Used in: security-role
--->
-<!ELEMENT role-name (#PCDATA)>
-
-<!--
-  The principal-name element is the name of the principal that is mapped
-  to the assembly role-name.
-
-  Used in: security-role
--->
-<!ELEMENT principal-name (#PCDATA)>
-

jboss-as-7.2.0.Final/docs/schema/jboss-app_4_2.dtd

@@ -1,188 +0,0 @@
-<?xml version='1.0' encoding='UTF-8' ?>
-
-<!-- The JBoss 4.2.x specific elements for ears.
-$Id: jboss-app_4_0.dtd 56293 2006-08-26 12:42:15Z vicky.kak@jboss.com $
-
-DOCTYPE jboss-app
-    PUBLIC "-//JBoss//DTD J2EE Application 4.2//EN"
-    "http://www.jboss.org/j2ee/dtd/jboss-app_4_2.dtd"
--->
-
-<!-- The jboss-app element is the root element.
--->
-<!ELEMENT jboss-app (module-order?,security-domain?, unauthenticated-principal?,
- loader-repository?, jmx-name?, library-directory?, module*, security-role*)>
-
-<!--
- The value of the module-order could be implicit or strict
- <module-order>strict</module-order>
- 	or 
- <module-order>implicit</module-order>
- The strict value indicates that the deployments of the modules will 
- be done in the order that would be specified in the application.xml 
- and jboss-app.xml file . 
- The implicit value indicates the deployment would follow the order 
- which would be specified in the DeploymentSorter.
- The default order will be implicit to support backward compatibility
---> 
-<!ELEMENT module-order (#PCDATA)>
-
-<!--
-  The security-domain element specifies the JNDI name of the security
-  manager that implements the EJBSecurityManager and RealmMapping for
-  the domain. When specified at the jboss level it specifies the security
-  domain for all j2ee components in the deployment unit.
-  One can override the global security-domain at the container
-  level using the security-domain element at the container-configuration
-  level.
-
-  Used in: jboss-app
--->
-<!ELEMENT security-domain (#PCDATA)>
-
-<!--
-  The unauthenticated-principal element specifies the name of the principal
-  that will be returned by the EJBContext.getCallerPrincipal() method if there
-  is no authenticated user. This Principal has no roles or privaledges to call
-  any other beans.
--->
-<!ELEMENT unauthenticated-principal (#PCDATA)>
-
-<!-- The loader-repository specifies the name of the UnifiedLoaderRepository
-   MBean to use for the ear to provide ear level scoping of classes deployed
-   in the ear. It is a unique JMX ObjectName string. It may also specify
-   an arbitrary configuration by including a loader-repository-config element.
-
-Examples:
-   <loader-repository>jboss.test:loader=cts-cmp2v1-sar.ear</loader-repository>
-
-   <loader-repository loaderRepositoryClass='dot.com.LoaderRepository'>
-      dot.com:loader=unique-archive-name
-      <loader-repository-config configParserClass='dot.com.LoaderParser'>
-         java2ParentDelegaton=true
-      </loader-repository-config>
-   </loader-repository>
--->
-<!ELEMENT loader-repository (#PCDATA | loader-repository-config)*>
-<!-- The loaderRepositoryClass attribute gives the classname of the
-org.jboss.mx.loading.LoaderRepository implementation.
--->
-<!ATTLIST loader-repository loaderRepositoryClass CDATA #IMPLIED>
-
-<!-- The loader-repository-config element specifies any arbitrary configuration
-fragment for use in configuring the loader-repository instance. The actual
-content of this element is specific to the loaderRepositoryClass and the
-code parsing the element.
--->
-<!ELEMENT loader-repository-config (#PCDATA)>
-<!-- The configParserClass attribute gives the classname of the
-org.jboss.mx.loading.LoaderRepositoryFactory.LoaderRepositoryConfigParser
-implementation to use to parse the loader-repository-config content.
--->
-<!ATTLIST loader-repository-config configParserClass CDATA #IMPLIED>
-
-<!-- The jmx-name element allows one to specify the JMX ObjectName to use
-for the MBean associated with the ejb-jar module. This must be a unique
-name and valid JMX ObjectName string.
-
-   Used in: jboss-app
--->
-<!ELEMENT jmx-name (#PCDATA)>
-
-<!-- An .ear file may contain a directory that contains libraries packaged in JAR files.
-The library-directory element of the .ear files deployment descriptor contains the name
-of this directory. If a library-directory element is not specified,
-the directory named lib is used.
-
-An empty library-directory element may be used to specify that there is no library directory.
-
-All files in this directory (but not subdirectories) with a .jar extension must be made available
-to all components packaged in the EAR file, including application clients.
-
-   Used in: jboss-app
--->
-<!ELEMENT library-directory (#PCDATA)>
-
-<!-- The module element is used to specify a jboss specific module archive.
--->
-<!ELEMENT module (service | har | web)>
-
-<!-- Allow the module to have a unique id -->
-<!ATTLIST module id ID #IMPLIED>
-
-<!-- The service element specifies a service archive (SAR) to deploy.
-
-Example:
-   <module>
-      <service>external.sar</service>
-   </module>
--->
-<!ELEMENT service (#PCDATA)>
-
-<!-- The har element specifies a Hibernate archive (HAR) to deploy.
-
-Example:
-   <module>
-      <har>myapp.har</har>
-   </module>
--->
-<!ELEMENT har (#PCDATA)>
-
-<!-- The web element specifies a war
-
-Example:
-   <module>
-      <web>
-         <web-uri>myapp.war</web-uri>
-         <context-root>/myapp</context-root>
-      </web>
-   </module>
--->
-<!ELEMENT web (web-uri, context-root)>
-
-<!--
-The web-uri element specifies the URI of a web application file,
-relative to the top level of the application package.
-
-Used in: web
--->
-<!ELEMENT web-uri (#PCDATA)>
-
-<!-- The context-root element specifies the context root of a web
-application. This is normally specified at the ear level using the standard
-J2EE application.xml descriptor, but it may be given here for standalone wars.
-This should not override the application.xml level specification.
-Used in: web
--->
-<!ELEMENT context-root (#PCDATA)>
-
-<!--
-  The security-role element contains the definition of a security role.
-  The definition consists of an the security role name and principal name element(s).
-
-Used in: jboss-app
-
-Example:
-		<security-role>
-      <role-name>Manager</role-name>
-      <principal-name>j2ee</principal-name>
-      <principal-name>javajoe</principal-name>
-		</security-role>
--->
-<!ELEMENT security-role (role-name, principal-name+)>
-
-<!--
-  The role-name element is the name of the role.
-
-  Used in: security-role
--->
-<!ELEMENT role-name (#PCDATA)>
-
-<!--
-  The principal-name element is the name of the principal that is mapped
-  to the assembly role-name.
-
-  Used in: security-role
--->
-<!ELEMENT principal-name (#PCDATA)>
-

jboss-as-7.2.0.Final/docs/schema/jboss-app_5_0.dtd

@@ -1,194 +0,0 @@
-<?xml version='1.0' encoding='UTF-8' ?>
-
-<!-- The JBoss 5.x specific elements for ears.
-$Id: jboss-app_5_0.dtd 81860 2008-11-30 22:12:20Z alex.loubyansky@jboss.com $
-
-DOCTYPE jboss-app
-    PUBLIC "-//JBoss//DTD Java EE Application 5.0//EN"
-    "http://www.jboss.org/j2ee/dtd/jboss-app_5_0.dtd"
--->
-
-<!-- The jboss-app element is the root element.
--->
-<!ELEMENT jboss-app (module-order?, security-domain?, unauthenticated-principal?,
- loader-repository?, jmx-name?, library-directory?, module*, security-role*)>
-
-
-<!--
-NOTE: legacy element from 4.x. Has absolutely no effect in JBoss_5.x.
-
- The value of the module-order could be implicit or strict
- <module-order>strict</module-order>
- 	or 
- <module-order>implicit</module-order>
- The strict value indicates that the deployments of the modules will 
- be done in the order that would be specified in the application.xml 
- and jboss-app.xml file . 
- The implicit value indicates the deployment would follow the order 
- which would be specified in the DeploymentSorter.
- The default order will be implicit to support backward compatibility
---> 
-<!ELEMENT module-order (#PCDATA)>
-
-<!--
-  The security-domain element specifies the JNDI name of the security
-  manager that implements the EJBSecurityManager and RealmMapping for
-  the domain. When specified at the jboss level it specifies the security
-  domain for all j2ee components in the deployment unit.
-  One can override the global security-domain at the container
-  level using the security-domain element at the container-configuration
-  level.
-
-  Used in: jboss-app
--->
-<!ELEMENT security-domain (#PCDATA)>
-
-<!--
-  The unauthenticated-principal element specifies the name of the principal
-  that will be returned by the EJBContext.getCallerPrincipal() method if there
-  is no authenticated user. This Principal has no roles or privaledges to call
-  any other beans.
--->
-<!ELEMENT unauthenticated-principal (#PCDATA)>
-
-<!-- The loader-repository specifies the name of the UnifiedLoaderRepository
-   MBean to use for the ear to provide ear level scoping of classes deployed
-   in the ear. It is a unique JMX ObjectName string. It may also specify
-   an arbitrary configuration by including a loader-repository-config element.
-
-Examples:
-   <loader-repository>jboss.test:loader=cts-cmp2v1-sar.ear</loader-repository>
-
-   <loader-repository loaderRepositoryClass='dot.com.LoaderRepository'>
-      dot.com:loader=unique-archive-name
-      <loader-repository-config configParserClass='dot.com.LoaderParser'>
-         java2ParentDelegaton=true
-      </loader-repository-config>
-   </loader-repository>
--->
-<!ELEMENT loader-repository (#PCDATA | loader-repository-config)*>
-<!-- The loaderRepositoryClass attribute gives the classname of the
-org.jboss.mx.loading.LoaderRepository implementation.
--->
-<!ATTLIST loader-repository loaderRepositoryClass CDATA #IMPLIED>
-
-<!-- The loader-repository-config element specifies any arbitrary configuration
-fragment for use in configuring the loader-repository instance. The actual
-content of this element is specific to the loaderRepositoryClass and the
-code parsing the element.
--->
-<!ELEMENT loader-repository-config (#PCDATA)>
-<!-- The configParserClass attribute gives the classname of the
-org.jboss.mx.loading.LoaderRepositoryFactory.LoaderRepositoryConfigParser
-implementation to use to parse the loader-repository-config content.
--->
-<!ATTLIST loader-repository-config configParserClass CDATA #IMPLIED>
-
-<!-- The jmx-name element allows one to specify the JMX ObjectName to use
-for the MBean associated with the ejb-jar module. This must be a unique
-name and valid JMX ObjectName string.
-
-   Used in: jboss-app
--->
-<!ELEMENT jmx-name (#PCDATA)>
-
-<!-- An .ear file may contain a directory that contains libraries packaged in JAR files.
-The library-directory element of the .ear files deployment descriptor contains the name
-of this directory. If a library-directory element is not specified,
-the directory named lib is used.
-
-An empty library-directory element may be used to specify that there is no library directory.
-
-All files in this directory (but not subdirectories) with a .jar extension must be made available
-to all components packaged in the EAR file, including application clients.
-
-   Used in: jboss-app
--->
-<!ELEMENT library-directory (#PCDATA)>
-
-<!-- The module element is used to specify a jboss specific module archive.
--->
-<!ELEMENT module (service | har | web)>
-
-<!-- The service element specifies a service archive (SAR) to deploy.
-
-Example:
-   <module>
-      <service>external.sar</service>
-   </module>
--->
-<!ELEMENT service (#PCDATA)>
-
-<!-- The har element specifies a Hibernate archive (HAR) to deploy.
-
-Example:
-   <module>
-      <har>myapp.har</har>
-   </module>
--->
-<!ELEMENT har (#PCDATA)>
-
-<!-- The web element specifies a war
-
-Example:
-   <module>
-      <web>
-         <web-uri>myapp.war</web-uri>
-         <context-root>/myapp</context-root>
-      </web>
-   </module>
--->
-<!ELEMENT web (web-uri, context-root)>
-
-<!--
-The web-uri element specifies the URI of a web application file,
-relative to the top level of the application package.
-
-Used in: web
--->
-<!ELEMENT web-uri (#PCDATA)>
-
-<!-- The context-root element specifies the context root of a web
-application. This is normally specified at the ear level using the standard
-J2EE application.xml descriptor, but it may be given here for standalone wars.
-This should not override the application.xml level specification.
-Used in: web
--->
-<!ELEMENT context-root (#PCDATA)>
-
-<!--
-  The security-role element contains the definition of a security role.
-  The definition consists of an the security role name and principal name element(s).
-
-Used in: jboss-app
-
-Example:
-		<security-role>
-      <role-name>Manager</role-name>
-      <principal-name>j2ee</principal-name>
-      <principal-name>javajoe</principal-name>
-		</security-role>
--->
-<!ELEMENT security-role (role-name, principal-name+)>
-
-<!--
-  The role-name element is the name of the role.
-
-  Used in: security-role
--->
-<!ELEMENT role-name (#PCDATA)>
-
-<!--
-  The principal-name element is the name of the principal that is mapped
-  to the assembly role-name.
-
-  Used in: security-role
--->
-<!ELEMENT principal-name (#PCDATA)>
-
-<!-- Allow the jboss-app to have a unique id -->
-<!ATTLIST jboss-app id ID #IMPLIED>
-<!-- Allow the module to have a unique id -->
-<!ATTLIST module id ID #IMPLIED>
-<!-- Allow the security-role to have a unique id -->
-<!ATTLIST security-role id ID #IMPLIED>

jboss-as-7.2.0.Final/docs/schema/jboss-app_7_0.xsd

@@ -1,123 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
-  ~ JBoss, Home of Professional Open Source.
-  ~ Copyright 2012, Red Hat, Inc., and individual contributors
-  ~ as indicated by the @author tags. See the copyright.txt file in the
-  ~ distribution for a full listing of individual contributors.
-  ~
-  ~ This is free software; you can redistribute it and/or modify it
-  ~ under the terms of the GNU Lesser General Public License as
-  ~ published by the Free Software Foundation; either version 2.1 of
-  ~ the License, or (at your option) any later version.
-  ~
-  ~ This software is distributed in the hope that it will be useful,
-  ~ but WITHOUT ANY WARRANTY; without even the implied warranty of
-  ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-  ~ Lesser General Public License for more details.
-  ~
-  ~ You should have received a copy of the GNU Lesser General Public
-  ~ License along with this software; if not, write to the Free
-  ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
-  ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
-  -->
-
-<xs:schema xmlns="http://www.jboss.com/xml/ns/javaee"
-           xmlns:xs="http://www.w3.org/2001/XMLSchema"
-           xmlns:javaee="http://java.sun.com/xml/ns/javaee"
-           xmlns:jboss="http://www.jboss.com/xml/ns/javaee"
-           targetNamespace="http://www.jboss.com/xml/ns/javaee"
-           version="7.0"
-           elementFormDefault="qualified">
-
-    <xs:annotation>
-        <xs:documentation>
-            <![CDATA[
-
-	This is the XML Schema for the JBoss AS7 EAR application deployment descriptor.
-	The deployment descriptor must be named "jboss-app.xml" and placed in the
-	.ear/META-INF folder. All the descriptors must indicate
-	the JBoss schema by using the Java EE namespace:
-
-	http://www.jboss.com/xml/ns/javaee
-
-	and by indicating the version of the schema by
-	using the version attribute as shown below:
-
-	    <jboss-app xmlns="http://www.jboss.com/xml/ns/javaee"
-             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-             version="7.0">
-	       ...
-            </jboss-app>
-
-    The instance documents may indicate the published version of
-	the schema using the xsi:schemaLocation attribute for the
-	Java EE namespace with the following location:
-
-	http://www.jboss.org/j2ee/schema/jboss-app_7_0.xsd
-
-	]]>
-        </xs:documentation>
-    </xs:annotation>
-
-    <!-- Import the Java EE6 xsd -->
-    <xs:import namespace="http://java.sun.com/xml/ns/javaee"
-               schemaLocation="application_6.xsd"/>
-
-    <!-- Include the common JBoss EE elements -->
-    <xs:include schemaLocation="jboss-common_6_0.xsd"/>
-
-
-    <xs:element name="jboss-app" type="jboss-appType"/>
-
-    <xs:complexType name="jboss-appType">
-        <xs:annotation>
-            <xs:documentation>
-                Root element for JBoss specific configurations in a .ear
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="javaee:applicationType">
-                <xs:sequence>
-                    <xs:element name="distinct-name" type="xs:string" minOccurs="0" maxOccurs="1">
-                        <xs:annotation>
-                            <xs:documentation>
-                                The distinct-name for this application.
-                            </xs:documentation>
-                        </xs:annotation>
-                    </xs:element>
-                    <xs:element name="security-domain" type="xs:string" minOccurs="0" maxOccurs="1">
-                        <xs:annotation>
-                            <xs:documentation>
-                                The security domain application for this application.
-                            </xs:documentation>
-                        </xs:annotation>
-                    </xs:element>
-                    <xs:element name="unauthenticated-principal" type="xs:string" minOccurs="0" maxOccurs="1">
-                        <xs:annotation>
-                            <xs:documentation>
-                                The principal that will be used for unauthenticated requests in this application
-                            </xs:documentation>
-                        </xs:annotation>
-                    </xs:element>
-
-                    <xs:element name="library-directory" type="xs:string" minOccurs="0" maxOccurs="1"/>
-
-                    <xs:element name="security-role" minOccurs="0" maxOccurs="unbounded"
-                                type="jboss:security-roleType"/>
-
-                    <xs:element name="module" minOccurs="0" maxOccurs="unbounded" type="moduleType"/>
-
-                </xs:sequence>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="moduleType">
-        <xs:sequence>
-            <xs:element name="service" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
-            <xs:element name="har" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
-            <xs:element name="web" type="javaee:webType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-</xs:schema>

jboss-as-7.2.0.Final/docs/schema/jboss-as-cli_1_0.xsd

@@ -1,103 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-  ~ JBoss, Home of Professional Open Source.
-  ~ Copyright 2011, Red Hat, Inc., and individual contributors
-  ~ as indicated by the @author tags. See the copyright.txt file in the
-  ~ distribution for a full listing of individual contributors.
-  ~
-  ~ This is free software; you can redistribute it and/or modify it
-  ~ under the terms of the GNU Lesser General Public License as
-  ~ published by the Free Software Foundation; either version 2.1 of
-  ~ the License, or (at your option) any later version.
-  ~
-  ~ This software is distributed in the hope that it will be useful,
-  ~ but WITHOUT ANY WARRANTY; without even the implied warranty of
-  ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-  ~ Lesser General Public License for more details.
-  ~
-  ~ You should have received a copy of the GNU Lesser General Public
-  ~ License along with this software; if not, write to the Free
-  ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
-  ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
-  -->
-
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
-           xmlns="urn:jboss:cli:1.0"
-           targetNamespace="urn:jboss:cli:1.0"
-           elementFormDefault="qualified"
-           attributeFormDefault="unqualified"
-        >
-
-
-    <xs:element name="jboss-cli">
-        <xs:annotation>
-            <xs:documentation>
-                Root element for the JBoss Command Line Interface configuration.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element ref="default-controller" minOccurs="0"/>
-                <xs:element ref="history" minOccurs="0"/>
-                <xs:element ref="ssl" minOccurs="0" maxOccurs="1"/>
-            </xs:sequence>
-        </xs:complexType>
-    </xs:element>
-    
-    <xs:element name="default-controller">
-        <xs:annotation>
-            <xs:documentation>
-                This element contains the configuration of the default controller to connect to
-                when the connect command is executed w/o arguments.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element name="host" type="xs:string" minOccurs="0" default="localhost"/>
-                <xs:element name="port" type="xs:int" minOccurs="0" default="9999"/>
-            </xs:sequence>
-        </xs:complexType>
-    </xs:element>
-    
-    <xs:element name="history">
-        <xs:annotation>
-            <xs:documentation>
-                This element contains the configuration for the commands and operations history log.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element name="enabled" type="xs:boolean" minOccurs="0" default="true"/>
-                <xs:element name="file-name" type="xs:string" minOccurs="0" default=".jboss-cli-history"/>
-                <xs:element name="file-dir" type="xs:string" minOccurs="0" default="${user.home}"/>
-                <xs:element name="max-size" type="xs:int" minOccurs="0" default="500"/>
-            </xs:sequence>
-        </xs:complexType>
-    </xs:element>
-    
-    <xs:element name="ssl">
-        <xs:annotation>
-            <xs:documentation>
-                This element contains the configuration for the Key and Trust stores
-                used for SSL.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element name="keyStore" type="xs:string" minOccurs="0" />
-                <xs:element name="keyStorePassword" type="xs:string" minOccurs="0" />
-                <xs:element name="trustStore" type="xs:string" minOccurs="0" />
-                <xs:element name="trustStorePassword" type="xs:string" minOccurs="0" />
-                <xs:element name="modifyTrustStore" type="xs:boolean" default="true" minOccurs="0">
-                    <xs:annotation>
-                        <xs:documentation>
-                            Setting to true will cause the CLI to prompt when unrecognised certificates are received
-                            and allow them to be stored in the truststore.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:element>
-            </xs:sequence>
-        </xs:complexType>
-    </xs:element>
-</xs:schema>

jboss-as-7.2.0.Final/docs/schema/jboss-as-cli_1_1.xsd

@@ -1,116 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-  ~ JBoss, Home of Professional Open Source.
-  ~ Copyright 2012, Red Hat, Inc., and individual contributors
-  ~ as indicated by the @author tags. See the copyright.txt file in the
-  ~ distribution for a full listing of individual contributors.
-  ~
-  ~ This is free software; you can redistribute it and/or modify it
-  ~ under the terms of the GNU Lesser General Public License as
-  ~ published by the Free Software Foundation; either version 2.1 of
-  ~ the License, or (at your option) any later version.
-  ~
-  ~ This software is distributed in the hope that it will be useful,
-  ~ but WITHOUT ANY WARRANTY; without even the implied warranty of
-  ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-  ~ Lesser General Public License for more details.
-  ~
-  ~ You should have received a copy of the GNU Lesser General Public
-  ~ License along with this software; if not, write to the Free
-  ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
-  ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
-  -->
-
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
-           xmlns="urn:jboss:cli:1.1"
-           targetNamespace="urn:jboss:cli:1.1"
-           elementFormDefault="qualified"
-           attributeFormDefault="unqualified"
-        >
-
-
-    <xs:element name="jboss-cli">
-        <xs:annotation>
-            <xs:documentation>
-                Root element for the JBoss Command Line Interface configuration.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element ref="default-controller" minOccurs="0"/>
-                <xs:element ref="validate-operation-requests" minOccurs="0"/>
-                <xs:element ref="history" minOccurs="0"/>
-                <xs:element ref="ssl" minOccurs="0" maxOccurs="1"/>
-            </xs:sequence>
-        </xs:complexType>
-    </xs:element>
-    
-    <xs:element name="default-controller">
-        <xs:annotation>
-            <xs:documentation>
-                This element contains the configuration of the default controller to connect to
-                when the connect command is executed w/o arguments.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element name="host" type="xs:string" minOccurs="0" default="localhost"/>
-                <xs:element name="port" type="xs:int" minOccurs="0" default="9999"/>
-            </xs:sequence>
-        </xs:complexType>
-    </xs:element>
-    
-    <xs:element name="validate-operation-requests" type="xs:boolean" default="true">
-        <xs:annotation>
-            <xs:documentation>
-                Indicates whether the parameter list of the operation reuqests
-                should be validated before the requests are sent to the controller
-                for the execution.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:element>
-    
-    <xs:element name="history">
-        <xs:annotation>
-            <xs:documentation>
-                This element contains the configuration for the commands and operations history log.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element name="enabled" type="xs:boolean" minOccurs="0" default="true"/>
-                <xs:element name="file-name" type="xs:string" minOccurs="0" default=".jboss-cli-history"/>
-                <xs:element name="file-dir" type="xs:string" minOccurs="0" default="${user.home}"/>
-                <xs:element name="max-size" type="xs:int" minOccurs="0" default="500"/>
-            </xs:sequence>
-        </xs:complexType>
-    </xs:element>
-    
-    <xs:element name="ssl">
-        <xs:annotation>
-            <xs:documentation>
-                This element contains the configuration for the Key and Trust stores
-                used for SSL.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element name="key-store" type="xs:string" minOccurs="0" />
-                <xs:element name="key-store-password" type="xs:string" minOccurs="0" />
-                <xs:element name="alias" type="xs:string" minOccurs="0" />
-                <xs:element name="key-password" type="xs:string" minOccurs="0" />                
-                <xs:element name="trust-store" type="xs:string" minOccurs="0" />
-                <xs:element name="trust-store-password" type="xs:string" minOccurs="0" />
-                <xs:element name="modify-trust-store" type="xs:boolean" default="true" minOccurs="0">
-                    <xs:annotation>
-                        <xs:documentation>
-                            Setting to true will cause the CLI to prompt when unrecognised certificates are received
-                            and allow them to be stored in the truststore.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:element>
-            </xs:sequence>
-        </xs:complexType>
-    </xs:element>
-</xs:schema>

jboss-as-7.2.0.Final/docs/schema/jboss-as-cli_1_2.xsd

@@ -1,150 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-  ~ JBoss, Home of Professional Open Source.
-  ~ Copyright 2012, Red Hat, Inc., and individual contributors
-  ~ as indicated by the @author tags. See the copyright.txt file in the
-  ~ distribution for a full listing of individual contributors.
-  ~
-  ~ This is free software; you can redistribute it and/or modify it
-  ~ under the terms of the GNU Lesser General Public License as
-  ~ published by the Free Software Foundation; either version 2.1 of
-  ~ the License, or (at your option) any later version.
-  ~
-  ~ This software is distributed in the hope that it will be useful,
-  ~ but WITHOUT ANY WARRANTY; without even the implied warranty of
-  ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-  ~ Lesser General Public License for more details.
-  ~
-  ~ You should have received a copy of the GNU Lesser General Public
-  ~ License along with this software; if not, write to the Free
-  ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
-  ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
-  -->
-
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
-           xmlns="urn:jboss:cli:1.1"
-           targetNamespace="urn:jboss:cli:1.1"
-           elementFormDefault="qualified"
-           attributeFormDefault="unqualified"
-        >
-
-
-    <xs:element name="jboss-cli">
-        <xs:annotation>
-            <xs:documentation>
-                Root element for the JBoss Command Line Interface configuration.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element ref="default-controller" minOccurs="0"/>
-                <xs:element ref="validate-operation-requests" minOccurs="0"/>
-                <xs:element ref="history" minOccurs="0"/>
-
-                <xs:element name="resolve-parameter-values" type="xs:boolean" minOccurs="0" maxOccurs="1" default="false">
-                    <xs:annotation>
-                        <xs:documentation>
-                            Whether to resolve system properties specified as command argument (or operation parameter)
-                            values before sending the operation request to the controller or let the resolution happen
-                            on the server side.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:element>
-
-                <xs:element ref="connection-timeout" minOccurs="0" maxOccurs="1"/>
-
-                <xs:element ref="ssl" minOccurs="0" maxOccurs="1"/>
-                
-                <xs:element ref="silent" minOccurs="0" maxOccurs="1"/>
-            </xs:sequence>
-        </xs:complexType>
-    </xs:element>
-
-    <xs:element name="default-controller">
-        <xs:annotation>
-            <xs:documentation>
-                This element contains the configuration of the default controller to connect to
-                when the connect command is executed w/o arguments.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element name="host" type="xs:string" minOccurs="0" default="localhost"/>
-                <xs:element name="port" type="xs:int" minOccurs="0" default="9999"/>
-            </xs:sequence>
-        </xs:complexType>
-    </xs:element>
-
-    <xs:element name="validate-operation-requests" type="xs:boolean" default="true">
-        <xs:annotation>
-            <xs:documentation>
-                Indicates whether the parameter list of the operation reuqests
-                should be validated before the requests are sent to the controller
-                for the execution.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:element>
-
-    <xs:element name="history">
-        <xs:annotation>
-            <xs:documentation>
-                This element contains the configuration for the commands and operations history log.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element name="enabled" type="xs:boolean" minOccurs="0" default="true"/>
-                <xs:element name="file-name" type="xs:string" minOccurs="0" default=".jboss-cli-history"/>
-                <xs:element name="file-dir" type="xs:string" minOccurs="0" default="${user.home}"/>
-                <xs:element name="max-size" type="xs:int" minOccurs="0" default="500"/>
-            </xs:sequence>
-        </xs:complexType>
-    </xs:element>
-
-    <xs:element name="connection-timeout" type="xs:int" default="5000">
-        <xs:annotation>
-            <xs:documentation>
-                The time allowed to establish a connection with the controller.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:element>
-
-    <xs:element name="ssl">
-        <xs:annotation>
-            <xs:documentation>
-                This element contains the configuration for the Key and Trust stores
-                used for SSL.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element name="key-store" type="xs:string" minOccurs="0" />
-                <xs:element name="key-store-password" type="xs:string" minOccurs="0" />
-                <xs:element name="alias" type="xs:string" minOccurs="0" />
-                <xs:element name="key-password" type="xs:string" minOccurs="0" />
-                <xs:element name="trust-store" type="xs:string" minOccurs="0" />
-                <xs:element name="trust-store-password" type="xs:string" minOccurs="0" />
-                <xs:element name="modify-trust-store" type="xs:boolean" default="true" minOccurs="0">
-                    <xs:annotation>
-                        <xs:documentation>
-                            Setting to true will cause the CLI to prompt when unrecognised certificates are received
-                            and allow them to be stored in the truststore.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:element>
-            </xs:sequence>
-        </xs:complexType>
-    </xs:element>
-    
-    <xs:element name="silent" type="xs:boolean" default="false">
-        <xs:annotation>
-            <xs:documentation>
-                Whether to write info and error messages to the terminal output.
-                Even if the value is false, the messages will still be logged
-                using the logger if its configuration allows and/or if the
-                output target was specified as part of the command line using '>'.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:element>
-</xs:schema>

jboss-as-7.2.0.Final/docs/schema/jboss-as-cmp_1_0.xsd

@@ -1,88 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-  ~ JBoss, Home of Professional Open Source.
-  ~ Copyright 2011, Red Hat, Inc., and individual contributors
-  ~ as indicated by the @author tags. See the copyright.txt file in the
-  ~ distribution for a full listing of individual contributors.
-  ~
-  ~ This is free software; you can redistribute it and/or modify it
-  ~ under the terms of the GNU Lesser General Public License as
-  ~ published by the Free Software Foundation; either version 2.1 of
-  ~ the License, or (at your option) any later version.
-  ~
-  ~ This software is distributed in the hope that it will be useful,
-  ~ but WITHOUT ANY WARRANTY; without even the implied warranty of
-  ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-  ~ Lesser General Public License for more details.
-  ~
-  ~ You should have received a copy of the GNU Lesser General Public
-  ~ License along with this software; if not, write to the Free
-  ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
-  ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
-  -->
-
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
-           targetNamespace="urn:jboss:domain:cmp:1.0"
-           xmlns="urn:jboss:domain:cmp:1.0"
-           elementFormDefault="qualified"
-           attributeFormDefault="unqualified"
-           version="1.0">
-
-    <!-- The cmp subsystem root element -->
-    <xs:element name="subsystem" type="subsystem"/>
-
-    <xs:complexType name="subsystem">
-        <xs:all>
-            <xs:element name="key-generators" type="keyGeneratorsType" minOccurs="0" maxOccurs="1"/>
-        </xs:all>
-    </xs:complexType>
-
-
-    <xs:complexType name="keyGeneratorsType">
-        <xs:sequence>
-            <xs:choice minOccurs="0" maxOccurs="unbounded">
-                <xs:element name="uuid" type="uuidType">
-                    <xs:annotation>
-                        <xs:documentation>
-                            <![CDATA[[
-                                Specifies a UUID based key generator.
-                            ]]>
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:element>
-                <xs:element name="hilo" type="hiloType">
-                    <xs:annotation>
-                        <xs:documentation>
-                            <![CDATA[[
-                                Specifies a HiLo based key generator.
-                            ]]>
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:element>
-            </xs:choice>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="uuidType">
-        <xs:attribute name="name" type="xs:string"/>
-    </xs:complexType>
-
-    <xs:complexType name="hiloType">
-        <xs:sequence>
-            <xs:element name="block-size" type="xs:long" maxOccurs="1"/>
-            <xs:element name="create-table" type="xs:boolean" maxOccurs="1"/>
-            <xs:element name="create-table-ddl" type="xs:string" maxOccurs="1"/>
-            <xs:element name="data-source" type="xs:token"  minOccurs="1" maxOccurs="1"/>
-            <xs:element name="drop-table" type="xs:boolean" maxOccurs="1"/>
-            <xs:element name="id-column" type="xs:token"  minOccurs="1" maxOccurs="1"/>
-            <xs:element name="select-hi-ddl" type="xs:string" maxOccurs="1"/>
-            <xs:element name="sequence-column" type="xs:token"  minOccurs="1" maxOccurs="1"/>
-            <xs:element name="sequence-name" type="xs:token"  minOccurs="1" maxOccurs="1"/>
-            <xs:element name="table-name" type="xs:token" minOccurs="1" maxOccurs="1"/>
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string"/>
-    </xs:complexType>
-
-
-</xs:schema>

jboss-as-7.2.0.Final/docs/schema/jboss-as-cmp_1_1.xsd

@@ -1,90 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-  ~ JBoss, Home of Professional Open Source.
-  ~ Copyright 2011, Red Hat, Inc., and individual contributors
-  ~ as indicated by the @author tags. See the copyright.txt file in the
-  ~ distribution for a full listing of individual contributors.
-  ~
-  ~ This is free software; you can redistribute it and/or modify it
-  ~ under the terms of the GNU Lesser General Public License as
-  ~ published by the Free Software Foundation; either version 2.1 of
-  ~ the License, or (at your option) any later version.
-  ~
-  ~ This software is distributed in the hope that it will be useful,
-  ~ but WITHOUT ANY WARRANTY; without even the implied warranty of
-  ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-  ~ Lesser General Public License for more details.
-  ~
-  ~ You should have received a copy of the GNU Lesser General Public
-  ~ License along with this software; if not, write to the Free
-  ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
-  ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
-  -->
-
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
-           targetNamespace="urn:jboss:domain:cmp:1.0"
-           xmlns="urn:jboss:domain:cmp:1.0"
-           elementFormDefault="qualified"
-           attributeFormDefault="unqualified"
-           version="1.0">
-
-    <!-- The cmp subsystem root element -->
-    <xs:element name="subsystem" type="subsystem"/>
-
-    <xs:complexType name="subsystem">
-        <xs:all>
-            <xs:element name="key-generators" type="keyGeneratorsType" minOccurs="0" maxOccurs="1"/>
-        </xs:all>
-    </xs:complexType>
-
-
-    <xs:complexType name="keyGeneratorsType">
-        <xs:sequence>
-            <xs:choice minOccurs="0" maxOccurs="unbounded">
-                <xs:element name="uuid" type="uuidType">
-                    <xs:annotation>
-                        <xs:documentation>
-                            <![CDATA[[
-                                Specifies a UUID based key generator.
-                            ]]>
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:element>
-                <xs:element name="hilo" type="hiloType">
-                    <xs:annotation>
-                        <xs:documentation>
-                            <![CDATA[[
-                                Specifies a HiLo based key generator.
-                            ]]>
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:element>
-            </xs:choice>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="uuidType">
-        <xs:attribute name="name" type="xs:string"/>
-        <xs:attribute name="jndi-name" type="xs:string" use="optional"/>
-    </xs:complexType>
-
-    <xs:complexType name="hiloType">
-        <xs:sequence>
-            <xs:element name="block-size" type="xs:long"/>
-            <xs:element name="create-table" type="xs:boolean"/>
-            <xs:element name="create-table-ddl" type="xs:string"/>
-            <xs:element name="data-source" type="xs:token"/>
-            <xs:element name="drop-table" type="xs:boolean"/>
-            <xs:element name="id-column" type="xs:token"/>
-            <xs:element name="select-hi-ddl" type="xs:string"/>
-            <xs:element name="sequence-column" type="xs:token"/>
-            <xs:element name="sequence-name" type="xs:token"/>
-            <xs:element name="table-name" type="xs:token"/>
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string"/>
-        <xs:attribute name="jndi-name" type="xs:string" use="optional"/>
-    </xs:complexType>
-
-
-</xs:schema>

jboss-as-7.2.0.Final/docs/schema/jboss-as-config_1_0.xsd

@@ -1,1601 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-  ~ JBoss, Home of Professional Open Source.
-  ~ Copyright 2010, Red Hat, Inc., and individual contributors
-  ~ as indicated by the @author tags. See the copyright.txt file in the
-  ~ distribution for a full listing of individual contributors.
-  ~
-  ~ This is free software; you can redistribute it and/or modify it
-  ~ under the terms of the GNU Lesser General Public License as
-  ~ published by the Free Software Foundation; either version 2.1 of
-  ~ the License, or (at your option) any later version.
-  ~
-  ~ This software is distributed in the hope that it will be useful,
-  ~ but WITHOUT ANY WARRANTY; without even the implied warranty of
-  ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-  ~ Lesser General Public License for more details.
-  ~
-  ~ You should have received a copy of the GNU Lesser General Public
-  ~ License along with this software; if not, write to the Free
-  ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
-  ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
-  -->
-
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
-           xmlns="urn:jboss:domain:1.0"
-           targetNamespace="urn:jboss:domain:1.0"
-           elementFormDefault="qualified"
-           attributeFormDefault="unqualified"
-        >
-
-
-    <xs:element name="domain">
-        <xs:annotation>
-            <xs:documentation>
-                Root element for the master document specifying the core configuration
-                for the servers in a domain. There should be one such master
-                document per domain, available to the host controller that
-                is configured to act as the domain controller.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element name="extensions" type="extensionsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="system-properties" type="properties-with-boottime" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="paths" type="named-pathsType" minOccurs="0" maxOccurs="1" />
-                <xs:element name="profiles" type="profilesType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="interfaces" type="named-interfacesType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="socket-binding-groups" type="socket-binding-groupsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="deployments" type="domain-deploymentsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="server-groups" type="server-groupsType" minOccurs="0" maxOccurs="1"/>
-            </xs:sequence>
-        </xs:complexType>
-    </xs:element>
-
-    <xs:element name="host">
-        <xs:annotation>
-            <xs:documentation>
-                Root element for a document configuring a host controller and
-                the group of servers under the control of that host controller.
-                The standard usage would be for a domain to have one such host controller
-                on each physical (or virtual) host machine. Emphasis in this
-                document is on enumerating the servers, configuring items that
-                are specific to the host environment (e.g. IP addresses), and
-                on any server-specific configuration settings.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element name="system-properties" type="properties-with-boottime" minOccurs="0"/>
-                <xs:element name="paths" type="specified-pathsType" minOccurs="0" maxOccurs="1" />
-                <xs:element name="management" type="managementType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="domain-controller" type="domain-controllerType"/>
-                <xs:element name="interfaces" type="specified-interfacesType" minOccurs="0"/>
-                <xs:element name="jvms" type="jvmsType" minOccurs="0"/>
-                <xs:element name="servers" type="serversType" minOccurs="0"/>
-            </xs:sequence>
-            <xs:attribute name="name" type="xs:string" use="optional">
-                <xs:annotation>
-                    <xs:documentation>
-                        The name to use for this host's host controller. Must be
-                        unique across the domain. If not set, defaults to the
-                        runtime value of InetAddress.getLocalHost().getHostName().
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:attribute>
-        </xs:complexType>
-    </xs:element>
-
-    <xs:element name="server">
-        <xs:annotation>
-            <xs:documentation>
-                Root element for a document specifying the configuration
-                of a single "standalone" server that does not operate
-                as part of a domain.
-
-                Note that this element is distinct from the 'serverType'
-                specified in this schema. The latter type forms part of the
-                configuration of a server that operates as part of a domain.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element name="extensions" type="extensionsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="system-properties" type="properties" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="paths" type="specified-pathsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="management" type="managementType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="profile" type="standalone-profileType" minOccurs="0"/>
-                <xs:element name="interfaces" type="specified-interfacesType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="socket-binding-group" type="standalone-socket-binding-groupType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="deployments" type="server-deploymentsType" minOccurs="0" maxOccurs="1"/>
-            </xs:sequence>
-            <xs:attribute name="name" type="xs:string" use="optional">
-                <xs:annotation>
-                    <xs:documentation>
-                        The name to use for this server. If not set, defaults to
-                        the runtime value of InetAddress.getLocalHost().getHostName().
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:attribute>
-        </xs:complexType>
-    </xs:element>
-
-    <xs:complexType name="domain-managementType">
-        <xs:annotation>
-            <xs:documentation>
-                Domain-wide default configuration settings for the management of standalone servers and a Host Controller.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="security-realms" minOccurs="0">
-                <xs:complexType>
-                    <xs:sequence>
-                        <xs:element name="security-realm" type="security-realmType" minOccurs="1"
-                                    maxOccurs="unbounded"/>
-                    </xs:sequence>
-                </xs:complexType>
-            </xs:element>
-            <xs:element name="outbound-connections" minOccurs="0">
-                <xs:complexType>
-                    <xs:sequence>
-                      <xs:element name="ldap" type="ldapType" minOccurs="1" /> <!-- TODO minOccurs only while ldap is only supported connection. -->
-                    </xs:sequence>
-                </xs:complexType>
-            </xs:element>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="managementType">
-        <xs:annotation>
-            <xs:documentation>
-                The centralized configuration for the management of standalone servers and a Host Controller.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="domain-managementType">
-                <xs:sequence>
-                    <xs:element name="management-interfaces" type="management-interfacesType" minOccurs="0"/>
-                </xs:sequence>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="ldapType"> <!-- TODO - May extend from a common connection type for name -->
-        <xs:annotation>
-            <xs:documentation>
-                The LDAP connection definition.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of this connection.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="url" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The URL to connect to ldap.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <!-- TODO - Later will be optional if we support GSSAPI to connect to LDAP -->
-        <xs:attribute name="search-dn" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The distinguished name to use when connecting to LDAP to perform searches.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="search-credential" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The credential to use when connecting to perform a search.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <!-- TODO - May drop this and just allow free name/value properties for extension. -->
-        <xs:attribute name="initial-context-factory" type="xs:string" default="com.sun.jndi.ldap.LdapCtxFactory">
-            <xs:annotation>
-                <xs:documentation>
-                    The initial context factory to establish the LdapContext.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="security-realmType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of a security realm for securing access to the management interfaces.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="server-identities" type="server-identitiesType" minOccurs="0" />
-            <xs:element name="authentication" type="authenticationType" minOccurs="0" />
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of this security-realm, each security-realm must be assigned a unique name.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="server-identitiesType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the identities that represent the server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-          <xs:element name="ssl" type="sslType" minOccurs="0" />
-          <xs:element name="secret" type="secretType" minOccurs="0" />
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="secretType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the SSL identity of this server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="value" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The secret / password - Base64 Encoded
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="sslType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the SSL identity of this server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="keystore" type="keystoreType" />
-        </xs:sequence>
-        <xs:attribute name="protocol" type="xs:string" default="TLS">
-            <xs:annotation>
-                <xs:documentation>
-                    The protocol to use when creating the SSLContext.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="keystoreType">
-        <xs:annotation>
-            <xs:documentation>
-                The keystore configuration for the server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="relative-to" use="optional" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of another previously named path, or of one of the
-                    standard paths provided by the system. If 'relative-to' is
-                    provided, the value of the 'path' attribute is treated as
-                    relative to the path specified by this attribute.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="path" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The path of the keystore.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="password" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The password to open the keystore.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="authenticationType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the server side authentication mechanisms.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="ldap" type="ldapAuthenticationType" minOccurs="0" />
-            <xs:element name="properties" type="propertiesAuthenticationType" minOccurs="0" />
-            <xs:element name="users" type="usersAuthenticationType" minOccurs="0" />
-        </xs:choice>
-        <xs:attribute name="useDomainController" type="xs:boolean" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Should the request delegate to the domain controller or handle the authentication locally.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="ldapAuthenticationType">
-        <xs:annotation>
-            <xs:documentation>
-                Definition to use LDAP as the user repository.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="connection" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the connection to use to connect to LDAP.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="base-dn" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The base distinguished name to commence the search for the user.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="username-attribute" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the attribute to search for the user.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="recursive" type="xs:boolean" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Should the search be recursive.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="user-dn" type="xs:string" default="dn">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the attribute which is the users distinguished name.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-
-    <xs:complexType name="usersAuthenticationType">
-           <xs:annotation>
-            <xs:documentation>
-                A set of users
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="user" type="userType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="userType">
-        <xs:annotation>
-            <xs:documentation>
-                A single user.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="password" type="xs:string" />
-        </xs:choice>
-        <xs:attribute name="username" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The users username.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="propertiesAuthenticationType">
-        <xs:annotation>
-            <xs:documentation>
-                Declaration of users stored within properties files.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="relative-to" use="optional" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of another previously named path, or of one of the
-                    standard paths provided by the system. If 'relative-to' is
-                    provided, the value of the 'path' attribute is treated as
-                    relative to the path specified by this attribute.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="path" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The path of the properties file containing the users.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="management-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of a host's or standalone server's exposed management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="interface" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    Network interface on which the host's socket for
-                    management communication should be opened.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="port" type="xs:int" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Port on which the host's socket for
-                    management communication should be opened.
-
-                    If not specified the port will not be opened.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="secure-port" type="xs:int" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Secure port on which the host's socket for
-                    management communication should be opened.
-
-                    If not specified the port will not be opened.
-
-                    If specified the security-realm will be required to obtain
-                    the SSL configuration.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="security-realm" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    The security realm to use for this management interface, the capabilities
-                    of the security realm will be queried to identify the authentication mechanism(s) to
-                    offer.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="management-interfacesType">
-        <xs:all minOccurs="0">
-            <xs:element name="native-interface" type="management-interfaceType"/>
-            <xs:element name="http-interface" type="management-interfaceType"/>
-        </xs:all>
-    </xs:complexType>
-
-    <xs:complexType name="domain-controllerType">
-        <xs:choice>
-            <xs:element name="local" type="domain-controller-localType"/>
-            <xs:element name="remote" type="domain-controller-remoteType"/>
-        </xs:choice>
-    </xs:complexType>
-
-    <xs:complexType name="domain-controller-localType" />
-
-    <xs:complexType name="domain-controller-remoteType">
-         <xs:attribute name="host" type="xs:string" use="required" />
-         <xs:attribute name="port" type="xs:integer" use="required" />
-         <xs:attribute name="security-realm" type="xs:string" use="optional" />
-    </xs:complexType>
-
-    <xs:complexType name="serversType">
-        <xs:sequence>
-            <xs:element name="server" type="serverType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="serverType">
-        <xs:all>
-            <xs:element name="paths" type="specified-pathsType" minOccurs="0" maxOccurs="1" />
-
-            <xs:element name="interface-specs" type="specified-interfacesType" minOccurs="0"/>
-            <xs:element name="socket-binding-group" type="socket-binding-group-refType" minOccurs="0"/>
-
-            <!--<xs:element name="loggers" type="loggersType" minOccurs="0"/>-->
-            <xs:element name="system-properties" type="properties-with-boottime" minOccurs="0"/>
-            <xs:element name="jvm" minOccurs="0" type="serverJvmType"/>
-        </xs:all>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="group" type="xs:string" use="required"/>
-        <xs:attribute name="auto-start" type="xs:boolean" default="true"/>
-    </xs:complexType>
-
-    <xs:complexType name="extensionsType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of extension modules.</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="extension" type="extensionType" minOccurs="1" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="extensionType">
-        <xs:annotation>
-            <xs:documentation>
-                A module that extends the standard capabilities of a domain
-                or a standalone server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="module" use="required" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>The name of the module</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="server-groupsType">
-        <xs:sequence>
-            <xs:element name="server-group" type="server-groupType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="server-groupType">
-        <xs:sequence>
-            <xs:element name="jvm" type="namedJvmType" minOccurs="0"/>
-            <xs:element name="socket-binding-group" type="socket-binding-group-refType" minOccurs="1"/>
-
-            <xs:element name="deployments" type="server-groupDeploymentsType" minOccurs="0"/>
-
-            <xs:element name="system-properties" minOccurs="0" type="properties-with-boottime"/>
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the server group
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="profile" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the profile this server is running.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="server-groupDeploymentsType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of deployments that have been mapped to a server-group.</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="deployment" type="base-deploymentType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="base-deploymentType">
-        <xs:attribute name="name" use="required">
-            <xs:annotation>
-                <xs:documentation>Unique identifier of the deployment. Must be unique across all deployments.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="runtime-name" use="required">
-            <xs:annotation>
-                <xs:documentation>Name by which the deployment will be known within a running server.of the deployment.
-                    Does not need to be unique across all deployments in the domain, although it must be unique within
-                    an individual server. For example, two different deployments running on different servers in
-                    the domain could both have a 'runtime-name' of 'example.war', with one having a 'name'
-                    of 'example.war_v1' and another with an 'name' of 'example.war_v2'.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType><xs:complexType name="server-deploymentsType">
-    <xs:annotation>
-        <xs:documentation>Contains a list of deployments that have been mapped to a server.</xs:documentation>
-    </xs:annotation>
-    <xs:sequence>
-        <xs:element name="deployment" type="server-deploymentType" maxOccurs="unbounded"/>
-    </xs:sequence>
-</xs:complexType>
-
-    <xs:complexType name="server-deploymentType">
-        <xs:annotation>
-            <xs:documentation>A deployment that has been mapped to a server.</xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="base-deploymentType">
-                <xs:sequence>
-                    <!-- TODO: maxOccurs should be unbounded once overlays are in place -->
-                    <xs:choice maxOccurs="1">
-                        <xs:element name="content" type="contentType"/>
-                        <xs:element name="fs-archive" type="fs-archiveType"/>
-                        <xs:element name="fs-exploded" type="fs-explodedType"/>
-                    </xs:choice>
-                </xs:sequence>
-                <!--  TODO clarify what a value of 'false' means -->
-                <xs:attribute name="enabled" use="optional" type="xs:boolean" default="true">
-                    <xs:annotation>
-                        <xs:documentation>Whether the deployment deploy automatically when the server starts up.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="contentType">
-        <xs:attribute name="sha1" use="required">
-            <xs:annotation>
-                <xs:documentation>The checksum of the content</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="fs-archiveType">
-        <xs:annotation>
-            <xs:documentation>Archived content found on the filesystem</xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="fs-baseType"/>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="fs-baseType">
-        <xs:complexContent>
-            <xs:extension base="pathType"/>
-        </xs:complexContent>
-        <!-- TODO: make path required
-        <xs:complexContent>
-            <xs:restriction base="pathType">
-                <xs:attribute name="path" use="required"/>
-            </xs:restriction>
-        </xs:complexContent>
-        -->
-    </xs:complexType>
-
-    <xs:complexType name="fs-explodedType">
-        <xs:annotation>
-            <xs:documentation>Exploded content found on the filesystem</xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="fs-baseType"/>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="domain-deploymentsType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of domain-level deployments</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="deployment" type="domain-deploymentType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="domain-deploymentType">
-        <xs:annotation>
-            <xs:documentation>Deployment represents anything that can be deployed (e.g. an application such as EJB-JAR,
-                WAR, EAR,
-                any kind of standard archive such as RAR or JBoss-specific deployment),
-                which can be enabled or disabled on a domain level.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="base-deploymentType">
-                <xs:sequence>
-                    <!-- TODO: maxOccurs should be unbounded once overlays are in place -->
-                    <xs:choice maxOccurs="1">
-                        <xs:element name="content" type="contentType"/>
-                        <xs:element name="fs-archive" type="fs-archiveType"/>
-                        <xs:element name="fs-exploded" type="fs-explodedType"/>
-                    </xs:choice>
-                </xs:sequence>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <!-- TODO this is not used anywhere yet -->
-    <xs:complexType name="clustersType">
-        <xs:complexContent>
-            <xs:extension base="server-groupType">
-                <xs:sequence>
-                    <xs:element name="partition-name" type="xs:string"/>
-                    <xs:element name="state-transfer-timeout" type="xs:integer"/>
-                    <xs:element name="method-call-timeout" type="xs:integer"/>
-                </xs:sequence>
-                <xs:attribute name="category" type="xs:string" use="required"/>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <!-- domain-configuration related definitions -->
-    <xs:complexType name="domain-configurationType">
-        <xs:annotation>
-            <xs:documentation>The domain controller/server bootstrap configuration</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element ref="bootstrapURI"/>
-        </xs:sequence>
-    </xs:complexType>
-    <xs:element name="bootstrapURI" type="xs:string">
-        <xs:annotation>
-            <xs:documentation>The URI for bootstrapping a domain server</xs:documentation>
-        </xs:annotation>
-    </xs:element>
-
-    <xs:complexType name="profilesType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of profiles available for use in the domain</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="profile" type="domain-profileType" minOccurs="1" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="domain-profileType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of subsystems</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="include" type="profile-includeType" minOccurs="0" maxOccurs="unbounded"/>
-            <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded">
-                <xs:annotation>
-                    <xs:documentation>A profile declaration may include configuration
-                        elements from other namespaces for the subsystems that make up the profile.
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:any>
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>Name of the profile</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="profile-includeType">
-        <xs:annotation>
-            <xs:documentation>Specifies that a contents of a named profile are to be included in
-                the profile whose definition includes this type.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="profile" use="required">
-            <xs:annotation>
-                <xs:documentation>Name of the profile to include</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="standalone-profileType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of subsystems</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:choice minOccurs="1" maxOccurs="unbounded">
-                <xs:any namespace="##other">
-                    <xs:annotation>
-                        <xs:documentation>A profile declaration may include configuration
-                            elements from other namespaces for the subsystems that make up the profile.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:any>
-            </xs:choice>
-        </xs:sequence>
-    </xs:complexType>
-
-    <!-- general socket definition -->
-    <xs:complexType name="socket-binding-groupsType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of socket binding groups</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="socket-binding-group" type="socket-binding-groupType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="socket-binding-groupType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of socket configurations</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="include" type="socket-binding-group-includeType" minOccurs="0" maxOccurs="unbounded"/>
-            <xs:element name="socket-binding" type="socket-bindingType" maxOccurs="unbounded"/>
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="default-interface" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of an interface that should be used as the interface for
-                    any sockets that do not explicitly declare one.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="socket-binding-group-includeType">
-        <xs:annotation>
-            <xs:documentation>Specifies that a contents of a named socket-binding-group are to be included in
-                the socket-binding-group whose definition includes this type.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="socket-binding-group" use="required">
-            <xs:annotation>
-                <xs:documentation>Name of the socket-binding-group to include</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="standalone-socket-binding-groupType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of socket configurations</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="socket-binding" type="socket-bindingType" maxOccurs="unbounded"/>
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="default-interface" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of an interface that should be used as the interface for
-                    any sockets that do not explicitly declare one.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-	    <xs:attribute name="port-offset" type="xs:int" use="optional" default="0">
-	        <xs:annotation>
-                <xs:documentation>
-	                    Increment to apply to the base port values defined in the
-	                    socket group to derive the values to use on this
-	                    server.
-	            </xs:documentation>
-	        </xs:annotation>
-	    </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="socket-bindingType">
-        <xs:annotation>
-            <xs:documentation>Configuration information for a socket.</xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="interface" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of the interface to which the socket should be bound, or, for multicast
-                    sockets, the interface on which it should listen. This should
-                    be one of the declared interfaces.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="port" type="xs:unsignedShort" use="optional" default="0">
-            <xs:annotation>
-                <xs:documentation>
-                    Number of the port to which the socket should be bound.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="fixed-port" type="xs:boolean" use="optional" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Whether the port value should remain fixed even if numerically offsets
-                    are applied to the other sockets in the socket group..
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="multicast-address" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Multicast address on which the socket should receive multicast
-                    traffic. If unspecified, the socket will not be configured
-                    to receive multicast.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="multicast-port" type="xs:positiveInteger" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Port on which the socket should receive multicast
-                    traffic. Must be configured if 'multicast-address' is configured.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="socket-binding-group-refType">
-        <xs:attribute name="ref" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The socket group to use for the server group or server.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="port-offset" type="xs:int" default="0">
-            <xs:annotation>
-                <xs:documentation>
-                    Increment to apply to the base port values defined in the
-                    referenced socket group to derive the values to use on this
-                    server.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-
-    <xs:complexType name="named-interfacesType">
-        <xs:annotation>
-            <xs:documentation>
-                A list of named network interfaces. The interfaces may or may
-                not be fully specified (i.e. include criteria on how to determine
-                their IP address.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="interface" type="named-interfaceType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <!-- TODO make this and specified-interfaceType the same except for interface-criteriaGroup minOccurs -->
-    <xs:complexType name="named-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                A named network interface, but without any criteria
-                for determining the IP address to associate with that interface.
-                Acts as a placeholder in the model (e.g. at the domain level)
-                until a fully specified interface definition is applied at a
-                lower level (e.g. at the server level, where available addresses
-                are known.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:group ref="interface-criteriaGroup" minOccurs="0"/>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-    </xs:complexType>
-
-    <xs:complexType name="specified-interfacesType">
-        <xs:annotation>
-            <xs:documentation>
-                A list of fully specified named network interfaces.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="interface" type="specified-interfaceType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="specified-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                A named network interface, along with required criteria
-                for determining the IP address to associate with that interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:group ref="interface-criteriaGroup" minOccurs="1"/>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-    </xs:complexType>
-
-    <xs:group name="interface-criteriaGroup">
-        <xs:annotation>
-            <xs:documentation>
-                A set of criteria that can be used at runtime to determine
-                what IP address to use for an interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="any-address" type="any-addressType"/>
-            <xs:element name="any-ipv6-address" type="any-ipv6-addressType"/>
-            <xs:element name="any-ipv4-address" type="any-ipv4-addressType"/>
-            <xs:choice maxOccurs="unbounded">
-                <xs:element name="inet-address" type="inet-addressType"/>
-                <xs:element name="loopback" type="loopbackType"/>
-                <xs:element name="loopback-address" type="loopback-addressType"/>
-                <xs:element name="multicast" type="multicastType"/>
-                <xs:element name="point-to-point" type="point-to-pointType"/>
-                <xs:element name="virtual" type="interface-virtualType"/>
-                <xs:element name="up" type="interface-upType"/>
-                <xs:element name="public-address" type="public-addressType"/>
-                <xs:element name="link-local-address" type="link-local-addressType"/>
-                <xs:element name="site-local-address" type="site-local-addressType"/>
-                <xs:element name="nic" type="nicType"/>
-                <xs:element name="nic-match" type="nic-matchType"/>
-                <xs:element name="subnet-match" type="subnet-matchType"/>
-                <xs:element name="not" type="address-exclusionType"/>
-                <xs:element name="any" type="address-exclusionType"/>
-            </xs:choice>
-        </xs:choice>
-    </xs:group>
-
-    <xs:complexType name="inet-addressType">
-        <xs:attribute name="value" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    Either a IP address in IPv6 or IPv4 dotted decimal notation,
-                    or a hostname that can be resolved to an IP address.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="nicType">
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of a network interface (e.g. eth0, eth1, lo).
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="nic-matchType">
-        <xs:attribute name="pattern" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    A regular expression against which the names of the network
-                    interfaces available on the machine can be matched to find
-                    an acceptable interface.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="subnet-matchType">
-        <xs:attribute name="value" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    A network IP address and the number of bits in the
-                    address' network prefix, written in "slash notation";
-                    e.g. "192.168.0.0/16".
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="address-exclusionType">
-        <xs:choice>
-            <xs:element name="inet-address" type="inet-addressType"/>
-            <xs:element name="loopback" type="loopbackType"/>
-            <xs:element name="loopback-address" type="loopback-addressType"/>
-            <xs:element name="multicast" type="multicastType"/>
-            <xs:element name="point-to-point" type="point-to-pointType"/>
-            <xs:element name="virtual" type="interface-virtualType"/>
-            <xs:element name="up" type="interface-upType"/>
-            <xs:element name="public-address" type="public-addressType"/>
-            <xs:element name="link-local-address" type="link-local-addressType"/>
-            <xs:element name="site-local-address" type="site-local-addressType"/>
-            <xs:element name="nic" type="nicType" minOccurs="0" maxOccurs="unbounded"/>
-            <xs:element name="nic-match" type="nic-matchType" minOccurs="0" maxOccurs="unbounded"/>
-            <xs:element name="subnet-match" type="subnet-matchType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:choice>
-    </xs:complexType>
-
-    <xs:complexType name="loopbackType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it is a loopback
-                interface.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="loopback-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                A loopback address that may not actually configured on the machine's loopback interface.
-                Differs from inet-addressType in that the given value will be used even if no NIC can
-                be found that has the IP address associated with it.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="value" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    An IP address in IPv6 or IPv4 dotted decimal notation.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="multicastType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it supports
-                multicast.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="point-to-pointType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it is a point-to-point
-                interface.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="interface-upType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it is currently up.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="interface-virtualType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it is a virtual
-                interface.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="public-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it has a publicly
-                routable address.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="site-local-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not an address associated
-                with it is site-local.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="link-local-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not an address associated
-                with it is link-local.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="any-ipv6-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that sockets using this interface
-                should be bound to the IPv6 wildcard address (::).
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="any-ipv4-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that sockets using this interface
-                should be bound to the IPv4 wildcard address (0.0.0.0).
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="any-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that sockets using this interface
-                should be bound to a wildcard address. The IPv6 wildcard
-                address (::) will be used unless the java.net.preferIpV4Stack
-                system property is set to true, in which case the IPv4
-                wildcard address (0.0.0.0) will be used. If a socket is
-                bound to an IPv6 anylocal address on a dual-stack machine,
-                it can accept both IPv6 and IPv4 traffic; if it is bound to
-                an IPv4 (IPv4-mapped) anylocal address, it can only accept
-                IPv4 traffic.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="socketType">
-        <xs:annotation>
-            <xs:documentation>Configuration information for a socket.</xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="interface" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of the interface to which the socket should be bound, or, for multicast
-                    sockets, the interface on which it should listen. This should
-                    be one of the declared interfaces.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="port" type="xs:unsignedShort" use="optional" default="0">
-            <xs:annotation>
-                <xs:documentation>
-                    Number of the port to which the socket should be bound.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="fixed-port" type="xs:boolean" use="optional" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Whether the port value should remain fixed even if numerically offsets
-                    are applied to the other sockets in the socket group..
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="multicast-address" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Multicast address on which the socket should receive multicast
-                    traffic. If unspecified, the socket will not be configured
-                    to receive multicast.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="multicast-port" type="xs:positiveInteger" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Port on which the socket should receive multicast
-                    traffic. If unspecified, the socket will not be configured
-                    to receive multicast.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <!-- Path configurations -->
-    <xs:complexType name="named-pathsType">
-        <xs:annotation>
-            <xs:documentation>
-                A list of named filesystem paths. The paths may or may
-                not be fully specified (i.e. include the actual paths.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="path" type="named-pathType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="named-pathType">
-        <xs:annotation>
-            <xs:documentation>
-                A named filesystem path, but without a requirement to specify
-                the actual path. If no actual path is specified, acts as a
-                as a placeholder in the model (e.g. at the domain level)
-                until a fully specified path definition is applied at a
-                lower level (e.g. at the host level, where available addresses
-                are known.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="pathType">
-                <xs:attribute name="name" type="xs:string" use="required">
-                    <xs:annotation>
-                        <xs:documentation>
-                        The name of the path. Cannot be one of the standard fixed paths
-                        provided by the system:
-
-                        jboss.home - the root directory of the JBoss AS distribution
-                        user.home - user's home directory
-                        user.dir - user's current working directory
-                        java.home - java installation directory
-                        jboss.server.base.dir - root directory for an individual server
-                                                instance
-
-                        Note that the system provides other standard paths that can be
-                        overridden by declaring them in the configuration file. See
-                        the 'relative-to' attribute documentation for a complete
-                        list of standard paths.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="pathType">
-        <xs:attribute name="path">
-            <xs:annotation>
-                <xs:documentation>
-                The actual filesystem path. Treated as an absolute path, unless the
-                'relative-to' attribute is specified, in which case the value
-                is treated as relative to that path.
-
-                If treated as an absolute path, the actual runtime pathname specified
-                by the value of this attribute will be determined as follows:
-
-                If this value is already absolute, then the value is directly
-                used.  Otherwise the runtime pathname is resolved in a
-                system-dependent way.  On UNIX systems, a relative pathname is
-                made absolute by resolving it against the current user directory.
-                On Microsoft Windows systems, a relative pathname is made absolute
-                by resolving it against the current directory of the drive named by the
-                pathname, if any; if not, it is resolved against the current user
-                directory.
-                </xs:documentation>
-            </xs:annotation>
-            <xs:simpleType>
-                <xs:restriction base="xs:string">
-                    <xs:minLength value="1"></xs:minLength>
-                </xs:restriction>
-            </xs:simpleType>
-        </xs:attribute>
-        <xs:attribute name="relative-to" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                The name of another previously named path, or of one of the
-                standard paths provided by the system. If 'relative-to' is
-                provided, the value of the 'path' attribute is treated as
-                relative to the path specified by this attribute. The standard
-                paths provided by the system include:
-
-                jboss.home - the root directory of the JBoss AS distribution
-                user.home - user's home directory
-                user.dir - user's current working directory
-                java.home - java installation directory
-                jboss.server.base.dir - root directory for an individual server
-                                        instance
-                jboss.server.config.dir - directory in which server configuration
-                                          files are stored.
-                jboss.server.data.dir - directory the server will use for persistent
-                                        data file storage
-                jboss.server.log.dir - directory the server will use for
-                                       log file storage
-                jboss.server.temp.dir - directory the server will use for
-                                       temporary file storage
-                jboss.domain.servers.dir - directory under which a host controller
-                                           will create the working area for
-                                           individual server instances
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="specified-pathsType">
-        <xs:annotation>
-            <xs:documentation>
-                A list of named filesystem paths.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="path" type="specified-pathType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="specified-pathType">
-        <xs:annotation>
-            <xs:documentation>
-                A named filesystem path.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                The name of the path. Cannot be one of the standard fixed paths
-                provided by the system:
-
-                jboss.home.dir - the root directory of the JBoss AS distribution
-                user.home - user's home directory
-                user.dir - user's current working directory
-                java.home - java installation directory
-                jboss.server.base.dir - root directory for an individual server
-                                        instance
-
-                Note that the system provides other standard paths that can be
-                overridden by declaring them in the configuration file. See
-                the 'relative-to' attribute documentation for a complete
-                list of standard paths.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="path" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                The actual filesystem path. Treated as an absolute path, unless the
-                'relative-to' attribute is specified, in which case the value
-                is treated as relative to that path.
-
-                If treated as an absolute path, the actual runtime pathname specified
-                by the value of this attribute will be determined as follows:
-
-                If this value is already absolute, then the value is directly
-                used.  Otherwise the runtime pathname is resolved in a
-                system-dependent way.  On UNIX systems, a relative pathname is
-                made absolute by resolving it against the current user directory.
-                On Microsoft Windows systems, a relative pathname is made absolute
-                by resolving it against the current directory of the drive named by the
-                pathname, if any; if not, it is resolved against the current user
-                directory.
-
-                Note relative path declarations have to use '/' as file separator.
-                </xs:documentation>
-            </xs:annotation>
-            <xs:simpleType>
-                <xs:restriction base="xs:string">
-                    <xs:minLength value="1"></xs:minLength>
-                </xs:restriction>
-            </xs:simpleType>
-        </xs:attribute>
-        <xs:attribute name="relative-to" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                The name of another previously named path, or of one of the
-                standard paths provided by the system. If 'relative-to' is
-                provided, the value of the 'path' attribute is treated as
-                relative to the path specified by this attribute. The standard
-                paths provided by the system include:
-
-                jboss.home.dir - the root directory of the JBoss AS distribution
-                user.home - user's home directory
-                user.dir - user's current working directory
-                java.home - java installation directory
-                jboss.server.base.dir - root directory for an individual server
-                                        instance
-                jboss.server.config.dir - directory in which server configuration
-                                          files are stored.
-                jboss.server.data.dir - directory the server will use for persistent
-                                        data file storage
-                jboss.server.log.dir - directory the server will use for
-                                       log file storage
-                jboss.server.temp.dir - directory the server will use for
-                                       temporary file storage
-                jboss.domain.servers.dir - directory under which a host controller
-                                           will create the working area for
-                                           individual server instances
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <!--  JVM configurations -->
-    <xs:complexType name="jvmsType">
-        <xs:sequence>
-            <xs:element name="jvm" type="namedJvmType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="jvmType">
-        <xs:all minOccurs="0" maxOccurs="1">
-            <xs:element name="heap" type="heapType" minOccurs="0"/>
-            <!-- XX:PermSize, XX:MaxPermSize -->
-            <xs:element name="permgen" type="bounded-memory-sizeType" minOccurs="0"/>
-            <!-- Xss -->
-            <xs:element name="stack" type="memory-sizeType" minOccurs="0"/>
-            <xs:element name="agent-lib" type="jvm-agentLibType" minOccurs="0"/>
-            <xs:element name="agent-path" type="jvm-agentPathType" minOccurs="0"/>
-            <xs:element name="java-agent" type="jvm-javaagentType" minOccurs="0"/>
-            <xs:element name="jvm-options" type="jvm-optionsType" minOccurs="0"/>
-            <xs:element name="environment-variables" type="environmentVariablesType" minOccurs="0"/>
-        </xs:all>
-        <xs:attribute name="java-home" type="xs:string"/>
-        <xs:attribute name="type" default="SUN">
-            <xs:simpleType>
-                <xs:restriction base="xs:token">
-                    <xs:enumeration value="SUN">
-			            <xs:annotation>
-			                <xs:documentation>Allows the full set of JVM options to be set via the jvm schema elements</xs:documentation>
-			            </xs:annotation>
-                    </xs:enumeration>
-                    <xs:enumeration value="IBM">
-                        <xs:annotation>
-                            <xs:documentation>Sets a subset of the JVM options via the jvm schema elements</xs:documentation>
-                        </xs:annotation>
-                    </xs:enumeration>
-                </xs:restriction>
-            </xs:simpleType>
-        </xs:attribute>
-        <xs:attribute name="env-classpath-ignored" default="true" type="xs:boolean"/>
-    </xs:complexType>
-
-    <xs:complexType name="namedJvmType">
-        <xs:complexContent>
-            <xs:extension base="jvmType">
-                <xs:attribute name="name" type="xs:string"/>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="serverJvmType">
-        <xs:complexContent>
-            <xs:extension base="namedJvmType">
-                <xs:attribute name="debug-enabled" type="xs:boolean" default="false"/>
-                <xs:attribute name="debug-options" type="xs:string" />
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="heapType">
-        <xs:attribute name="size" use="optional">
-            <xs:annotation>
-                <xs:documentation>Initial JVM heap size</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="max-size" use="optional">
-            <xs:annotation>
-                <xs:documentation>Maximum JVM heap size</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-optionsType">
-        <xs:sequence>
-            <xs:element name="option" type="jvm-optionType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-optionType">
-        <xs:attribute name="value" use="required">
-            <xs:annotation>
-                <xs:documentation>JVM option value</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-agentLibType">
-        <xs:attribute name="value" use="required">
-            <xs:annotation>
-                <xs:documentation>JVM agent lib value </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-agentPathType">
-        <xs:attribute name="value" use="required">
-            <xs:annotation>
-                <xs:documentation>JVM agent path value </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-javaagentType">
-        <xs:attribute name="value" use="required">
-            <xs:annotation>
-                <xs:documentation>JVM javaagent value </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="bounded-memory-sizeType">
-        <xs:attribute name="size" type="xs:string"/>
-        <xs:attribute name="max-size" type="xs:string"/>
-    </xs:complexType>
-
-    <xs:complexType name="memory-sizeType">
-        <xs:attribute name="size" type="xs:string" use="required"/>
-    </xs:complexType>
-
-    <xs:complexType name="properties-with-boottime">
-        <xs:sequence>
-            <xs:element name="property" type="boottimePropertyType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="properties">
-        <xs:sequence>
-            <xs:element name="property" type="propertyType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="environmentVariablesType">
-        <xs:sequence>
-            <xs:element name="variable" type="propertyType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="propertyType">
-        <xs:attribute name="name" use="required"/>
-        <xs:attribute name="value" use="optional"/>
-    </xs:complexType>
-
-    <xs:complexType name="boottimePropertyType">
-        <xs:complexContent>
-            <xs:extension base="propertyType">
-                <xs:attribute name="boot-time" type="xs:boolean" default="true"/>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-</xs:schema>

jboss-as-7.2.0.Final/docs/schema/jboss-as-config_1_1.xsd

@@ -1,2139 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-  ~ JBoss, Home of Professional Open Source.
-  ~ Copyright 2010, Red Hat, Inc., and individual contributors
-  ~ as indicated by the @author tags. See the copyright.txt file in the
-  ~ distribution for a full listing of individual contributors.
-  ~
-  ~ This is free software; you can redistribute it and/or modify it
-  ~ under the terms of the GNU Lesser General Public License as
-  ~ published by the Free Software Foundation; either version 2.1 of
-  ~ the License, or (at your option) any later version.
-  ~
-  ~ This software is distributed in the hope that it will be useful,
-  ~ but WITHOUT ANY WARRANTY; without even the implied warranty of
-  ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-  ~ Lesser General Public License for more details.
-  ~
-  ~ You should have received a copy of the GNU Lesser General Public
-  ~ License along with this software; if not, write to the Free
-  ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
-  ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
-  -->
-
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
-           xmlns="urn:jboss:domain:1.1"
-           targetNamespace="urn:jboss:domain:1.1"
-           elementFormDefault="qualified"
-           attributeFormDefault="unqualified"
-        >
-
-
-    <xs:element name="domain">
-        <xs:annotation>
-            <xs:documentation>
-                Root element for the master document specifying the core configuration
-                for the servers in a domain. There should be one such master
-                document per domain, available to the host controller that
-                is configured to act as the domain controller.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element name="extensions" type="extensionsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="system-properties" type="properties-with-boottime" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="paths" type="named-pathsType" minOccurs="0" maxOccurs="1" />
-                <xs:element name="profiles" type="profilesType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="interfaces" type="named-interfacesType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="socket-binding-groups" type="socket-binding-groupsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="deployments" type="domain-deploymentsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="server-groups" type="server-groupsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="management-client-content" type="management-client-contentType" minOccurs="0" maxOccurs="1"/>
-            </xs:sequence>
-        </xs:complexType>
-    </xs:element>
-
-    <xs:element name="host">
-        <xs:annotation>
-            <xs:documentation>
-                Root element for a document configuring a host controller and
-                the group of servers under the control of that host controller.
-                The standard usage would be for a domain to have one such host controller
-                on each physical (or virtual) host machine. Emphasis in this
-                document is on enumerating the servers, configuring items that
-                are specific to the host environment (e.g. IP addresses), and
-                on any server-specific configuration settings.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element name="system-properties" type="properties-with-boottime" minOccurs="0"/>
-                <xs:element name="paths" type="specified-pathsType" minOccurs="0" maxOccurs="1" />
-                <xs:element name="vault" type="vaultType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="management" type="host-managementType" minOccurs="1" maxOccurs="1"/>
-                <xs:element name="domain-controller" type="domain-controllerType"/>
-                <xs:element name="interfaces" type="specified-interfacesType" minOccurs="0"/>
-                <xs:element name="jvms" type="jvmsType" minOccurs="0"/>
-                <xs:element name="servers" type="serversType" minOccurs="0"/>
-            </xs:sequence>
-            <xs:attribute name="name" type="xs:string" use="optional">
-                <xs:annotation>
-                    <xs:documentation>
-                        The name to use for this host's host controller. Must be unique across the domain.
-                        If not set, defaults to the runtime value "HOSTNAME" or "COMPUTERNAME" environment variables,
-                        or, if neither environment variable is present, to the value of InetAddress.getLocalHost().getHostName().
-
-                        If the special value "jboss.domain.uuid" is used, a java.util.UUID will be created
-                        and used, based on the value of InetAddress.getLocalHost().
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:attribute>
-        </xs:complexType>
-    </xs:element>
-
-    <xs:element name="server">
-        <xs:annotation>
-            <xs:documentation>
-                Root element for a document specifying the configuration
-                of a single "standalone" server that does not operate
-                as part of a domain.
-
-                Note that this element is distinct from the 'serverType'
-                specified in this schema. The latter type forms part of the
-                configuration of a server that operates as part of a domain.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element name="extensions" type="extensionsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="system-properties" type="properties" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="paths" type="specified-pathsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="vault" type="vaultType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="management" type="server-managementType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="profile" type="standalone-profileType" minOccurs="0"/>
-                <xs:element name="interfaces" type="specified-interfacesType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="socket-binding-group" type="standalone-socket-binding-groupType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="deployments" type="server-deploymentsType" minOccurs="0" maxOccurs="1"/>
-            </xs:sequence>
-            <xs:attribute name="name" type="xs:string" use="optional">
-                <xs:annotation>
-                    <xs:documentation>
-                        The name to use for this server.
-                        If not set, defaults to the runtime value "HOSTNAME" or "COMPUTERNAME" environment variables,
-                        or, if neither environment variable is present, to the value of InetAddress.getLocalHost().getHostName().
-
-                        If the special value "jboss.domain.uuid" is used, a java.util.UUID will be created
-                        and used, based on the value of InetAddress.getLocalHost().
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:attribute>
-        </xs:complexType>
-    </xs:element>
-
-    <xs:complexType name="domain-managementType">
-        <xs:annotation>
-            <xs:documentation>
-                Domain-wide default configuration settings for the management of standalone servers and a Host Controller.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="security-realms" minOccurs="0">
-                <xs:complexType>
-                    <xs:sequence>
-                        <xs:element name="security-realm" type="security-realmType" minOccurs="1"
-                                    maxOccurs="unbounded"/>
-                    </xs:sequence>
-                </xs:complexType>
-            </xs:element>
-            <xs:element name="outbound-connections" minOccurs="0">
-                <xs:complexType>
-                    <xs:sequence>
-                      <xs:element name="ldap" type="ldapType" minOccurs="1" /> <!-- TODO minOccurs only while ldap is only supported connection. -->
-                    </xs:sequence>
-                </xs:complexType>
-            </xs:element>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="host-managementType">
-        <xs:annotation>
-            <xs:documentation>
-                The centralized configuration for the management of a Host Controller.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="domain-managementType">
-                <xs:sequence>
-                    <xs:element name="management-interfaces" type="host-management-interfacesType" minOccurs="1"/>
-                </xs:sequence>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="server-managementType">
-        <xs:annotation>
-            <xs:documentation>
-                The centralized configuration for the management of standalone server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="domain-managementType">
-                <xs:sequence>
-                    <xs:element name="management-interfaces" type="server-management-interfacesType" minOccurs="0"/>
-                </xs:sequence>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="ldapType">
-        <xs:annotation>
-            <xs:documentation>
-                The LDAP connection definition.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of this connection.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="url" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The URL to connect to ldap.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <!-- TODO - Later will be optional if we support GSSAPI to connect to LDAP -->
-        <xs:attribute name="search-dn" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The distinguished name to use when connecting to LDAP to perform searches.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="search-credential" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The credential to use when connecting to perform a search.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="initial-context-factory" type="xs:string" default="com.sun.jndi.ldap.LdapCtxFactory">
-            <xs:annotation>
-                <xs:documentation>
-                    The initial context factory to establish the LdapContext.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="security-realmType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of a security realm for securing access to the management interfaces.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="server-identities" type="server-identitiesType" minOccurs="0" />
-            <xs:element name="authentication" type="authenticationType" minOccurs="0" />
-            <xs:element name="authorization" type="authorizationType" minOccurs="0" />
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of this security-realm, each security-realm must be assigned a unique name.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="authorizationType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration defining how to load the authorization information for the authenticated user.
-
-                After a user has been authenticated additional information such as roles can be loaded and
-                associated with the user for subsequent authorization checks, this type is used to define
-                how the roles are loaded.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="properties" type="propertiesFileType" minOccurs="1" />  <!-- minOccurs="1" while this is the only mech -->
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="server-identitiesType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the identities that represent the server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-          <xs:element name="ssl" type="sslType" minOccurs="0" />
-          <xs:element name="secret" type="secretType" minOccurs="0" />
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="secretType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the secret/password-based identity of this server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="value" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The secret / password - Base64 Encoded
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="sslType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the SSL identity of this server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="keystore" type="keystoreType" />
-        </xs:sequence>
-        <xs:attribute name="protocol" type="xs:string" default="TLS">
-            <xs:annotation>
-                <xs:documentation>
-                    The protocol to use when creating the SSLContext.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="keystoreType">
-        <xs:annotation>
-            <xs:documentation>
-                The keystore configuration for the server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="path" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The path of the keystore.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="relative-to" use="optional" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of another previously named path, or of one of the
-                    standard paths provided by the system. If 'relative-to' is
-                    provided, the value of the 'path' attribute is treated as
-                    relative to the path specified by this attribute.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="password" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The password to open the keystore.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="authenticationType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the server side authentication mechanisms.
-
-                Optionally one truststore can be defined and one username/password based store can be defined.
-                Authentication will first attempt to use the truststore and if this is not available will fall back
-                to the username/password authentication.
-
-                If none of these are specified the only available mechanism will be the local mechanism for the
-                Native interface and the HTTP interface will not be accessible.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="truststore" type="keystoreType" minOccurs="0">
-                <xs:annotation>
-                    <xs:documentation>
-                        Configuration of a keystore to use to create a trust manager to verify clients.
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:element>
-            <xs:choice minOccurs="0">
-                <xs:element name="jaas" type="jaasAuthenticationType" minOccurs="0" />
-                <xs:element name="ldap" type="ldapAuthenticationType" minOccurs="0" />
-                <xs:element name="properties" type="propertiesAuthenticationType" minOccurs="0" />
-                <xs:element name="users" type="usersAuthenticationType" minOccurs="0" />
-            </xs:choice>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="jaasAuthenticationType">
-        <xs:annotation>
-            <xs:documentation>
-                Definition to use a JAAS based configuration for authentication.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name identifying the jaas configuration of LoginModules.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="ldapAuthenticationType">
-        <xs:annotation>
-            <xs:documentation>
-                Definition to use LDAP as the user repository.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="username-filter">
-                <xs:complexType>
-                    <xs:attribute name="attribute" type="xs:string" use="required">
-                        <xs:annotation>
-                            <xs:documentation>
-                                The name of the attribute to search for the user, this filter will then perform
-                                a simple search where the username entered by the user matches the attribute
-                                specified here.
-                            </xs:documentation>
-                        </xs:annotation>
-                    </xs:attribute>
-                </xs:complexType>
-            </xs:element>
-            <xs:element name="advanced-filter">
-                <xs:complexType>
-                    <xs:attribute name="filter" type="xs:string" use="required">
-                        <xs:annotation>
-                            <xs:documentation>
-                                The fully defined filter to be used to search for the user based on their entered
-                                user ID. The filter should contain a variable in the form {0} - this will be
-                                replaced with the username supplied by the user.
-                            </xs:documentation>
-                        </xs:annotation>
-                    </xs:attribute>
-                </xs:complexType>
-            </xs:element>
-        </xs:choice>
-
-        <xs:attribute name="connection" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the connection to use to connect to LDAP.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="base-dn" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The base distinguished name to commence the search for the user.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="recursive" type="xs:boolean" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Should the search be recursive.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="user-dn" type="xs:string" default="dn">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the attribute which is the users distinguished name.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-
-    <xs:complexType name="usersAuthenticationType">
-           <xs:annotation>
-            <xs:documentation>
-                A set of users
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="user" type="userType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="userType">
-        <xs:annotation>
-            <xs:documentation>
-                A single user.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="password" type="xs:string" />
-        </xs:choice>
-        <xs:attribute name="username" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The users username.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="propertiesFileType">
-        <xs:annotation>
-            <xs:documentation>
-                Declaration of a location of a properties file.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="relative-to" use="optional" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of another previously named path, or of one of the
-                    standard paths provided by the system. If 'relative-to' is
-                    provided, the value of the 'path' attribute is treated as
-                    relative to the path specified by this attribute.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="path" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The path of the properties file.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="propertiesAuthenticationType">
-        <xs:annotation>
-            <xs:documentation>
-                Declaration of users stored within properties files.
-
-                The entries within the properties file are username={credentials} with each user
-                being specified on it's own line.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="propertiesFileType">
-                <xs:attribute name="plain-text" type="xs:boolean" default="false">
-                    <xs:annotation>
-                        <xs:documentation>
-                            Are the credentials within the properties file stored in plain text, if not
-                            the {credential} is expected to be the hex encoded Digest hash
-                            of 'username : realm : password'.
-                        </xs:documentation>
-                    </xs:annotation>
-            </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="host-management-interfacesType">
-        <xs:sequence>
-            <xs:element name="native-interface" type="host-native-management-interfaceType"/>
-            <xs:element name="http-interface" type="host-http-management-interfaceType" minOccurs="0"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="management-interfaceType">
-        <xs:attribute name="security-realm" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    The security realm to use for this management interface, the capabilities
-                    of the security realm will be queried to identify the authentication mechanism(s) to
-                    offer.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="host-native-management-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of a host's exposed native management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="management-interfaceType">
-                <xs:sequence>
-                    <xs:element name="socket" type="native-management-socketType"/>
-                </xs:sequence>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="management-socketType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the socket used by host or standalone server's exposed management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="interface" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    Network interface on which the host's socket for
-                    management communication should be opened.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="native-management-socketType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the socket used by host or standalone server's exposed HTTP management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="management-socketType">
-                <xs:attribute name="port" type="xs:int" use="required">
-                    <xs:annotation>
-                        <xs:documentation>
-                            Port on which the host's socket for native
-                            management communication should be opened.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="host-http-management-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of a host's exposed HTTP management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="management-interfaceType">
-                <xs:sequence>
-                    <xs:element name="socket" type="http-management-socketType"/>
-                </xs:sequence>
-                <xs:attribute name="console-enabled" type="xs:boolean" use="optional" default="true"/>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="http-management-socketType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the socket used by host or standalone server's exposed HTTP management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="management-socketType">
-                <xs:attribute name="port" type="xs:int" use="optional">
-                    <xs:annotation>
-                        <xs:documentation>
-                            Port on which the host's socket for
-                            management communication should be opened.
-
-                            If not specified the port will not be opened.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-                <xs:attribute name="secure-port" type="xs:int" use="optional">
-                    <xs:annotation>
-                        <xs:documentation>
-                            Port on which the host's socket for HTTPS
-                            management communication should be opened.
-
-                            If not specified the port will not be opened.
-
-                            If specified the security-realm will be required to obtain
-                            the SSL configuration.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="server-management-interfacesType">
-        <xs:sequence>
-            <xs:element name="native-remoting-interface" type="management-remoting-interfaceType" minOccurs="0"/>
-            <xs:element name="native-interface" type="server-native-management-interfaceType" minOccurs="0"/>
-            <xs:element name="http-interface" type="server-http-management-interfaceType" minOccurs="0"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="server-native-management-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the socket used by host or standalone server's exposed HTTP management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="management-interfaceType">
-                <xs:annotation>
-                    <xs:documentation>
-                        Configuration of the socket to use for the native management interface is a choice
-                        between a direct configuration of the address and port, or a reference to a socket-binding
-                        configuration in the server's socket-binding-group element. The latter is the recommended
-                        approach is it makes it easier to avoid port conflicts by taking advantage of the
-                        socket-binding-group's port-offset configuration. Direct configuration of the address and
-                        ports is provided to preserve backward compatibility.
-                    </xs:documentation>
-                </xs:annotation>
-                <xs:choice>
-                    <xs:element name="socket" type="native-management-socketType"/>
-                    <xs:element name="socket-binding" type="native-management-socket-binding-refType"/>
-                </xs:choice>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="native-management-socket-binding-refType">
-        <xs:annotation>
-            <xs:documentation>
-                Reference to the configuration of the socket to be used by a standalone server's exposed native management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="native" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of a socket-binding configuration declared in the server's socket-binding-group.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="server-http-management-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of a standalone server's exposed HTTP/HTTPS management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="management-interfaceType">
-                <xs:annotation>
-                    <xs:documentation>
-                        Configuration of the socket to use for the HTTP/HTTPS management interface is a choice
-                        between a direct configuration of the address and ports, or a reference to socket-binding
-                        configurations in the server's socket-binding-group element. The latter is the recommended
-                        approach is it makes it easier to avoid port conflicts by taking advantage of the
-                        socket-binding-group's port-offset configuration. Direct configuration of the address and
-                        ports is provided to preserve backward compatibility.
-                    </xs:documentation>
-                </xs:annotation>
-                <xs:choice>
-                    <xs:element name="socket" type="http-management-socketType"/>
-                    <xs:element name="socket-binding" type="http-management-socket-binding-refType"/>
-                </xs:choice>
-                <xs:attribute name="console-enabled" type="xs:boolean" use="optional" default="true"/>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="http-management-socket-binding-refType">
-        <xs:annotation>
-            <xs:documentation>
-                Reference to the configurations of the sockets to be used by a standalone server's exposed HTTP and HTTPS management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="http" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of a socket-binding configuration declared in the server's socket-binding-group to use for a HTTP socket.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="https" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of a socket-binding configuration declared in the server's socket-binding-group to use for a HTTPS socket.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="management-remoting-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                Makes the native management interface available via the connectors set up in the remoting subsystem,
-                using the remoting subsystem's endpoint. This should only be used for a server not for a HC/DC.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="domain-controllerType">
-        <xs:choice>
-            <xs:element name="local" type="domain-controller-localType"/>
-            <xs:element name="remote" type="domain-controller-remoteType"/>
-        </xs:choice>
-    </xs:complexType>
-
-    <xs:complexType name="domain-controller-localType" />
-
-    <xs:complexType name="domain-controller-remoteType">
-        <xs:sequence>
-            <xs:element name="ignored-resources" type="ignored-resourcesType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-        <xs:attribute name="host" type="xs:string" use="required" />
-        <xs:attribute name="port" type="xs:integer" use="required" />
-        <xs:attribute name="security-realm" type="xs:string" use="optional" />
-    </xs:complexType>
-
-    <xs:complexType name="ignored-resourcesType">
-        <xs:annotation>
-            <xs:documentation>
-                Provides names of direct child resources of the domain root resource requests for which the
-                Host Controller should ignore. Only relevant on a slave Host Controller. Configuring such
-                "ignored resources" may help allow a Host Controller from an earlier release to function as a
-                slave to a master Host Controller running a later release, by letting the slave ignore portions
-                of the configuration its version of the software cannot understand. This strategy can only be
-                successful if the servers managed by the slave Host Controller do not reference any of the
-                ignored configuration.
-
-                Supports the following attributes:
-
-                type -- the type of resource (e.g. 'profile' or 'socket-binding-group') certain instances of which
-                        should be ignored. The value corresponds to the 'key' portion of the first element in the
-                        resource's address (e.g. 'profile' in the address /profile=ha/subsystem=web)
-
-                wildcard -- if 'true', all resources of the given type should be ignored.
-
-                Child elements list the names of specific instances of the given type of resource
-                that should be ignored. Each element in the list corresponds to the 'value' portion of
-                the first element in the resource's address (e.g. 'ha' in the address /profile=ha/subsystem=web.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="instance" type="ignored-resource-instanceType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-        <xs:attribute name="type" type="xs:string" use="required" />
-        <xs:attribute name="wildcard" type="xs:boolean" use="optional" default="false" />
-        <xs:attribute name="names" type="xs:string" use="optional" />
-    </xs:complexType>
-
-    <xs:complexType name="ignored-resource-instanceType">
-        <xs:annotation>
-            <xs:documentation>
-                The name of a specific instances of a particular type of resource that should be ignored.
-                The 'name' attribute corresponds to the 'value' portion of the first element in the resource's address
-                (e.g. 'ha' in the address /profile=ha/subsystem=web.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="required" />
-    </xs:complexType>
-
-    <xs:complexType name="serversType">
-        <xs:sequence>
-            <xs:element name="server" type="serverType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="serverType">
-        <xs:all>
-            <xs:element name="paths" type="specified-pathsType" minOccurs="0" maxOccurs="1" />
-
-            <xs:element name="interfaces" type="specified-interfacesType" minOccurs="0"/>
-            <xs:element name="socket-bindings" type="server-socket-bindingsType" minOccurs="0"/>
-
-            <!--<xs:element name="loggers" type="loggersType" minOccurs="0"/>-->
-            <xs:element name="system-properties" type="properties-with-boottime" minOccurs="0"/>
-            <xs:element name="jvm" minOccurs="0" type="serverJvmType"/>
-        </xs:all>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="group" type="xs:string" use="required"/>
-        <xs:attribute name="auto-start" type="xs:boolean" default="true"/>
-    </xs:complexType>
-
-    <xs:complexType name="server-socket-bindingsType">
-        <xs:annotation>
-            <xs:documentation>
-            <![CDATA[
-                Server-specific overrides to the default socket binding configuration inherited from the server group.
-            ]]>
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="socket-binding-group" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                <![CDATA[
-                    The socket binding group to use for the server. If undefined, the socket binding group
-                    specified for the server group is used.
-                ]]>
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="port-offset" type="xs:int" default="0">
-            <xs:annotation>
-                <xs:documentation>
-                <![CDATA[
-                    Increment to apply to the base port values defined in the
-                    referenced socket binding group to derive the values to use on this
-                    server.
-                ]]>
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="extensionsType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of extension modules.</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="extension" type="extensionType" minOccurs="1" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="extensionType">
-        <xs:annotation>
-            <xs:documentation>
-                A module that extends the standard capabilities of a domain
-                or a standalone server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="module" use="required" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>The name of the module</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="server-groupsType">
-        <xs:sequence>
-            <xs:element name="server-group" type="server-groupType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="server-groupType">
-        <xs:sequence>
-            <xs:element name="jvm" type="namedJvmType" minOccurs="0"/>
-            <xs:element name="socket-binding-group" type="socket-binding-group-refType" minOccurs="1"/>
-
-            <xs:element name="deployments" type="server-groupDeploymentsType" minOccurs="0"/>
-
-            <xs:element name="system-properties" minOccurs="0" type="properties-with-boottime"/>
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the server group
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="profile" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the profile this server is running.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="management-subsystem-endpoint" type="xs:boolean" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Set to true to have servers belonging to the server group connect back to the host controller using the
-                    endpoint from their remoting subsystem. The subsystem must be preset for this to
-                    work.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="server-groupDeploymentsType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of deployments that have been mapped to a server-group.</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="deployment" type="base-deploymentType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="server-groupDeploymentType">
-        <xs:annotation>
-            <xs:documentation>A deployment that has been mapped to a server group.</xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="base-deploymentType">
-                <!--  TODO clarify what a value of 'false' means -->
-                <xs:attribute name="enabled" use="optional" type="xs:boolean" default="true">
-                    <xs:annotation>
-                        <xs:documentation>Whether the deployment deploy automatically when the server starts up.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="base-deploymentType">
-        <xs:attribute name="name" use="required">
-            <xs:annotation>
-                <xs:documentation>Unique identifier of the deployment. Must be unique across all deployments.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="runtime-name" use="required">
-            <xs:annotation>
-                <xs:documentation>Name by which the deployment will be known within a running server.of the deployment.
-                    Does not need to be unique across all deployments in the domain, although it must be unique within
-                    an individual server. For example, two different deployments running on different servers in
-                    the domain could both have a 'runtime-name' of 'example.war', with one having a 'name'
-                    of 'example.war_v1' and another with an 'name' of 'example.war_v2'.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="server-deploymentsType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of deployments that have been mapped to a server.</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="deployment" type="server-deploymentType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="server-deploymentType">
-        <xs:annotation>
-            <xs:documentation>A deployment that has been mapped to a server.</xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="base-deploymentType">
-                <xs:sequence>
-                    <!-- TODO: maxOccurs should be unbounded once overlays are in place -->
-                    <xs:choice maxOccurs="1">
-                        <xs:element name="content" type="contentType"/>
-                        <xs:element name="fs-archive" type="fs-archiveType"/>
-                        <xs:element name="fs-exploded" type="fs-explodedType"/>
-                    </xs:choice>
-                </xs:sequence>
-                <!--  TODO clarify what a value of 'false' means -->
-                <xs:attribute name="enabled" use="optional" type="xs:boolean" default="true">
-                    <xs:annotation>
-                        <xs:documentation>Whether the deployment deploy automatically when the server starts up.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="contentType">
-        <xs:attribute name="sha1" use="required">
-            <xs:annotation>
-                <xs:documentation>The checksum of the content</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="fs-archiveType">
-        <xs:annotation>
-            <xs:documentation>Archived content found on the filesystem</xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="fs-baseType"/>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="fs-baseType">
-        <xs:complexContent>
-            <xs:extension base="pathType"/>
-        </xs:complexContent>
-        <!-- TODO: make path required
-        <xs:complexContent>
-            <xs:restriction base="pathType">
-                <xs:attribute name="path" use="required"/>
-            </xs:restriction>
-        </xs:complexContent>
-        -->
-    </xs:complexType>
-
-    <xs:complexType name="fs-explodedType">
-        <xs:annotation>
-            <xs:documentation>Exploded content found on the filesystem</xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="fs-baseType"/>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="domain-deploymentsType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of domain-level deployments</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="deployment" type="domain-deploymentType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="domain-deploymentType">
-        <xs:annotation>
-            <xs:documentation>Deployment represents anything that can be deployed (e.g. an application such as EJB-JAR,
-                WAR, EAR,
-                any kind of standard archive such as RAR or JBoss-specific deployment),
-                which can be enabled or disabled on a domain level.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="base-deploymentType">
-                <xs:sequence>
-                    <!-- TODO: maxOccurs should be unbounded once overlays are in place -->
-                    <xs:choice maxOccurs="1">
-                        <xs:element name="content" type="contentType"/>
-                        <xs:element name="fs-archive" type="fs-archiveType"/>
-                        <xs:element name="fs-exploded" type="fs-explodedType"/>
-                    </xs:choice>
-                </xs:sequence>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <!-- TODO this is not used anywhere yet -->
-    <xs:complexType name="clustersType">
-        <xs:complexContent>
-            <xs:extension base="server-groupType">
-                <xs:sequence>
-                    <xs:element name="partition-name" type="xs:string"/>
-                    <xs:element name="state-transfer-timeout" type="xs:integer"/>
-                    <xs:element name="method-call-timeout" type="xs:integer"/>
-                </xs:sequence>
-                <xs:attribute name="category" type="xs:string" use="required"/>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <!-- domain-configuration related definitions -->
-    <xs:complexType name="domain-configurationType">
-        <xs:annotation>
-            <xs:documentation>The domain controller/server bootstrap configuration</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element ref="bootstrapURI"/>
-        </xs:sequence>
-    </xs:complexType>
-    <xs:element name="bootstrapURI" type="xs:string">
-        <xs:annotation>
-            <xs:documentation>The URI for bootstrapping a domain server</xs:documentation>
-        </xs:annotation>
-    </xs:element>
-
-    <xs:complexType name="profilesType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of profiles available for use in the domain</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="profile" type="domain-profileType" minOccurs="1" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="domain-profileType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of subsystems</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded">
-                <xs:annotation>
-                    <xs:documentation>A profile declaration may include configuration
-                        elements from other namespaces for the subsystems that make up the profile.
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:any>
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>Name of the profile</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="standalone-profileType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of subsystems</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:choice minOccurs="1" maxOccurs="unbounded">
-                <xs:any namespace="##other">
-                    <xs:annotation>
-                        <xs:documentation>A profile declaration may include configuration
-                            elements from other namespaces for the subsystems that make up the profile.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:any>
-            </xs:choice>
-        </xs:sequence>
-    </xs:complexType>
-
-    <!-- general socket definition -->
-    <xs:complexType name="socket-binding-groupsType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of socket binding groups</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="socket-binding-group" type="socket-binding-groupType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="socket-binding-groupType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of socket configurations</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="socket-binding" type="socket-bindingType" maxOccurs="unbounded"/>
-            <xs:element name="outbound-socket-binding" type="outbound-socket-bindingType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="default-interface" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of an interface that should be used as the interface for
-                    any sockets that do not explicitly declare one.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="standalone-socket-binding-groupType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of socket configurations</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="socket-binding" type="socket-bindingType" maxOccurs="unbounded"/>
-            <xs:element name="outbound-socket-binding" type="outbound-socket-bindingType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="default-interface" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of an interface that should be used as the interface for
-                    any sockets that do not explicitly declare one.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-	    <xs:attribute name="port-offset" type="xs:int" use="optional" default="0">
-	        <xs:annotation>
-                <xs:documentation>
-	                    Increment to apply to the base port values defined in the
-	                    socket group to derive the values to use on this
-	                    server.
-	            </xs:documentation>
-	        </xs:annotation>
-	    </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="socket-bindingType">
-        <xs:annotation>
-            <xs:documentation>Configuration information for a socket.</xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="client-mapping" type="socket-binding-client-mappingType"
-                        minOccurs="0" maxOccurs="unbounded">
-                <xs:annotation>
-                    <xs:documentation>
-                        Specifies zero or more client mappings for this socket binding.
-                        A client connecting to this socket should use the destination address
-                        specified in the mapping that matches its desired outbound interface.
-                        This allows for advanced network topologies that use either network
-                        address translation, or have bindings on multiple network interfaces
-                        to function.
-
-                        Each mapping should be evaluated in declared order, with the first successful
-                        match used to determine the destination.
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:element>
-        </xs:choice>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="interface" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of the interface to which the socket should be bound, or, for multicast
-                    sockets, the interface on which it should listen. This should
-                    be one of the declared interfaces.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="port" type="xs:unsignedShort" use="optional" default="0">
-            <xs:annotation>
-                <xs:documentation>
-                    Number of the port to which the socket should be bound.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="fixed-port" type="xs:boolean" use="optional" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Whether the port value should remain fixed even if numerically offsets
-                    are applied to the other sockets in the socket group..
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="multicast-address" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Multicast address on which the socket should receive multicast
-                    traffic. If unspecified, the socket will not be configured
-                    to receive multicast.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="multicast-port" type="xs:positiveInteger" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Port on which the socket should receive multicast
-                    traffic. Must be configured if 'multicast-address' is configured.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="socket-binding-client-mappingType">
-        <xs:annotation>
-                <xs:documentation>
-                    Type definition for a client mapping on a socket binding. A client
-                    mapping specifies how external clients should connect to this
-                    socket's port, provided that the client's outbound interface
-                    match the specified source network value.
-                </xs:documentation>
-            </xs:annotation>
-        <xs:attribute name="source-network" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Source network the client connection binds on. This value is in
-                    the form of ip/netmask. A client should match this value against
-                    the desired client host network interface, and if matched the
-                    client should connect to the corresponding destination values.
-
-                    If omitted this mapping should match any interface.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="destination-address" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The destination address that a client should connect to if the
-                    source-network matches. This value can either be a hostname or
-                    an ip address.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="destination-port" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    The destination port that a client should connect to if the
-                    source-network matches.
-
-                    If omitted this mapping will reuse the effective socket binding
-                    port.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="outbound-socket-bindingType">
-        <xs:annotation>
-            <xs:documentation>Configuration information for a outbound socket.</xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="remote-destination" type="remote-destinationType" maxOccurs="1"/>
-            <xs:element name="local-destination" type="local-destinationType" maxOccurs="1"/>
-        </xs:choice>
-
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the outbound socket binding
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="source-interface" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the interface that should be used for setting up the source address of the
-                    outbound socket. This should be one of the declared interfaces.
-                </xs:documentation>
-            </xs:annotation>
-
-        </xs:attribute>
-        <xs:attribute name="source-port" type="xs:positiveInteger" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    The port number that will be used for setting the source addresss of the outbound socket. If the
-                    source-interface attribute has been specified and the source-port attribute is absent,
-                    then the system uses a ephemeral port while binding the socket to a source address.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="fixed-source-port" type="xs:boolean" use="optional" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Whether the source-port value should remain fixed even if the socket binding group specifies
-                    a port offset
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="remote-destinationType">
-        <xs:attribute name="host" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The remote server address to which the outbound socket has to be connect.
-                    The address can be either a IP address of the host server of the hostname of the server
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="port" type="xs:positiveInteger" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The remote port to which the outbound socket has to connect.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="local-destinationType">
-        <xs:attribute name="socket-binding-ref" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The reference to a socket binding that has to be used as the destination for the outbound
-                    socket binding. This socket binding name should belong to the same socket binding group
-                    to which this local destination client socket belongs.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="socket-binding-group-refType">
-        <xs:attribute name="ref" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The socket group to use for the server group or server.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="port-offset" type="xs:int" default="0">
-            <xs:annotation>
-                <xs:documentation>
-                    Increment to apply to the base port values defined in the
-                    referenced socket group to derive the values to use on this
-                    server.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-
-    <xs:complexType name="named-interfacesType">
-        <xs:annotation>
-            <xs:documentation>
-                A list of named network interfaces. The interfaces may or may
-                not be fully specified (i.e. include criteria on how to determine
-                their IP address.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="interface" type="named-interfaceType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <!-- TODO make this and specified-interfaceType the same except for interface-criteriaGroup minOccurs -->
-    <xs:complexType name="named-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                A named network interface, but without any criteria
-                for determining the IP address to associate with that interface.
-                Acts as a placeholder in the model (e.g. at the domain level)
-                until a fully specified interface definition is applied at a
-                lower level (e.g. at the server level, where available addresses
-                are known.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:group ref="interface-criteriaGroup" minOccurs="0"/>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-    </xs:complexType>
-
-    <xs:complexType name="specified-interfacesType">
-        <xs:annotation>
-            <xs:documentation>
-                A list of fully specified named network interfaces.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="interface" type="specified-interfaceType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="specified-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                A named network interface, along with required criteria
-                for determining the IP address to associate with that interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:group ref="interface-criteriaGroup" minOccurs="1"/>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-    </xs:complexType>
-
-    <xs:group name="interface-criteriaGroup">
-        <xs:annotation>
-            <xs:documentation>
-                A set of criteria that can be used at runtime to determine
-                what IP address to use for an interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="any-address" type="any-addressType"/>
-            <xs:element name="any-ipv6-address" type="any-ipv6-addressType"/>
-            <xs:element name="any-ipv4-address" type="any-ipv4-addressType"/>
-            <xs:choice maxOccurs="unbounded">
-                <xs:element name="inet-address" type="inet-addressType"/>
-                <xs:element name="loopback" type="loopbackType"/>
-                <xs:element name="loopback-address" type="loopback-addressType"/>
-                <xs:element name="multicast" type="multicastType"/>
-                <xs:element name="point-to-point" type="point-to-pointType"/>
-                <xs:element name="virtual" type="interface-virtualType"/>
-                <xs:element name="up" type="interface-upType"/>
-                <xs:element name="public-address" type="public-addressType"/>
-                <xs:element name="link-local-address" type="link-local-addressType"/>
-                <xs:element name="site-local-address" type="site-local-addressType"/>
-                <xs:element name="nic" type="nicType"/>
-                <xs:element name="nic-match" type="nic-matchType"/>
-                <xs:element name="subnet-match" type="subnet-matchType"/>
-                <xs:element name="not" type="address-exclusionType"/>
-                <xs:element name="any" type="address-exclusionType"/>
-            </xs:choice>
-        </xs:choice>
-    </xs:group>
-
-    <xs:complexType name="inet-addressType">
-        <xs:attribute name="value" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    Either a IP address in IPv6 or IPv4 dotted decimal notation,
-                    or a hostname that can be resolved to an IP address.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="nicType">
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of a network interface (e.g. eth0, eth1, lo).
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="nic-matchType">
-        <xs:attribute name="pattern" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    A regular expression against which the names of the network
-                    interfaces available on the machine can be matched to find
-                    an acceptable interface.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="subnet-matchType">
-        <xs:attribute name="value" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    A network IP address and the number of bits in the
-                    address' network prefix, written in "slash notation";
-                    e.g. "192.168.0.0/16".
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="address-exclusionType">
-        <xs:choice>
-            <xs:element name="inet-address" type="inet-addressType" minOccurs="0" maxOccurs="unbounded"/>
-            <xs:element name="loopback" type="loopbackType"/>
-            <xs:element name="loopback-address" type="loopback-addressType"/>
-            <xs:element name="multicast" type="multicastType"/>
-            <xs:element name="point-to-point" type="point-to-pointType"/>
-            <xs:element name="virtual" type="interface-virtualType"/>
-            <xs:element name="up" type="interface-upType"/>
-            <xs:element name="public-address" type="public-addressType"/>
-            <xs:element name="link-local-address" type="link-local-addressType"/>
-            <xs:element name="site-local-address" type="site-local-addressType"/>
-            <xs:element name="nic" type="nicType" minOccurs="0" maxOccurs="unbounded"/>
-            <xs:element name="nic-match" type="nic-matchType" minOccurs="0" maxOccurs="unbounded"/>
-            <xs:element name="subnet-match" type="subnet-matchType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:choice>
-    </xs:complexType>
-
-    <xs:complexType name="loopbackType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it is a loopback
-                interface.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="loopback-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                A loopback address that may not actually be configured on the machine's loopback interface.
-                Differs from inet-addressType in that the given value will be used even if no NIC can
-                be found that has the IP address associated with it.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="value" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    An IP address in IPv6 or IPv4 dotted decimal notation.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="multicastType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it supports
-                multicast.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="point-to-pointType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it is a point-to-point
-                interface.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="interface-upType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it is currently up.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="interface-virtualType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it is a virtual
-                interface.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="public-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it has a publicly
-                routable address.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="site-local-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not an address associated
-                with it is site-local.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="link-local-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not an address associated
-                with it is link-local.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="any-ipv6-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that sockets using this interface
-                should be bound to the IPv6 wildcard address (::).
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="any-ipv4-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that sockets using this interface
-                should be bound to the IPv4 wildcard address (0.0.0.0).
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="any-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that sockets using this interface
-                should be bound to a wildcard address. The IPv6 wildcard
-                address (::) will be used unless the java.net.preferIpV4Stack
-                system property is set to true, in which case the IPv4
-                wildcard address (0.0.0.0) will be used. If a socket is
-                bound to an IPv6 anylocal address on a dual-stack machine,
-                it can accept both IPv6 and IPv4 traffic; if it is bound to
-                an IPv4 (IPv4-mapped) anylocal address, it can only accept
-                IPv4 traffic.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="socketType">
-        <xs:annotation>
-            <xs:documentation>Configuration information for a socket.</xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="interface" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of the interface to which the socket should be bound, or, for multicast
-                    sockets, the interface on which it should listen. This should
-                    be one of the declared interfaces.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="port" type="xs:unsignedShort" use="optional" default="0">
-            <xs:annotation>
-                <xs:documentation>
-                    Number of the port to which the socket should be bound.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="fixed-port" type="xs:boolean" use="optional" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Whether the port value should remain fixed even if numerically offsets
-                    are applied to the other sockets in the socket group..
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="multicast-address" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Multicast address on which the socket should receive multicast
-                    traffic. If unspecified, the socket will not be configured
-                    to receive multicast.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="multicast-port" type="xs:positiveInteger" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Port on which the socket should receive multicast
-                    traffic. If unspecified, the socket will not be configured
-                    to receive multicast.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <!-- Path configurations -->
-    <xs:complexType name="named-pathsType">
-        <xs:annotation>
-            <xs:documentation>
-                A list of named filesystem paths. The paths may or may
-                not be fully specified (i.e. include the actual paths.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="path" type="named-pathType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="named-pathType">
-        <xs:annotation>
-            <xs:documentation>
-                A named filesystem path, but without a requirement to specify
-                the actual path. If no actual path is specified, acts as a
-                as a placeholder in the model (e.g. at the domain level)
-                until a fully specified path definition is applied at a
-                lower level (e.g. at the host level, where available addresses
-                are known.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="pathType">
-                <xs:attribute name="name" type="xs:string" use="required">
-                    <xs:annotation>
-                        <xs:documentation>
-                        The name of the path. Cannot be one of the standard fixed paths
-                        provided by the system:
-
-                        jboss.home - the root directory of the JBoss AS distribution
-                        user.home - user's home directory
-                        user.dir - user's current working directory
-                        java.home - java installation directory
-                        jboss.server.base.dir - root directory for an individual server
-                                                instance
-
-                        Note that the system provides other standard paths that can be
-                        overridden by declaring them in the configuration file. See
-                        the 'relative-to' attribute documentation for a complete
-                        list of standard paths.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="pathType">
-        <xs:attribute name="path">
-            <xs:annotation>
-                <xs:documentation>
-                The actual filesystem path. Treated as an absolute path, unless the
-                'relative-to' attribute is specified, in which case the value
-                is treated as relative to that path.
-
-                If treated as an absolute path, the actual runtime pathname specified
-                by the value of this attribute will be determined as follows:
-
-                If this value is already absolute, then the value is directly
-                used.  Otherwise the runtime pathname is resolved in a
-                system-dependent way.  On UNIX systems, a relative pathname is
-                made absolute by resolving it against the current user directory.
-                On Microsoft Windows systems, a relative pathname is made absolute
-                by resolving it against the current directory of the drive named by the
-                pathname, if any; if not, it is resolved against the current user
-                directory.
-                </xs:documentation>
-            </xs:annotation>
-            <xs:simpleType>
-                <xs:restriction base="xs:string">
-                    <xs:minLength value="1"/>
-                </xs:restriction>
-            </xs:simpleType>
-        </xs:attribute>
-        <xs:attribute name="relative-to" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                The name of another previously named path, or of one of the
-                standard paths provided by the system. If 'relative-to' is
-                provided, the value of the 'path' attribute is treated as
-                relative to the path specified by this attribute. The standard
-                paths provided by the system include:
-
-                jboss.home - the root directory of the JBoss AS distribution
-                user.home - user's home directory
-                user.dir - user's current working directory
-                java.home - java installation directory
-                jboss.server.base.dir - root directory for an individual server
-                                        instance
-                jboss.server.config.dir - directory in which server configuration
-                                          files are stored.
-                jboss.server.data.dir - directory the server will use for persistent
-                                        data file storage
-                jboss.server.log.dir - directory the server will use for
-                                       log file storage
-                jboss.server.temp.dir - directory the server will use for
-                                       temporary file storage
-                jboss.domain.servers.dir - directory under which a host controller
-                                           will create the working area for
-                                           individual server instances
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="specified-pathsType">
-        <xs:annotation>
-            <xs:documentation>
-                A list of named filesystem paths.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="path" type="specified-pathType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="specified-pathType">
-        <xs:annotation>
-            <xs:documentation>
-                A named filesystem path.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                The name of the path. Cannot be one of the standard fixed paths
-                provided by the system:
-
-                jboss.home.dir - the root directory of the JBoss AS distribution
-                user.home - user's home directory
-                user.dir - user's current working directory
-                java.home - java installation directory
-                jboss.server.base.dir - root directory for an individual server
-                                        instance
-
-                Note that the system provides other standard paths that can be
-                overridden by declaring them in the configuration file. See
-                the 'relative-to' attribute documentation for a complete
-                list of standard paths.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="path" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                The actual filesystem path. Treated as an absolute path, unless the
-                'relative-to' attribute is specified, in which case the value
-                is treated as relative to that path.
-
-                If treated as an absolute path, the actual runtime pathname specified
-                by the value of this attribute will be determined as follows:
-
-                If this value is already absolute, then the value is directly
-                used.  Otherwise the runtime pathname is resolved in a
-                system-dependent way.  On UNIX systems, a relative pathname is
-                made absolute by resolving it against the current user directory.
-                On Microsoft Windows systems, a relative pathname is made absolute
-                by resolving it against the current directory of the drive named by the
-                pathname, if any; if not, it is resolved against the current user
-                directory.
-
-                Note relative path declarations have to use '/' as file separator.
-                </xs:documentation>
-            </xs:annotation>
-            <xs:simpleType>
-                <xs:restriction base="xs:string">
-                    <xs:minLength value="1"/>
-                </xs:restriction>
-            </xs:simpleType>
-        </xs:attribute>
-        <xs:attribute name="relative-to" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                The name of another previously named path, or of one of the
-                standard paths provided by the system. If 'relative-to' is
-                provided, the value of the 'path' attribute is treated as
-                relative to the path specified by this attribute. The standard
-                paths provided by the system include:
-
-                jboss.home.dir - the root directory of the JBoss AS distribution
-                user.home - user's home directory
-                user.dir - user's current working directory
-                java.home - java installation directory
-                jboss.server.base.dir - root directory for an individual server
-                                        instance
-                jboss.server.config.dir - directory in which server configuration
-                                          files are stored.
-                jboss.server.data.dir - directory the server will use for persistent
-                                        data file storage
-                jboss.server.log.dir - directory the server will use for
-                                       log file storage
-                jboss.server.temp.dir - directory the server will use for
-                                       temporary file storage
-                jboss.domain.servers.dir - directory under which a host controller
-                                           will create the working area for
-                                           individual server instances
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <!--  JVM configurations -->
-    <xs:complexType name="jvmsType">
-        <xs:sequence>
-            <xs:element name="jvm" type="namedJvmType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="jvmType">
-        <xs:all minOccurs="0" maxOccurs="1">
-            <xs:element name="heap" type="heapType" minOccurs="0"/>
-            <!-- XX:PermSize, XX:MaxPermSize -->
-            <xs:element name="permgen" type="bounded-memory-sizeType" minOccurs="0"/>
-            <!-- Xss -->
-            <xs:element name="stack" type="memory-sizeType" minOccurs="0"/>
-            <xs:element name="agent-lib" type="jvm-agentLibType" minOccurs="0"/>
-            <xs:element name="agent-path" type="jvm-agentPathType" minOccurs="0"/>
-            <xs:element name="java-agent" type="jvm-javaagentType" minOccurs="0"/>
-            <xs:element name="jvm-options" type="jvm-optionsType" minOccurs="0"/>
-            <xs:element name="environment-variables" type="environmentVariablesType" minOccurs="0"/>
-        </xs:all>
-        <xs:attribute name="java-home" type="xs:string"/>
-        <xs:attribute name="type" default="SUN">
-            <xs:simpleType>
-                <xs:restriction base="xs:token">
-                    <xs:enumeration value="SUN">
-			            <xs:annotation>
-			                <xs:documentation>Allows the full set of JVM options to be set via the jvm schema elements</xs:documentation>
-			            </xs:annotation>
-                    </xs:enumeration>
-                    <xs:enumeration value="IBM">
-                        <xs:annotation>
-                            <xs:documentation>Sets a subset of the JVM options via the jvm schema elements</xs:documentation>
-                        </xs:annotation>
-                    </xs:enumeration>
-                </xs:restriction>
-            </xs:simpleType>
-        </xs:attribute>
-        <xs:attribute name="env-classpath-ignored" default="true" type="xs:boolean"/>
-    </xs:complexType>
-
-    <xs:complexType name="namedJvmType">
-        <xs:complexContent>
-            <xs:extension base="jvmType">
-                <xs:attribute name="name" type="xs:string"/>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="serverJvmType">
-        <xs:complexContent>
-            <xs:extension base="namedJvmType">
-                <xs:attribute name="debug-enabled" type="xs:boolean" default="false"/>
-                <xs:attribute name="debug-options" type="xs:string" />
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="heapType">
-        <xs:attribute name="size" use="optional">
-            <xs:annotation>
-                <xs:documentation>Initial JVM heap size</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="max-size" use="optional">
-            <xs:annotation>
-                <xs:documentation>Maximum JVM heap size</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-optionsType">
-        <xs:sequence>
-            <xs:element name="option" type="jvm-optionType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-optionType">
-        <xs:attribute name="value" use="required">
-            <xs:annotation>
-                <xs:documentation>JVM option value</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-agentLibType">
-        <xs:attribute name="value" use="required">
-            <xs:annotation>
-                <xs:documentation>JVM agent lib value </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-agentPathType">
-        <xs:attribute name="value" use="required">
-            <xs:annotation>
-                <xs:documentation>JVM agent path value </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-javaagentType">
-        <xs:attribute name="value" use="required">
-            <xs:annotation>
-                <xs:documentation>JVM javaagent value </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="bounded-memory-sizeType">
-        <xs:attribute name="size" type="xs:string"/>
-        <xs:attribute name="max-size" type="xs:string"/>
-    </xs:complexType>
-
-    <xs:complexType name="memory-sizeType">
-        <xs:attribute name="size" type="xs:string" use="required"/>
-    </xs:complexType>
-
-    <xs:complexType name="properties-with-boottime">
-        <xs:sequence>
-            <xs:element name="property" type="boottimePropertyType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="properties">
-        <xs:sequence>
-            <xs:element name="property" type="propertyType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="environmentVariablesType">
-        <xs:sequence>
-            <xs:element name="variable" type="propertyType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="propertyType">
-        <xs:attribute name="name" use="required"/>
-        <xs:attribute name="value" use="optional"/>
-    </xs:complexType>
-
-    <xs:complexType name="boottimePropertyType">
-        <xs:complexContent>
-            <xs:extension base="propertyType">
-                <xs:attribute name="boot-time" type="xs:boolean" default="true"/>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-   <xs:complexType name="vaultType">
-      <xs:annotation>
-         <xs:documentation>
-               <![CDATA[
-                    Vault Configuration.
-                ]]>
-         </xs:documentation>
-      </xs:annotation>
-      <xs:sequence>
-          <xs:element name="vault-option" type="propertyType" minOccurs="0" maxOccurs="unbounded"/>
-      </xs:sequence>
-      <xs:attribute name="code" type="xs:string" use="optional"/>
-   </xs:complexType>
-
-    <xs:complexType name="management-client-contentType">
-        <xs:annotation>
-            <xs:documentation>
-                <![CDATA[
-                   Storage information about re-usable chunks of data useful to management clients that are stored
-                   in the domain content repository.
-                ]]>
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="rollout-plans" type="contentType" minOccurs="0" maxOccurs="1">
-                <xs:annotation>
-                    <xs:documentation>
-                        <![CDATA[
-                           Storage information about a set of named management update rollout plans useful to management
-                           clients that are stored in the domain content repository. The management API exposed by the domain
-                           controller provides access to these plans to management clients, allowing clients to use the plans
-                           by referencing them by name, avoiding the need to recreate them for each use.
-                        ]]>
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:element>
-        </xs:sequence>
-    </xs:complexType>
-
-
-</xs:schema>

jboss-as-7.2.0.Final/docs/schema/jboss-as-config_1_2.xsd

@@ -1,2162 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-  ~ JBoss, Home of Professional Open Source.
-  ~ Copyright 2012, Red Hat, Inc., and individual contributors
-  ~ as indicated by the @author tags. See the copyright.txt file in the
-  ~ distribution for a full listing of individual contributors.
-  ~
-  ~ This is free software; you can redistribute it and/or modify it
-  ~ under the terms of the GNU Lesser General Public License as
-  ~ published by the Free Software Foundation; either version 2.1 of
-  ~ the License, or (at your option) any later version.
-  ~
-  ~ This software is distributed in the hope that it will be useful,
-  ~ but WITHOUT ANY WARRANTY; without even the implied warranty of
-  ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-  ~ Lesser General Public License for more details.
-  ~
-  ~ You should have received a copy of the GNU Lesser General Public
-  ~ License along with this software; if not, write to the Free
-  ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
-  ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
-  -->
-
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
-           xmlns="urn:jboss:domain:1.2"
-           targetNamespace="urn:jboss:domain:1.2"
-           elementFormDefault="qualified"
-           attributeFormDefault="unqualified"
-        >
-
-
-    <xs:element name="domain">
-        <xs:annotation>
-            <xs:documentation>
-                Root element for the master document specifying the core configuration
-                for the servers in a domain. There should be one such master
-                document per domain, available to the host controller that
-                is configured to act as the domain controller.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element name="extensions" type="extensionsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="system-properties" type="properties-with-boottime" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="paths" type="named-pathsType" minOccurs="0" maxOccurs="1" />
-                <xs:element name="profiles" type="profilesType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="interfaces" type="named-interfacesType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="socket-binding-groups" type="socket-binding-groupsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="deployments" type="domain-deploymentsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="server-groups" type="server-groupsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="management-client-content" type="management-client-contentType" minOccurs="0" maxOccurs="1"/>
-            </xs:sequence>
-        </xs:complexType>
-    </xs:element>
-
-    <xs:element name="host">
-        <xs:annotation>
-            <xs:documentation>
-                Root element for a document configuring a host controller and
-                the group of servers under the control of that host controller.
-                The standard usage would be for a domain to have one such host controller
-                on each physical (or virtual) host machine. Emphasis in this
-                document is on enumerating the servers, configuring items that
-                are specific to the host environment (e.g. IP addresses), and
-                on any server-specific configuration settings.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element name="system-properties" type="properties-with-boottime" minOccurs="0"/>
-                <xs:element name="paths" type="specified-pathsType" minOccurs="0" maxOccurs="1" />
-                <xs:element name="vault" type="vaultType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="management" type="host-managementType" minOccurs="1" maxOccurs="1"/>
-                <xs:element name="domain-controller" type="domain-controllerType"/>
-                <xs:element name="interfaces" type="specified-interfacesType" minOccurs="0"/>
-                <xs:element name="jvms" type="jvmsType" minOccurs="0"/>
-                <xs:element name="servers" type="serversType" minOccurs="0"/>
-            </xs:sequence>
-            <xs:attribute name="name" type="xs:string" use="optional">
-                <xs:annotation>
-                    <xs:documentation>
-                        The name to use for this host's host controller. Must be unique across the domain.
-                        If not set, defaults to the runtime value "HOSTNAME" or "COMPUTERNAME" environment variables,
-                        or, if neither environment variable is present, to the value of InetAddress.getLocalHost().getHostName().
-
-                        If the special value "jboss.domain.uuid" is used, a java.util.UUID will be created
-                        and used, based on the value of InetAddress.getLocalHost().
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:attribute>
-        </xs:complexType>
-    </xs:element>
-
-    <xs:element name="server">
-        <xs:annotation>
-            <xs:documentation>
-                Root element for a document specifying the configuration
-                of a single "standalone" server that does not operate
-                as part of a domain.
-
-                Note that this element is distinct from the 'serverType'
-                specified in this schema. The latter type forms part of the
-                configuration of a server that operates as part of a domain.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element name="extensions" type="extensionsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="system-properties" type="properties" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="paths" type="specified-pathsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="vault" type="vaultType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="management" type="server-managementType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="profile" type="standalone-profileType" minOccurs="0"/>
-                <xs:element name="interfaces" type="specified-interfacesType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="socket-binding-group" type="standalone-socket-binding-groupType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="deployments" type="server-deploymentsType" minOccurs="0" maxOccurs="1"/>
-            </xs:sequence>
-            <xs:attribute name="name" type="xs:string" use="optional">
-                <xs:annotation>
-                    <xs:documentation>
-                        The name to use for this server.
-                        If not set, defaults to the runtime value "HOSTNAME" or "COMPUTERNAME" environment variables,
-                        or, if neither environment variable is present, to the value of InetAddress.getLocalHost().getHostName().
-
-                        If the special value "jboss.domain.uuid" is used, a java.util.UUID will be created
-                        and used, based on the value of InetAddress.getLocalHost().
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:attribute>
-        </xs:complexType>
-    </xs:element>
-
-    <xs:complexType name="domain-managementType">
-        <xs:annotation>
-            <xs:documentation>
-                Domain-wide default configuration settings for the management of standalone servers and a Host Controller.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="security-realms" minOccurs="0">
-                <xs:complexType>
-                    <xs:sequence>
-                        <xs:element name="security-realm" type="security-realmType" minOccurs="1"
-                                    maxOccurs="unbounded"/>
-                    </xs:sequence>
-                </xs:complexType>
-            </xs:element>
-            <xs:element name="outbound-connections" minOccurs="0">
-                <xs:complexType>
-                    <xs:sequence>
-                      <xs:element name="ldap" type="ldapType" minOccurs="1" /> <!-- TODO minOccurs only while ldap is only supported connection. -->
-                    </xs:sequence>
-                </xs:complexType>
-            </xs:element>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="host-managementType">
-        <xs:annotation>
-            <xs:documentation>
-                The centralized configuration for the management of a Host Controller.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="domain-managementType">
-                <xs:sequence>
-                    <xs:element name="management-interfaces" type="host-management-interfacesType" minOccurs="1"/>
-                </xs:sequence>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="server-managementType">
-        <xs:annotation>
-            <xs:documentation>
-                The centralized configuration for the management of standalone server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="domain-managementType">
-                <xs:sequence>
-                    <xs:element name="management-interfaces" type="server-management-interfacesType" minOccurs="0"/>
-                </xs:sequence>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="ldapType">
-        <xs:annotation>
-            <xs:documentation>
-                The LDAP connection definition.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of this connection.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="url" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The URL to connect to ldap.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <!-- TODO - Later will be optional if we support GSSAPI to connect to LDAP -->
-        <xs:attribute name="search-dn" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The distinguished name to use when connecting to LDAP to perform searches.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="search-credential" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The credential to use when connecting to perform a search.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="initial-context-factory" type="xs:string" default="com.sun.jndi.ldap.LdapCtxFactory">
-            <xs:annotation>
-                <xs:documentation>
-                    The initial context factory to establish the LdapContext.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="security-realmType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of a security realm for securing access to the management interfaces.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="server-identities" type="server-identitiesType" minOccurs="0" />
-            <xs:element name="authentication" type="authenticationType" minOccurs="0" />
-            <xs:element name="authorization" type="authorizationType" minOccurs="0" />
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of this security-realm, each security-realm must be assigned a unique name.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="authorizationType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration defining how to load the authorization information for the authenticated user.
-
-                After a user has been authenticated additional information such as roles can be loaded and
-                associated with the user for subsequent authorization checks, this type is used to define
-                how the roles are loaded.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="properties" type="propertiesFileType" minOccurs="1" />  <!-- minOccurs="1" while this is the only mech -->
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="server-identitiesType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the identities that represent the server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-          <xs:element name="ssl" type="sslType" minOccurs="0" />
-          <xs:element name="secret" type="secretType" minOccurs="0" />
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="secretType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the secret/password-based identity of this server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="value" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The secret / password - Base64 Encoded
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="sslType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the SSL identity of this server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="keystore" type="keystoreType" />
-        </xs:sequence>
-        <xs:attribute name="protocol" type="xs:string" default="TLS">
-            <xs:annotation>
-                <xs:documentation>
-                    The protocol to use when creating the SSLContext.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="keystoreType">
-        <xs:annotation>
-            <xs:documentation>
-                The keystore configuration for the server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="path" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The path of the keystore.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="relative-to" use="optional" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of another previously named path, or of one of the
-                    standard paths provided by the system. If 'relative-to' is
-                    provided, the value of the 'path' attribute is treated as
-                    relative to the path specified by this attribute.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="password" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The password to open the keystore.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="authenticationType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the server side authentication mechanisms.
-
-                Optionally one truststore can be defined and one username/password based store can be defined.
-                Authentication will first attempt to use the truststore and if this is not available will fall back
-                to the username/password authentication.
-
-                If none of these are specified the only available mechanism will be the local mechanism for the
-                Native interface and the HTTP interface will not be accessible.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="truststore" type="keystoreType" minOccurs="0">
-                <xs:annotation>
-                    <xs:documentation>
-                        Configuration of a keystore to use to create a trust manager to verify clients.
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:element>
-            <xs:choice minOccurs="0">
-                <xs:element name="jaas" type="jaasAuthenticationType" minOccurs="0" />
-                <xs:element name="ldap" type="ldapAuthenticationType" minOccurs="0" />
-                <xs:element name="properties" type="propertiesAuthenticationType" minOccurs="0" />
-                <xs:element name="users" type="usersAuthenticationType" minOccurs="0" />
-            </xs:choice>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="jaasAuthenticationType">
-        <xs:annotation>
-            <xs:documentation>
-                Definition to use a JAAS based configuration for authentication.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name identifying the jaas configuration of LoginModules.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="ldapAuthenticationType">
-        <xs:annotation>
-            <xs:documentation>
-                Definition to use LDAP as the user repository.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="username-filter">
-                <xs:complexType>
-                    <xs:attribute name="attribute" type="xs:string" use="required">
-                        <xs:annotation>
-                            <xs:documentation>
-                                The name of the attribute to search for the user, this filter will then perform
-                                a simple search where the username entered by the user matches the attribute
-                                specified here.
-                            </xs:documentation>
-                        </xs:annotation>
-                    </xs:attribute>
-                </xs:complexType>
-            </xs:element>
-            <xs:element name="advanced-filter">
-                <xs:complexType>
-                    <xs:attribute name="filter" type="xs:string" use="required">
-                        <xs:annotation>
-                            <xs:documentation>
-                                The fully defined filter to be used to search for the user based on their entered
-                                user ID. The filter should contain a variable in the form {0} - this will be
-                                replaced with the username supplied by the user.
-                            </xs:documentation>
-                        </xs:annotation>
-                    </xs:attribute>
-                </xs:complexType>
-            </xs:element>
-        </xs:choice>
-
-        <xs:attribute name="connection" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the connection to use to connect to LDAP.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="base-dn" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The base distinguished name to commence the search for the user.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="recursive" type="xs:boolean" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Should the search be recursive.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="user-dn" type="xs:string" default="dn">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the attribute which is the users distinguished name.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-
-    <xs:complexType name="usersAuthenticationType">
-           <xs:annotation>
-            <xs:documentation>
-                A set of users
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="user" type="userType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="userType">
-        <xs:annotation>
-            <xs:documentation>
-                A single user.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="password" type="xs:string" />
-        </xs:choice>
-        <xs:attribute name="username" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The users username.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="propertiesFileType">
-        <xs:annotation>
-            <xs:documentation>
-                Declaration of a location of a properties file.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="relative-to" use="optional" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of another previously named path, or of one of the
-                    standard paths provided by the system. If 'relative-to' is
-                    provided, the value of the 'path' attribute is treated as
-                    relative to the path specified by this attribute.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="path" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The path of the properties file.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="propertiesAuthenticationType">
-        <xs:annotation>
-            <xs:documentation>
-                Declaration of users stored within properties files.
-
-                The entries within the properties file are username={credentials} with each user
-                being specified on it's own line.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="propertiesFileType">
-                <xs:attribute name="plain-text" type="xs:boolean" default="false">
-                    <xs:annotation>
-                        <xs:documentation>
-                            Are the credentials within the properties file stored in plain text, if not
-                            the {credential} is expected to be the hex encoded Digest hash
-                            of 'username : realm : password'.
-                        </xs:documentation>
-                    </xs:annotation>
-            </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="host-management-interfacesType">
-        <xs:sequence>
-            <xs:element name="native-interface" type="host-native-management-interfaceType"/>
-            <xs:element name="http-interface" type="host-http-management-interfaceType" minOccurs="0"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="management-interfaceType">
-        <xs:attribute name="security-realm" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    The security realm to use for this management interface, the capabilities
-                    of the security realm will be queried to identify the authentication mechanism(s) to
-                    offer.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="host-native-management-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of a host's exposed native management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="management-interfaceType">
-                <xs:sequence>
-                    <xs:element name="socket" type="native-management-socketType"/>
-                </xs:sequence>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="management-socketType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the socket used by host or standalone server's exposed management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="interface" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    Network interface on which the host's socket for
-                    management communication should be opened.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="native-management-socketType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the socket used by host or standalone server's exposed HTTP management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="management-socketType">
-                <xs:attribute name="port" type="xs:int" use="required">
-                    <xs:annotation>
-                        <xs:documentation>
-                            Port on which the host's socket for native
-                            management communication should be opened.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="host-http-management-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of a host's exposed HTTP management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="management-interfaceType">
-                <xs:sequence>
-                    <xs:element name="socket" type="http-management-socketType"/>
-                </xs:sequence>
-                <xs:attribute name="console-enabled" type="xs:boolean" use="optional" default="true"/>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="http-management-socketType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the socket used by host or standalone server's exposed HTTP management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="management-socketType">
-                <xs:attribute name="port" type="xs:int" use="optional">
-                    <xs:annotation>
-                        <xs:documentation>
-                            Port on which the host's socket for
-                            management communication should be opened.
-
-                            If not specified the port will not be opened.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-                <xs:attribute name="secure-port" type="xs:int" use="optional">
-                    <xs:annotation>
-                        <xs:documentation>
-                            Port on which the host's socket for HTTPS
-                            management communication should be opened.
-
-                            If not specified the port will not be opened.
-
-                            If specified the security-realm will be required to obtain
-                            the SSL configuration.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="server-management-interfacesType">
-        <xs:sequence>
-            <xs:element name="native-remoting-interface" type="management-remoting-interfaceType" minOccurs="0"/>
-            <xs:element name="native-interface" type="server-native-management-interfaceType" minOccurs="0"/>
-            <xs:element name="http-interface" type="server-http-management-interfaceType" minOccurs="0"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="server-native-management-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the socket used by host or standalone server's exposed HTTP management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="management-interfaceType">
-                <xs:annotation>
-                    <xs:documentation>
-                        Configuration of the socket to use for the native management interface is a choice
-                        between a direct configuration of the address and port, or a reference to a socket-binding
-                        configuration in the server's socket-binding-group element. The latter is the recommended
-                        approach is it makes it easier to avoid port conflicts by taking advantage of the
-                        socket-binding-group's port-offset configuration. Direct configuration of the address and
-                        ports is provided to preserve backward compatibility.
-                    </xs:documentation>
-                </xs:annotation>
-                <xs:choice>
-                    <xs:element name="socket" type="native-management-socketType"/>
-                    <xs:element name="socket-binding" type="native-management-socket-binding-refType"/>
-                </xs:choice>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="native-management-socket-binding-refType">
-        <xs:annotation>
-            <xs:documentation>
-                Reference to the configuration of the socket to be used by a standalone server's exposed native management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="native" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of a socket-binding configuration declared in the server's socket-binding-group.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="server-http-management-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of a standalone server's exposed HTTP/HTTPS management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="management-interfaceType">
-                <xs:annotation>
-                    <xs:documentation>
-                        Configuration of the socket to use for the HTTP/HTTPS management interface is a choice
-                        between a direct configuration of the address and ports, or a reference to socket-binding
-                        configurations in the server's socket-binding-group element. The latter is the recommended
-                        approach is it makes it easier to avoid port conflicts by taking advantage of the
-                        socket-binding-group's port-offset configuration. Direct configuration of the address and
-                        ports is provided to preserve backward compatibility.
-                    </xs:documentation>
-                </xs:annotation>
-                <xs:choice>
-                    <xs:element name="socket" type="http-management-socketType"/>
-                    <xs:element name="socket-binding" type="http-management-socket-binding-refType"/>
-                </xs:choice>
-                <xs:attribute name="console-enabled" type="xs:boolean" use="optional" default="true"/>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="http-management-socket-binding-refType">
-        <xs:annotation>
-            <xs:documentation>
-                Reference to the configurations of the sockets to be used by a standalone server's exposed HTTP and HTTPS management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="http" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of a socket-binding configuration declared in the server's socket-binding-group to use for a HTTP socket.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="https" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of a socket-binding configuration declared in the server's socket-binding-group to use for a HTTPS socket.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="management-remoting-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                Makes the native management interface available via the connectors set up in the remoting subsystem,
-                using the remoting subsystem's endpoint. This should only be used for a server not for a HC/DC.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="domain-controllerType">
-        <xs:choice>
-            <xs:element name="local" type="domain-controller-localType"/>
-            <xs:element name="remote" type="domain-controller-remoteType"/>
-        </xs:choice>
-    </xs:complexType>
-
-    <xs:complexType name="domain-controller-localType" />
-
-    <xs:complexType name="domain-controller-remoteType">
-        <xs:sequence>
-            <xs:element name="ignored-resources" type="ignored-resourcesType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-        <xs:attribute name="host" type="xs:string" use="required" />
-        <xs:attribute name="port" type="xs:integer" use="required" />
-        <xs:attribute name="security-realm" type="xs:string" use="optional" />
-    </xs:complexType>
-
-    <xs:complexType name="ignored-resourcesType">
-        <xs:annotation>
-            <xs:documentation>
-                Provides names of direct child resources of the domain root resource requests for which the
-                Host Controller should ignore. Only relevant on a slave Host Controller. Configuring such
-                "ignored resources" may help allow a Host Controller from an earlier release to function as a
-                slave to a master Host Controller running a later release, by letting the slave ignore portions
-                of the configuration its version of the software cannot understand. This strategy can only be
-                successful if the servers managed by the slave Host Controller do not reference any of the
-                ignored configuration.
-
-                Supports the following attributes:
-
-                type -- the type of resource (e.g. 'profile' or 'socket-binding-group') certain instances of which
-                        should be ignored. The value corresponds to the 'key' portion of the first element in the
-                        resource's address (e.g. 'profile' in the address /profile=ha/subsystem=web)
-
-                wildcard -- if 'true', all resources of the given type should be ignored.
-
-                Child elements list the names of specific instances of the given type of resource
-                that should be ignored. Each element in the list corresponds to the 'value' portion of
-                the first element in the resource's address (e.g. 'ha' in the address /profile=ha/subsystem=web.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="instance" type="ignored-resource-instanceType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-        <xs:attribute name="type" type="xs:string" use="required" />
-        <xs:attribute name="wildcard" type="xs:boolean" use="optional" default="false" />
-        <xs:attribute name="names" type="xs:string" use="optional" />
-    </xs:complexType>
-
-    <xs:complexType name="ignored-resource-instanceType">
-        <xs:annotation>
-            <xs:documentation>
-                The name of a specific instances of a particular type of resource that should be ignored.
-                The 'name' attribute corresponds to the 'value' portion of the first element in the resource's address
-                (e.g. 'ha' in the address /profile=ha/subsystem=web.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="required" />
-    </xs:complexType>
-
-    <xs:complexType name="serversType">
-        <xs:sequence>
-            <xs:element name="server" type="serverType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-        <xs:attribute name="directory-grouping" default="by-server" use="optional">
-            <xs:simpleType>
-                <xs:restriction base="xs:token">
-                    <xs:enumeration value="by-server">
-                        <xs:annotation>
-                            <xs:documentation>
-                                Indicates each server's writable directories should be grouped under the server's name
-                                in the domain/servers directory. This is the default option.
-                            </xs:documentation>
-                        </xs:annotation>
-                    </xs:enumeration>
-                    <xs:enumeration value="by-type">
-                        <xs:annotation>
-                            <xs:documentation>
-                                Indicates each server's writable directories should be grouped based on their "type"
-                                (i.e. "data", "log", "tmp") with directories of a given type for all servers appearing
-                                in the domain level directory for that type, e.g. domain/data/servers/server-name.
-                            </xs:documentation>
-                        </xs:annotation>
-                    </xs:enumeration>
-                </xs:restriction>
-            </xs:simpleType>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="serverType">
-        <xs:all>
-            <xs:element name="paths" type="specified-pathsType" minOccurs="0" maxOccurs="1" />
-
-            <xs:element name="interfaces" type="specified-interfacesType" minOccurs="0"/>
-            <xs:element name="socket-bindings" type="server-socket-bindingsType" minOccurs="0"/>
-
-            <!--<xs:element name="loggers" type="loggersType" minOccurs="0"/>-->
-            <xs:element name="system-properties" type="properties-with-boottime" minOccurs="0"/>
-            <xs:element name="jvm" minOccurs="0" type="serverJvmType"/>
-        </xs:all>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="group" type="xs:string" use="required"/>
-        <xs:attribute name="auto-start" type="xs:boolean" default="true"/>
-    </xs:complexType>
-
-    <xs:complexType name="server-socket-bindingsType">
-        <xs:annotation>
-            <xs:documentation>
-            <![CDATA[
-                Server-specific overrides to the default socket binding configuration inherited from the server group.
-            ]]>
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="socket-binding-group" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                <![CDATA[
-                    The socket binding group to use for the server. If undefined, the socket binding group
-                    specified for the server group is used.
-                ]]>
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="port-offset" type="xs:int" default="0" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                <![CDATA[
-                    Increment to apply to the base port values defined in the
-                    referenced socket binding group to derive the values to use on this
-                    server.
-                ]]>
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="extensionsType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of extension modules.</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="extension" type="extensionType" minOccurs="1" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="extensionType">
-        <xs:annotation>
-            <xs:documentation>
-                A module that extends the standard capabilities of a domain
-                or a standalone server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="module" use="required" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>The name of the module</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="server-groupsType">
-        <xs:sequence>
-            <xs:element name="server-group" type="server-groupType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="server-groupType">
-        <xs:sequence>
-            <xs:element name="jvm" type="namedJvmType" minOccurs="0"/>
-            <xs:element name="socket-binding-group" type="socket-binding-group-refType" minOccurs="1"/>
-
-            <xs:element name="deployments" type="server-groupDeploymentsType" minOccurs="0"/>
-
-            <xs:element name="system-properties" minOccurs="0" type="properties-with-boottime"/>
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the server group
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="profile" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the profile this server is running.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="management-subsystem-endpoint" type="xs:boolean" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Set to true to have servers belonging to the server group connect back to the host controller using the
-                    endpoint from their remoting subsystem. The subsystem must be preset for this to
-                    work.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="server-groupDeploymentsType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of deployments that have been mapped to a server-group.</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="deployment" type="base-deploymentType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="server-groupDeploymentType">
-        <xs:annotation>
-            <xs:documentation>A deployment that has been mapped to a server group.</xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="base-deploymentType">
-                <!--  TODO clarify what a value of 'false' means -->
-                <xs:attribute name="enabled" use="optional" type="xs:boolean" default="true">
-                    <xs:annotation>
-                        <xs:documentation>Whether the deployment deploy automatically when the server starts up.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="base-deploymentType">
-        <xs:attribute name="name" use="required">
-            <xs:annotation>
-                <xs:documentation>Unique identifier of the deployment. Must be unique across all deployments.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="runtime-name" use="required">
-            <xs:annotation>
-                <xs:documentation>Name by which the deployment will be known within a running server.of the deployment.
-                    Does not need to be unique across all deployments in the domain, although it must be unique within
-                    an individual server. For example, two different deployments running on different servers in
-                    the domain could both have a 'runtime-name' of 'example.war', with one having a 'name'
-                    of 'example.war_v1' and another with an 'name' of 'example.war_v2'.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="server-deploymentsType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of deployments that have been mapped to a server.</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="deployment" type="server-deploymentType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="server-deploymentType">
-        <xs:annotation>
-            <xs:documentation>A deployment that has been mapped to a server.</xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="base-deploymentType">
-                <xs:sequence>
-                    <!-- TODO: maxOccurs should be unbounded once overlays are in place -->
-                    <xs:choice maxOccurs="1">
-                        <xs:element name="content" type="contentType"/>
-                        <xs:element name="fs-archive" type="fs-archiveType"/>
-                        <xs:element name="fs-exploded" type="fs-explodedType"/>
-                    </xs:choice>
-                </xs:sequence>
-                <!--  TODO clarify what a value of 'false' means -->
-                <xs:attribute name="enabled" use="optional" type="xs:boolean" default="true">
-                    <xs:annotation>
-                        <xs:documentation>Whether the deployment deploy automatically when the server starts up.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="contentType">
-        <xs:attribute name="sha1" use="required">
-            <xs:annotation>
-                <xs:documentation>The checksum of the content</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="fs-archiveType">
-        <xs:annotation>
-            <xs:documentation>Archived content found on the filesystem</xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="fs-baseType"/>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="fs-baseType">
-        <xs:complexContent>
-            <xs:extension base="pathType"/>
-        </xs:complexContent>
-        <!-- TODO: make path required
-        <xs:complexContent>
-            <xs:restriction base="pathType">
-                <xs:attribute name="path" use="required"/>
-            </xs:restriction>
-        </xs:complexContent>
-        -->
-    </xs:complexType>
-
-    <xs:complexType name="fs-explodedType">
-        <xs:annotation>
-            <xs:documentation>Exploded content found on the filesystem</xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="fs-baseType"/>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="domain-deploymentsType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of domain-level deployments</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="deployment" type="domain-deploymentType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="domain-deploymentType">
-        <xs:annotation>
-            <xs:documentation>Deployment represents anything that can be deployed (e.g. an application such as EJB-JAR,
-                WAR, EAR,
-                any kind of standard archive such as RAR or JBoss-specific deployment),
-                which can be enabled or disabled on a domain level.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="base-deploymentType">
-                <xs:sequence>
-                    <!-- TODO: maxOccurs should be unbounded once overlays are in place -->
-                    <xs:choice maxOccurs="1">
-                        <xs:element name="content" type="contentType"/>
-                        <xs:element name="fs-archive" type="fs-archiveType"/>
-                        <xs:element name="fs-exploded" type="fs-explodedType"/>
-                    </xs:choice>
-                </xs:sequence>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <!-- TODO this is not used anywhere yet -->
-    <xs:complexType name="clustersType">
-        <xs:complexContent>
-            <xs:extension base="server-groupType">
-                <xs:sequence>
-                    <xs:element name="partition-name" type="xs:string"/>
-                    <xs:element name="state-transfer-timeout" type="xs:integer"/>
-                    <xs:element name="method-call-timeout" type="xs:integer"/>
-                </xs:sequence>
-                <xs:attribute name="category" type="xs:string" use="required"/>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <!-- domain-configuration related definitions -->
-    <xs:complexType name="domain-configurationType">
-        <xs:annotation>
-            <xs:documentation>The domain controller/server bootstrap configuration</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element ref="bootstrapURI"/>
-        </xs:sequence>
-    </xs:complexType>
-    <xs:element name="bootstrapURI" type="xs:string">
-        <xs:annotation>
-            <xs:documentation>The URI for bootstrapping a domain server</xs:documentation>
-        </xs:annotation>
-    </xs:element>
-
-    <xs:complexType name="profilesType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of profiles available for use in the domain</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="profile" type="domain-profileType" minOccurs="1" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="domain-profileType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of subsystems</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded">
-                <xs:annotation>
-                    <xs:documentation>A profile declaration may include configuration
-                        elements from other namespaces for the subsystems that make up the profile.
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:any>
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>Name of the profile</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="standalone-profileType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of subsystems</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:choice minOccurs="1" maxOccurs="unbounded">
-                <xs:any namespace="##other">
-                    <xs:annotation>
-                        <xs:documentation>A profile declaration may include configuration
-                            elements from other namespaces for the subsystems that make up the profile.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:any>
-            </xs:choice>
-        </xs:sequence>
-    </xs:complexType>
-
-    <!-- general socket definition -->
-    <xs:complexType name="socket-binding-groupsType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of socket binding groups</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="socket-binding-group" type="socket-binding-groupType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="socket-binding-groupType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of socket configurations</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="socket-binding" type="socket-bindingType" maxOccurs="unbounded"/>
-            <xs:element name="outbound-socket-binding" type="outbound-socket-bindingType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="default-interface" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of an interface that should be used as the interface for
-                    any sockets that do not explicitly declare one.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="standalone-socket-binding-groupType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of socket configurations</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="socket-binding" type="socket-bindingType" maxOccurs="unbounded"/>
-            <xs:element name="outbound-socket-binding" type="outbound-socket-bindingType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="default-interface" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of an interface that should be used as the interface for
-                    any sockets that do not explicitly declare one.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-	    <xs:attribute name="port-offset" type="xs:int" use="optional" default="0">
-	        <xs:annotation>
-                <xs:documentation>
-	                    Increment to apply to the base port values defined in the
-	                    socket group to derive the values to use on this
-	                    server.
-	            </xs:documentation>
-	        </xs:annotation>
-	    </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="socket-bindingType">
-        <xs:annotation>
-            <xs:documentation>Configuration information for a socket.</xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="client-mapping" type="socket-binding-client-mappingType"
-                        minOccurs="0" maxOccurs="unbounded">
-                <xs:annotation>
-                    <xs:documentation>
-                        Specifies zero or more client mappings for this socket binding.
-                        A client connecting to this socket should use the destination address
-                        specified in the mapping that matches its desired outbound interface.
-                        This allows for advanced network topologies that use either network
-                        address translation, or have bindings on multiple network interfaces
-                        to function.
-
-                        Each mapping should be evaluated in declared order, with the first successful
-                        match used to determine the destination.
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:element>
-        </xs:choice>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="interface" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of the interface to which the socket should be bound, or, for multicast
-                    sockets, the interface on which it should listen. This should
-                    be one of the declared interfaces.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="port" type="xs:unsignedShort" use="optional" default="0">
-            <xs:annotation>
-                <xs:documentation>
-                    Number of the port to which the socket should be bound.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="fixed-port" type="xs:boolean" use="optional" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Whether the port value should remain fixed even if numerically offsets
-                    are applied to the other sockets in the socket group..
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="multicast-address" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Multicast address on which the socket should receive multicast
-                    traffic. If unspecified, the socket will not be configured
-                    to receive multicast.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="multicast-port" type="xs:positiveInteger" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Port on which the socket should receive multicast
-                    traffic. Must be configured if 'multicast-address' is configured.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="socket-binding-client-mappingType">
-        <xs:annotation>
-                <xs:documentation>
-                    Type definition for a client mapping on a socket binding. A client
-                    mapping specifies how external clients should connect to this
-                    socket's port, provided that the client's outbound interface
-                    match the specified source network value.
-                </xs:documentation>
-            </xs:annotation>
-        <xs:attribute name="source-network" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Source network the client connection binds on. This value is in
-                    the form of ip/netmask. A client should match this value against
-                    the desired client host network interface, and if matched the
-                    client should connect to the corresponding destination values.
-
-                    If omitted this mapping should match any interface.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="destination-address" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The destination address that a client should connect to if the
-                    source-network matches. This value can either be a hostname or
-                    an ip address.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="destination-port" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    The destination port that a client should connect to if the
-                    source-network matches.
-
-                    If omitted this mapping will reuse the effective socket binding
-                    port.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="outbound-socket-bindingType">
-        <xs:annotation>
-            <xs:documentation>Configuration information for a outbound socket.</xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="remote-destination" type="remote-destinationType" maxOccurs="1"/>
-            <xs:element name="local-destination" type="local-destinationType" maxOccurs="1"/>
-        </xs:choice>
-
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the outbound socket binding
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="source-interface" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the interface that should be used for setting up the source address of the
-                    outbound socket. This should be one of the declared interfaces.
-                </xs:documentation>
-            </xs:annotation>
-
-        </xs:attribute>
-        <xs:attribute name="source-port" type="xs:positiveInteger" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    The port number that will be used for setting the source addresss of the outbound socket. If the
-                    source-interface attribute has been specified and the source-port attribute is absent,
-                    then the system uses a ephemeral port while binding the socket to a source address.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="fixed-source-port" type="xs:boolean" use="optional" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Whether the source-port value should remain fixed even if the socket binding group specifies
-                    a port offset
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="remote-destinationType">
-        <xs:attribute name="host" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The remote server address to which the outbound socket has to be connect.
-                    The address can be either a IP address of the host server of the hostname of the server
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="port" type="xs:positiveInteger" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The remote port to which the outbound socket has to connect.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="local-destinationType">
-        <xs:attribute name="socket-binding-ref" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The reference to a socket binding that has to be used as the destination for the outbound
-                    socket binding. This socket binding name should belong to the same socket binding group
-                    to which this local destination client socket belongs.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="socket-binding-group-refType">
-        <xs:attribute name="ref" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The socket group to use for the server group or server.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="port-offset" type="xs:int" default="0" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Increment to apply to the base port values defined in the
-                    referenced socket group to derive the values to use on this
-                    server.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-
-    <xs:complexType name="named-interfacesType">
-        <xs:annotation>
-            <xs:documentation>
-                A list of named network interfaces. The interfaces may or may
-                not be fully specified (i.e. include criteria on how to determine
-                their IP address.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="interface" type="named-interfaceType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <!-- TODO make this and specified-interfaceType the same except for interface-criteriaGroup minOccurs -->
-    <xs:complexType name="named-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                A named network interface, but without any criteria
-                for determining the IP address to associate with that interface.
-                Acts as a placeholder in the model (e.g. at the domain level)
-                until a fully specified interface definition is applied at a
-                lower level (e.g. at the server level, where available addresses
-                are known.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:group ref="interface-criteriaGroup" minOccurs="0"/>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-    </xs:complexType>
-
-    <xs:complexType name="specified-interfacesType">
-        <xs:annotation>
-            <xs:documentation>
-                A list of fully specified named network interfaces.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="interface" type="specified-interfaceType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="specified-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                A named network interface, along with required criteria
-                for determining the IP address to associate with that interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:group ref="interface-criteriaGroup" minOccurs="1"/>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-    </xs:complexType>
-
-    <xs:group name="interface-criteriaGroup">
-        <xs:annotation>
-            <xs:documentation>
-                A set of criteria that can be used at runtime to determine
-                what IP address to use for an interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="any-address" type="any-addressType"/>
-            <xs:element name="any-ipv6-address" type="any-ipv6-addressType"/>
-            <xs:element name="any-ipv4-address" type="any-ipv4-addressType"/>
-            <xs:choice maxOccurs="unbounded">
-                <xs:element name="inet-address" type="inet-addressType"/>
-                <xs:element name="loopback" type="loopbackType"/>
-                <xs:element name="loopback-address" type="loopback-addressType"/>
-                <xs:element name="multicast" type="multicastType"/>
-                <xs:element name="point-to-point" type="point-to-pointType"/>
-                <xs:element name="virtual" type="interface-virtualType"/>
-                <xs:element name="up" type="interface-upType"/>
-                <xs:element name="public-address" type="public-addressType"/>
-                <xs:element name="link-local-address" type="link-local-addressType"/>
-                <xs:element name="site-local-address" type="site-local-addressType"/>
-                <xs:element name="nic" type="nicType"/>
-                <xs:element name="nic-match" type="nic-matchType"/>
-                <xs:element name="subnet-match" type="subnet-matchType"/>
-                <xs:element name="not" type="address-exclusionType"/>
-                <xs:element name="any" type="address-exclusionType"/>
-            </xs:choice>
-        </xs:choice>
-    </xs:group>
-
-    <xs:complexType name="inet-addressType">
-        <xs:attribute name="value" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    Either a IP address in IPv6 or IPv4 dotted decimal notation,
-                    or a hostname that can be resolved to an IP address.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="nicType">
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of a network interface (e.g. eth0, eth1, lo).
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="nic-matchType">
-        <xs:attribute name="pattern" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    A regular expression against which the names of the network
-                    interfaces available on the machine can be matched to find
-                    an acceptable interface.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="subnet-matchType">
-        <xs:attribute name="value" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    A network IP address and the number of bits in the
-                    address' network prefix, written in "slash notation";
-                    e.g. "192.168.0.0/16".
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="address-exclusionType">
-        <xs:choice>
-            <xs:element name="inet-address" type="inet-addressType" minOccurs="0" maxOccurs="unbounded"/>
-            <xs:element name="loopback" type="loopbackType"/>
-            <xs:element name="loopback-address" type="loopback-addressType"/>
-            <xs:element name="multicast" type="multicastType"/>
-            <xs:element name="point-to-point" type="point-to-pointType"/>
-            <xs:element name="virtual" type="interface-virtualType"/>
-            <xs:element name="up" type="interface-upType"/>
-            <xs:element name="public-address" type="public-addressType"/>
-            <xs:element name="link-local-address" type="link-local-addressType"/>
-            <xs:element name="site-local-address" type="site-local-addressType"/>
-            <xs:element name="nic" type="nicType" minOccurs="0" maxOccurs="unbounded"/>
-            <xs:element name="nic-match" type="nic-matchType" minOccurs="0" maxOccurs="unbounded"/>
-            <xs:element name="subnet-match" type="subnet-matchType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:choice>
-    </xs:complexType>
-
-    <xs:complexType name="loopbackType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it is a loopback
-                interface.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="loopback-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                A loopback address that may not actually be configured on the machine's loopback interface.
-                Differs from inet-addressType in that the given value will be used even if no NIC can
-                be found that has the IP address associated with it.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="value" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    An IP address in IPv6 or IPv4 dotted decimal notation.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="multicastType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it supports
-                multicast.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="point-to-pointType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it is a point-to-point
-                interface.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="interface-upType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it is currently up.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="interface-virtualType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it is a virtual
-                interface.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="public-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it has a publicly
-                routable address.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="site-local-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not an address associated
-                with it is site-local.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="link-local-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not an address associated
-                with it is link-local.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="any-ipv6-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that sockets using this interface
-                should be bound to the IPv6 wildcard address (::).
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="any-ipv4-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that sockets using this interface
-                should be bound to the IPv4 wildcard address (0.0.0.0).
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="any-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that sockets using this interface
-                should be bound to a wildcard address. The IPv6 wildcard
-                address (::) will be used unless the java.net.preferIpV4Stack
-                system property is set to true, in which case the IPv4
-                wildcard address (0.0.0.0) will be used. If a socket is
-                bound to an IPv6 anylocal address on a dual-stack machine,
-                it can accept both IPv6 and IPv4 traffic; if it is bound to
-                an IPv4 (IPv4-mapped) anylocal address, it can only accept
-                IPv4 traffic.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="socketType">
-        <xs:annotation>
-            <xs:documentation>Configuration information for a socket.</xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="interface" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of the interface to which the socket should be bound, or, for multicast
-                    sockets, the interface on which it should listen. This should
-                    be one of the declared interfaces.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="port" type="xs:unsignedShort" use="optional" default="0">
-            <xs:annotation>
-                <xs:documentation>
-                    Number of the port to which the socket should be bound.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="fixed-port" type="xs:boolean" use="optional" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Whether the port value should remain fixed even if numerically offsets
-                    are applied to the other sockets in the socket group..
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="multicast-address" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Multicast address on which the socket should receive multicast
-                    traffic. If unspecified, the socket will not be configured
-                    to receive multicast.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="multicast-port" type="xs:positiveInteger" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Port on which the socket should receive multicast
-                    traffic. If unspecified, the socket will not be configured
-                    to receive multicast.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <!-- Path configurations -->
-    <xs:complexType name="named-pathsType">
-        <xs:annotation>
-            <xs:documentation>
-                A list of named filesystem paths. The paths may or may
-                not be fully specified (i.e. include the actual paths.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="path" type="named-pathType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="named-pathType">
-        <xs:annotation>
-            <xs:documentation>
-                A named filesystem path, but without a requirement to specify
-                the actual path. If no actual path is specified, acts as a
-                as a placeholder in the model (e.g. at the domain level)
-                until a fully specified path definition is applied at a
-                lower level (e.g. at the host level, where available addresses
-                are known.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="pathType">
-                <xs:attribute name="name" type="xs:string" use="required">
-                    <xs:annotation>
-                        <xs:documentation>
-                        The name of the path. Cannot be one of the standard fixed paths
-                        provided by the system:
-
-                        jboss.home - the root directory of the JBoss AS distribution
-                        user.home - user's home directory
-                        user.dir - user's current working directory
-                        java.home - java installation directory
-                        jboss.server.base.dir - root directory for an individual server
-                                                instance
-
-                        Note that the system provides other standard paths that can be
-                        overridden by declaring them in the configuration file. See
-                        the 'relative-to' attribute documentation for a complete
-                        list of standard paths.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="pathType">
-        <xs:attribute name="path">
-            <xs:annotation>
-                <xs:documentation>
-                The actual filesystem path. Treated as an absolute path, unless the
-                'relative-to' attribute is specified, in which case the value
-                is treated as relative to that path.
-
-                If treated as an absolute path, the actual runtime pathname specified
-                by the value of this attribute will be determined as follows:
-
-                If this value is already absolute, then the value is directly
-                used.  Otherwise the runtime pathname is resolved in a
-                system-dependent way.  On UNIX systems, a relative pathname is
-                made absolute by resolving it against the current user directory.
-                On Microsoft Windows systems, a relative pathname is made absolute
-                by resolving it against the current directory of the drive named by the
-                pathname, if any; if not, it is resolved against the current user
-                directory.
-                </xs:documentation>
-            </xs:annotation>
-            <xs:simpleType>
-                <xs:restriction base="xs:string">
-                    <xs:minLength value="1"/>
-                </xs:restriction>
-            </xs:simpleType>
-        </xs:attribute>
-        <xs:attribute name="relative-to" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                The name of another previously named path, or of one of the
-                standard paths provided by the system. If 'relative-to' is
-                provided, the value of the 'path' attribute is treated as
-                relative to the path specified by this attribute. The standard
-                paths provided by the system include:
-
-                jboss.home - the root directory of the JBoss AS distribution
-                user.home - user's home directory
-                user.dir - user's current working directory
-                java.home - java installation directory
-                jboss.server.base.dir - root directory for an individual server
-                                        instance
-                jboss.server.config.dir - directory in which server configuration
-                                          files are stored.
-                jboss.server.data.dir - directory the server will use for persistent
-                                        data file storage
-                jboss.server.log.dir - directory the server will use for
-                                       log file storage
-                jboss.server.temp.dir - directory the server will use for
-                                       temporary file storage
-                jboss.domain.servers.dir - directory under which a host controller
-                                           will create the working area for
-                                           individual server instances
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="specified-pathsType">
-        <xs:annotation>
-            <xs:documentation>
-                A list of named filesystem paths.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="path" type="specified-pathType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="specified-pathType">
-        <xs:annotation>
-            <xs:documentation>
-                A named filesystem path.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                The name of the path. Cannot be one of the standard fixed paths
-                provided by the system:
-
-                jboss.home.dir - the root directory of the JBoss AS distribution
-                user.home - user's home directory
-                user.dir - user's current working directory
-                java.home - java installation directory
-                jboss.server.base.dir - root directory for an individual server
-                                        instance
-
-                Note that the system provides other standard paths that can be
-                overridden by declaring them in the configuration file. See
-                the 'relative-to' attribute documentation for a complete
-                list of standard paths.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="path" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                The actual filesystem path. Treated as an absolute path, unless the
-                'relative-to' attribute is specified, in which case the value
-                is treated as relative to that path.
-
-                If treated as an absolute path, the actual runtime pathname specified
-                by the value of this attribute will be determined as follows:
-
-                If this value is already absolute, then the value is directly
-                used.  Otherwise the runtime pathname is resolved in a
-                system-dependent way.  On UNIX systems, a relative pathname is
-                made absolute by resolving it against the current user directory.
-                On Microsoft Windows systems, a relative pathname is made absolute
-                by resolving it against the current directory of the drive named by the
-                pathname, if any; if not, it is resolved against the current user
-                directory.
-
-                Note relative path declarations have to use '/' as file separator.
-                </xs:documentation>
-            </xs:annotation>
-            <xs:simpleType>
-                <xs:restriction base="xs:string">
-                    <xs:minLength value="1"/>
-                </xs:restriction>
-            </xs:simpleType>
-        </xs:attribute>
-        <xs:attribute name="relative-to" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                The name of another previously named path, or of one of the
-                standard paths provided by the system. If 'relative-to' is
-                provided, the value of the 'path' attribute is treated as
-                relative to the path specified by this attribute. The standard
-                paths provided by the system include:
-
-                jboss.home.dir - the root directory of the JBoss AS distribution
-                user.home - user's home directory
-                user.dir - user's current working directory
-                java.home - java installation directory
-                jboss.server.base.dir - root directory for an individual server
-                                        instance
-                jboss.server.config.dir - directory in which server configuration
-                                          files are stored.
-                jboss.server.data.dir - directory the server will use for persistent
-                                        data file storage
-                jboss.server.log.dir - directory the server will use for
-                                       log file storage
-                jboss.server.temp.dir - directory the server will use for
-                                       temporary file storage
-                jboss.domain.servers.dir - directory under which a host controller
-                                           will create the working area for
-                                           individual server instances
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <!--  JVM configurations -->
-    <xs:complexType name="jvmsType">
-        <xs:sequence>
-            <xs:element name="jvm" type="namedJvmType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="jvmType">
-        <xs:all minOccurs="0" maxOccurs="1">
-            <xs:element name="heap" type="heapType" minOccurs="0"/>
-            <!-- XX:PermSize, XX:MaxPermSize -->
-            <xs:element name="permgen" type="bounded-memory-sizeType" minOccurs="0"/>
-            <!-- Xss -->
-            <xs:element name="stack" type="memory-sizeType" minOccurs="0"/>
-            <xs:element name="agent-lib" type="jvm-agentLibType" minOccurs="0"/>
-            <xs:element name="agent-path" type="jvm-agentPathType" minOccurs="0"/>
-            <xs:element name="java-agent" type="jvm-javaagentType" minOccurs="0"/>
-            <xs:element name="jvm-options" type="jvm-optionsType" minOccurs="0"/>
-            <xs:element name="environment-variables" type="environmentVariablesType" minOccurs="0"/>
-        </xs:all>
-        <xs:attribute name="java-home" type="xs:string"/>
-        <xs:attribute name="type" default="SUN">
-            <xs:simpleType>
-                <xs:restriction base="xs:token">
-                    <xs:enumeration value="SUN">
-			            <xs:annotation>
-			                <xs:documentation>Allows the full set of JVM options to be set via the jvm schema elements</xs:documentation>
-			            </xs:annotation>
-                    </xs:enumeration>
-                    <xs:enumeration value="IBM">
-                        <xs:annotation>
-                            <xs:documentation>Sets a subset of the JVM options via the jvm schema elements</xs:documentation>
-                        </xs:annotation>
-                    </xs:enumeration>
-                </xs:restriction>
-            </xs:simpleType>
-        </xs:attribute>
-        <xs:attribute name="env-classpath-ignored" default="true" type="xs:boolean"/>
-    </xs:complexType>
-
-    <xs:complexType name="namedJvmType">
-        <xs:complexContent>
-            <xs:extension base="jvmType">
-                <xs:attribute name="name" type="xs:string"/>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="serverJvmType">
-        <xs:complexContent>
-            <xs:extension base="namedJvmType">
-                <xs:attribute name="debug-enabled" type="xs:boolean" default="false"/>
-                <xs:attribute name="debug-options" type="xs:string" />
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="heapType">
-        <xs:attribute name="size" use="optional">
-            <xs:annotation>
-                <xs:documentation>Initial JVM heap size</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="max-size" use="optional">
-            <xs:annotation>
-                <xs:documentation>Maximum JVM heap size</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-optionsType">
-        <xs:sequence>
-            <xs:element name="option" type="jvm-optionType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-optionType">
-        <xs:attribute name="value" use="required">
-            <xs:annotation>
-                <xs:documentation>JVM option value</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-agentLibType">
-        <xs:attribute name="value" use="required">
-            <xs:annotation>
-                <xs:documentation>JVM agent lib value </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-agentPathType">
-        <xs:attribute name="value" use="required">
-            <xs:annotation>
-                <xs:documentation>JVM agent path value </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-javaagentType">
-        <xs:attribute name="value" use="required">
-            <xs:annotation>
-                <xs:documentation>JVM javaagent value </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="bounded-memory-sizeType">
-        <xs:attribute name="size" type="xs:string"/>
-        <xs:attribute name="max-size" type="xs:string"/>
-    </xs:complexType>
-
-    <xs:complexType name="memory-sizeType">
-        <xs:attribute name="size" type="xs:string" use="required"/>
-    </xs:complexType>
-
-    <xs:complexType name="properties-with-boottime">
-        <xs:sequence>
-            <xs:element name="property" type="boottimePropertyType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="properties">
-        <xs:sequence>
-            <xs:element name="property" type="propertyType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="environmentVariablesType">
-        <xs:sequence>
-            <xs:element name="variable" type="propertyType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="propertyType">
-        <xs:attribute name="name" use="required"/>
-        <xs:attribute name="value" use="optional"/>
-    </xs:complexType>
-
-    <xs:complexType name="boottimePropertyType">
-        <xs:complexContent>
-            <xs:extension base="propertyType">
-                <xs:attribute name="boot-time" type="xs:boolean" default="true"/>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-   <xs:complexType name="vaultType">
-      <xs:annotation>
-         <xs:documentation>
-               <![CDATA[
-                    Vault Configuration.
-                ]]>
-         </xs:documentation>
-      </xs:annotation>
-      <xs:sequence>
-          <xs:element name="vault-option" type="propertyType" minOccurs="0" maxOccurs="unbounded"/>
-      </xs:sequence>
-      <xs:attribute name="code" type="xs:string" use="optional"/>
-   </xs:complexType>
-
-    <xs:complexType name="management-client-contentType">
-        <xs:annotation>
-            <xs:documentation>
-                <![CDATA[
-                   Storage information about re-usable chunks of data useful to management clients that are stored
-                   in the domain content repository.
-                ]]>
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="rollout-plans" type="contentType" minOccurs="0" maxOccurs="1">
-                <xs:annotation>
-                    <xs:documentation>
-                        <![CDATA[
-                           Storage information about a set of named management update rollout plans useful to management
-                           clients that are stored in the domain content repository. The management API exposed by the domain
-                           controller provides access to these plans to management clients, allowing clients to use the plans
-                           by referencing them by name, avoiding the need to recreate them for each use.
-                        ]]>
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:element>
-        </xs:sequence>
-    </xs:complexType>
-
-
-</xs:schema>

jboss-as-7.2.0.Final/docs/schema/jboss-as-config_1_3.xsd

@@ -1,2299 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-  ~ JBoss, Home of Professional Open Source.
-  ~ Copyright 2012, Red Hat, Inc., and individual contributors
-  ~ as indicated by the @author tags. See the copyright.txt file in the
-  ~ distribution for a full listing of individual contributors.
-  ~
-  ~ This is free software; you can redistribute it and/or modify it
-  ~ under the terms of the GNU Lesser General Public License as
-  ~ published by the Free Software Foundation; either version 2.1 of
-  ~ the License, or (at your option) any later version.
-  ~
-  ~ This software is distributed in the hope that it will be useful,
-  ~ but WITHOUT ANY WARRANTY; without even the implied warranty of
-  ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-  ~ Lesser General Public License for more details.
-  ~
-  ~ You should have received a copy of the GNU Lesser General Public
-  ~ License along with this software; if not, write to the Free
-  ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
-  ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
-  -->
-
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
-           xmlns="urn:jboss:domain:1.3"
-           targetNamespace="urn:jboss:domain:1.3"
-           elementFormDefault="qualified"
-           attributeFormDefault="unqualified"
-        >
-
-
-    <xs:element name="domain">
-        <xs:annotation>
-            <xs:documentation>
-                Root element for the master document specifying the core configuration
-                for the servers in a domain. There should be one such master
-                document per domain, available to the host controller that
-                is configured to act as the domain controller.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element name="extensions" type="extensionsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="system-properties" type="properties-with-boottime" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="paths" type="named-pathsType" minOccurs="0" maxOccurs="1" />
-                <xs:element name="profiles" type="profilesType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="interfaces" type="named-interfacesType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="socket-binding-groups" type="socket-binding-groupsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="deployments" type="domain-deploymentsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="server-groups" type="server-groupsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="management-client-content" type="management-client-contentType" minOccurs="0" maxOccurs="1"/>
-            </xs:sequence>
-            <xs:attribute name="name" type="xs:string" use="optional" default="Unnamed Domain">
-               <xs:annotation>
-                  <xs:documentation>
-                     The name to use for the domain controller. Useful for administrators who need to work with multiple domains.
-                  </xs:documentation>
-               </xs:annotation>
-            </xs:attribute>
-        </xs:complexType>
-    </xs:element>
-
-    <xs:element name="host">
-        <xs:annotation>
-            <xs:documentation>
-                Root element for a document configuring a host controller and
-                the group of servers under the control of that host controller.
-                The standard usage would be for a domain to have one such host controller
-                on each physical (or virtual) host machine. Emphasis in this
-                document is on enumerating the servers, configuring items that
-                are specific to the host environment (e.g. IP addresses), and
-                on any server-specific configuration settings.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element name="system-properties" type="properties-with-boottime" minOccurs="0"/>
-                <xs:element name="paths" type="specified-pathsType" minOccurs="0" maxOccurs="1" />
-                <xs:element name="vault" type="vaultType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="management" type="host-managementType" minOccurs="1" maxOccurs="1"/>
-                <xs:element name="domain-controller" type="domain-controllerType"/>
-                <xs:element name="interfaces" type="specified-interfacesType" minOccurs="0"/>
-                <xs:element name="jvms" type="jvmsType" minOccurs="0"/>
-                <xs:element name="servers" type="serversType" minOccurs="0"/>
-            </xs:sequence>
-            <xs:attribute name="name" type="xs:string" use="optional">
-                <xs:annotation>
-                    <xs:documentation>
-                        The name to use for this host's host controller. Must be unique across the domain.
-                        If not set, defaults to the runtime value "HOSTNAME" or "COMPUTERNAME" environment variables,
-                        or, if neither environment variable is present, to the value of InetAddress.getLocalHost().getHostName().
-
-                        If the special value "jboss.domain.uuid" is used, a java.util.UUID will be created
-                        and used, based on the value of InetAddress.getLocalHost().
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:attribute>
-        </xs:complexType>
-    </xs:element>
-
-    <xs:element name="server">
-        <xs:annotation>
-            <xs:documentation>
-                Root element for a document specifying the configuration
-                of a single "standalone" server that does not operate
-                as part of a domain.
-
-                Note that this element is distinct from the 'serverType'
-                specified in this schema. The latter type forms part of the
-                configuration of a server that operates as part of a domain.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element name="extensions" type="extensionsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="system-properties" type="properties" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="paths" type="specified-pathsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="vault" type="vaultType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="management" type="server-managementType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="profile" type="standalone-profileType" minOccurs="0"/>
-                <xs:element name="interfaces" type="specified-interfacesType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="socket-binding-group" type="standalone-socket-binding-groupType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="deployments" type="server-deploymentsType" minOccurs="0" maxOccurs="1"/>
-            </xs:sequence>
-            <xs:attribute name="name" type="xs:string" use="optional">
-                <xs:annotation>
-                    <xs:documentation>
-                        The name to use for this server.
-                        If not set, defaults to the runtime value "HOSTNAME" or "COMPUTERNAME" environment variables,
-                        or, if neither environment variable is present, to the value of InetAddress.getLocalHost().getHostName().
-
-                        If the special value "jboss.domain.uuid" is used, a java.util.UUID will be created
-                        and used, based on the value of InetAddress.getLocalHost().
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:attribute>
-        </xs:complexType>
-    </xs:element>
-
-    <xs:complexType name="domain-managementType">
-        <xs:annotation>
-            <xs:documentation>
-                Domain-wide default configuration settings for the management of standalone servers and a Host Controller.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="security-realms" minOccurs="0">
-                <xs:complexType>
-                    <xs:sequence>
-                        <xs:element name="security-realm" type="security-realmType" minOccurs="1"
-                                    maxOccurs="unbounded"/>
-                    </xs:sequence>
-                </xs:complexType>
-            </xs:element>
-            <xs:element name="outbound-connections" minOccurs="0">
-                <xs:complexType>
-                    <xs:sequence>
-                      <xs:element name="ldap" type="ldapType" minOccurs="1" /> <!-- TODO minOccurs only while ldap is only supported connection. -->
-                    </xs:sequence>
-                </xs:complexType>
-            </xs:element>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="host-managementType">
-        <xs:annotation>
-            <xs:documentation>
-                The centralized configuration for the management of a Host Controller.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="domain-managementType">
-                <xs:sequence>
-                    <xs:element name="management-interfaces" type="host-management-interfacesType" minOccurs="1"/>
-                </xs:sequence>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="server-managementType">
-        <xs:annotation>
-            <xs:documentation>
-                The centralized configuration for the management of standalone server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="domain-managementType">
-                <xs:sequence>
-                    <xs:element name="management-interfaces" type="server-management-interfacesType" minOccurs="0"/>
-                </xs:sequence>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="ldapType">
-        <xs:annotation>
-            <xs:documentation>
-                The LDAP connection definition.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of this connection.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="url" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The URL to connect to ldap.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <!-- TODO - Later will be optional if we support GSSAPI to connect to LDAP -->
-        <xs:attribute name="search-dn" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The distinguished name to use when connecting to LDAP to perform searches.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="search-credential" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The credential to use when connecting to perform a search.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="initial-context-factory" type="xs:string" default="com.sun.jndi.ldap.LdapCtxFactory">
-            <xs:annotation>
-                <xs:documentation>
-                    The initial context factory to establish the LdapContext.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="security-realmType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of a security realm for securing access to the management interfaces.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="plug-ins" type="plug-insType" minOccurs="0" />
-            <xs:element name="server-identities" type="server-identitiesType" minOccurs="0" />
-            <xs:element name="authentication" type="authenticationType" minOccurs="0" />
-            <xs:element name="authorization" type="authorizationType" minOccurs="0" />
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of this security-realm, each security-realm must be assigned a unique name.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-    
-    <xs:complexType name="plug-insType">
-        <xs:annotation>
-            <xs:documentation>
-                List of modules to be searched for supported security realm plug-ins.              
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="plug-in" type="plug-inType" />
-        </xs:sequence>
-    </xs:complexType>
-    
-    <xs:complexType name="plug-inType">
-        <xs:attribute name="module" use="required" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>The name of the module.</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>    
-    </xs:complexType>
-    
-    <xs:complexType name="plug-inAuthType">
-        <xs:annotation>
-            <xs:documentation>
-                This type defines which plug in will be used to handle either the loading of the 
-                authentication data or authorization data during the authentication process.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="properties" type="properties" minOccurs="0">
-                <xs:annotation>
-                    <xs:documentation>
-                        The properties to be made available to the plug-in.
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:element>            
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The short name of the plug-in as already dynamically registered by being referenced 
-                    in the plug-ins element.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="mechanism" default="DIGEST" use="optional">
-           <xs:annotation>
-              <xs:documentation>
-                   By default plug-ins will be assumed to be used with the DIGEST authentication mechanism, 
-                   this attribute can override the plug-in for use with the PLAIN mechanism.
-              </xs:documentation>
-           </xs:annotation>        
-           <xs:simpleType>
-              <xs:restriction base="xs:string">
-                 <xs:enumeration value="DIGEST" />
-                 <xs:enumeration value="PLAIN" />
-              </xs:restriction>
-           </xs:simpleType>        
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="authorizationType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration defining how to load the authorization information for the authenticated user.
-
-                After a user has been authenticated additional information such as roles can be loaded and
-                associated with the user for subsequent authorization checks, this type is used to define
-                how the roles are loaded.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="properties" type="propertiesFileType" minOccurs="0" />  
-            <xs:element name="plug-in" type="plug-inAuthType" minOccurs="0" />
-        </xs:choice>
-    </xs:complexType>
-
-    <xs:complexType name="server-identitiesType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the identities that represent the server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-          <xs:element name="ssl" type="sslType" minOccurs="0" />
-          <xs:element name="secret" type="secretType" minOccurs="0" />
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="secretType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the secret/password-based identity of this server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="value" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The secret / password - Base64 Encoded
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="sslType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the SSL identity of this server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="keystore" type="extendedKeyStoreType" />
-        </xs:sequence>
-        <xs:attribute name="protocol" type="xs:string" default="TLS">
-            <xs:annotation>
-                <xs:documentation>
-                    The protocol to use when creating the SSLContext.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="keyStoreType">
-        <xs:annotation>
-            <xs:documentation>
-                The keystore configuration for the server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="path" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The path of the keystore.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="relative-to" use="optional" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of another previously named path, or of one of the
-                    standard paths provided by the system. If 'relative-to' is
-                    provided, the value of the 'path' attribute is treated as
-                    relative to the path specified by this attribute.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="keystore-password" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The password to open the keystore.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-    
-    <xs:complexType name="extendedKeyStoreType">
-        <xs:annotation>
-            <xs:documentation>
-                This is a more complex keystore definition which also allows for an alias
-                and key password to be specified.
-            </xs:documentation>
-        </xs:annotation>
-	    <xs:complexContent>
-		    <xs:extension base="keyStoreType">
-                <xs:attribute name="alias" type="xs:string" use="optional">
-                    <xs:annotation>
-                        <xs:documentation>
-                            The alias of the entry to use from the keystore, if specified all remaining
-                            entries in the keystore will be ignored.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>			
-                <xs:attribute name="key-password" type="xs:string" use="optional">
-                    <xs:annotation>
-                        <xs:documentation>
-                            The password to use when loading keys from the keystore.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>                
-		    </xs:extension>
-	    </xs:complexContent>                            
-    </xs:complexType>
-    
-    <xs:complexType name="localType">
-        <xs:annotation>
-            <xs:documentation>
-                This type definition is used to control the local authentication mechanism.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="default-user" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    When using the local mechanism it is optional for the client side to send an
-                    authentication user name - this attribute specifies the user name to be assumed
-                    if the remote client does not send one.
-                </xs:documentation>
-            </xs:annotation>            
-        </xs:attribute>
-        <xs:attribute name="allowed-users" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    A comma separated list of users that can be specified by the client when connecting 
-                    using the local authentication mechanism.
-                
-                    If a default user has been specified then that user is automatically added to the 
-                    allowed list.  If both default-user and allowed-users are ommitted despite the mechanism
-                    being enabled no incomming connection attemps using the mechanism will succeed.
-                  
-                    If any user name should be accepted the value should be set to "*".
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-    
-    <xs:complexType name="authenticationType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the server side authentication mechanisms.
-
-                Optionally one truststore can be defined and one username/password based store can be defined.
-                Authentication will first attempt to use the truststore and if this is not available will fall back
-                to the username/password authentication.
-
-                If none of these are specified the only available mechanism will be the local mechanism for the
-                Native interface and the HTTP interface will not be accessible.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="truststore" type="keyStoreType" minOccurs="0">
-                <xs:annotation>
-                    <xs:documentation>
-                        Configuration of a keystore to use to create a trust manager to verify clients.
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:element>
-            <xs:element name="local" type="localType" minOccurs="0">
-                <xs:annotation>
-                    <xs:documentation>
-                        Configuration to enable the local authentication mechanism, if this element
-                        is ommitted then local authentication will be disabled.
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:element>
-            <xs:choice minOccurs="0">
-                <xs:element name="jaas" type="jaasAuthenticationType" minOccurs="0" />
-                <xs:element name="ldap" type="ldapAuthenticationType" minOccurs="0" />
-                <xs:element name="properties" type="propertiesAuthenticationType" minOccurs="0" />
-                <xs:element name="users" type="usersAuthenticationType" minOccurs="0" />
-                <xs:element name="plug-in" type="plug-inAuthType" minOccurs="0" />
-            </xs:choice>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="jaasAuthenticationType">
-        <xs:annotation>
-            <xs:documentation>
-                Definition to use a JAAS based configuration for authentication.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name identifying the jaas configuration of LoginModules.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="ldapAuthenticationType">
-        <xs:annotation>
-            <xs:documentation>
-                Definition to use LDAP as the user repository.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="username-filter">
-                <xs:complexType>
-                    <xs:attribute name="attribute" type="xs:string" use="required">
-                        <xs:annotation>
-                            <xs:documentation>
-                                The name of the attribute to search for the user, this filter will then perform
-                                a simple search where the username entered by the user matches the attribute
-                                specified here.
-                            </xs:documentation>
-                        </xs:annotation>
-                    </xs:attribute>
-                </xs:complexType>
-            </xs:element>
-            <xs:element name="advanced-filter">
-                <xs:complexType>
-                    <xs:attribute name="filter" type="xs:string" use="required">
-                        <xs:annotation>
-                            <xs:documentation>
-                                The fully defined filter to be used to search for the user based on their entered
-                                user ID. The filter should contain a variable in the form {0} - this will be
-                                replaced with the username supplied by the user.
-                            </xs:documentation>
-                        </xs:annotation>
-                    </xs:attribute>
-                </xs:complexType>
-            </xs:element>
-        </xs:choice>
-
-        <xs:attribute name="connection" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the connection to use to connect to LDAP.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="base-dn" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The base distinguished name to commence the search for the user.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="recursive" type="xs:boolean" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Should the search be recursive.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="user-dn" type="xs:string" default="dn">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the attribute which is the users distinguished name.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-
-    <xs:complexType name="usersAuthenticationType">
-           <xs:annotation>
-            <xs:documentation>
-                A set of users
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="user" type="userType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="userType">
-        <xs:annotation>
-            <xs:documentation>
-                A single user.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="password" type="xs:string" />
-        </xs:choice>
-        <xs:attribute name="username" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The users username.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="propertiesFileType">
-        <xs:annotation>
-            <xs:documentation>
-                Declaration of a location of a properties file.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="relative-to" use="optional" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of another previously named path, or of one of the
-                    standard paths provided by the system. If 'relative-to' is
-                    provided, the value of the 'path' attribute is treated as
-                    relative to the path specified by this attribute.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="path" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The path of the properties file.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="propertiesAuthenticationType">
-        <xs:annotation>
-            <xs:documentation>
-                Declaration of users stored within properties files.
-
-                The entries within the properties file are username={credentials} with each user
-                being specified on it's own line.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="propertiesFileType">
-                <xs:attribute name="plain-text" type="xs:boolean" default="false">
-                    <xs:annotation>
-                        <xs:documentation>
-                            Are the credentials within the properties file stored in plain text, if not
-                            the {credential} is expected to be the hex encoded Digest hash
-                            of 'username : realm : password'.
-                        </xs:documentation>
-                    </xs:annotation>
-            </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="host-management-interfacesType">
-        <xs:sequence>
-            <xs:element name="native-interface" type="host-native-management-interfaceType"/>
-            <xs:element name="http-interface" type="host-http-management-interfaceType" minOccurs="0"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="management-interfaceType">
-        <xs:attribute name="security-realm" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    The security realm to use for this management interface, the capabilities
-                    of the security realm will be queried to identify the authentication mechanism(s) to
-                    offer.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="host-native-management-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of a host's exposed native management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="management-interfaceType">
-                <xs:sequence>
-                    <xs:element name="socket" type="native-management-socketType"/>
-                </xs:sequence>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="management-socketType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the socket used by host or standalone server's exposed management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="interface" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    Network interface on which the host's socket for
-                    management communication should be opened.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="native-management-socketType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the socket used by host or standalone server's exposed HTTP management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="management-socketType">
-                <xs:attribute name="port" type="xs:int" use="required">
-                    <xs:annotation>
-                        <xs:documentation>
-                            Port on which the host's socket for native
-                            management communication should be opened.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="host-http-management-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of a host's exposed HTTP management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="management-interfaceType">
-                <xs:sequence>
-                    <xs:element name="socket" type="http-management-socketType"/>
-                </xs:sequence>
-                <xs:attribute name="console-enabled" type="xs:boolean" use="optional" default="true"/>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="http-management-socketType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the socket used by host or standalone server's exposed HTTP management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="management-socketType">
-                <xs:attribute name="port" type="xs:int" use="optional">
-                    <xs:annotation>
-                        <xs:documentation>
-                            Port on which the host's socket for
-                            management communication should be opened.
-
-                            If not specified the port will not be opened.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-                <xs:attribute name="secure-port" type="xs:int" use="optional">
-                    <xs:annotation>
-                        <xs:documentation>
-                            Port on which the host's socket for HTTPS
-                            management communication should be opened.
-
-                            If not specified the port will not be opened.
-
-                            If specified the security-realm will be required to obtain
-                            the SSL configuration.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="server-management-interfacesType">
-        <xs:sequence>
-            <xs:element name="native-remoting-interface" type="management-remoting-interfaceType" minOccurs="0"/>
-            <xs:element name="native-interface" type="server-native-management-interfaceType" minOccurs="0"/>
-            <xs:element name="http-interface" type="server-http-management-interfaceType" minOccurs="0"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="server-native-management-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the socket used by host or standalone server's exposed HTTP management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="management-interfaceType">
-                <xs:annotation>
-                    <xs:documentation>
-                        Configuration of the socket to use for the native management interface is a choice
-                        between a direct configuration of the address and port, or a reference to a socket-binding
-                        configuration in the server's socket-binding-group element. The latter is the recommended
-                        approach is it makes it easier to avoid port conflicts by taking advantage of the
-                        socket-binding-group's port-offset configuration. Direct configuration of the address and
-                        ports is provided to preserve backward compatibility.
-                    </xs:documentation>
-                </xs:annotation>
-                <xs:choice>
-                    <xs:element name="socket" type="native-management-socketType"/>
-                    <xs:element name="socket-binding" type="native-management-socket-binding-refType"/>
-                </xs:choice>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="native-management-socket-binding-refType">
-        <xs:annotation>
-            <xs:documentation>
-                Reference to the configuration of the socket to be used by a standalone server's exposed native management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="native" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of a socket-binding configuration declared in the server's socket-binding-group.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="server-http-management-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of a standalone server's exposed HTTP/HTTPS management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="management-interfaceType">
-                <xs:annotation>
-                    <xs:documentation>
-                        Configuration of the socket to use for the HTTP/HTTPS management interface is a choice
-                        between a direct configuration of the address and ports, or a reference to socket-binding
-                        configurations in the server's socket-binding-group element. The latter is the recommended
-                        approach is it makes it easier to avoid port conflicts by taking advantage of the
-                        socket-binding-group's port-offset configuration. Direct configuration of the address and
-                        ports is provided to preserve backward compatibility.
-                    </xs:documentation>
-                </xs:annotation>
-                <xs:choice>
-                    <xs:element name="socket" type="http-management-socketType"/>
-                    <xs:element name="socket-binding" type="http-management-socket-binding-refType"/>
-                </xs:choice>
-                <xs:attribute name="console-enabled" type="xs:boolean" use="optional" default="true"/>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="http-management-socket-binding-refType">
-        <xs:annotation>
-            <xs:documentation>
-                Reference to the configurations of the sockets to be used by a standalone server's exposed HTTP and HTTPS management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="http" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of a socket-binding configuration declared in the server's socket-binding-group to use for a HTTP socket.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="https" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of a socket-binding configuration declared in the server's socket-binding-group to use for a HTTPS socket.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="management-remoting-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                Makes the native management interface available via the connectors set up in the remoting subsystem,
-                using the remoting subsystem's endpoint. This should only be used for a server not for a HC/DC.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="domain-controllerType">
-        <xs:choice>
-            <xs:element name="local" type="domain-controller-localType"/>
-            <xs:element name="remote" type="domain-controller-remoteType"/>
-        </xs:choice>
-    </xs:complexType>
-
-    <xs:complexType name="domain-controller-localType" />
-
-    <xs:complexType name="domain-controller-remoteType">
-        <xs:sequence>
-            <xs:element name="ignored-resources" type="ignored-resourcesType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-        <xs:attribute name="host" type="xs:string" use="required" />
-        <xs:attribute name="port" type="xs:integer" use="required" />
-        <xs:attribute name="security-realm" type="xs:string" use="optional" />
-        <xs:attribute name="username" type="xs:string" use="optional" />
-    </xs:complexType>
-
-    <xs:complexType name="ignored-resourcesType">
-        <xs:annotation>
-            <xs:documentation>
-                Provides names of direct child resources of the domain root resource requests for which the
-                Host Controller should ignore. Only relevant on a slave Host Controller. Configuring such
-                "ignored resources" may help allow a Host Controller from an earlier release to function as a
-                slave to a master Host Controller running a later release, by letting the slave ignore portions
-                of the configuration its version of the software cannot understand. This strategy can only be
-                successful if the servers managed by the slave Host Controller do not reference any of the
-                ignored configuration.
-
-                Supports the following attributes:
-
-                type -- the type of resource (e.g. 'profile' or 'socket-binding-group') certain instances of which
-                        should be ignored. The value corresponds to the 'key' portion of the first element in the
-                        resource's address (e.g. 'profile' in the address /profile=ha/subsystem=web)
-
-                wildcard -- if 'true', all resources of the given type should be ignored.
-
-                Child elements list the names of specific instances of the given type of resource
-                that should be ignored. Each element in the list corresponds to the 'value' portion of
-                the first element in the resource's address (e.g. 'ha' in the address /profile=ha/subsystem=web.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="instance" type="ignored-resource-instanceType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-        <xs:attribute name="type" type="xs:string" use="required" />
-        <xs:attribute name="wildcard" type="xs:boolean" use="optional" default="false" />
-        <xs:attribute name="names" type="xs:string" use="optional" />
-    </xs:complexType>
-
-    <xs:complexType name="ignored-resource-instanceType">
-        <xs:annotation>
-            <xs:documentation>
-                The name of a specific instances of a particular type of resource that should be ignored.
-                The 'name' attribute corresponds to the 'value' portion of the first element in the resource's address
-                (e.g. 'ha' in the address /profile=ha/subsystem=web.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="required" />
-    </xs:complexType>
-
-    <xs:complexType name="serversType">
-        <xs:sequence>
-            <xs:element name="server" type="serverType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-        <xs:attribute name="directory-grouping" default="by-server" use="optional">
-            <xs:simpleType>
-                <xs:restriction base="xs:token">
-                    <xs:enumeration value="by-server">
-                        <xs:annotation>
-                            <xs:documentation>
-                                Indicates each server's writable directories should be grouped under the server's name
-                                in the domain/servers directory. This is the default option.
-                            </xs:documentation>
-                        </xs:annotation>
-                    </xs:enumeration>
-                    <xs:enumeration value="by-type">
-                        <xs:annotation>
-                            <xs:documentation>
-                                Indicates each server's writable directories should be grouped based on their "type"
-                                (i.e. "data", "log", "tmp") with directories of a given type for all servers appearing
-                                in the domain level directory for that type, e.g. domain/data/servers/server-name.
-                            </xs:documentation>
-                        </xs:annotation>
-                    </xs:enumeration>
-                </xs:restriction>
-            </xs:simpleType>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="serverType">
-        <xs:all>
-            <xs:element name="paths" type="specified-pathsType" minOccurs="0" maxOccurs="1" />
-
-            <xs:element name="interfaces" type="specified-interfacesType" minOccurs="0"/>
-            <xs:element name="socket-bindings" type="server-socket-bindingsType" minOccurs="0"/>
-
-            <!--<xs:element name="loggers" type="loggersType" minOccurs="0"/>-->
-            <xs:element name="system-properties" type="properties-with-boottime" minOccurs="0"/>
-            <xs:element name="jvm" minOccurs="0" type="serverJvmType"/>
-        </xs:all>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="group" type="xs:string" use="required"/>
-        <xs:attribute name="auto-start" type="xs:boolean" default="true"/>
-    </xs:complexType>
-
-    <xs:complexType name="server-socket-bindingsType">
-        <xs:annotation>
-            <xs:documentation>
-            <![CDATA[
-                Server-specific overrides to the default socket binding configuration inherited from the server group.
-            ]]>
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="socket-binding-group" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                <![CDATA[
-                    The socket binding group to use for the server. If undefined, the socket binding group
-                    specified for the server group is used.
-                ]]>
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="port-offset" type="xs:int" default="0" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                <![CDATA[
-                    Increment to apply to the base port values defined in the
-                    referenced socket binding group to derive the values to use on this
-                    server.
-                ]]>
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="extensionsType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of extension modules.</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="extension" type="extensionType" minOccurs="1" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="extensionType">
-        <xs:annotation>
-            <xs:documentation>
-                A module that extends the standard capabilities of a domain
-                or a standalone server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="module" use="required" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>The name of the module</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="server-groupsType">
-        <xs:sequence>
-            <xs:element name="server-group" type="server-groupType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="server-groupType">
-        <xs:sequence>
-            <xs:element name="jvm" type="namedJvmType" minOccurs="0"/>
-            <xs:element name="socket-binding-group" type="socket-binding-group-refType" minOccurs="1"/>
-
-            <xs:element name="deployments" type="server-groupDeploymentsType" minOccurs="0"/>
-
-            <xs:element name="system-properties" minOccurs="0" type="properties-with-boottime"/>
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the server group
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="profile" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the profile this server is running.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="management-subsystem-endpoint" type="xs:boolean" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Set to true to have servers belonging to the server group connect back to the host controller using the
-                    endpoint from their remoting subsystem. The subsystem must be preset for this to
-                    work.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="server-groupDeploymentsType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of deployments that have been mapped to a server-group.</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="deployment" type="base-deploymentType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="server-groupDeploymentType">
-        <xs:annotation>
-            <xs:documentation>A deployment that has been mapped to a server group.</xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="base-deploymentType">
-                <!--  TODO clarify what a value of 'false' means -->
-                <xs:attribute name="enabled" use="optional" type="xs:boolean" default="true">
-                    <xs:annotation>
-                        <xs:documentation>Whether the deployment deploy automatically when the server starts up.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="base-deploymentType">
-        <xs:attribute name="name" use="required">
-            <xs:annotation>
-                <xs:documentation>Unique identifier of the deployment. Must be unique across all deployments.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="runtime-name" use="required">
-            <xs:annotation>
-                <xs:documentation>Name by which the deployment will be known within a running server.of the deployment.
-                    Does not need to be unique across all deployments in the domain, although it must be unique within
-                    an individual server. For example, two different deployments running on different servers in
-                    the domain could both have a 'runtime-name' of 'example.war', with one having a 'name'
-                    of 'example.war_v1' and another with an 'name' of 'example.war_v2'.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="server-deploymentsType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of deployments that have been mapped to a server.</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="deployment" type="server-deploymentType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="server-deploymentType">
-        <xs:annotation>
-            <xs:documentation>A deployment that has been mapped to a server.</xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="base-deploymentType">
-                <xs:sequence>
-                    <!-- TODO: maxOccurs should be unbounded once overlays are in place -->
-                    <xs:choice maxOccurs="1">
-                        <xs:element name="content" type="contentType"/>
-                        <xs:element name="fs-archive" type="fs-archiveType"/>
-                        <xs:element name="fs-exploded" type="fs-explodedType"/>
-                    </xs:choice>
-                </xs:sequence>
-                <!--  TODO clarify what a value of 'false' means -->
-                <xs:attribute name="enabled" use="optional" type="xs:boolean" default="true">
-                    <xs:annotation>
-                        <xs:documentation>Whether the deployment deploy automatically when the server starts up.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="contentType">
-        <xs:attribute name="sha1" use="required">
-            <xs:annotation>
-                <xs:documentation>The checksum of the content</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="fs-archiveType">
-        <xs:annotation>
-            <xs:documentation>Archived content found on the filesystem</xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="fs-baseType"/>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="fs-baseType">
-        <xs:complexContent>
-            <xs:extension base="pathType"/>
-        </xs:complexContent>
-        <!-- TODO: make path required
-        <xs:complexContent>
-            <xs:restriction base="pathType">
-                <xs:attribute name="path" use="required"/>
-            </xs:restriction>
-        </xs:complexContent>
-        -->
-    </xs:complexType>
-
-    <xs:complexType name="fs-explodedType">
-        <xs:annotation>
-            <xs:documentation>Exploded content found on the filesystem</xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="fs-baseType"/>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="domain-deploymentsType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of domain-level deployments</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="deployment" type="domain-deploymentType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="domain-deploymentType">
-        <xs:annotation>
-            <xs:documentation>Deployment represents anything that can be deployed (e.g. an application such as EJB-JAR,
-                WAR, EAR,
-                any kind of standard archive such as RAR or JBoss-specific deployment),
-                which can be enabled or disabled on a domain level.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="base-deploymentType">
-                <xs:sequence>
-                    <!-- TODO: maxOccurs should be unbounded once overlays are in place -->
-                    <xs:choice maxOccurs="1">
-                        <xs:element name="content" type="contentType"/>
-                        <xs:element name="fs-archive" type="fs-archiveType"/>
-                        <xs:element name="fs-exploded" type="fs-explodedType"/>
-                    </xs:choice>
-                </xs:sequence>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <!-- TODO this is not used anywhere yet -->
-    <xs:complexType name="clustersType">
-        <xs:complexContent>
-            <xs:extension base="server-groupType">
-                <xs:sequence>
-                    <xs:element name="partition-name" type="xs:string"/>
-                    <xs:element name="state-transfer-timeout" type="xs:integer"/>
-                    <xs:element name="method-call-timeout" type="xs:integer"/>
-                </xs:sequence>
-                <xs:attribute name="category" type="xs:string" use="required"/>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <!-- domain-configuration related definitions -->
-    <xs:complexType name="domain-configurationType">
-        <xs:annotation>
-            <xs:documentation>The domain controller/server bootstrap configuration</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element ref="bootstrapURI"/>
-        </xs:sequence>
-    </xs:complexType>
-    <xs:element name="bootstrapURI" type="xs:string">
-        <xs:annotation>
-            <xs:documentation>The URI for bootstrapping a domain server</xs:documentation>
-        </xs:annotation>
-    </xs:element>
-
-    <xs:complexType name="profilesType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of profiles available for use in the domain</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="profile" type="domain-profileType" minOccurs="1" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="domain-profileType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of subsystems</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded">
-                <xs:annotation>
-                    <xs:documentation>A profile declaration may include configuration
-                        elements from other namespaces for the subsystems that make up the profile.
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:any>
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>Name of the profile</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="standalone-profileType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of subsystems</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:choice minOccurs="1" maxOccurs="unbounded">
-                <xs:any namespace="##other">
-                    <xs:annotation>
-                        <xs:documentation>A profile declaration may include configuration
-                            elements from other namespaces for the subsystems that make up the profile.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:any>
-            </xs:choice>
-        </xs:sequence>
-    </xs:complexType>
-
-    <!-- general socket definition -->
-    <xs:complexType name="socket-binding-groupsType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of socket binding groups</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="socket-binding-group" type="socket-binding-groupType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="socket-binding-groupType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of socket configurations</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="socket-binding" type="socket-bindingType" maxOccurs="unbounded"/>
-            <xs:element name="outbound-socket-binding" type="outbound-socket-bindingType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="default-interface" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of an interface that should be used as the interface for
-                    any sockets that do not explicitly declare one.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="standalone-socket-binding-groupType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of socket configurations</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="socket-binding" type="socket-bindingType" maxOccurs="unbounded"/>
-            <xs:element name="outbound-socket-binding" type="outbound-socket-bindingType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="default-interface" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of an interface that should be used as the interface for
-                    any sockets that do not explicitly declare one.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-	    <xs:attribute name="port-offset" type="xs:int" use="optional" default="0">
-	        <xs:annotation>
-                <xs:documentation>
-	                    Increment to apply to the base port values defined in the
-	                    socket group to derive the values to use on this
-	                    server.
-	            </xs:documentation>
-	        </xs:annotation>
-	    </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="socket-bindingType">
-        <xs:annotation>
-            <xs:documentation>Configuration information for a socket.</xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="client-mapping" type="socket-binding-client-mappingType"
-                        minOccurs="0" maxOccurs="unbounded">
-                <xs:annotation>
-                    <xs:documentation>
-                        Specifies zero or more client mappings for this socket binding.
-                        A client connecting to this socket should use the destination address
-                        specified in the mapping that matches its desired outbound interface.
-                        This allows for advanced network topologies that use either network
-                        address translation, or have bindings on multiple network interfaces
-                        to function.
-
-                        Each mapping should be evaluated in declared order, with the first successful
-                        match used to determine the destination.
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:element>
-        </xs:choice>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="interface" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of the interface to which the socket should be bound, or, for multicast
-                    sockets, the interface on which it should listen. This should
-                    be one of the declared interfaces.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="port" type="xs:unsignedShort" use="optional" default="0">
-            <xs:annotation>
-                <xs:documentation>
-                    Number of the port to which the socket should be bound.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="fixed-port" type="xs:boolean" use="optional" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Whether the port value should remain fixed even if numerically offsets
-                    are applied to the other sockets in the socket group..
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="multicast-address" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Multicast address on which the socket should receive multicast
-                    traffic. If unspecified, the socket will not be configured
-                    to receive multicast.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="multicast-port" type="xs:positiveInteger" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Port on which the socket should receive multicast
-                    traffic. Must be configured if 'multicast-address' is configured.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="socket-binding-client-mappingType">
-        <xs:annotation>
-                <xs:documentation>
-                    Type definition for a client mapping on a socket binding. A client
-                    mapping specifies how external clients should connect to this
-                    socket's port, provided that the client's outbound interface
-                    match the specified source network value.
-                </xs:documentation>
-            </xs:annotation>
-        <xs:attribute name="source-network" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Source network the client connection binds on. This value is in
-                    the form of ip/netmask. A client should match this value against
-                    the desired client host network interface, and if matched the
-                    client should connect to the corresponding destination values.
-
-                    If omitted this mapping should match any interface.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="destination-address" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The destination address that a client should connect to if the
-                    source-network matches. This value can either be a hostname or
-                    an ip address.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="destination-port" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    The destination port that a client should connect to if the
-                    source-network matches.
-
-                    If omitted this mapping will reuse the effective socket binding
-                    port.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="outbound-socket-bindingType">
-        <xs:annotation>
-            <xs:documentation>Configuration information for a outbound socket.</xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="remote-destination" type="remote-destinationType" maxOccurs="1"/>
-            <xs:element name="local-destination" type="local-destinationType" maxOccurs="1"/>
-        </xs:choice>
-
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the outbound socket binding
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="source-interface" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the interface that should be used for setting up the source address of the
-                    outbound socket. This should be one of the declared interfaces.
-                </xs:documentation>
-            </xs:annotation>
-
-        </xs:attribute>
-        <xs:attribute name="source-port" type="xs:positiveInteger" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    The port number that will be used for setting the source addresss of the outbound socket. If the
-                    source-interface attribute has been specified and the source-port attribute is absent,
-                    then the system uses a ephemeral port while binding the socket to a source address.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="fixed-source-port" type="xs:boolean" use="optional" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Whether the source-port value should remain fixed even if the socket binding group specifies
-                    a port offset
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="remote-destinationType">
-        <xs:attribute name="host" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The remote server address to which the outbound socket has to be connect.
-                    The address can be either a IP address of the host server of the hostname of the server
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="port" type="xs:positiveInteger" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The remote port to which the outbound socket has to connect.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="local-destinationType">
-        <xs:attribute name="socket-binding-ref" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The reference to a socket binding that has to be used as the destination for the outbound
-                    socket binding. This socket binding name should belong to the same socket binding group
-                    to which this local destination client socket belongs.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="socket-binding-group-refType">
-        <xs:attribute name="ref" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The socket group to use for the server group or server.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="port-offset" type="xs:int" default="0" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Increment to apply to the base port values defined in the
-                    referenced socket group to derive the values to use on this
-                    server.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-
-    <xs:complexType name="named-interfacesType">
-        <xs:annotation>
-            <xs:documentation>
-                A list of named network interfaces. The interfaces may or may
-                not be fully specified (i.e. include criteria on how to determine
-                their IP address.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="interface" type="named-interfaceType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <!-- TODO make this and specified-interfaceType the same except for interface-criteriaGroup minOccurs -->
-    <xs:complexType name="named-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                A named network interface, but without any criteria
-                for determining the IP address to associate with that interface.
-                Acts as a placeholder in the model (e.g. at the domain level)
-                until a fully specified interface definition is applied at a
-                lower level (e.g. at the server level, where available addresses
-                are known.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:group ref="interface-criteriaGroup" minOccurs="0"/>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-    </xs:complexType>
-
-    <xs:complexType name="specified-interfacesType">
-        <xs:annotation>
-            <xs:documentation>
-                A list of fully specified named network interfaces.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="interface" type="specified-interfaceType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="specified-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                A named network interface, along with required criteria
-                for determining the IP address to associate with that interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:group ref="interface-criteriaGroup" minOccurs="1"/>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-    </xs:complexType>
-
-    <xs:group name="interface-criteriaGroup">
-        <xs:annotation>
-            <xs:documentation>
-                A set of criteria that can be used at runtime to determine
-                what IP address to use for an interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="any-address" type="any-addressType"/>
-            <xs:element name="any-ipv6-address" type="any-ipv6-addressType"/>
-            <xs:element name="any-ipv4-address" type="any-ipv4-addressType"/>
-            <xs:choice maxOccurs="unbounded">
-                <xs:element name="inet-address" type="inet-addressType"/>
-                <xs:element name="loopback" type="loopbackType"/>
-                <xs:element name="loopback-address" type="loopback-addressType"/>
-                <xs:element name="multicast" type="multicastType"/>
-                <xs:element name="point-to-point" type="point-to-pointType"/>
-                <xs:element name="virtual" type="interface-virtualType"/>
-                <xs:element name="up" type="interface-upType"/>
-                <xs:element name="public-address" type="public-addressType"/>
-                <xs:element name="link-local-address" type="link-local-addressType"/>
-                <xs:element name="site-local-address" type="site-local-addressType"/>
-                <xs:element name="nic" type="nicType"/>
-                <xs:element name="nic-match" type="nic-matchType"/>
-                <xs:element name="subnet-match" type="subnet-matchType"/>
-                <xs:element name="not" type="address-exclusionType"/>
-                <xs:element name="any" type="address-exclusionType"/>
-            </xs:choice>
-        </xs:choice>
-    </xs:group>
-
-    <xs:complexType name="inet-addressType">
-        <xs:attribute name="value" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    Either a IP address in IPv6 or IPv4 dotted decimal notation,
-                    or a hostname that can be resolved to an IP address.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="nicType">
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of a network interface (e.g. eth0, eth1, lo).
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="nic-matchType">
-        <xs:attribute name="pattern" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    A regular expression against which the names of the network
-                    interfaces available on the machine can be matched to find
-                    an acceptable interface.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="subnet-matchType">
-        <xs:attribute name="value" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    A network IP address and the number of bits in the
-                    address' network prefix, written in "slash notation";
-                    e.g. "192.168.0.0/16".
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="address-exclusionType">
-        <xs:choice>
-            <xs:element name="inet-address" type="inet-addressType" minOccurs="0" maxOccurs="unbounded"/>
-            <xs:element name="loopback" type="loopbackType"/>
-            <xs:element name="loopback-address" type="loopback-addressType"/>
-            <xs:element name="multicast" type="multicastType"/>
-            <xs:element name="point-to-point" type="point-to-pointType"/>
-            <xs:element name="virtual" type="interface-virtualType"/>
-            <xs:element name="up" type="interface-upType"/>
-            <xs:element name="public-address" type="public-addressType"/>
-            <xs:element name="link-local-address" type="link-local-addressType"/>
-            <xs:element name="site-local-address" type="site-local-addressType"/>
-            <xs:element name="nic" type="nicType" minOccurs="0" maxOccurs="unbounded"/>
-            <xs:element name="nic-match" type="nic-matchType" minOccurs="0" maxOccurs="unbounded"/>
-            <xs:element name="subnet-match" type="subnet-matchType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:choice>
-    </xs:complexType>
-
-    <xs:complexType name="loopbackType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it is a loopback
-                interface.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="loopback-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                A loopback address that may not actually be configured on the machine's loopback interface.
-                Differs from inet-addressType in that the given value will be used even if no NIC can
-                be found that has the IP address associated with it.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="value" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    An IP address in IPv6 or IPv4 dotted decimal notation.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="multicastType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it supports
-                multicast.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="point-to-pointType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it is a point-to-point
-                interface.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="interface-upType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it is currently up.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="interface-virtualType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it is a virtual
-                interface.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="public-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it has a publicly
-                routable address.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="site-local-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not an address associated
-                with it is site-local.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="link-local-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not an address associated
-                with it is link-local.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="any-ipv6-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that sockets using this interface
-                should be bound to the IPv6 wildcard address (::).
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="any-ipv4-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that sockets using this interface
-                should be bound to the IPv4 wildcard address (0.0.0.0).
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="any-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that sockets using this interface
-                should be bound to a wildcard address. The IPv6 wildcard
-                address (::) will be used unless the java.net.preferIpV4Stack
-                system property is set to true, in which case the IPv4
-                wildcard address (0.0.0.0) will be used. If a socket is
-                bound to an IPv6 anylocal address on a dual-stack machine,
-                it can accept both IPv6 and IPv4 traffic; if it is bound to
-                an IPv4 (IPv4-mapped) anylocal address, it can only accept
-                IPv4 traffic.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="socketType">
-        <xs:annotation>
-            <xs:documentation>Configuration information for a socket.</xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="interface" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of the interface to which the socket should be bound, or, for multicast
-                    sockets, the interface on which it should listen. This should
-                    be one of the declared interfaces.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="port" type="xs:unsignedShort" use="optional" default="0">
-            <xs:annotation>
-                <xs:documentation>
-                    Number of the port to which the socket should be bound.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="fixed-port" type="xs:boolean" use="optional" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Whether the port value should remain fixed even if numerically offsets
-                    are applied to the other sockets in the socket group..
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="multicast-address" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Multicast address on which the socket should receive multicast
-                    traffic. If unspecified, the socket will not be configured
-                    to receive multicast.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="multicast-port" type="xs:positiveInteger" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Port on which the socket should receive multicast
-                    traffic. If unspecified, the socket will not be configured
-                    to receive multicast.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <!-- Path configurations -->
-    <xs:complexType name="named-pathsType">
-        <xs:annotation>
-            <xs:documentation>
-                A list of named filesystem paths. The paths may or may
-                not be fully specified (i.e. include the actual paths.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="path" type="named-pathType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="named-pathType">
-        <xs:annotation>
-            <xs:documentation>
-                A named filesystem path, but without a requirement to specify
-                the actual path. If no actual path is specified, acts as a
-                as a placeholder in the model (e.g. at the domain level)
-                until a fully specified path definition is applied at a
-                lower level (e.g. at the host level, where available addresses
-                are known.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="pathType">
-                <xs:attribute name="name" type="xs:string" use="required">
-                    <xs:annotation>
-                        <xs:documentation>
-                        The name of the path. Cannot be one of the standard fixed paths
-                        provided by the system:
-
-                        jboss.home - the root directory of the JBoss AS distribution
-                        user.home - user's home directory
-                        user.dir - user's current working directory
-                        java.home - java installation directory
-                        jboss.server.base.dir - root directory for an individual server
-                                                instance
-
-                        Note that the system provides other standard paths that can be
-                        overridden by declaring them in the configuration file. See
-                        the 'relative-to' attribute documentation for a complete
-                        list of standard paths.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="pathType">
-        <xs:attribute name="path">
-            <xs:annotation>
-                <xs:documentation>
-                The actual filesystem path. Treated as an absolute path, unless the
-                'relative-to' attribute is specified, in which case the value
-                is treated as relative to that path.
-
-                If treated as an absolute path, the actual runtime pathname specified
-                by the value of this attribute will be determined as follows:
-
-                If this value is already absolute, then the value is directly
-                used.  Otherwise the runtime pathname is resolved in a
-                system-dependent way.  On UNIX systems, a relative pathname is
-                made absolute by resolving it against the current user directory.
-                On Microsoft Windows systems, a relative pathname is made absolute
-                by resolving it against the current directory of the drive named by the
-                pathname, if any; if not, it is resolved against the current user
-                directory.
-                </xs:documentation>
-            </xs:annotation>
-            <xs:simpleType>
-                <xs:restriction base="xs:string">
-                    <xs:minLength value="1"/>
-                </xs:restriction>
-            </xs:simpleType>
-        </xs:attribute>
-        <xs:attribute name="relative-to" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                The name of another previously named path, or of one of the
-                standard paths provided by the system. If 'relative-to' is
-                provided, the value of the 'path' attribute is treated as
-                relative to the path specified by this attribute. The standard
-                paths provided by the system include:
-
-                jboss.home - the root directory of the JBoss AS distribution
-                user.home - user's home directory
-                user.dir - user's current working directory
-                java.home - java installation directory
-                jboss.server.base.dir - root directory for an individual server
-                                        instance
-                jboss.server.config.dir - directory in which server configuration
-                                          files are stored.
-                jboss.server.data.dir - directory the server will use for persistent
-                                        data file storage
-                jboss.server.log.dir - directory the server will use for
-                                       log file storage
-                jboss.server.temp.dir - directory the server will use for
-                                       temporary file storage
-                jboss.domain.servers.dir - directory under which a host controller
-                                           will create the working area for
-                                           individual server instances
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="specified-pathsType">
-        <xs:annotation>
-            <xs:documentation>
-                A list of named filesystem paths.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="path" type="specified-pathType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="specified-pathType">
-        <xs:annotation>
-            <xs:documentation>
-                A named filesystem path.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                The name of the path. Cannot be one of the standard fixed paths
-                provided by the system:
-
-                jboss.home.dir - the root directory of the JBoss AS distribution
-                user.home - user's home directory
-                user.dir - user's current working directory
-                java.home - java installation directory
-                jboss.server.base.dir - root directory for an individual server
-                                        instance
-
-                Note that the system provides other standard paths that can be
-                overridden by declaring them in the configuration file. See
-                the 'relative-to' attribute documentation for a complete
-                list of standard paths.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="path" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                The actual filesystem path. Treated as an absolute path, unless the
-                'relative-to' attribute is specified, in which case the value
-                is treated as relative to that path.
-
-                If treated as an absolute path, the actual runtime pathname specified
-                by the value of this attribute will be determined as follows:
-
-                If this value is already absolute, then the value is directly
-                used.  Otherwise the runtime pathname is resolved in a
-                system-dependent way.  On UNIX systems, a relative pathname is
-                made absolute by resolving it against the current user directory.
-                On Microsoft Windows systems, a relative pathname is made absolute
-                by resolving it against the current directory of the drive named by the
-                pathname, if any; if not, it is resolved against the current user
-                directory.
-
-                Note relative path declarations have to use '/' as file separator.
-                </xs:documentation>
-            </xs:annotation>
-            <xs:simpleType>
-                <xs:restriction base="xs:string">
-                    <xs:minLength value="1"/>
-                </xs:restriction>
-            </xs:simpleType>
-        </xs:attribute>
-        <xs:attribute name="relative-to" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                The name of another previously named path, or of one of the
-                standard paths provided by the system. If 'relative-to' is
-                provided, the value of the 'path' attribute is treated as
-                relative to the path specified by this attribute. The standard
-                paths provided by the system include:
-
-                jboss.home.dir - the root directory of the JBoss AS distribution
-                user.home - user's home directory
-                user.dir - user's current working directory
-                java.home - java installation directory
-                jboss.server.base.dir - root directory for an individual server
-                                        instance
-                jboss.server.config.dir - directory in which server configuration
-                                          files are stored.
-                jboss.server.data.dir - directory the server will use for persistent
-                                        data file storage
-                jboss.server.log.dir - directory the server will use for
-                                       log file storage
-                jboss.server.temp.dir - directory the server will use for
-                                       temporary file storage
-                jboss.domain.servers.dir - directory under which a host controller
-                                           will create the working area for
-                                           individual server instances
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <!--  JVM configurations -->
-    <xs:complexType name="jvmsType">
-        <xs:sequence>
-            <xs:element name="jvm" type="namedJvmType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="jvmType">
-        <xs:all minOccurs="0" maxOccurs="1">
-            <xs:element name="heap" type="heapType" minOccurs="0"/>
-            <!-- XX:PermSize, XX:MaxPermSize -->
-            <xs:element name="permgen" type="bounded-memory-sizeType" minOccurs="0"/>
-            <!-- Xss -->
-            <xs:element name="stack" type="memory-sizeType" minOccurs="0"/>
-            <xs:element name="agent-lib" type="jvm-agentLibType" minOccurs="0"/>
-            <xs:element name="agent-path" type="jvm-agentPathType" minOccurs="0"/>
-            <xs:element name="java-agent" type="jvm-javaagentType" minOccurs="0"/>
-            <xs:element name="jvm-options" type="jvm-optionsType" minOccurs="0"/>
-            <xs:element name="environment-variables" type="environmentVariablesType" minOccurs="0"/>
-        </xs:all>
-        <xs:attribute name="java-home" type="xs:string"/>
-        <xs:attribute name="type" default="SUN">
-            <xs:simpleType>
-                <xs:restriction base="xs:token">
-                    <xs:enumeration value="SUN">
-			            <xs:annotation>
-			                <xs:documentation>Allows the full set of JVM options to be set via the jvm schema elements</xs:documentation>
-			            </xs:annotation>
-                    </xs:enumeration>
-                    <xs:enumeration value="IBM">
-                        <xs:annotation>
-                            <xs:documentation>Sets a subset of the JVM options via the jvm schema elements</xs:documentation>
-                        </xs:annotation>
-                    </xs:enumeration>
-                </xs:restriction>
-            </xs:simpleType>
-        </xs:attribute>
-        <xs:attribute name="env-classpath-ignored" default="true" type="xs:boolean"/>
-    </xs:complexType>
-
-    <xs:complexType name="namedJvmType">
-        <xs:complexContent>
-            <xs:extension base="jvmType">
-                <xs:attribute name="name" type="xs:string"/>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="serverJvmType">
-        <xs:complexContent>
-            <xs:extension base="namedJvmType">
-                <xs:attribute name="debug-enabled" type="xs:boolean" default="false"/>
-                <xs:attribute name="debug-options" type="xs:string" />
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="heapType">
-        <xs:attribute name="size" use="optional">
-            <xs:annotation>
-                <xs:documentation>Initial JVM heap size</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="max-size" use="optional">
-            <xs:annotation>
-                <xs:documentation>Maximum JVM heap size</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-optionsType">
-        <xs:sequence>
-            <xs:element name="option" type="jvm-optionType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-optionType">
-        <xs:attribute name="value" use="required">
-            <xs:annotation>
-                <xs:documentation>JVM option value</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-agentLibType">
-        <xs:attribute name="value" use="required">
-            <xs:annotation>
-                <xs:documentation>JVM agent lib value </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-agentPathType">
-        <xs:attribute name="value" use="required">
-            <xs:annotation>
-                <xs:documentation>JVM agent path value </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-javaagentType">
-        <xs:attribute name="value" use="required">
-            <xs:annotation>
-                <xs:documentation>JVM javaagent value </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="bounded-memory-sizeType">
-        <xs:attribute name="size" type="xs:string"/>
-        <xs:attribute name="max-size" type="xs:string"/>
-    </xs:complexType>
-
-    <xs:complexType name="memory-sizeType">
-        <xs:attribute name="size" type="xs:string" use="required"/>
-    </xs:complexType>
-
-    <xs:complexType name="properties-with-boottime">
-        <xs:sequence>
-            <xs:element name="property" type="boottimePropertyType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="properties">
-        <xs:sequence>
-            <xs:element name="property" type="propertyType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="environmentVariablesType">
-        <xs:sequence>
-            <xs:element name="variable" type="propertyType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="propertyType">
-        <xs:attribute name="name" use="required"/>
-        <xs:attribute name="value" use="optional"/>
-    </xs:complexType>
-
-    <xs:complexType name="boottimePropertyType">
-        <xs:complexContent>
-            <xs:extension base="propertyType">
-                <xs:attribute name="boot-time" type="xs:boolean" default="true"/>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-   <xs:complexType name="vaultType">
-      <xs:annotation>
-         <xs:documentation>
-               <![CDATA[
-                    Vault Configuration.
-                ]]>
-         </xs:documentation>
-      </xs:annotation>
-      <xs:sequence>
-          <xs:element name="vault-option" type="propertyType" minOccurs="0" maxOccurs="unbounded"/>
-      </xs:sequence>
-      <xs:attribute name="code" type="xs:string" use="optional"/>
-   </xs:complexType>
-
-    <xs:complexType name="management-client-contentType">
-        <xs:annotation>
-            <xs:documentation>
-                <![CDATA[
-                   Storage information about re-usable chunks of data useful to management clients that are stored
-                   in the domain content repository.
-                ]]>
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="rollout-plans" type="contentType" minOccurs="0" maxOccurs="1">
-                <xs:annotation>
-                    <xs:documentation>
-                        <![CDATA[
-                           Storage information about a set of named management update rollout plans useful to management
-                           clients that are stored in the domain content repository. The management API exposed by the domain
-                           controller provides access to these plans to management clients, allowing clients to use the plans
-                           by referencing them by name, avoiding the need to recreate them for each use.
-                        ]]>
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:element>
-        </xs:sequence>
-    </xs:complexType>
-
-
-</xs:schema>

jboss-as-7.2.0.Final/docs/schema/jboss-as-config_1_4.xsd

@@ -1,2390 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-  ~ JBoss, Home of Professional Open Source.
-  ~ Copyright 2012, Red Hat, Inc., and individual contributors
-  ~ as indicated by the @author tags. See the copyright.txt file in the
-  ~ distribution for a full listing of individual contributors.
-  ~
-  ~ This is free software; you can redistribute it and/or modify it
-  ~ under the terms of the GNU Lesser General Public License as
-  ~ published by the Free Software Foundation; either version 2.1 of
-  ~ the License, or (at your option) any later version.
-  ~
-  ~ This software is distributed in the hope that it will be useful,
-  ~ but WITHOUT ANY WARRANTY; without even the implied warranty of
-  ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-  ~ Lesser General Public License for more details.
-  ~
-  ~ You should have received a copy of the GNU Lesser General Public
-  ~ License along with this software; if not, write to the Free
-  ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
-  ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
-  -->
-
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
-           xmlns="urn:jboss:domain:1.4"
-           targetNamespace="urn:jboss:domain:1.4"
-           elementFormDefault="qualified"
-           attributeFormDefault="unqualified"
-        >
-
-
-    <xs:element name="domain">
-        <xs:annotation>
-            <xs:documentation>
-                Root element for the master document specifying the core configuration
-                for the servers in a domain. There should be one such master
-                document per domain, available to the host controller that
-                is configured to act as the domain controller.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element name="extensions" type="extensionsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="system-properties" type="properties-with-boottime" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="paths" type="named-pathsType" minOccurs="0" maxOccurs="1" />
-                <xs:element name="profiles" type="profilesType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="interfaces" type="named-interfacesType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="socket-binding-groups" type="socket-binding-groupsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="deployments" type="domain-deploymentsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="deployment-overlays" type="domain-deployment-overlaysType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="server-groups" type="server-groupsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="management-client-content" type="management-client-contentType" minOccurs="0" maxOccurs="1"/>
-            </xs:sequence>
-            <xs:attribute name="name" type="xs:string" use="optional" default="Unnamed Domain">
-               <xs:annotation>
-                  <xs:documentation>
-                     The name to use for the domain controller. Useful for administrators who need to work with multiple domains.
-                  </xs:documentation>
-               </xs:annotation>
-            </xs:attribute>
-        </xs:complexType>
-    </xs:element>
-
-    <xs:element name="host">
-        <xs:annotation>
-            <xs:documentation>
-                Root element for a document configuring a host controller and
-                the group of servers under the control of that host controller.
-                The standard usage would be for a domain to have one such host controller
-                on each physical (or virtual) host machine. Emphasis in this
-                document is on enumerating the servers, configuring items that
-                are specific to the host environment (e.g. IP addresses), and
-                on any server-specific configuration settings.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element name="system-properties" type="properties-with-boottime" minOccurs="0"/>
-                <xs:element name="paths" type="specified-pathsType" minOccurs="0" maxOccurs="1" />
-                <xs:element name="vault" type="vaultType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="management" type="host-managementType" minOccurs="1" maxOccurs="1"/>
-                <xs:element name="domain-controller" type="domain-controllerType"/>
-                <xs:element name="interfaces" type="specified-interfacesType" minOccurs="0"/>
-                <xs:element name="jvms" type="jvmsType" minOccurs="0"/>
-                <xs:element name="servers" type="serversType" minOccurs="0"/>
-            </xs:sequence>
-            <xs:attribute name="name" type="xs:string" use="optional">
-                <xs:annotation>
-                    <xs:documentation>
-                        The name to use for this host's host controller. Must be unique across the domain.
-                        If not set, defaults to the runtime value "HOSTNAME" or "COMPUTERNAME" environment variables,
-                        or, if neither environment variable is present, to the value of InetAddress.getLocalHost().getHostName().
-
-                        If the special value "jboss.domain.uuid" is used, a java.util.UUID will be created
-                        and used, based on the value of InetAddress.getLocalHost().
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:attribute>
-        </xs:complexType>
-    </xs:element>
-
-    <xs:element name="server">
-        <xs:annotation>
-            <xs:documentation>
-                Root element for a document specifying the configuration
-                of a single "standalone" server that does not operate
-                as part of a domain.
-
-                Note that this element is distinct from the 'serverType'
-                specified in this schema. The latter type forms part of the
-                configuration of a server that operates as part of a domain.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexType>
-            <xs:sequence>
-                <xs:element name="extensions" type="extensionsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="system-properties" type="properties" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="paths" type="specified-pathsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="vault" type="vaultType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="management" type="server-managementType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="profile" type="standalone-profileType" minOccurs="0"/>
-                <xs:element name="interfaces" type="specified-interfacesType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="socket-binding-group" type="standalone-socket-binding-groupType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="deployments" type="server-deploymentsType" minOccurs="0" maxOccurs="1"/>
-                <xs:element name="deployment-overlays" type="standalone-deployment-overlaysType" minOccurs="0" maxOccurs="1"/>
-            </xs:sequence>
-            <xs:attribute name="name" type="xs:string" use="optional">
-                <xs:annotation>
-                    <xs:documentation>
-                        The name to use for this server.
-                        If not set, defaults to the runtime value "HOSTNAME" or "COMPUTERNAME" environment variables,
-                        or, if neither environment variable is present, to the value of InetAddress.getLocalHost().getHostName().
-
-                        If the special value "jboss.domain.uuid" is used, a java.util.UUID will be created
-                        and used, based on the value of InetAddress.getLocalHost().
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:attribute>
-        </xs:complexType>
-    </xs:element>
-
-    <xs:complexType name="domain-managementType">
-        <xs:annotation>
-            <xs:documentation>
-                Domain-wide default configuration settings for the management of standalone servers and a Host Controller.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="security-realms" minOccurs="0">
-                <xs:complexType>
-                    <xs:sequence>
-                        <xs:element name="security-realm" type="security-realmType" minOccurs="1"
-                                    maxOccurs="unbounded"/>
-                    </xs:sequence>
-                </xs:complexType>
-            </xs:element>
-            <xs:element name="outbound-connections" minOccurs="0">
-                <xs:complexType>
-                    <xs:sequence>
-                      <xs:element name="ldap" type="ldapType" minOccurs="1" /> <!-- TODO minOccurs only while ldap is only supported connection. -->
-                    </xs:sequence>
-                </xs:complexType>
-            </xs:element>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="host-managementType">
-        <xs:annotation>
-            <xs:documentation>
-                The centralized configuration for the management of a Host Controller.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="domain-managementType">
-                <xs:sequence>
-                    <xs:element name="management-interfaces" type="host-management-interfacesType" minOccurs="1"/>
-                </xs:sequence>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="server-managementType">
-        <xs:annotation>
-            <xs:documentation>
-                The centralized configuration for the management of standalone server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="domain-managementType">
-                <xs:sequence>
-                    <xs:element name="management-interfaces" type="server-management-interfacesType" minOccurs="0"/>
-                </xs:sequence>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="ldapType">
-        <xs:annotation>
-            <xs:documentation>
-                The LDAP connection definition.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of this connection.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="url" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The URL to connect to ldap.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="search-dn" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    The distinguished name to use when connecting to LDAP to perform searches.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="search-credential" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    The credential to use when connecting to perform a search.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="security-realm" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    A reference to a security realm to obtain an initialised SSLContext to use when establishing a
-                    connection to the LDAP server.
-
-                    The realm referenced here MUST NOT be a realm that is also configured to use this connection.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="initial-context-factory" type="xs:string" default="com.sun.jndi.ldap.LdapCtxFactory">
-            <xs:annotation>
-                <xs:documentation>
-                    The initial context factory to establish the LdapContext.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="security-realmType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of a security realm for securing access to the management interfaces.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="plug-ins" type="plug-insType" minOccurs="0" />
-            <xs:element name="server-identities" type="server-identitiesType" minOccurs="0" />
-            <xs:element name="authentication" type="authenticationType" minOccurs="0" />
-            <xs:element name="authorization" type="authorizationType" minOccurs="0" />
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of this security-realm, each security-realm must be assigned a unique name.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="plug-insType">
-        <xs:annotation>
-            <xs:documentation>
-                List of modules to be searched for supported security realm plug-ins.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="plug-in" type="plug-inType" />
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="plug-inType">
-        <xs:attribute name="module" use="required" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>The name of the module.</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="plug-inAuthType">
-        <xs:annotation>
-            <xs:documentation>
-                This type defines which plug in will be used to handle either the loading of the
-                authentication data or authorization data during the authentication process.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="properties" type="properties" minOccurs="0">
-                <xs:annotation>
-                    <xs:documentation>
-                        The properties to be made available to the plug-in.
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:element>
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The short name of the plug-in as already dynamically registered by being referenced
-                    in the plug-ins element.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="mechanism" default="DIGEST" use="optional">
-           <xs:annotation>
-              <xs:documentation>
-                   By default plug-ins will be assumed to be used with the DIGEST authentication mechanism,
-                   this attribute can override the plug-in for use with the PLAIN mechanism.
-              </xs:documentation>
-           </xs:annotation>
-           <xs:simpleType>
-              <xs:restriction base="xs:string">
-                 <xs:enumeration value="DIGEST" />
-                 <xs:enumeration value="PLAIN" />
-              </xs:restriction>
-           </xs:simpleType>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="authorizationType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration defining how to load the authorization information for the authenticated user.
-
-                After a user has been authenticated additional information such as roles can be loaded and
-                associated with the user for subsequent authorization checks, this type is used to define
-                how the roles are loaded.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="properties" type="propertiesFileType" minOccurs="0" />
-            <xs:element name="plug-in" type="plug-inAuthType" minOccurs="0" />
-        </xs:choice>
-    </xs:complexType>
-
-    <xs:complexType name="server-identitiesType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the identities that represent the server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-          <xs:element name="ssl" type="sslType" minOccurs="0" />
-          <xs:element name="secret" type="secretType" minOccurs="0" />
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="secretType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the secret/password-based identity of this server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="value" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The secret / password - Base64 Encoded
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="sslType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the SSL identity of this server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="keystore" type="extendedKeyStoreType" />
-        </xs:sequence>
-        <xs:attribute name="protocol" type="xs:string" default="TLS">
-            <xs:annotation>
-                <xs:documentation>
-                    The protocol to use when creating the SSLContext.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="keyStoreType">
-        <xs:annotation>
-            <xs:documentation>
-                The keystore configuration for the server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="path" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The path of the keystore.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="relative-to" use="optional" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of another previously named path, or of one of the
-                    standard paths provided by the system. If 'relative-to' is
-                    provided, the value of the 'path' attribute is treated as
-                    relative to the path specified by this attribute.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="keystore-password" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The password to open the keystore.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="extendedKeyStoreType">
-        <xs:annotation>
-            <xs:documentation>
-                This is a more complex keystore definition which also allows for an alias
-                and key password to be specified.
-            </xs:documentation>
-        </xs:annotation>
-	    <xs:complexContent>
-            <xs:extension base="keyStoreType">
-                <xs:attribute name="alias" type="xs:string" use="optional">
-                    <xs:annotation>
-                        <xs:documentation>
-                            The alias of the entry to use from the keystore, if specified all remaining
-                            entries in the keystore will be ignored.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-                <xs:attribute name="key-password" type="xs:string" use="optional">
-                    <xs:annotation>
-                        <xs:documentation>
-                            The password to use when loading keys from the keystore.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-		    </xs:extension>
-	    </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="localType">
-        <xs:annotation>
-            <xs:documentation>
-                This type definition is used to control the local authentication mechanism.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="default-user" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    When using the local mechanism it is optional for the client side to send an
-                    authentication user name - this attribute specifies the user name to be assumed
-                    if the remote client does not send one.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="allowed-users" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    A comma separated list of users that can be specified by the client when connecting
-                    using the local authentication mechanism.
-
-                    If a default user has been specified then that user is automatically added to the
-                    allowed list.  If both default-user and allowed-users are ommitted despite the mechanism
-                    being enabled no incomming connection attemps using the mechanism will succeed.
-
-                    If any user name should be accepted the value should be set to "*".
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="authenticationType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the server side authentication mechanisms.
-
-                Optionally one truststore can be defined and one username/password based store can be defined.
-                Authentication will first attempt to use the truststore and if this is not available will fall back
-                to the username/password authentication.
-
-                If none of these are specified the only available mechanism will be the local mechanism for the
-                Native interface and the HTTP interface will not be accessible.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="truststore" type="keyStoreType" minOccurs="0">
-                <xs:annotation>
-                    <xs:documentation>
-                        Configuration of a keystore to use to create a trust manager to verify clients.
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:element>
-            <xs:element name="local" type="localType" minOccurs="0">
-                <xs:annotation>
-                    <xs:documentation>
-                        Configuration to enable the local authentication mechanism, if this element
-                        is ommitted then local authentication will be disabled.
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:element>
-            <xs:choice minOccurs="0">
-                <xs:element name="jaas" type="jaasAuthenticationType" minOccurs="0" />
-                <xs:element name="ldap" type="ldapAuthenticationType" minOccurs="0" />
-                <xs:element name="properties" type="propertiesAuthenticationType" minOccurs="0" />
-                <xs:element name="users" type="usersAuthenticationType" minOccurs="0" />
-                <xs:element name="plug-in" type="plug-inAuthType" minOccurs="0" />
-            </xs:choice>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="jaasAuthenticationType">
-        <xs:annotation>
-            <xs:documentation>
-                Definition to use a JAAS based configuration for authentication.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name identifying the jaas configuration of LoginModules.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="ldapAuthenticationType">
-        <xs:annotation>
-            <xs:documentation>
-                Definition to use LDAP as the user repository.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="username-filter">
-                <xs:complexType>
-                    <xs:attribute name="attribute" type="xs:string" use="required">
-                        <xs:annotation>
-                            <xs:documentation>
-                                The name of the attribute to search for the user, this filter will then perform
-                                a simple search where the username entered by the user matches the attribute
-                                specified here.
-                            </xs:documentation>
-                        </xs:annotation>
-                    </xs:attribute>
-                </xs:complexType>
-            </xs:element>
-            <xs:element name="advanced-filter">
-                <xs:complexType>
-                    <xs:attribute name="filter" type="xs:string" use="required">
-                        <xs:annotation>
-                            <xs:documentation>
-                                The fully defined filter to be used to search for the user based on their entered
-                                user ID. The filter should contain a variable in the form {0} - this will be
-                                replaced with the username supplied by the user.
-                            </xs:documentation>
-                        </xs:annotation>
-                    </xs:attribute>
-                </xs:complexType>
-            </xs:element>
-        </xs:choice>
-
-        <xs:attribute name="connection" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the connection to use to connect to LDAP.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="base-dn" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The base distinguished name to commence the search for the user.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="recursive" type="xs:boolean" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Should the search be recursive.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="user-dn" type="xs:string" default="dn">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the attribute which is the users distinguished name.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="allow-empty-passwords" type="xs:boolean" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Should users be allowed to supply an empty password?  Some LDAP servers will
-                    allow an anonymous bind so an empty password could appear as a successful authentication
-                    even though no password was sent to verify.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-
-    <xs:complexType name="usersAuthenticationType">
-           <xs:annotation>
-            <xs:documentation>
-                A set of users
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="user" type="userType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="userType">
-        <xs:annotation>
-            <xs:documentation>
-                A single user.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="password" type="xs:string" />
-        </xs:choice>
-        <xs:attribute name="username" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The users username.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="propertiesFileType">
-        <xs:annotation>
-            <xs:documentation>
-                Declaration of a location of a properties file.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="relative-to" use="optional" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of another previously named path, or of one of the
-                    standard paths provided by the system. If 'relative-to' is
-                    provided, the value of the 'path' attribute is treated as
-                    relative to the path specified by this attribute.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="path" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The path of the properties file.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="propertiesAuthenticationType">
-        <xs:annotation>
-            <xs:documentation>
-                Declaration of users stored within properties files.
-
-                The entries within the properties file are username={credentials} with each user
-                being specified on it's own line.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="propertiesFileType">
-                <xs:attribute name="plain-text" type="xs:boolean" default="false">
-                    <xs:annotation>
-                        <xs:documentation>
-                            Are the credentials within the properties file stored in plain text, if not
-                            the {credential} is expected to be the hex encoded Digest hash
-                            of 'username : realm : password'.
-                        </xs:documentation>
-                    </xs:annotation>
-            </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="host-management-interfacesType">
-        <xs:sequence>
-            <xs:element name="native-interface" type="host-native-management-interfaceType"/>
-            <xs:element name="http-interface" type="host-http-management-interfaceType" minOccurs="0"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="management-interfaceType">
-        <xs:attribute name="security-realm" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    The security realm to use for this management interface, the capabilities
-                    of the security realm will be queried to identify the authentication mechanism(s) to
-                    offer.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="host-native-management-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of a host's exposed native management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="management-interfaceType">
-                <xs:sequence>
-                    <xs:element name="socket" type="native-management-socketType"/>
-                </xs:sequence>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="management-socketType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the socket used by host or standalone server's exposed management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="interface" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    Network interface on which the host's socket for
-                    management communication should be opened.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="native-management-socketType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the socket used by host or standalone server's exposed HTTP management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="management-socketType">
-                <xs:attribute name="port" type="xs:int" use="required">
-                    <xs:annotation>
-                        <xs:documentation>
-                            Port on which the host's socket for native
-                            management communication should be opened.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="host-http-management-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of a host's exposed HTTP management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="management-interfaceType">
-                <xs:sequence>
-                    <xs:element name="socket" type="http-management-socketType"/>
-                </xs:sequence>
-                <xs:attribute name="console-enabled" type="xs:boolean" use="optional" default="true"/>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="http-management-socketType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the socket used by host or standalone server's exposed HTTP management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="management-socketType">
-                <xs:attribute name="port" type="xs:int" use="optional">
-                    <xs:annotation>
-                        <xs:documentation>
-                            Port on which the host's socket for
-                            management communication should be opened.
-
-                            If not specified the port will not be opened.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-                <xs:attribute name="secure-port" type="xs:int" use="optional">
-                    <xs:annotation>
-                        <xs:documentation>
-                            Port on which the host's socket for HTTPS
-                            management communication should be opened.
-
-                            If not specified the port will not be opened.
-
-                            If specified the security-realm will be required to obtain
-                            the SSL configuration.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="server-management-interfacesType">
-        <xs:sequence>
-            <xs:element name="native-remoting-interface" type="management-remoting-interfaceType" minOccurs="0"/>
-            <xs:element name="native-interface" type="server-native-management-interfaceType" minOccurs="0"/>
-            <xs:element name="http-interface" type="server-http-management-interfaceType" minOccurs="0"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="server-native-management-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of the socket used by host or standalone server's exposed HTTP management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="management-interfaceType">
-                <xs:annotation>
-                    <xs:documentation>
-                        Configuration of the socket to use for the native management interface is a choice
-                        between a direct configuration of the address and port, or a reference to a socket-binding
-                        configuration in the server's socket-binding-group element. The latter is the recommended
-                        approach is it makes it easier to avoid port conflicts by taking advantage of the
-                        socket-binding-group's port-offset configuration. Direct configuration of the address and
-                        ports is provided to preserve backward compatibility.
-                    </xs:documentation>
-                </xs:annotation>
-                <xs:choice>
-                    <xs:element name="socket" type="native-management-socketType"/>
-                    <xs:element name="socket-binding" type="native-management-socket-binding-refType"/>
-                </xs:choice>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="native-management-socket-binding-refType">
-        <xs:annotation>
-            <xs:documentation>
-                Reference to the configuration of the socket to be used by a standalone server's exposed native management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="native" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of a socket-binding configuration declared in the server's socket-binding-group.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="server-http-management-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                Configuration of a standalone server's exposed HTTP/HTTPS management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="management-interfaceType">
-                <xs:annotation>
-                    <xs:documentation>
-                        Configuration of the socket to use for the HTTP/HTTPS management interface is a choice
-                        between a direct configuration of the address and ports, or a reference to socket-binding
-                        configurations in the server's socket-binding-group element. The latter is the recommended
-                        approach is it makes it easier to avoid port conflicts by taking advantage of the
-                        socket-binding-group's port-offset configuration. Direct configuration of the address and
-                        ports is provided to preserve backward compatibility.
-                    </xs:documentation>
-                </xs:annotation>
-                <xs:choice>
-                    <xs:element name="socket" type="http-management-socketType"/>
-                    <xs:element name="socket-binding" type="http-management-socket-binding-refType"/>
-                </xs:choice>
-                <xs:attribute name="console-enabled" type="xs:boolean" use="optional" default="true"/>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="http-management-socket-binding-refType">
-        <xs:annotation>
-            <xs:documentation>
-                Reference to the configurations of the sockets to be used by a standalone server's exposed HTTP and HTTPS management interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="http" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of a socket-binding configuration declared in the server's socket-binding-group to use for a HTTP socket.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="https" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of a socket-binding configuration declared in the server's socket-binding-group to use for a HTTPS socket.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="management-remoting-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                Makes the native management interface available via the connectors set up in the remoting subsystem,
-                using the remoting subsystem's endpoint. This should only be used for a server not for a HC/DC.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="domain-controllerType">
-        <xs:choice>
-            <xs:element name="local" type="domain-controller-localType"/>
-            <xs:element name="remote" type="domain-controller-remoteType"/>
-        </xs:choice>
-    </xs:complexType>
-
-    <xs:complexType name="domain-controller-localType" />
-
-    <xs:complexType name="domain-controller-remoteType">
-        <xs:sequence>
-            <xs:element name="ignored-resources" type="ignored-resourcesType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-        <xs:attribute name="host" type="xs:string" use="required" />
-        <xs:attribute name="port" type="xs:integer" use="required" />
-        <xs:attribute name="security-realm" type="xs:string" use="optional" />
-        <xs:attribute name="username" type="xs:string" use="optional" />
-    </xs:complexType>
-
-    <xs:complexType name="ignored-resourcesType">
-        <xs:annotation>
-            <xs:documentation>
-                Provides names of direct child resources of the domain root resource requests for which the
-                Host Controller should ignore. Only relevant on a slave Host Controller. Configuring such
-                "ignored resources" may help allow a Host Controller from an earlier release to function as a
-                slave to a master Host Controller running a later release, by letting the slave ignore portions
-                of the configuration its version of the software cannot understand. This strategy can only be
-                successful if the servers managed by the slave Host Controller do not reference any of the
-                ignored configuration.
-
-                Supports the following attributes:
-
-                type -- the type of resource (e.g. 'profile' or 'socket-binding-group') certain instances of which
-                        should be ignored. The value corresponds to the 'key' portion of the first element in the
-                        resource's address (e.g. 'profile' in the address /profile=ha/subsystem=web)
-
-                wildcard -- if 'true', all resources of the given type should be ignored.
-
-                Child elements list the names of specific instances of the given type of resource
-                that should be ignored. Each element in the list corresponds to the 'value' portion of
-                the first element in the resource's address (e.g. 'ha' in the address /profile=ha/subsystem=web.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="instance" type="ignored-resource-instanceType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-        <xs:attribute name="type" type="xs:string" use="required" />
-        <xs:attribute name="wildcard" type="xs:boolean" use="optional" default="false" />
-        <xs:attribute name="names" type="xs:string" use="optional" />
-    </xs:complexType>
-
-    <xs:complexType name="ignored-resource-instanceType">
-        <xs:annotation>
-            <xs:documentation>
-                The name of a specific instances of a particular type of resource that should be ignored.
-                The 'name' attribute corresponds to the 'value' portion of the first element in the resource's address
-                (e.g. 'ha' in the address /profile=ha/subsystem=web.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="required" />
-    </xs:complexType>
-
-    <xs:complexType name="serversType">
-        <xs:sequence>
-            <xs:element name="server" type="serverType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-        <xs:attribute name="directory-grouping" default="by-server" use="optional">
-            <xs:simpleType>
-                <xs:restriction base="xs:token">
-                    <xs:enumeration value="by-server">
-                        <xs:annotation>
-                            <xs:documentation>
-                                Indicates each server's writable directories should be grouped under the server's name
-                                in the domain/servers directory. This is the default option.
-                            </xs:documentation>
-                        </xs:annotation>
-                    </xs:enumeration>
-                    <xs:enumeration value="by-type">
-                        <xs:annotation>
-                            <xs:documentation>
-                                Indicates each server's writable directories should be grouped based on their "type"
-                                (i.e. "data", "log", "tmp") with directories of a given type for all servers appearing
-                                in the domain level directory for that type, e.g. domain/data/servers/server-name.
-                            </xs:documentation>
-                        </xs:annotation>
-                    </xs:enumeration>
-                </xs:restriction>
-            </xs:simpleType>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="serverType">
-        <xs:all>
-            <xs:element name="paths" type="specified-pathsType" minOccurs="0" maxOccurs="1" />
-
-            <xs:element name="interfaces" type="specified-interfacesType" minOccurs="0"/>
-            <xs:element name="socket-bindings" type="server-socket-bindingsType" minOccurs="0"/>
-
-            <!--<xs:element name="loggers" type="loggersType" minOccurs="0"/>-->
-            <xs:element name="system-properties" type="properties-with-boottime" minOccurs="0"/>
-            <xs:element name="jvm" minOccurs="0" type="serverJvmType"/>
-        </xs:all>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="group" type="xs:string" use="required"/>
-        <xs:attribute name="auto-start" type="xs:boolean" default="true"/>
-    </xs:complexType>
-
-    <xs:complexType name="server-socket-bindingsType">
-        <xs:annotation>
-            <xs:documentation>
-            <![CDATA[
-                Server-specific overrides to the default socket binding configuration inherited from the server group.
-            ]]>
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="socket-binding-group" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                <![CDATA[
-                    The socket binding group to use for the server. If undefined, the socket binding group
-                    specified for the server group is used.
-                ]]>
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="port-offset" type="xs:int" default="0" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                <![CDATA[
-                    Increment to apply to the base port values defined in the
-                    referenced socket binding group to derive the values to use on this
-                    server.
-                ]]>
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="extensionsType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of extension modules.</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="extension" type="extensionType" minOccurs="1" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="extensionType">
-        <xs:annotation>
-            <xs:documentation>
-                A module that extends the standard capabilities of a domain
-                or a standalone server.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="module" use="required" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>The name of the module</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="server-groupsType">
-        <xs:sequence>
-            <xs:element name="server-group" type="server-groupType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="server-groupType">
-        <xs:sequence>
-            <xs:element name="jvm" type="namedJvmType" minOccurs="0"/>
-            <xs:element name="socket-binding-group" type="socket-binding-group-refType" minOccurs="1"/>
-
-            <xs:element name="deployments" type="server-groupDeploymentsType" minOccurs="0"/>
-            <xs:element name="deployment-overlays" type="server-group-deployment-overlaysType" minOccurs="0" maxOccurs="1"/>
-
-            <xs:element name="system-properties" minOccurs="0" type="properties-with-boottime"/>
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the server group
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="profile" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the profile this server is running.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="management-subsystem-endpoint" type="xs:boolean" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Set to true to have servers belonging to the server group connect back to the host controller using the
-                    endpoint from their remoting subsystem. The subsystem must be preset for this to
-                    work.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="server-groupDeploymentsType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of deployments that have been mapped to a server-group.</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="deployment" type="base-deploymentType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="server-groupDeploymentType">
-        <xs:annotation>
-            <xs:documentation>A deployment that has been mapped to a server group.</xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="base-deploymentType">
-                <!--  TODO clarify what a value of 'false' means -->
-                <xs:attribute name="enabled" use="optional" type="xs:boolean" default="true">
-                    <xs:annotation>
-                        <xs:documentation>Whether the deployment deploy automatically when the server starts up.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="base-deploymentType">
-        <xs:attribute name="name" use="required">
-            <xs:annotation>
-                <xs:documentation>Unique identifier of the deployment. Must be unique across all deployments.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="runtime-name" use="required">
-            <xs:annotation>
-                <xs:documentation>Name by which the deployment will be known within a running server.of the deployment.
-                    Does not need to be unique across all deployments in the domain, although it must be unique within
-                    an individual server. For example, two different deployments running on different servers in
-                    the domain could both have a 'runtime-name' of 'example.war', with one having a 'name'
-                    of 'example.war_v1' and another with an 'name' of 'example.war_v2'.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="server-deploymentsType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of deployments that have been mapped to a server.</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="deployment" type="server-deploymentType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="server-deploymentType">
-        <xs:annotation>
-            <xs:documentation>A deployment that has been mapped to a server.</xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="base-deploymentType">
-                <xs:sequence>
-                    <!-- TODO: maxOccurs should be unbounded once overlays are in place -->
-                    <xs:choice maxOccurs="1">
-                        <xs:element name="content" type="contentType"/>
-                        <xs:element name="fs-archive" type="fs-archiveType"/>
-                        <xs:element name="fs-exploded" type="fs-explodedType"/>
-                    </xs:choice>
-                </xs:sequence>
-                <!--  TODO clarify what a value of 'false' means -->
-                <xs:attribute name="enabled" use="optional" type="xs:boolean" default="true">
-                    <xs:annotation>
-                        <xs:documentation>Whether the deployment deploy automatically when the server starts up.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="contentType">
-        <xs:attribute name="sha1" use="required">
-            <xs:annotation>
-                <xs:documentation>The checksum of the content</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="fs-archiveType">
-        <xs:annotation>
-            <xs:documentation>Archived content found on the filesystem</xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="fs-baseType"/>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="fs-baseType">
-        <xs:complexContent>
-            <xs:extension base="pathType"/>
-        </xs:complexContent>
-        <!-- TODO: make path required
-        <xs:complexContent>
-            <xs:restriction base="pathType">
-                <xs:attribute name="path" use="required"/>
-            </xs:restriction>
-        </xs:complexContent>
-        -->
-    </xs:complexType>
-
-    <xs:complexType name="fs-explodedType">
-        <xs:annotation>
-            <xs:documentation>Exploded content found on the filesystem</xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="fs-baseType"/>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="domain-deploymentsType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of domain-level deployments</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="deployment" type="domain-deploymentType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="domain-deploymentType">
-        <xs:annotation>
-            <xs:documentation>Deployment represents anything that can be deployed (e.g. an application such as EJB-JAR,
-                WAR, EAR,
-                any kind of standard archive such as RAR or JBoss-specific deployment),
-                which can be enabled or disabled on a domain level.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="base-deploymentType">
-                <xs:sequence>
-                    <!-- TODO: maxOccurs should be unbounded once overlays are in place -->
-                    <xs:choice maxOccurs="1">
-                        <xs:element name="content" type="contentType"/>
-                        <xs:element name="fs-archive" type="fs-archiveType"/>
-                        <xs:element name="fs-exploded" type="fs-explodedType"/>
-                    </xs:choice>
-                </xs:sequence>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <!-- TODO this is not used anywhere yet -->
-    <xs:complexType name="clustersType">
-        <xs:complexContent>
-            <xs:extension base="server-groupType">
-                <xs:sequence>
-                    <xs:element name="partition-name" type="xs:string"/>
-                    <xs:element name="state-transfer-timeout" type="xs:integer"/>
-                    <xs:element name="method-call-timeout" type="xs:integer"/>
-                </xs:sequence>
-                <xs:attribute name="category" type="xs:string" use="required"/>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <!-- domain-configuration related definitions -->
-    <xs:complexType name="domain-configurationType">
-        <xs:annotation>
-            <xs:documentation>The domain controller/server bootstrap configuration</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element ref="bootstrapURI"/>
-        </xs:sequence>
-    </xs:complexType>
-    <xs:element name="bootstrapURI" type="xs:string">
-        <xs:annotation>
-            <xs:documentation>The URI for bootstrapping a domain server</xs:documentation>
-        </xs:annotation>
-    </xs:element>
-
-    <xs:complexType name="profilesType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of profiles available for use in the domain</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="profile" type="domain-profileType" minOccurs="1" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="domain-profileType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of subsystems</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded">
-                <xs:annotation>
-                    <xs:documentation>A profile declaration may include configuration
-                        elements from other namespaces for the subsystems that make up the profile.
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:any>
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>Name of the profile</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="standalone-profileType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of subsystems</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:choice minOccurs="1" maxOccurs="unbounded">
-                <xs:any namespace="##other">
-                    <xs:annotation>
-                        <xs:documentation>A profile declaration may include configuration
-                            elements from other namespaces for the subsystems that make up the profile.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:any>
-            </xs:choice>
-        </xs:sequence>
-    </xs:complexType>
-
-    <!-- general socket definition -->
-    <xs:complexType name="socket-binding-groupsType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of socket binding groups</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="socket-binding-group" type="socket-binding-groupType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="socket-binding-groupType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of socket configurations</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="socket-binding" type="socket-bindingType" maxOccurs="unbounded"/>
-            <xs:element name="outbound-socket-binding" type="outbound-socket-bindingType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="default-interface" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of an interface that should be used as the interface for
-                    any sockets that do not explicitly declare one.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="standalone-socket-binding-groupType">
-        <xs:annotation>
-            <xs:documentation>Contains a list of socket configurations</xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="socket-binding" type="socket-bindingType" maxOccurs="unbounded"/>
-            <xs:element name="outbound-socket-binding" type="outbound-socket-bindingType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="default-interface" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of an interface that should be used as the interface for
-                    any sockets that do not explicitly declare one.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-	    <xs:attribute name="port-offset" type="xs:int" use="optional" default="0">
-	        <xs:annotation>
-                <xs:documentation>
-	                    Increment to apply to the base port values defined in the
-	                    socket group to derive the values to use on this
-	                    server.
-	            </xs:documentation>
-	        </xs:annotation>
-	    </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="socket-bindingType">
-        <xs:annotation>
-            <xs:documentation>Configuration information for a socket.</xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="client-mapping" type="socket-binding-client-mappingType"
-                        minOccurs="0" maxOccurs="unbounded">
-                <xs:annotation>
-                    <xs:documentation>
-                        Specifies zero or more client mappings for this socket binding.
-                        A client connecting to this socket should use the destination address
-                        specified in the mapping that matches its desired outbound interface.
-                        This allows for advanced network topologies that use either network
-                        address translation, or have bindings on multiple network interfaces
-                        to function.
-
-                        Each mapping should be evaluated in declared order, with the first successful
-                        match used to determine the destination.
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:element>
-        </xs:choice>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="interface" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of the interface to which the socket should be bound, or, for multicast
-                    sockets, the interface on which it should listen. This should
-                    be one of the declared interfaces.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="port" type="xs:unsignedShort" use="optional" default="0">
-            <xs:annotation>
-                <xs:documentation>
-                    Number of the port to which the socket should be bound.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="fixed-port" type="xs:boolean" use="optional" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Whether the port value should remain fixed even if numerically offsets
-                    are applied to the other sockets in the socket group..
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="multicast-address" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Multicast address on which the socket should receive multicast
-                    traffic. If unspecified, the socket will not be configured
-                    to receive multicast.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="multicast-port" type="xs:positiveInteger" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Port on which the socket should receive multicast
-                    traffic. Must be configured if 'multicast-address' is configured.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="socket-binding-client-mappingType">
-        <xs:annotation>
-                <xs:documentation>
-                    Type definition for a client mapping on a socket binding. A client
-                    mapping specifies how external clients should connect to this
-                    socket's port, provided that the client's outbound interface
-                    match the specified source network value.
-                </xs:documentation>
-            </xs:annotation>
-        <xs:attribute name="source-network" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Source network the client connection binds on. This value is in
-                    the form of ip/netmask. A client should match this value against
-                    the desired client host network interface, and if matched the
-                    client should connect to the corresponding destination values.
-
-                    If omitted this mapping should match any interface.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="destination-address" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The destination address that a client should connect to if the
-                    source-network matches. This value can either be a hostname or
-                    an ip address.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="destination-port" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    The destination port that a client should connect to if the
-                    source-network matches.
-
-                    If omitted this mapping will reuse the effective socket binding
-                    port.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="outbound-socket-bindingType">
-        <xs:annotation>
-            <xs:documentation>Configuration information for a outbound socket.</xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="remote-destination" type="remote-destinationType" maxOccurs="1"/>
-            <xs:element name="local-destination" type="local-destinationType" maxOccurs="1"/>
-        </xs:choice>
-
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the outbound socket binding
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="source-interface" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of the interface that should be used for setting up the source address of the
-                    outbound socket. This should be one of the declared interfaces.
-                </xs:documentation>
-            </xs:annotation>
-
-        </xs:attribute>
-        <xs:attribute name="source-port" type="xs:positiveInteger" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    The port number that will be used for setting the source addresss of the outbound socket. If the
-                    source-interface attribute has been specified and the source-port attribute is absent,
-                    then the system uses a ephemeral port while binding the socket to a source address.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="fixed-source-port" type="xs:boolean" use="optional" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Whether the source-port value should remain fixed even if the socket binding group specifies
-                    a port offset
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="remote-destinationType">
-        <xs:attribute name="host" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The remote server address to which the outbound socket has to be connect.
-                    The address can be either a IP address of the host server of the hostname of the server
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="port" type="xs:positiveInteger" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The remote port to which the outbound socket has to connect.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="local-destinationType">
-        <xs:attribute name="socket-binding-ref" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The reference to a socket binding that has to be used as the destination for the outbound
-                    socket binding. This socket binding name should belong to the same socket binding group
-                    to which this local destination client socket belongs.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="socket-binding-group-refType">
-        <xs:attribute name="ref" type="xs:string">
-            <xs:annotation>
-                <xs:documentation>
-                    The socket group to use for the server group or server.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="port-offset" type="xs:int" default="0" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Increment to apply to the base port values defined in the
-                    referenced socket group to derive the values to use on this
-                    server.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-
-    <xs:complexType name="named-interfacesType">
-        <xs:annotation>
-            <xs:documentation>
-                A list of named network interfaces. The interfaces may or may
-                not be fully specified (i.e. include criteria on how to determine
-                their IP address.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="interface" type="named-interfaceType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <!-- TODO make this and specified-interfaceType the same except for interface-criteriaGroup minOccurs -->
-    <xs:complexType name="named-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                A named network interface, but without any criteria
-                for determining the IP address to associate with that interface.
-                Acts as a placeholder in the model (e.g. at the domain level)
-                until a fully specified interface definition is applied at a
-                lower level (e.g. at the server level, where available addresses
-                are known.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:group ref="interface-criteriaGroup" minOccurs="0"/>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-    </xs:complexType>
-
-    <xs:complexType name="specified-interfacesType">
-        <xs:annotation>
-            <xs:documentation>
-                A list of fully specified named network interfaces.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="interface" type="specified-interfaceType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="specified-interfaceType">
-        <xs:annotation>
-            <xs:documentation>
-                A named network interface, along with required criteria
-                for determining the IP address to associate with that interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:group ref="interface-criteriaGroup" minOccurs="1"/>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-    </xs:complexType>
-
-    <xs:group name="interface-criteriaGroup">
-        <xs:annotation>
-            <xs:documentation>
-                A set of criteria that can be used at runtime to determine
-                what IP address to use for an interface.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:choice>
-            <xs:element name="any-address" type="any-addressType"/>
-            <xs:element name="any-ipv6-address" type="any-ipv6-addressType"/>
-            <xs:element name="any-ipv4-address" type="any-ipv4-addressType"/>
-            <xs:choice maxOccurs="unbounded">
-                <xs:element name="inet-address" type="inet-addressType"/>
-                <xs:element name="loopback" type="loopbackType"/>
-                <xs:element name="loopback-address" type="loopback-addressType"/>
-                <xs:element name="multicast" type="multicastType"/>
-                <xs:element name="point-to-point" type="point-to-pointType"/>
-                <xs:element name="virtual" type="interface-virtualType"/>
-                <xs:element name="up" type="interface-upType"/>
-                <xs:element name="public-address" type="public-addressType"/>
-                <xs:element name="link-local-address" type="link-local-addressType"/>
-                <xs:element name="site-local-address" type="site-local-addressType"/>
-                <xs:element name="nic" type="nicType"/>
-                <xs:element name="nic-match" type="nic-matchType"/>
-                <xs:element name="subnet-match" type="subnet-matchType"/>
-                <xs:element name="not" type="address-exclusionType"/>
-                <xs:element name="any" type="address-exclusionType"/>
-            </xs:choice>
-        </xs:choice>
-    </xs:group>
-
-    <xs:complexType name="inet-addressType">
-        <xs:attribute name="value" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    Either a IP address in IPv6 or IPv4 dotted decimal notation,
-                    or a hostname that can be resolved to an IP address.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="nicType">
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    The name of a network interface (e.g. eth0, eth1, lo).
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="nic-matchType">
-        <xs:attribute name="pattern" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    A regular expression against which the names of the network
-                    interfaces available on the machine can be matched to find
-                    an acceptable interface.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="subnet-matchType">
-        <xs:attribute name="value" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    A network IP address and the number of bits in the
-                    address' network prefix, written in "slash notation";
-                    e.g. "192.168.0.0/16".
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="address-exclusionType">
-        <xs:choice>
-            <xs:element name="inet-address" type="inet-addressType" minOccurs="0" maxOccurs="unbounded"/>
-            <xs:element name="loopback" type="loopbackType"/>
-            <xs:element name="loopback-address" type="loopback-addressType"/>
-            <xs:element name="multicast" type="multicastType"/>
-            <xs:element name="point-to-point" type="point-to-pointType"/>
-            <xs:element name="virtual" type="interface-virtualType"/>
-            <xs:element name="up" type="interface-upType"/>
-            <xs:element name="public-address" type="public-addressType"/>
-            <xs:element name="link-local-address" type="link-local-addressType"/>
-            <xs:element name="site-local-address" type="site-local-addressType"/>
-            <xs:element name="nic" type="nicType" minOccurs="0" maxOccurs="unbounded"/>
-            <xs:element name="nic-match" type="nic-matchType" minOccurs="0" maxOccurs="unbounded"/>
-            <xs:element name="subnet-match" type="subnet-matchType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:choice>
-    </xs:complexType>
-
-    <xs:complexType name="loopbackType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it is a loopback
-                interface.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="loopback-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                A loopback address that may not actually be configured on the machine's loopback interface.
-                Differs from inet-addressType in that the given value will be used even if no NIC can
-                be found that has the IP address associated with it.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="value" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                    An IP address in IPv6 or IPv4 dotted decimal notation.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="multicastType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it supports
-                multicast.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="point-to-pointType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it is a point-to-point
-                interface.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="interface-upType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it is currently up.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="interface-virtualType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it is a virtual
-                interface.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="public-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not it has a publicly
-                routable address.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="site-local-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not an address associated
-                with it is site-local.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="link-local-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that part of the selection criteria
-                for an interface should be whether or not an address associated
-                with it is link-local.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="any-ipv6-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that sockets using this interface
-                should be bound to the IPv6 wildcard address (::).
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="any-ipv4-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that sockets using this interface
-                should be bound to the IPv4 wildcard address (0.0.0.0).
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="any-addressType">
-        <xs:annotation>
-            <xs:documentation>
-                Empty element indicating that sockets using this interface
-                should be bound to a wildcard address. The IPv6 wildcard
-                address (::) will be used unless the java.net.preferIpV4Stack
-                system property is set to true, in which case the IPv4
-                wildcard address (0.0.0.0) will be used. If a socket is
-                bound to an IPv6 anylocal address on a dual-stack machine,
-                it can accept both IPv6 and IPv4 traffic; if it is bound to
-                an IPv4 (IPv4-mapped) anylocal address, it can only accept
-                IPv4 traffic.
-            </xs:documentation>
-        </xs:annotation>
-    </xs:complexType>
-
-    <xs:complexType name="socketType">
-        <xs:annotation>
-            <xs:documentation>Configuration information for a socket.</xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="interface" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Name of the interface to which the socket should be bound, or, for multicast
-                    sockets, the interface on which it should listen. This should
-                    be one of the declared interfaces.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="port" type="xs:unsignedShort" use="optional" default="0">
-            <xs:annotation>
-                <xs:documentation>
-                    Number of the port to which the socket should be bound.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="fixed-port" type="xs:boolean" use="optional" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Whether the port value should remain fixed even if numerically offsets
-                    are applied to the other sockets in the socket group..
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="multicast-address" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Multicast address on which the socket should receive multicast
-                    traffic. If unspecified, the socket will not be configured
-                    to receive multicast.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="multicast-port" type="xs:positiveInteger" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Port on which the socket should receive multicast
-                    traffic. If unspecified, the socket will not be configured
-                    to receive multicast.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <!-- Path configurations -->
-    <xs:complexType name="named-pathsType">
-        <xs:annotation>
-            <xs:documentation>
-                A list of named filesystem paths. The paths may or may
-                not be fully specified (i.e. include the actual paths.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="path" type="named-pathType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="named-pathType">
-        <xs:annotation>
-            <xs:documentation>
-                A named filesystem path, but without a requirement to specify
-                the actual path. If no actual path is specified, acts as a
-                as a placeholder in the model (e.g. at the domain level)
-                until a fully specified path definition is applied at a
-                lower level (e.g. at the host level, where available addresses
-                are known.)
-            </xs:documentation>
-        </xs:annotation>
-        <xs:complexContent>
-            <xs:extension base="pathType">
-                <xs:attribute name="name" type="xs:string" use="required">
-                    <xs:annotation>
-                        <xs:documentation>
-                        The name of the path. Cannot be one of the standard fixed paths
-                        provided by the system:
-
-                        jboss.home - the root directory of the JBoss AS distribution
-                        user.home - user's home directory
-                        user.dir - user's current working directory
-                        java.home - java installation directory
-                        jboss.server.base.dir - root directory for an individual server
-                                                instance
-
-                        Note that the system provides other standard paths that can be
-                        overridden by declaring them in the configuration file. See
-                        the 'relative-to' attribute documentation for a complete
-                        list of standard paths.
-                        </xs:documentation>
-                    </xs:annotation>
-                </xs:attribute>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="pathType">
-        <xs:attribute name="path">
-            <xs:annotation>
-                <xs:documentation>
-                The actual filesystem path. Treated as an absolute path, unless the
-                'relative-to' attribute is specified, in which case the value
-                is treated as relative to that path.
-
-                If treated as an absolute path, the actual runtime pathname specified
-                by the value of this attribute will be determined as follows:
-
-                If this value is already absolute, then the value is directly
-                used.  Otherwise the runtime pathname is resolved in a
-                system-dependent way.  On UNIX systems, a relative pathname is
-                made absolute by resolving it against the current user directory.
-                On Microsoft Windows systems, a relative pathname is made absolute
-                by resolving it against the current directory of the drive named by the
-                pathname, if any; if not, it is resolved against the current user
-                directory.
-                </xs:documentation>
-            </xs:annotation>
-            <xs:simpleType>
-                <xs:restriction base="xs:string">
-                    <xs:minLength value="1"/>
-                </xs:restriction>
-            </xs:simpleType>
-        </xs:attribute>
-        <xs:attribute name="relative-to" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                The name of another previously named path, or of one of the
-                standard paths provided by the system. If 'relative-to' is
-                provided, the value of the 'path' attribute is treated as
-                relative to the path specified by this attribute. The standard
-                paths provided by the system include:
-
-                jboss.home - the root directory of the JBoss AS distribution
-                user.home - user's home directory
-                user.dir - user's current working directory
-                java.home - java installation directory
-                jboss.server.base.dir - root directory for an individual server
-                                        instance
-                jboss.server.config.dir - directory in which server configuration
-                                          files are stored.
-                jboss.server.data.dir - directory the server will use for persistent
-                                        data file storage
-                jboss.server.log.dir - directory the server will use for
-                                       log file storage
-                jboss.server.temp.dir - directory the server will use for
-                                       temporary file storage
-                jboss.domain.servers.dir - directory under which a host controller
-                                           will create the working area for
-                                           individual server instances
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="specified-pathsType">
-        <xs:annotation>
-            <xs:documentation>
-                A list of named filesystem paths.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="path" type="specified-pathType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="specified-pathType">
-        <xs:annotation>
-            <xs:documentation>
-                A named filesystem path.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                The name of the path. Cannot be one of the standard fixed paths
-                provided by the system:
-
-                jboss.home.dir - the root directory of the JBoss AS distribution
-                user.home - user's home directory
-                user.dir - user's current working directory
-                java.home - java installation directory
-                jboss.server.base.dir - root directory for an individual server
-                                        instance
-
-                Note that the system provides other standard paths that can be
-                overridden by declaring them in the configuration file. See
-                the 'relative-to' attribute documentation for a complete
-                list of standard paths.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="path" use="required">
-            <xs:annotation>
-                <xs:documentation>
-                The actual filesystem path. Treated as an absolute path, unless the
-                'relative-to' attribute is specified, in which case the value
-                is treated as relative to that path.
-
-                If treated as an absolute path, the actual runtime pathname specified
-                by the value of this attribute will be determined as follows:
-
-                If this value is already absolute, then the value is directly
-                used.  Otherwise the runtime pathname is resolved in a
-                system-dependent way.  On UNIX systems, a relative pathname is
-                made absolute by resolving it against the current user directory.
-                On Microsoft Windows systems, a relative pathname is made absolute
-                by resolving it against the current directory of the drive named by the
-                pathname, if any; if not, it is resolved against the current user
-                directory.
-
-                Note relative path declarations have to use '/' as file separator.
-                </xs:documentation>
-            </xs:annotation>
-            <xs:simpleType>
-                <xs:restriction base="xs:string">
-                    <xs:minLength value="1"/>
-                </xs:restriction>
-            </xs:simpleType>
-        </xs:attribute>
-        <xs:attribute name="relative-to" type="xs:string" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                The name of another previously named path, or of one of the
-                standard paths provided by the system. If 'relative-to' is
-                provided, the value of the 'path' attribute is treated as
-                relative to the path specified by this attribute. The standard
-                paths provided by the system include:
-
-                jboss.home.dir - the root directory of the JBoss AS distribution
-                user.home - user's home directory
-                user.dir - user's current working directory
-                java.home - java installation directory
-                jboss.server.base.dir - root directory for an individual server
-                                        instance
-                jboss.server.config.dir - directory in which server configuration
-                                          files are stored.
-                jboss.server.data.dir - directory the server will use for persistent
-                                        data file storage
-                jboss.server.log.dir - directory the server will use for
-                                       log file storage
-                jboss.server.temp.dir - directory the server will use for
-                                       temporary file storage
-                jboss.domain.servers.dir - directory under which a host controller
-                                           will create the working area for
-                                           individual server instances
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <!--  JVM configurations -->
-    <xs:complexType name="jvmsType">
-        <xs:sequence>
-            <xs:element name="jvm" type="namedJvmType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="jvmType">
-        <xs:all minOccurs="0" maxOccurs="1">
-            <xs:element name="heap" type="heapType" minOccurs="0"/>
-            <!-- XX:PermSize, XX:MaxPermSize -->
-            <xs:element name="permgen" type="bounded-memory-sizeType" minOccurs="0"/>
-            <!-- Xss -->
-            <xs:element name="stack" type="memory-sizeType" minOccurs="0"/>
-            <xs:element name="agent-lib" type="jvm-agentLibType" minOccurs="0"/>
-            <xs:element name="agent-path" type="jvm-agentPathType" minOccurs="0"/>
-            <xs:element name="java-agent" type="jvm-javaagentType" minOccurs="0"/>
-            <xs:element name="jvm-options" type="jvm-optionsType" minOccurs="0"/>
-            <xs:element name="environment-variables" type="environmentVariablesType" minOccurs="0"/>
-        </xs:all>
-        <xs:attribute name="java-home" type="xs:string"/>
-        <xs:attribute name="type" default="SUN">
-            <xs:simpleType>
-                <xs:restriction base="xs:token">
-                    <xs:enumeration value="SUN">
-			            <xs:annotation>
-			                <xs:documentation>Allows the full set of JVM options to be set via the jvm schema elements</xs:documentation>
-			            </xs:annotation>
-                    </xs:enumeration>
-                    <xs:enumeration value="IBM">
-                        <xs:annotation>
-                            <xs:documentation>Sets a subset of the JVM options via the jvm schema elements</xs:documentation>
-                        </xs:annotation>
-                    </xs:enumeration>
-                </xs:restriction>
-            </xs:simpleType>
-        </xs:attribute>
-        <xs:attribute name="env-classpath-ignored" default="true" type="xs:boolean"/>
-    </xs:complexType>
-
-    <xs:complexType name="namedJvmType">
-        <xs:complexContent>
-            <xs:extension base="jvmType">
-                <xs:attribute name="name" type="xs:string"/>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="serverJvmType">
-        <xs:complexContent>
-            <xs:extension base="namedJvmType">
-                <xs:attribute name="debug-enabled" type="xs:boolean" default="false"/>
-                <xs:attribute name="debug-options" type="xs:string" />
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-    <xs:complexType name="heapType">
-        <xs:attribute name="size" use="optional">
-            <xs:annotation>
-                <xs:documentation>Initial JVM heap size</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="max-size" use="optional">
-            <xs:annotation>
-                <xs:documentation>Maximum JVM heap size</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-optionsType">
-        <xs:sequence>
-            <xs:element name="option" type="jvm-optionType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-optionType">
-        <xs:attribute name="value" use="required">
-            <xs:annotation>
-                <xs:documentation>JVM option value</xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-agentLibType">
-        <xs:attribute name="value" use="required">
-            <xs:annotation>
-                <xs:documentation>JVM agent lib value </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-agentPathType">
-        <xs:attribute name="value" use="required">
-            <xs:annotation>
-                <xs:documentation>JVM agent path value </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="jvm-javaagentType">
-        <xs:attribute name="value" use="required">
-            <xs:annotation>
-                <xs:documentation>JVM javaagent value </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="bounded-memory-sizeType">
-        <xs:attribute name="size" type="xs:string"/>
-        <xs:attribute name="max-size" type="xs:string"/>
-    </xs:complexType>
-
-    <xs:complexType name="memory-sizeType">
-        <xs:attribute name="size" type="xs:string" use="required"/>
-    </xs:complexType>
-
-    <xs:complexType name="properties-with-boottime">
-        <xs:sequence>
-            <xs:element name="property" type="boottimePropertyType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="properties">
-        <xs:sequence>
-            <xs:element name="property" type="propertyType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="environmentVariablesType">
-        <xs:sequence>
-            <xs:element name="variable" type="propertyType" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="propertyType">
-        <xs:attribute name="name" use="required"/>
-        <xs:attribute name="value" use="optional"/>
-    </xs:complexType>
-
-    <xs:complexType name="boottimePropertyType">
-        <xs:complexContent>
-            <xs:extension base="propertyType">
-                <xs:attribute name="boot-time" type="xs:boolean" default="true"/>
-            </xs:extension>
-        </xs:complexContent>
-    </xs:complexType>
-
-   <xs:complexType name="vaultType">
-      <xs:annotation>
-         <xs:documentation>
-               <![CDATA[
-                    Vault Configuration.
-                ]]>
-         </xs:documentation>
-      </xs:annotation>
-      <xs:sequence>
-          <xs:element name="vault-option" type="propertyType" minOccurs="0" maxOccurs="unbounded"/>
-      </xs:sequence>
-      <xs:attribute name="code" type="xs:string" use="optional"/>
-   </xs:complexType>
-
-    <xs:complexType name="management-client-contentType">
-        <xs:annotation>
-            <xs:documentation>
-                <![CDATA[
-                   Storage information about re-usable chunks of data useful to management clients that are stored
-                   in the domain content repository.
-                ]]>
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="rollout-plans" type="contentType" minOccurs="0" maxOccurs="1">
-                <xs:annotation>
-                    <xs:documentation>
-                        <![CDATA[
-                           Storage information about a set of named management update rollout plans useful to management
-                           clients that are stored in the domain content repository. The management API exposed by the domain
-                           controller provides access to these plans to management clients, allowing clients to use the plans
-                           by referencing them by name, avoiding the need to recreate them for each use.
-                        ]]>
-                    </xs:documentation>
-                </xs:annotation>
-            </xs:element>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="standalone-deployment-overlaysType">
-        <xs:annotation>
-            <xs:documentation>
-                <![CDATA[
-                   Stores information about deployment overlays that can be used to override deployment content.
-                ]]>
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="deployment-overlay" type="standalone-deployment-overlayType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="standalone-deployment-overlayType">
-        <xs:sequence>
-            <xs:element name="content" type="deployment-overlay-contentType" minOccurs="0" maxOccurs="unbounded"/>
-            <xs:element name="deployment" type="deployment-overlay-deploymentType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-        <xs:attribute name="name" use="required" type="xs:token"/>
-    </xs:complexType>
-
-    <xs:complexType name="domain-deployment-overlaysType">
-        <xs:annotation>
-            <xs:documentation>
-                <![CDATA[
-                   Stores information about deployment overlays that can be used to override deployment content.
-                ]]>
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="deployment-overlay" type="domain-deployment-overlayType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="domain-deployment-overlayType">
-        <xs:sequence>
-            <xs:element name="content" type="deployment-overlay-contentType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-        <xs:attribute name="name" use="required" type="xs:token"/>
-    </xs:complexType>
-
-    <xs:complexType name="server-group-deployment-overlaysType">
-        <xs:annotation>
-            <xs:documentation>
-                <![CDATA[
-                   Stores information about deployment overlays that can be used to override deployment content.
-                ]]>
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="deployment-overlay" type="server-group-deployment-overlayType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="server-group-deployment-overlayType">
-        <xs:sequence>
-            <xs:element name="deployment" type="deployment-overlay-deploymentType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-        <xs:attribute name="name" use="required" type="xs:token"/>
-    </xs:complexType>
-
-    <xs:complexType name="deployment-overlay-contentType">
-        <xs:attribute name="path" type="xs:token" use="required"/>
-        <xs:attribute name="content" type="xs:token" use="required"/>
-    </xs:complexType>
-
-    <xs:complexType name="deployment-overlay-deploymentType">
-        <xs:attribute name="name" type="xs:string" use="required"/>
-    </xs:complexType>
-
-
-</xs:schema>

jboss-as-7.2.0.Final/docs/schema/jboss-as-configadmin_1_0.xsd

@@ -1,60 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-  ~ JBoss, Home of Professional Open Source.
-  ~ Copyright 2011, Red Hat, Inc., and individual contributors
-  ~ as indicated by the @author tags. See the copyright.txt file in the
-  ~ distribution for a full listing of individual contributors.
-  ~
-  ~ This is free software; you can redistribute it and/or modify it
-  ~ under the terms of the GNU Lesser General Public License as
-  ~ published by the Free Software Foundation; either version 2.1 of
-  ~ the License, or (at your option) any later version.
-  ~
-  ~ This software is distributed in the hope that it will be useful,
-  ~ but WITHOUT ANY WARRANTY; without even the implied warranty of
-  ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-  ~ Lesser General Public License for more details.
-  ~
-  ~ You should have received a copy of the GNU Lesser General Public
-  ~ License along with this software; if not, write to the Free
-  ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
-  ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
-  -->
-
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
-            targetNamespace="urn:jboss:domain:configadmin:1.0"
-            xmlns="urn:jboss:domain:configadmin:1.0"
-            elementFormDefault="qualified"
-            attributeFormDefault="unqualified"
-            version="1.0">
-
-    <!-- The ConfigAdmin subsystem root element -->
-    <xs:element name="subsystem" type="subsystemType"/>
-
-    <xs:complexType name="subsystemType">
-        <xs:annotation>
-            <xs:documentation>
-            <![CDATA[
-                The configuration of the ConfigAdmin subsystem.
-            ]]>
-            </xs:documentation>
-        </xs:annotation>
-        <xs:sequence>
-            <xs:element name="configuration" type="configurationType" minOccurs="0" maxOccurs="unbounded"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="configurationType">
-        <xs:choice minOccurs="0" maxOccurs="unbounded">
-            <xs:element name="property" type="propertyType"/>
-        </xs:choice>
-        <xs:attribute name="pid" type="xs:string" use="required"/>
-    </xs:complexType>
-
-    <xs:complexType name="propertyType">
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="value" type="xs:string" use="required"/>
-    </xs:complexType>
-    
-</xs:schema>

jboss-as-7.2.0.Final/docs/schema/jboss-as-datasources_1_0.xsd

@@ -1,957 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
-  ~ JBoss, Home of Professional Open Source.
-  ~ Copyright 2011, Red Hat, Inc., and individual contributors
-  ~ as indicated by the @author tags. See the copyright.txt file in the
-  ~ distribution for a full listing of individual contributors.
-  ~
-  ~ This is free software; you can redistribute it and/or modify it
-  ~ under the terms of the GNU Lesser General Public License as
-  ~ published by the Free Software Foundation; either version 2.1 of
-  ~ the License, or (at your option) any later version.
-  ~
-  ~ This software is distributed in the hope that it will be useful,
-  ~ but WITHOUT ANY WARRANTY; without even the implied warranty of
-  ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-  ~ Lesser General Public License for more details.
-  ~
-  ~ You should have received a copy of the GNU Lesser General Public
-  ~ License along with this software; if not, write to the Free
-  ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
-  ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
-  -->
-
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
-           targetNamespace="urn:jboss:domain:datasources:1.0" xmlns="urn:jboss:domain:datasources:1.0"
-           elementFormDefault="qualified" attributeFormDefault="unqualified">
-
-  <xs:element name="subsystem" type="subsystemType"/>
-
-  <xs:complexType name="subsystemType">
-    <xs:all>
-      <xs:element name="datasources" type="datasourcesType" minOccurs="1" maxOccurs="1"/>
-    </xs:all>
-  </xs:complexType>
-
-  <xs:complexType name="datasourcesType">
-    <xs:sequence>
-      <xs:choice minOccurs="0" maxOccurs="unbounded">
-        <xs:element name="datasource" type="datasourceType">
-          <xs:annotation>
-            <xs:documentation>
-              <![CDATA[[
-                Specifies a non-XA datasource, using local transactions
-               ]]>
-            </xs:documentation>
-          </xs:annotation>
-        </xs:element>
-        <xs:element name="xa-datasource" type="xa-datasourceType">
-          <xs:annotation>
-            <xs:documentation>
-              <![CDATA[[
-                Specifies a XA datasource
-                ]]>
-            </xs:documentation>
-          </xs:annotation>
-        </xs:element>
-      </xs:choice>
-      <xs:element name="drivers" type="driversType" maxOccurs="1" minOccurs="0"></xs:element>
-    </xs:sequence>
-  </xs:complexType>
-  <xs:complexType name="datasourceType" mixed="false">
-    <xs:sequence>
-      <xs:element name="connection-url" type="xs:token">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The JDBC driver connection URL Ex: <connection-url>jdbc:hsqldb:hsql://localhost:1701</connection-url>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="driver-class" type="xs:token" maxOccurs="1" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The fully qualifed name of the JDBC driver class Ex: <driver-class>org.hsqldb.jdbcDriver</driver-class>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="datasource-class" type="xs:token" maxOccurs="1" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The fully qualifed name of the JDBC datasource class Ex: <datasource-class>org.h2.jdbcx.JdbcDataSource</datasource-class>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="driver" type="xs:token" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              An unique reference to the classloader module which contains the JDBC driver
-              The accepted format is driverName#majorVersion.minorVersion
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="connection-property" type="connection-propertyType" minOccurs="0" maxOccurs="unbounded">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The connection-property element allows you to pass in arbitrary connection
-              properties to the Driver.connect(url, props) method. Each connection-property
-              specifies a string name/value pair with the property name coming from the
-              name attribute and the value coming from the element content. Ex:
-              <connection-property name="char.encoding">UTF-8</connection-property>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="new-connection-sql" type="xs:string" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specify an SQL statement to execute whenever a connection is added
-              to the connection pool.
-              ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="transaction-isolation" type="transaction-isolationType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Set java.sql.Connection transaction isolation level to use. The constants
-              defined by transaction-isolation-values are the possible transaction isolation
-              levels and include: TRANSACTION_READ_UNCOMMITTED TRANSACTION_READ_COMMITTED
-              TRANSACTION_REPEATABLE_READ TRANSACTION_SERIALIZABLE TRANSACTION_NONE
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="url-delimiter" type="xs:token" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the delimeter for URLs in connection-url for HA datasources
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="url-selector-strategy-class-name" type="xs:token" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              A class that implements org.jboss.jca.adapters.jdbc.URLSelectorStrategy
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="pool" type="poolType" minOccurs="0" maxOccurs="1">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the pooling settings
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="security" type="dsSecurityType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the security settings
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="validation" type="validationType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the validation settings
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="timeout" type="timeoutType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the time out settings
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="statement" type="statementType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the statement settings
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-    </xs:sequence>
-    <xs:attribute name="jta" type="xs:boolean" default="true" use="optional">
-      <xs:annotation>
-        <xs:documentation>
-          <![CDATA[[
-            Enable JTA integration
-           ]]>
-        </xs:documentation>
-      </xs:annotation>
-    </xs:attribute>
-    <xs:attributeGroup ref="common-datasourceAttributes" />
-  </xs:complexType>
-  <xs:complexType name="xa-datasourceType">
-    <xs:sequence>
-      <xs:element name="xa-datasource-property" type="xa-datasource-propertyType" minOccurs="1" maxOccurs="unbounded">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies a property to assign to the XADataSource implementation class.
-              Each property is identified by the name attribute and the property value
-              is given by the xa-datasource-property element content. The property is mapped
-              onto the XADataSource implementation by looking for a JavaBeans style getter
-              method for the property name. If found, the value of the property is set
-              using the JavaBeans setter with the element text translated to the true property
-              type using the java.beans.PropertyEditor for the type. Ex:
-              <xa-datasource-property name="IfxWAITTIME">10</xa-datasource-property>
-              <xa-datasource-property name="IfxIFXHOST">myhost.mydomain.com</xa-datasource-property>
-              <xa-datasource-property name="PortNumber">1557</xa-datasource-property>
-              <xa-datasource-property name="DatabaseName">mydb</xa-datasource-property>
-              <xa-datasource-property name="ServerName">myserver</xa-datasource-property>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="xa-datasource-class" type="xs:token" maxOccurs="1" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The fully qualifed name of the javax.sql.XADataSource implementation
-              class. Ex: <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="driver" type="xs:token" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              An unique reference to the classloader module which contains the JDBC driver
-              The accepted format is driverName#majorVersion.minorVersion
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="url-delimiter" type="xs:token" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-               Specifies the delimeter for URLs in the connection url for HA datasources
-              ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="url-selector-strategy-class-name" type="xs:token" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-               A class that implements org.jboss.jca.adapters.jdbc.URLSelectorStrategy
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="new-connection-sql" type="xs:string" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-               Specifies an SQL statement to execute whenever a connection is added
-               to the connection pool.
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="transaction-isolation" type="transaction-isolationType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Set java.sql.Connection transaction isolation level to use. The constants
-              defined by transaction-isolation-values are the possible transaction isolation
-              levels and include: TRANSACTION_READ_UNCOMMITTED TRANSACTION_READ_COMMITTED
-              TRANSACTION_REPEATABLE_READ TRANSACTION_SERIALIZABLE TRANSACTION_NONE
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="xa-pool" type="xa-poolType" minOccurs="0" maxOccurs="1">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the pooling settings
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="security" type="dsSecurityType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the security settings
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="validation" type="validationType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the validation settings
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="timeout" type="timeoutType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the time out settings
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="statement" type="statementType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the statement settings
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="recovery" type="recoverType" minOccurs="0" maxOccurs="1"></xs:element>
-    </xs:sequence>
-    <xs:attributeGroup ref="common-datasourceAttributes" />
-  </xs:complexType>
-  <xs:complexType name="boolean-presenceType" />
-  <xs:attributeGroup name="common-datasourceAttributes">
-    <xs:attribute name="jndi-name" type="xs:token" use="required">
-      <xs:annotation>
-        <xs:documentation>
-          <![CDATA[[
-            Specifies the JNDI name for the datasource
-           ]]>
-        </xs:documentation>
-      </xs:annotation>
-    </xs:attribute>
-    <xs:attribute name="pool-name" type="xs:token" use="required">
-      <xs:annotation>
-        <xs:documentation>
-          <![CDATA[[
-            Specifies the pool name for the datasource used for management
-           ]]>
-        </xs:documentation>
-      </xs:annotation>
-    </xs:attribute>
-    <xs:attribute name="enabled" type="xs:boolean" default="true" form="unqualified" use="optional">
-      <xs:annotation>
-        <xs:documentation>
-          <![CDATA[[
-            Specifies if the datasource should be enabled
-           ]]>
-        </xs:documentation>
-      </xs:annotation>
-    </xs:attribute>
-    <xs:attribute default="true" name="use-java-context" type="xs:boolean">
-      <xs:annotation>
-        <xs:documentation>
-          <![CDATA[[
-            Setting this to false will bind the DataSource into global JNDI
-            Ex: use-java-context="true"
-           ]]>
-        </xs:documentation>
-      </xs:annotation>
-    </xs:attribute>
-    <xs:attribute default="false" name="spy" type="xs:boolean">
-      <xs:annotation>
-        <xs:documentation>
-          <![CDATA[[
-            Enable spy functionality on the JDBC layer - e.g. log all JDBC traffic to the datasource.
-            Remember to enable the logging category (org.jboss.jdbc) too.
-            Ex: spy="true"
-           ]]>
-        </xs:documentation>
-      </xs:annotation>
-    </xs:attribute>
-    <xs:attribute default="true" name="use-ccm" type="xs:boolean">
-      <xs:annotation>
-        <xs:documentation>
-          <![CDATA[[
-            Enable the use of a cached connection manager
-            Ex: use-ccm="true"
-           ]]>
-        </xs:documentation>
-      </xs:annotation>
-    </xs:attribute>
-  </xs:attributeGroup>
-  <xs:simpleType name="transaction-isolationType">
-    <xs:annotation>
-      <xs:documentation>
-        <![CDATA[[
-          Define constants used as the possible transaction isolation levels in transaction-isolation
-          type. Include: TRANSACTION_READ_UNCOMMITTED, TRANSACTION_READ_COMMITTED, TRANSACTION_REPEATABLE_READ,
-          TRANSACTION_SERIALIZABLE, TRANSACTION_NONE
-         ]]>
-      </xs:documentation>
-    </xs:annotation>
-    <xs:restriction base="xs:token">
-      <xs:enumeration value="TRANSACTION_READ_UNCOMMITTED" />
-      <xs:enumeration value="TRANSACTION_READ_COMMITTED" />
-      <xs:enumeration value="TRANSACTION_REPEATABLE_READ" />
-      <xs:enumeration value="TRANSACTION_SERIALIZABLE" />
-      <xs:enumeration value="TRANSACTION_NONE" />
-    </xs:restriction>
-  </xs:simpleType>
-  <xs:complexType name="xa-datasource-propertyType" mixed="true">
-    <xs:attribute name="name" use="required" type="xs:token" />
-  </xs:complexType>
-  <xs:complexType name="connection-propertyType" mixed="true">
-    <xs:attribute name="name" use="required" type="xs:token" />
-  </xs:complexType>
-  <xs:complexType name="validationType">
-    <xs:sequence>
-      <xs:element name="valid-connection-checker" type="extensionType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              An org.jboss.jca.adapters.jdbc.ValidConnectionChecker that provides
-              a SQLException isValidConnection(Connection e) method to validate is a connection
-              is valid. An exception means the connection is destroyed. This overrides
-              the check-valid-connection-sql when present. Ex:
-              <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.vendor.OracleValidConnectionChecker"/>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-
-      <xs:element name="check-valid-connection-sql" type="xs:string" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specify an SQL statement to check validity of a pool connection. This
-              may be called when managed connection is taken from pool for use.
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="validate-on-match" type="xs:boolean" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The validate-on-match element indicates whether or not connection
-              level validation should be done when a connection factory attempts to match
-              a managed connection for a given set. This is typically exclusive to the
-              use of background validation
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="background-validation" type="xs:boolean" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              An element to specify that connections should be validated on a background
-              thread versus being validated prior to use
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="background-validation-millis" type="xs:nonNegativeInteger" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The background-validation-millis element specifies the amount of
-              time, in millis, that background validation will run.
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="use-fast-fail" type="xs:boolean" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Whether fail a connection allocation on the first connection if it
-              is invalid (true) or keep trying until the pool is exhausted of all potential
-              connections (false) default false. e.g. <use-fast-fail>true</use-fast-fail>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element minOccurs="0" name="stale-connection-checker" type="extensionType">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              An org.jboss.jca.adapters.jdbc.StaleConnectionChecker that provides
-              a boolean isStaleConnection(SQLException e) method which if it it returns
-              true will wrap the exception in an org.jboss.jca.adapters.jdbc.StaleConnectionException
-              which is a subclass of SQLException. Ex:
-              <stale-connection-checker class-name="org.jboss.jca.adapters.jdbc.vendor.OracleStaleConnectionChecker"/>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="exception-sorter" type="extensionType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              An org.jboss.jca.adapters.jdbc.ExceptionSorter that provides a
-              boolean isExceptionFatal(SQLException e) method to validate is an exception
-              should be broadcast to all javax.resource.spi.ConnectionEventListener as
-              a connectionErrorOccurred message. Ex:
-              <exception-sorter class-name="org.jboss.jca.adapters.jdbc.vendor.OracleExceptionSorter"/>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-    </xs:sequence>
-  </xs:complexType>
-  <xs:complexType name="timeoutType">
-    <xs:sequence>
-      <xs:element name="blocking-timeout-millis" type="xs:nonNegativeInteger" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The blocking-timeout-millis element indicates the maximum time in
-              milliseconds to block while waiting for a connection before throwing an exception.
-              Note that this blocks only while waiting for a permit for a connection, and
-              will never throw an exception if creating a new connection takes an inordinately
-              long time. The default is 30000 (30 seconds).
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="idle-timeout-minutes" type="xs:nonNegativeInteger" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The idle-timeout-minutes elements indicates the maximum time in minutes
-              a connection may be idle before being closed. The actual maximum time depends
-              also on the IdleRemover scan time, which is 1/2 the smallest idle-timeout-minutes
-              of any pool.
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="set-tx-query-timeout" type="boolean-presenceType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Whether to set the query timeout based on the time remaining until
-              transaction timeout, any configured query timeout will be used if there is
-              no transaction. The default is false. e.g. <set-tx-query-timeout/>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="query-timeout" type="xs:nonNegativeInteger" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Any configured query timeout in seconds The default is no timeout
-              e.g. 5 minutes <query-timeout>300</query-timeout>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="use-try-lock" type="xs:nonNegativeInteger" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Any configured timeout for internal locks on the resource adapter
-              objects in seconds The default is a 60 second timeout e.g. 5 minutes <use-try-lock>300</use-try-lock>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="allocation-retry" type="xs:nonNegativeInteger" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The allocation retry element indicates the number of times that allocating
-              a connection should be tried before throwing an exception. The default is 0.
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="allocation-retry-wait-millis" type="xs:nonNegativeInteger" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The allocation retry wait millis element indicates the time in milliseconds
-              to wait between retrying to allocate a connection. The default is 5000 (5 seconds).
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="xa-resource-timeout" type="xs:token" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Passed to XAResource.setTransactionTimeout() Default is zero which
-              does not invoke the setter. In seconds e.g. 5 minutes <xa-resource-timeout>300</xa-resource-timeout>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-    </xs:sequence>
-  </xs:complexType>
-  <xs:simpleType name="track-statementsType">
-    <xs:restriction base="xs:token">
-      <xs:enumeration value="true" />
-      <xs:enumeration value="false" />
-      <xs:enumeration value="nowarn" />
-    </xs:restriction>
-  </xs:simpleType>
-  <xs:complexType name="statementType">
-    <xs:sequence>
-      <xs:element name="track-statements" type="track-statementsType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Whether to check for unclosed statements when a connection is returned
-              to the pool and result sets are closed when a statement is closed/return
-              to the prepared statement cache. valid values are: false - do not track statements
-              and results true - track statements and result sets and warn when they are
-              not closed nowarn - track statements but do no warn about them being unclosed
-              (the default) e.g. <track-statements>nowarn</track-statements>
-            ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="prepared-statement-cache-size" type="xs:nonNegativeInteger" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The number of prepared statements per connection in an LRU cache
-            ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="share-prepared-statements" type="boolean-presenceType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Whether to share prepare statements, i.e. whether asking for same
-              statement twice without closing uses the same underlying prepared statement.
-              The default is false. e.g. <share-prepared-statements/>
-            ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-    </xs:sequence>
-  </xs:complexType>
-  <xs:complexType name="poolType">
-    <xs:sequence>
-      <xs:element name="min-pool-size" type="xs:nonNegativeInteger" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The min-pool-size element indicates the minimum number of connections
-              a pool should hold. These are not created until a Subject is known from a
-              request for a connection. This default to 0. Ex: <min-pool-size>1</min-pool-size>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="max-pool-size" type="xs:nonNegativeInteger" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The max-pool-size element indicates the maximum number of connections
-              for a pool. No more connections will be created in each sub-pool.
-              This defaults to 20.
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="prefill" type="xs:boolean" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Whether to attempt to prefill the connection pool. Empty element denotes
-              a true value. e.g. <prefill>true</prefill>.
-              Default is false
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="use-strict-min" type="xs:boolean" minOccurs="0" maxOccurs="1">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Define if the min-pool-size should be considered a strictly.
-              Default false
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="flush-strategy" type="xs:token" minOccurs="0" maxOccurs="1">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies how the pool should be flush in case of an error.
-              Valid values are: FailingConnectionOnly (default), IdleConnections, EntirePool
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-    </xs:sequence>
-  </xs:complexType>
-  <xs:complexType name="xa-poolType">
-    <xs:complexContent>
-      <xs:extension base="poolType">
-        <xs:sequence>
-          <xs:element name="is-same-rm-override" type="xs:boolean" minOccurs="0">
-            <xs:annotation>
-              <xs:documentation>
-                <![CDATA[[
-                  The is-same-rm-override element allows one to unconditionally
-                  set whether the javax.transaction.xa.XAResource.isSameRM(XAResource) returns
-                  true or false. Ex: <is-same-rm-override>true</is-same-rm-override>
-                 ]]>
-              </xs:documentation>
-            </xs:annotation>
-          </xs:element>
-          <xs:element name="interleaving" type="boolean-presenceType" minOccurs="0">
-            <xs:annotation>
-              <xs:documentation>
-                <![CDATA[[
-                  An element to enable interleaving for XA connection factories
-                  Ex: <interleaving/>
-                 ]]>
-              </xs:documentation>
-            </xs:annotation>
-          </xs:element>
-          <xs:element name="no-tx-separate-pools" type="boolean-presenceType" minOccurs="0">
-            <xs:annotation>
-              <xs:documentation>
-                <![CDATA[[
-                  Oracle does not like XA connections getting used both inside and outside a JTA transaction.
-                  To workaround the problem you can create separate sub-pools for the different contexts
-                  using <no-tx-separate-pools/>
-                  Ex: <no-tx-separate-pools/>
-                 ]]>
-              </xs:documentation>
-            </xs:annotation>
-          </xs:element>
-          <xs:element name="pad-xid" type="xs:boolean" default="false" minOccurs="0">
-            <xs:annotation>
-              <xs:documentation>
-                <![CDATA[[
-                   Should the Xid be padded
-                   Ex: <pad-xid>true</pad-xid>
-                 ]]>
-              </xs:documentation>
-            </xs:annotation>
-          </xs:element>
-          <xs:element name="wrap-xa-resource" type="xs:boolean" default="false" minOccurs="0">
-            <xs:annotation>
-              <xs:documentation>
-                <![CDATA[[
-                   Should the XAResource instances be wrapped in a org.jboss.tm.XAResourceWrapper
-                   instance
-                   Ex: <wrap-xa-resource>true</wrap-xa-resource>
-                 ]]>
-              </xs:documentation>
-            </xs:annotation>
-          </xs:element>
-        </xs:sequence>
-      </xs:extension>
-    </xs:complexContent>
-  </xs:complexType>
-  <xs:complexType name="dsSecurityType">
-    <xs:sequence>
-      <xs:element name="user-name" type="xs:token" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-                Specify the username used when creating a new connection.
-                Ex: <user-name>sa</user-name>
-               ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="password" type="xs:token" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-                Specify the password used when creating a new connection.
-                Ex: <password>sa-pass</password>
-               ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="security-domain" type="xs:token" minOccurs="0" maxOccurs="1">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Indicates Subject (from security domain) are used to distinguish connections in the pool.
-              The content of the security-domain is the name of the JAAS security manager that will handle
-              authentication. This name correlates to the JAAS login-config.xml descriptor
-              application-policy/name attribute.
-              Ex:
-              <security-domain>HsqlDbRealm</security-domain>
-            ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="reauth-plugin" type="extensionType" minOccurs="0" maxOccurs="1"></xs:element>
-    </xs:sequence>
-  </xs:complexType>
-
-  <xs:complexType name="extensionType">
-    <xs:sequence>
-      <xs:element name="config-property" type="config-propertyType" minOccurs="0" maxOccurs="unbounded"></xs:element>
-    </xs:sequence>
-    <xs:attribute name="class-name" type="xs:token" use="required"></xs:attribute>
-  </xs:complexType>
-
-  <xs:complexType name="config-propertyType" mixed="true">
-    <xs:annotation>
-      <xs:documentation>
-        <![CDATA[[
-          Specifies a Java bean property value
-         ]]>
-      </xs:documentation>
-    </xs:annotation>
-    <xs:simpleContent>
-      <xs:extension base="xs:token">
-        <xs:attribute use="required" name="name" type="xs:token">
-          <xs:annotation>
-            <xs:documentation>
-              <![CDATA[[
-                Specifies the name of the config-property
-               ]]>
-            </xs:documentation>
-          </xs:annotation>
-        </xs:attribute>
-      </xs:extension>
-    </xs:simpleContent>
-  </xs:complexType>
-  <xs:complexType name="recoverType">
-    <xs:sequence>
-      <xs:element name="recover-credential" type="dsSecurityType" minOccurs="0" maxOccurs="1">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the security options used when creating a connection during recovery.
-              Note: if this credential are not specified the security credential are used for recover too
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="recover-plugin" type="extensionType" minOccurs="0" maxOccurs="1">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the extension plugin used in spi (core.spi.xa)
-              which can be implemented by various plugins to provide better feedback to the XA recovery system.
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-    </xs:sequence>
-    <xs:attribute name="no-recovery" type="xs:boolean" default="false" use="optional">
-      <xs:annotation>
-        <xs:documentation>
-          <![CDATA[[
-            Specify if the xa-datasource should be excluded from recovery.
-            Default false.
-           ]]>
-        </xs:documentation>
-      </xs:annotation>
-    </xs:attribute>
-  </xs:complexType>
-
-  <xs:complexType name="driverType">
-    <xs:sequence>
-      <xs:element name="driver-class" type="xs:token" maxOccurs="1" minOccurs="0">
-      <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The fully qualifed name of the JDBC driver class Ex: <driver-class>org.hsqldb.jdbcDriver</driver-class>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="datasource-class" type="xs:token" maxOccurs="1" minOccurs="0">
-      <xs:annotation>
-          <xs:documentation>
-           <![CDATA[[
-              The fully qualifed name of the javax.sql.DataSource implementation
-              class.
-             ]]>
-          </xs:documentation>
-        </xs:annotation></xs:element>
-      <xs:element name="xa-datasource-class" type="xs:token" maxOccurs="1" minOccurs="0">
-      <xs:annotation>
-          <xs:documentation>
-           <![CDATA[[
-              The fully qualifed name of the javax.sql.XADataSource implementation
-              class. Ex: <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
-             ]]>
-          </xs:documentation>
-        </xs:annotation></xs:element>
-    </xs:sequence>
-    <xs:attribute name="name" type="xs:token" use="required">
-      <xs:annotation>
-        <xs:documentation>
-          <![CDATA[[
-            Specifies the symbolic name of this driver used to reference this driver
-           ]]>
-        </xs:documentation>
-      </xs:annotation>
-    </xs:attribute>
-    <xs:attribute name="module" type="xs:token" use="optional">
-      <xs:annotation>
-        <xs:documentation>
-          <![CDATA[[
-            Specifies the name of AS7 module providing this driver.
-            Thios tag is not used in IronJacamar standalone container.
-           ]]>
-        </xs:documentation>
-      </xs:annotation>
-    </xs:attribute>
-    <xs:attribute name="major-version" type="xs:int" use="optional">
-      <xs:annotation>
-        <xs:documentation>
-          <![CDATA[[
-            Specifies the major version of this driver. If the major and minor version is obmitted the fist availabe
-            Driver in module will be used.
-           ]]>
-        </xs:documentation>
-      </xs:annotation>
-    </xs:attribute>
-    <xs:attribute name="minor-verion" type="xs:int" use="optional">
-    <xs:annotation>
-        <xs:documentation>
-          <![CDATA[[
-            Specifies the minor version of this driver. If the major and minor version is obmitted the fist availabe
-            Driver in module will be used.
-           ]]>
-        </xs:documentation>
-      </xs:annotation>
-    </xs:attribute>
-  </xs:complexType>
-
-  <xs:complexType name="driversType">
-    <xs:sequence>
-      <xs:element name="driver" type="driverType" maxOccurs="unbounded" minOccurs="1"></xs:element>
-    </xs:sequence>
-  </xs:complexType>
-</xs:schema>

jboss-as-7.2.0.Final/docs/schema/jboss-as-datasources_1_1.xsd

@@ -1,967 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
-  ~ JBoss, Home of Professional Open Source.
-  ~ Copyright 2011, Red Hat, Inc., and individual contributors
-  ~ as indicated by the @author tags. See the copyright.txt file in the
-  ~ distribution for a full listing of individual contributors.
-  ~
-  ~ This is free software; you can redistribute it and/or modify it
-  ~ under the terms of the GNU Lesser General Public License as
-  ~ published by the Free Software Foundation; either version 2.1 of
-  ~ the License, or (at your option) any later version.
-  ~
-  ~ This software is distributed in the hope that it will be useful,
-  ~ but WITHOUT ANY WARRANTY; without even the implied warranty of
-  ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-  ~ Lesser General Public License for more details.
-  ~
-  ~ You should have received a copy of the GNU Lesser General Public
-  ~ License along with this software; if not, write to the Free
-  ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
-  ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
-  -->
-
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
-           targetNamespace="urn:jboss:domain:datasources:1.1" xmlns="urn:jboss:domain:datasources:1.1"
-           elementFormDefault="qualified" attributeFormDefault="unqualified">
-
-  <xs:element name="subsystem" type="subsystemType"/>
-
-  <xs:complexType name="subsystemType">
-    <xs:all>
-      <xs:element name="datasources" type="datasourcesType" minOccurs="1" maxOccurs="1"/>
-    </xs:all>
-  </xs:complexType>
-
-  <xs:complexType name="datasourcesType">
-    <xs:sequence>
-      <xs:choice minOccurs="0" maxOccurs="unbounded">
-        <xs:element name="datasource" type="datasourceType">
-          <xs:annotation>
-            <xs:documentation>
-              <![CDATA[[
-                Specifies a non-XA datasource, using local transactions
-               ]]>
-            </xs:documentation>
-          </xs:annotation>
-        </xs:element>
-        <xs:element name="xa-datasource" type="xa-datasourceType">
-          <xs:annotation>
-            <xs:documentation>
-              <![CDATA[[
-                Specifies a XA datasource
-                ]]>
-            </xs:documentation>
-          </xs:annotation>
-        </xs:element>
-      </xs:choice>
-      <xs:element name="drivers" type="driversType" maxOccurs="1" minOccurs="0"></xs:element>
-    </xs:sequence>
-  </xs:complexType>
-  <xs:complexType name="datasourceType" mixed="false">
-    <xs:sequence>
-      <xs:element name="connection-url" type="xs:token">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The JDBC driver connection URL Ex: <connection-url>jdbc:hsqldb:hsql://localhost:1701</connection-url>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="driver-class" type="xs:token" maxOccurs="1" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The fully qualifed name of the JDBC driver class Ex: <driver-class>org.hsqldb.jdbcDriver</driver-class>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="datasource-class" type="xs:token" maxOccurs="1" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The fully qualifed name of the JDBC datasource class Ex: <datasource-class>org.h2.jdbcx.JdbcDataSource</datasource-class>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="driver" type="xs:token" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              An unique reference to the classloader module which contains the JDBC driver
-              The accepted format is driverName#majorVersion.minorVersion
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="connection-property" type="connection-propertyType" minOccurs="0" maxOccurs="unbounded">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The connection-property element allows you to pass in arbitrary connection
-              properties to the Driver.connect(url, props) method. Each connection-property
-              specifies a string name/value pair with the property name coming from the
-              name attribute and the value coming from the element content. Ex:
-              <connection-property name="char.encoding">UTF-8</connection-property>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="new-connection-sql" type="xs:string" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specify an SQL statement to execute whenever a connection is added
-              to the connection pool.
-              ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="transaction-isolation" type="transaction-isolationType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Set java.sql.Connection transaction isolation level to use. The constants
-              defined by transaction-isolation-values are the possible transaction isolation
-              levels and include: TRANSACTION_READ_UNCOMMITTED TRANSACTION_READ_COMMITTED
-              TRANSACTION_REPEATABLE_READ TRANSACTION_SERIALIZABLE TRANSACTION_NONE
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="url-delimiter" type="xs:token" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the delimeter for URLs in connection-url for HA datasources
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="url-selector-strategy-class-name" type="xs:token" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              A class that implements org.jboss.jca.adapters.jdbc.URLSelectorStrategy
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="pool" type="poolType" minOccurs="0" maxOccurs="1">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the pooling settings
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="security" type="dsSecurityType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the security settings
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="validation" type="validationType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the validation settings
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="timeout" type="timeoutType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the time out settings
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="statement" type="statementType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the statement settings
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-    </xs:sequence>
-    <xs:attribute name="jta" type="xs:boolean" default="true" use="optional">
-      <xs:annotation>
-        <xs:documentation>
-          <![CDATA[[
-            Enable JTA integration
-           ]]>
-        </xs:documentation>
-      </xs:annotation>
-    </xs:attribute>
-    <xs:attributeGroup ref="common-datasourceAttributes" />
-  </xs:complexType>
-  <xs:complexType name="xa-datasourceType">
-    <xs:sequence>
-      <xs:element name="xa-datasource-property" type="xa-datasource-propertyType" minOccurs="1" maxOccurs="unbounded">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies a property to assign to the XADataSource implementation class.
-              Each property is identified by the name attribute and the property value
-              is given by the xa-datasource-property element content. The property is mapped
-              onto the XADataSource implementation by looking for a JavaBeans style getter
-              method for the property name. If found, the value of the property is set
-              using the JavaBeans setter with the element text translated to the true property
-              type using the java.beans.PropertyEditor for the type. Ex:
-              <xa-datasource-property name="IfxWAITTIME">10</xa-datasource-property>
-              <xa-datasource-property name="IfxIFXHOST">myhost.mydomain.com</xa-datasource-property>
-              <xa-datasource-property name="PortNumber">1557</xa-datasource-property>
-              <xa-datasource-property name="DatabaseName">mydb</xa-datasource-property>
-              <xa-datasource-property name="ServerName">myserver</xa-datasource-property>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="xa-datasource-class" type="xs:token" maxOccurs="1" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The fully qualifed name of the javax.sql.XADataSource implementation
-              class. Ex: <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="driver" type="xs:token" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              An unique reference to the classloader module which contains the JDBC driver
-              The accepted format is driverName#majorVersion.minorVersion
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="url-delimiter" type="xs:token" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-               Specifies the delimeter for URLs in the connection url for HA datasources
-              ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="url-selector-strategy-class-name" type="xs:token" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-               A class that implements org.jboss.jca.adapters.jdbc.URLSelectorStrategy
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="new-connection-sql" type="xs:string" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-               Specifies an SQL statement to execute whenever a connection is added
-               to the connection pool.
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="transaction-isolation" type="transaction-isolationType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Set java.sql.Connection transaction isolation level to use. The constants
-              defined by transaction-isolation-values are the possible transaction isolation
-              levels and include: TRANSACTION_READ_UNCOMMITTED TRANSACTION_READ_COMMITTED
-              TRANSACTION_REPEATABLE_READ TRANSACTION_SERIALIZABLE TRANSACTION_NONE
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="xa-pool" type="xa-poolType" minOccurs="0" maxOccurs="1">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the pooling settings
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="security" type="dsSecurityType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the security settings
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="validation" type="validationType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the validation settings
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="timeout" type="timeoutType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the time out settings
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="statement" type="statementType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the statement settings
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="recovery" type="recoverType" minOccurs="0" maxOccurs="1"></xs:element>
-    </xs:sequence>
-    <xs:attributeGroup ref="common-datasourceAttributes" />
-  </xs:complexType>
-  <xs:complexType name="boolean-presenceType" />
-  <xs:attributeGroup name="common-datasourceAttributes">
-    <xs:attribute name="jndi-name" type="xs:token" use="required">
-      <xs:annotation>
-        <xs:documentation>
-          <![CDATA[[
-            Specifies the JNDI name for the datasource
-           ]]>
-        </xs:documentation>
-      </xs:annotation>
-    </xs:attribute>
-    <xs:attribute name="pool-name" type="xs:token" use="required">
-      <xs:annotation>
-        <xs:documentation>
-          <![CDATA[[
-            Specifies the pool name for the datasource used for management
-           ]]>
-        </xs:documentation>
-      </xs:annotation>
-    </xs:attribute>
-    <xs:attribute name="enabled" type="xs:boolean" default="true" form="unqualified" use="optional">
-      <xs:annotation>
-        <xs:documentation>
-          <![CDATA[[
-            Specifies if the datasource should be enabled
-           ]]>
-        </xs:documentation>
-      </xs:annotation>
-    </xs:attribute>
-    <xs:attribute default="true" name="use-java-context" type="xs:boolean">
-      <xs:annotation>
-        <xs:documentation>
-          <![CDATA[[
-            Setting this to false will bind the DataSource into global JNDI
-            Ex: use-java-context="true"
-           ]]>
-        </xs:documentation>
-      </xs:annotation>
-    </xs:attribute>
-    <xs:attribute default="false" name="spy" type="xs:boolean">
-      <xs:annotation>
-        <xs:documentation>
-          <![CDATA[[
-            Enable spy functionality on the JDBC layer - e.g. log all JDBC traffic to the datasource.
-            Remember to enable the logging category (org.jboss.jdbc) too.
-            Ex: spy="true"
-           ]]>
-        </xs:documentation>
-      </xs:annotation>
-    </xs:attribute>
-    <xs:attribute default="true" name="use-ccm" type="xs:boolean">
-      <xs:annotation>
-        <xs:documentation>
-          <![CDATA[[
-            Enable the use of a cached connection manager
-            Ex: use-ccm="true"
-           ]]>
-        </xs:documentation>
-      </xs:annotation>
-    </xs:attribute>
-  </xs:attributeGroup>
-  <xs:simpleType name="transaction-isolationType">
-    <xs:annotation>
-      <xs:documentation>
-        <![CDATA[[
-          Define constants used as the possible transaction isolation levels in transaction-isolation
-          type. Include: TRANSACTION_READ_UNCOMMITTED, TRANSACTION_READ_COMMITTED, TRANSACTION_REPEATABLE_READ,
-          TRANSACTION_SERIALIZABLE, TRANSACTION_NONE
-         ]]>
-      </xs:documentation>
-    </xs:annotation>
-    <xs:restriction base="xs:token">
-      <xs:enumeration value="TRANSACTION_READ_UNCOMMITTED" />
-      <xs:enumeration value="TRANSACTION_READ_COMMITTED" />
-      <xs:enumeration value="TRANSACTION_REPEATABLE_READ" />
-      <xs:enumeration value="TRANSACTION_SERIALIZABLE" />
-      <xs:enumeration value="TRANSACTION_NONE" />
-    </xs:restriction>
-  </xs:simpleType>
-  <xs:complexType name="xa-datasource-propertyType" mixed="true">
-    <xs:attribute name="name" use="required" type="xs:token" />
-  </xs:complexType>
-  <xs:complexType name="connection-propertyType" mixed="true">
-    <xs:attribute name="name" use="required" type="xs:token" />
-  </xs:complexType>
-  <xs:complexType name="validationType">
-    <xs:sequence>
-      <xs:element name="valid-connection-checker" type="extensionType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              An org.jboss.jca.adapters.jdbc.ValidConnectionChecker that provides
-              a SQLException isValidConnection(Connection e) method to validate is a connection
-              is valid. An exception means the connection is destroyed. This overrides
-              the check-valid-connection-sql when present. Ex:
-              <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.vendor.OracleValidConnectionChecker"/>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-
-      <xs:element name="check-valid-connection-sql" type="xs:string" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specify an SQL statement to check validity of a pool connection. This
-              may be called when managed connection is taken from pool for use.
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="validate-on-match" type="xs:boolean" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The validate-on-match element indicates whether or not connection
-              level validation should be done when a connection factory attempts to match
-              a managed connection for a given set. This is typically exclusive to the
-              use of background validation
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="background-validation" type="xs:boolean" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              An element to specify that connections should be validated on a background
-              thread versus being validated prior to use
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="background-validation-millis" type="xs:nonNegativeInteger" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The background-validation-millis element specifies the amount of
-              time, in millis, that background validation will run.
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="use-fast-fail" type="xs:boolean" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Whether fail a connection allocation on the first connection if it
-              is invalid (true) or keep trying until the pool is exhausted of all potential
-              connections (false) default false. e.g. <use-fast-fail>true</use-fast-fail>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element minOccurs="0" name="stale-connection-checker" type="extensionType">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              An org.jboss.jca.adapters.jdbc.StaleConnectionChecker that provides
-              a boolean isStaleConnection(SQLException e) method which if it it returns
-              true will wrap the exception in an org.jboss.jca.adapters.jdbc.StaleConnectionException
-              which is a subclass of SQLException. Ex:
-              <stale-connection-checker class-name="org.jboss.jca.adapters.jdbc.vendor.OracleStaleConnectionChecker"/>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="exception-sorter" type="extensionType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              An org.jboss.jca.adapters.jdbc.ExceptionSorter that provides a
-              boolean isExceptionFatal(SQLException e) method to validate is an exception
-              should be broadcast to all javax.resource.spi.ConnectionEventListener as
-              a connectionErrorOccurred message. Ex:
-              <exception-sorter class-name="org.jboss.jca.adapters.jdbc.vendor.OracleExceptionSorter"/>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-    </xs:sequence>
-  </xs:complexType>
-  <xs:complexType name="timeoutType">
-    <xs:sequence>
-      <xs:element name="blocking-timeout-millis" type="xs:nonNegativeInteger" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The blocking-timeout-millis element indicates the maximum time in
-              milliseconds to block while waiting for a connection before throwing an exception.
-              Note that this blocks only while waiting for a permit for a connection, and
-              will never throw an exception if creating a new connection takes an inordinately
-              long time. The default is 30000 (30 seconds).
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="idle-timeout-minutes" type="xs:nonNegativeInteger" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The idle-timeout-minutes elements indicates the maximum time in minutes
-              a connection may be idle before being closed. The actual maximum time depends
-              also on the IdleRemover scan time, which is 1/2 the smallest idle-timeout-minutes
-              of any pool.
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="set-tx-query-timeout" type="boolean-presenceType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Whether to set the query timeout based on the time remaining until
-              transaction timeout, any configured query timeout will be used if there is
-              no transaction. The default is false. e.g. <set-tx-query-timeout/>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="query-timeout" type="xs:nonNegativeInteger" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Any configured query timeout in seconds The default is no timeout
-              e.g. 5 minutes <query-timeout>300</query-timeout>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="use-try-lock" type="xs:nonNegativeInteger" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Any configured timeout for internal locks on the resource adapter
-              objects in seconds The default is a 60 second timeout e.g. 5 minutes <use-try-lock>300</use-try-lock>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="allocation-retry" type="xs:nonNegativeInteger" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The allocation retry element indicates the number of times that allocating
-              a connection should be tried before throwing an exception. The default is 0.
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="allocation-retry-wait-millis" type="xs:nonNegativeInteger" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The allocation retry wait millis element indicates the time in milliseconds
-              to wait between retrying to allocate a connection. The default is 5000 (5 seconds).
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="xa-resource-timeout" type="xs:token" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Passed to XAResource.setTransactionTimeout() Default is zero which
-              does not invoke the setter. In seconds e.g. 5 minutes <xa-resource-timeout>300</xa-resource-timeout>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-    </xs:sequence>
-  </xs:complexType>
-  <xs:simpleType name="track-statementsType">
-    <xs:restriction base="xs:token">
-      <xs:enumeration value="true" />
-      <xs:enumeration value="false" />
-      <xs:enumeration value="nowarn" />
-    </xs:restriction>
-  </xs:simpleType>
-  <xs:complexType name="statementType">
-    <xs:sequence>
-      <xs:element name="track-statements" type="track-statementsType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Whether to check for unclosed statements when a connection is returned
-              to the pool and result sets are closed when a statement is closed/return
-              to the prepared statement cache. valid values are: false - do not track statements
-              and results true - track statements and result sets and warn when they are
-              not closed nowarn - track statements but do no warn about them being unclosed
-              (the default) e.g. <track-statements>nowarn</track-statements>
-            ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="prepared-statement-cache-size" type="xs:nonNegativeInteger" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The number of prepared statements per connection in an LRU cache
-            ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="share-prepared-statements" type="boolean-presenceType" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Whether to share prepare statements, i.e. whether asking for same
-              statement twice without closing uses the same underlying prepared statement.
-              The default is false. e.g. <share-prepared-statements/>
-            ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-    </xs:sequence>
-  </xs:complexType>
-  <xs:complexType name="poolType">
-    <xs:sequence>
-      <xs:element name="min-pool-size" type="xs:nonNegativeInteger" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The min-pool-size element indicates the minimum number of connections
-              a pool should hold. These are not created until a Subject is known from a
-              request for a connection. This default to 0. Ex: <min-pool-size>1</min-pool-size>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="max-pool-size" type="xs:nonNegativeInteger" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The max-pool-size element indicates the maximum number of connections
-              for a pool. No more connections will be created in each sub-pool.
-              This defaults to 20.
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="prefill" type="xs:boolean" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Whether to attempt to prefill the connection pool. Empty element denotes
-              a true value. e.g. <prefill>true</prefill>.
-              Default is false
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="use-strict-min" type="xs:boolean" minOccurs="0" maxOccurs="1">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Define if the min-pool-size should be considered a strictly.
-              Default false
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="flush-strategy" type="xs:token" minOccurs="0" maxOccurs="1">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies how the pool should be flush in case of an error.
-              Valid values are: FailingConnectionOnly (default), IdleConnections, EntirePool
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="allow-multiple-users" type="boolean-presenceType" minOccurs="0" maxOccurs="1">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies if multiple users will access the datasource through the getConnection(user, password)
-              method and hence if the internal pool type should account for that
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-    </xs:sequence>
-  </xs:complexType>
-  <xs:complexType name="xa-poolType">
-    <xs:complexContent>
-      <xs:extension base="poolType">
-        <xs:sequence>
-          <xs:element name="is-same-rm-override" type="xs:boolean" minOccurs="0">
-            <xs:annotation>
-              <xs:documentation>
-                <![CDATA[[
-                  The is-same-rm-override element allows one to unconditionally
-                  set whether the javax.transaction.xa.XAResource.isSameRM(XAResource) returns
-                  true or false. Ex: <is-same-rm-override>true</is-same-rm-override>
-                 ]]>
-              </xs:documentation>
-            </xs:annotation>
-          </xs:element>
-          <xs:element name="interleaving" type="boolean-presenceType" minOccurs="0">
-            <xs:annotation>
-              <xs:documentation>
-                <![CDATA[[
-                  An element to enable interleaving for XA connection factories
-                  Ex: <interleaving/>
-                 ]]>
-              </xs:documentation>
-            </xs:annotation>
-          </xs:element>
-          <xs:element name="no-tx-separate-pools" type="boolean-presenceType" minOccurs="0">
-            <xs:annotation>
-              <xs:documentation>
-                <![CDATA[[
-                  Oracle does not like XA connections getting used both inside and outside a JTA transaction.
-                  To workaround the problem you can create separate sub-pools for the different contexts
-                  using <no-tx-separate-pools/>
-                  Ex: <no-tx-separate-pools/>
-                 ]]>
-              </xs:documentation>
-            </xs:annotation>
-          </xs:element>
-          <xs:element name="pad-xid" type="xs:boolean" default="false" minOccurs="0">
-            <xs:annotation>
-              <xs:documentation>
-                <![CDATA[[
-                   Should the Xid be padded
-                   Ex: <pad-xid>true</pad-xid>
-                 ]]>
-              </xs:documentation>
-            </xs:annotation>
-          </xs:element>
-          <xs:element name="wrap-xa-resource" type="xs:boolean" default="false" minOccurs="0">
-            <xs:annotation>
-              <xs:documentation>
-                <![CDATA[[
-                   Should the XAResource instances be wrapped in a org.jboss.tm.XAResourceWrapper
-                   instance
-                   Ex: <wrap-xa-resource>true</wrap-xa-resource>
-                 ]]>
-              </xs:documentation>
-            </xs:annotation>
-          </xs:element>
-        </xs:sequence>
-      </xs:extension>
-    </xs:complexContent>
-  </xs:complexType>
-  <xs:complexType name="dsSecurityType">
-    <xs:sequence>
-      <xs:element name="user-name" type="xs:token" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-                Specify the username used when creating a new connection.
-                Ex: <user-name>sa</user-name>
-               ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="password" type="xs:token" minOccurs="0">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-                Specify the password used when creating a new connection.
-                Ex: <password>sa-pass</password>
-               ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="security-domain" type="xs:token" minOccurs="0" maxOccurs="1">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Indicates Subject (from security domain) are used to distinguish connections in the pool.
-              The content of the security-domain is the name of the JAAS security manager that will handle
-              authentication. This name correlates to the JAAS login-config.xml descriptor
-              application-policy/name attribute.
-              Ex:
-              <security-domain>HsqlDbRealm</security-domain>
-            ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="reauth-plugin" type="extensionType" minOccurs="0" maxOccurs="1"></xs:element>
-    </xs:sequence>
-  </xs:complexType>
-
-  <xs:complexType name="extensionType">
-    <xs:sequence>
-      <xs:element name="config-property" type="config-propertyType" minOccurs="0" maxOccurs="unbounded"></xs:element>
-    </xs:sequence>
-    <xs:attribute name="class-name" type="xs:token" use="required"></xs:attribute>
-  </xs:complexType>
-
-  <xs:complexType name="config-propertyType" mixed="true">
-    <xs:annotation>
-      <xs:documentation>
-        <![CDATA[[
-          Specifies a Java bean property value
-         ]]>
-      </xs:documentation>
-    </xs:annotation>
-    <xs:simpleContent>
-      <xs:extension base="xs:token">
-        <xs:attribute use="required" name="name" type="xs:token">
-          <xs:annotation>
-            <xs:documentation>
-              <![CDATA[[
-                Specifies the name of the config-property
-               ]]>
-            </xs:documentation>
-          </xs:annotation>
-        </xs:attribute>
-      </xs:extension>
-    </xs:simpleContent>
-  </xs:complexType>
-  <xs:complexType name="recoverType">
-    <xs:sequence>
-      <xs:element name="recover-credential" type="dsSecurityType" minOccurs="0" maxOccurs="1">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the security options used when creating a connection during recovery.
-              Note: if this credential are not specified the security credential are used for recover too
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="recover-plugin" type="extensionType" minOccurs="0" maxOccurs="1">
-        <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              Specifies the extension plugin used in spi (core.spi.xa)
-              which can be implemented by various plugins to provide better feedback to the XA recovery system.
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-    </xs:sequence>
-    <xs:attribute name="no-recovery" type="xs:boolean" default="false" use="optional">
-      <xs:annotation>
-        <xs:documentation>
-          <![CDATA[[
-            Specify if the xa-datasource should be excluded from recovery.
-            Default false.
-           ]]>
-        </xs:documentation>
-      </xs:annotation>
-    </xs:attribute>
-  </xs:complexType>
-
-  <xs:complexType name="driverType">
-    <xs:sequence>
-      <xs:element name="driver-class" type="xs:token" maxOccurs="1" minOccurs="0">
-      <xs:annotation>
-          <xs:documentation>
-            <![CDATA[[
-              The fully qualifed name of the JDBC driver class Ex: <driver-class>org.hsqldb.jdbcDriver</driver-class>
-             ]]>
-          </xs:documentation>
-        </xs:annotation>
-      </xs:element>
-      <xs:element name="datasource-class" type="xs:token" maxOccurs="1" minOccurs="0">
-      <xs:annotation>
-          <xs:documentation>
-           <![CDATA[[
-              The fully qualifed name of the javax.sql.DataSource implementation
-              class.
-             ]]>
-          </xs:documentation>
-        </xs:annotation></xs:element>
-      <xs:element name="xa-datasource-class" type="xs:token" maxOccurs="1" minOccurs="0">
-      <xs:annotation>
-          <xs:documentation>
-           <![CDATA[[
-              The fully qualifed name of the javax.sql.XADataSource implementation
-              class. Ex: <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
-             ]]>
-          </xs:documentation>
-        </xs:annotation></xs:element>
-    </xs:sequence>
-    <xs:attribute name="name" type="xs:token" use="required">
-      <xs:annotation>
-        <xs:documentation>
-          <![CDATA[[
-            Specifies the symbolic name of this driver used to reference this driver
-           ]]>
-        </xs:documentation>
-      </xs:annotation>
-    </xs:attribute>
-    <xs:attribute name="module" type="xs:token" use="optional">
-      <xs:annotation>
-        <xs:documentation>
-          <![CDATA[[
-            Specifies the name of AS7 module providing this driver.
-            Thios tag is not used in IronJacamar standalone container.
-           ]]>
-        </xs:documentation>
-      </xs:annotation>
-    </xs:attribute>
-    <xs:attribute name="major-version" type="xs:int" use="optional">
-      <xs:annotation>
-        <xs:documentation>
-          <![CDATA[[
-            Specifies the major version of this driver. If the major and minor version is obmitted the fist availabe
-            Driver in module will be used.
-           ]]>
-        </xs:documentation>
-      </xs:annotation>
-    </xs:attribute>
-    <xs:attribute name="minor-verion" type="xs:int" use="optional">
-    <xs:annotation>
-        <xs:documentation>
-          <![CDATA[[
-            Specifies the minor version of this driver. If the major and minor version is obmitted the fist availabe
-            Driver in module will be used.
-           ]]>
-        </xs:documentation>
-      </xs:annotation>
-    </xs:attribute>
-  </xs:complexType>
-
-  <xs:complexType name="driversType">
-    <xs:sequence>
-      <xs:element name="driver" type="driverType" maxOccurs="unbounded" minOccurs="1"></xs:element>
-    </xs:sequence>
-  </xs:complexType>
-</xs:schema>

jboss-as-7.2.0.Final/docs/schema/jboss-as-deployment-scanner_1_0.xsd

@@ -1,108 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!--
-  ~ JBoss, Home of Professional Open Source.
-  ~ Copyright 2011, Red Hat, Inc., and individual contributors
-  ~ as indicated by the @author tags. See the copyright.txt file in the
-  ~ distribution for a full listing of individual contributors.
-  ~
-  ~ This is free software; you can redistribute it and/or modify it
-  ~ under the terms of the GNU Lesser General Public License as
-  ~ published by the Free Software Foundation; either version 2.1 of
-  ~ the License, or (at your option) any later version.
-  ~
-  ~ This software is distributed in the hope that it will be useful,
-  ~ but WITHOUT ANY WARRANTY; without even the implied warranty of
-  ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-  ~ Lesser General Public License for more details.
-  ~
-  ~ You should have received a copy of the GNU Lesser General Public
-  ~ License along with this software; if not, write to the Free
-  ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
-  ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
-  -->
-<xs:schema xmlns="urn:jboss:domain:deployment-scanner:1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema" attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="urn:jboss:domain:deployment-scanner:1.0" version="1.0">
-
-    <!-- The threads subsystem root element -->
-    <xs:element name="subsystem" type="subsystem"/>
-
-    <xs:complexType name="subsystem">
-        <xs:annotation>
-            <xs:documentation>
-                <![CDATA[
-                The filesystem deployment scanner subsystem configuration.
-                ]]>
-            </xs:documentation>
-        </xs:annotation>
-        <xs:choice maxOccurs="unbounded" minOccurs="0">
-            <xs:element maxOccurs="unbounded" minOccurs="0" name="deployment-scanner" type="standalone-deployment-scanner-type"/>
-        </xs:choice>
-    </xs:complexType>
-
-    <xs:complexType name="standalone-deployment-scanner-type">
-        <xs:annotation>
-            <xs:documentation>Allows configuration of an additional location where deployment
-                content can be stored.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute default="default" name="name" type="xs:string" use="optional"/>
-        <xs:attribute name="relative-to" type="xs:string" use="optional">
-           <xs:annotation>
-                <xs:documentation>Reference to a filesystem path defined in the "paths" section
-                of the server configuration.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="path" use="required">
-            <xs:annotation>
-                <xs:documentation>The actual filesystem path. Treated as an absolute path, unless the
-                'relative-to' attribute is specified, in which case the value
-                is treated as relative to that path.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute default="0" name="scan-interval" type="xs:int" use="optional">
-            <xs:annotation>
-                <xs:documentation>Periodic interval, in milliseconds, at which the repository
-                    should be scanned for changes. A value of less than 1 indicates the
-                    repository should only be scanned at initial startup.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute default="true" name="scan-enabled" type="xs:boolean" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Flag indicating that all scanning (including initial scanning at startup)
-                    should be disabled.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute default="true" name="auto-deploy-zipped" type="xs:boolean" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Controls whether zipped deployment content should be automatically deployed by
-                    the scanner without requiring the user to add a .dodeploy marker file.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute default="false" name="auto-deploy-exploded" type="xs:boolean" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                    Controls whether zipped deployment content should be automatically deployed by
-                    the scanner without requiring the user to add a .dodeploy marker file. Setting
-                    this to 'true' is not recommended for anything but basic development scenarios,
-                    as there is no way to ensure that deployment will not occur in the middle of
-                    changes to the content.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute default="60" name="deployment-timeout" type="xs:int" use="optional">
-            <xs:annotation>
-                <xs:documentation>
-                   Timout used. in seconds, for deployment operations.  If an individual deployment operation
-                   takes longer than this timeout it will be canceled and marked as failed.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-</xs:schema>

jboss-as-7.2.0.Final/docs/schema/jboss-as-deployment-scanner_1_1.xsd

@@ -1,116 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!--
-  ~ JBoss, Home of Professional Open Source.
-  ~ Copyright 2011, Red Hat, Inc., and individual contributors
-  ~ as indicated by the @author tags. See the copyright.txt file in the
-  ~ distribution for a full listing of individual contributors.
-  ~
-  ~ This is free software; you can redistribute it and/or modify it
-  ~ under the terms of the GNU Lesser General Public License as
-  ~ published by the Free Software Foundation; either version 2.1 of
-  ~ the License, or (at your option) any later version.
-  ~
-  ~ This software is distributed in the hope that it will be useful,
-  ~ but WITHOUT ANY WARRANTY; without even the implied warranty of
-  ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-  ~ Lesser General Public License for more details.
-  ~
-  ~ You should have received a copy of the GNU Lesser General Public
-  ~ License along with this software; if not, write to the Free
-  ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
-  ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
-  -->
-<xs:schema xmlns="urn:jboss:domain:deployment-scanner:1.1" xmlns:xs="http://www.w3.org/2001/XMLSchema" attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="urn:jboss:domain:deployment-scanner:1.1" version="1.0">
-
-    <!-- The threads subsystem root element -->
-    <xs:element name="subsystem" type="subsystem"/>
-
-    <xs:complexType name="subsystem">
-        <xs:annotation>
-            <xs:documentation>
-                <![CDATA[
-                The filesystem deployment scanner subsystem configuration.
-                ]]>
-            </xs:documentation>
-        </xs:annotation>
-        <xs:choice maxOccurs="unbounded" minOccurs="0">
-            <xs:element maxOccurs="unbounded" minOccurs="0" name="deployment-scanner" type="standalone-deployment-scanner-type"/>
-        </xs:choice>
-    </xs:complexType>
-
-    <xs:complexType name="standalone-deployment-scanner-type">
-        <xs:annotation>
-            <xs:documentation>Allows configuration of an additional location where deployment
-                content can be stored.
-            </xs:documentation>
-        </xs:annotation>
-        <xs:attribute name="name" type="xs:string" use="optional" default="default" />
-        <xs:attribute name="path" use="required">
-            <xs:annotation>
-                <xs:documentation>The actual filesystem path. Treated as an absolute path, unless the
-                'relative-to' attribute is specified, in which case the value
-                is treated as relative to that path.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="relative-to" type="xs:string" use="optional">
-           <xs:annotation>
-                <xs:documentation>Reference to a filesystem path defined in the "paths" section
-                of the server configuration.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="scan-enabled" type="xs:boolean" use="optional" default="true">
-            <xs:annotation>
-                <xs:documentation>
-                    Flag indicating that all scanning (including initial scanning at startup)
-                    should be disabled.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="scan-interval" type="xs:int" use="optional" default="0">
-            <xs:annotation>
-                <xs:documentation>Periodic interval, in milliseconds, at which the repository
-                    should be scanned for changes. A value of less than 1 indicates the
-                    repository should only be scanned at initial startup.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="auto-deploy-zipped" type="xs:boolean" use="optional" default="true">
-            <xs:annotation>
-                <xs:documentation>
-                    Controls whether zipped deployment content should be automatically deployed by
-                    the scanner without requiring the user to add a .dodeploy marker file.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="auto-deploy-exploded" type="xs:boolean" use="optional" default="false">
-            <xs:annotation>
-                <xs:documentation>
-                    Controls whether exploded deployment content should be automatically deployed by
-                    the scanner without requiring the user to add a .dodeploy marker file. Setting
-                    this to 'true' is not recommended for anything but basic development scenarios,
-                    as there is no way to ensure that deployment will not occur in the middle of
-                    changes to the content.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="auto-deploy-xml" type="xs:boolean" use="optional" default="true">
-            <xs:annotation>
-                <xs:documentation>
-                    Controls whether xml deployment content should be automatically deployed by
-                    the scanner without requiring the user to add a .dodeploy marker file.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="deployment-timeout" type="xs:int" use="optional" default="600">
-            <xs:annotation>
-                <xs:documentation>
-                   Timout used, in seconds, for deployment operations.  If an individual deployment operation
-                   takes longer than this timeout it will be canceled and marked as failed.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-</xs:schema>

jboss-as-7.2.0.Final/docs/schema/jboss-as-ee_1_0.xsd

@@ -1,82 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-  ~ JBoss, Home of Professional Open Source.
-  ~ Copyright 2011, Red Hat, Inc., and individual contributors
-  ~ as indicated by the @author tags. See the copyright.txt file in the
-  ~ distribution for a full listing of individual contributors.
-  ~
-  ~ This is free software; you can redistribute it and/or modify it
-  ~ under the terms of the GNU Lesser General Public License as
-  ~ published by the Free Software Foundation; either version 2.1 of
-  ~ the License, or (at your option) any later version.
-  ~
-  ~ This software is distributed in the hope that it will be useful,
-  ~ but WITHOUT ANY WARRANTY; without even the implied warranty of
-  ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-  ~ Lesser General Public License for more details.
-  ~
-  ~ You should have received a copy of the GNU Lesser General Public
-  ~ License along with this software; if not, write to the Free
-  ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
-  ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
-  -->
-
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
-            targetNamespace="urn:jboss:domain:ee:1.0"
-            xmlns="urn:jboss:domain:ee:1.0"
-            elementFormDefault="qualified"
-            attributeFormDefault="unqualified"
-            version="1.0">
-
-    <!-- The EE subsystem root element -->
-    <xs:element name="subsystem" type="subsystem"/>
-
-    <xs:complexType name="subsystem">
-        <xs:sequence>
-            <xs:element name="global-modules" type="modulesType" minOccurs="0" maxOccurs="1"/>
-            <xs:element name="ear-subdeployments-isolated" default="false" type="ear-subdeployments-isolatedType" minOccurs="0" maxOccurs="1"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="modulesType">
-        <xs:choice minOccurs="0" maxOccurs="unbounded">
-            <xs:element name="module" type="moduleType"/>
-        </xs:choice>
-    </xs:complexType>
-
-    <xs:complexType name="moduleType">
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="slot" type="xs:string"/>
-    </xs:complexType>
-
-    <xs:simpleType name="ear-subdeployments-isolatedType">
-        <xs:annotation>
-                <xs:documentation>
-                    Flag indicating whether each of the subdeployments within a .ear can access classes belonging to
-                    another subdeployment within the same .ear. Setting this to false, allows the subdeployments to
-                    see classes belonging to other subdeployments within the .ear.
-                    For example:
-                    myapp.ear
-                     |
-                     |--- web.war
-                     |
-                     |--- ejb1.jar
-                     |
-                     |--- ejb2.jar
-
-                    If the ear-subdeployments-isolated is set to false, then the classes in web.war can access classes
-                    belonging to ejb1.jar and ejb2.jar. Similarly, classes from ejb1.jar can access classes from ejb2.jar
-                    (and vice-versa).
-
-                    *Note that this flag, has no effect on the isolated classloader of the .war file(s). i.e. irrespective
-                    of whether this flag is set to true or false, the .war within a .ear will have a isolated classloader
-                    and other subdeployments within that .ear will not be able to access classes from that .war. This is
-                    as per spec*
-                </xs:documentation>
-        </xs:annotation>
-
-        <xs:restriction base="xs:boolean"/>
-    </xs:simpleType>
-
-</xs:schema>

jboss-as-7.2.0.Final/docs/schema/jboss-as-ee_1_1.xsd

@@ -1,100 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-  ~ JBoss, Home of Professional Open Source.
-  ~ Copyright 2011, Red Hat, Inc., and individual contributors
-  ~ as indicated by the @author tags. See the copyright.txt file in the
-  ~ distribution for a full listing of individual contributors.
-  ~
-  ~ This is free software; you can redistribute it and/or modify it
-  ~ under the terms of the GNU Lesser General Public License as
-  ~ published by the Free Software Foundation; either version 2.1 of
-  ~ the License, or (at your option) any later version.
-  ~
-  ~ This software is distributed in the hope that it will be useful,
-  ~ but WITHOUT ANY WARRANTY; without even the implied warranty of
-  ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-  ~ Lesser General Public License for more details.
-  ~
-  ~ You should have received a copy of the GNU Lesser General Public
-  ~ License along with this software; if not, write to the Free
-  ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
-  ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
-  -->
-
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
-            targetNamespace="urn:jboss:domain:ee:1.1"
-            xmlns="urn:jboss:domain:ee:1.1"
-            elementFormDefault="qualified"
-            attributeFormDefault="unqualified"
-            version="1.1">
-
-    <!-- The EE subsystem root element -->
-    <xs:element name="subsystem" type="subsystem"/>
-
-    <xs:complexType name="subsystem">
-        <xs:sequence>
-            <xs:element name="global-modules" type="modulesType" minOccurs="0" maxOccurs="1"/>
-            <xs:element name="ear-subdeployments-isolated" default="false" type="ear-subdeployments-isolatedType" minOccurs="0" maxOccurs="1"/>
-            <xs:element name="spec-descriptor-property-replacement" type="descriptor-property-replacementType" minOccurs="0" maxOccurs="1" />
-            <xs:element name="jboss-descriptor-property-replacement" type="descriptor-property-replacementType" minOccurs="0" maxOccurs="1" />
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="modulesType">
-        <xs:choice minOccurs="0" maxOccurs="unbounded">
-            <xs:element name="module" type="moduleType"/>
-        </xs:choice>
-    </xs:complexType>
-
-    <xs:complexType name="moduleType">
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="slot" type="xs:string"/>
-    </xs:complexType>
-
-    <xs:simpleType name="ear-subdeployments-isolatedType">
-        <xs:annotation>
-                <xs:documentation>
-                    Flag indicating whether each of the subdeployments within a .ear can access classes belonging to
-                    another subdeployment within the same .ear. Setting this to false, allows the subdeployments to
-                    see classes belonging to other subdeployments within the .ear.
-                    For example:
-                    myapp.ear
-                     |
-                     |--- web.war
-                     |
-                     |--- ejb1.jar
-                     |
-                     |--- ejb2.jar
-
-                    If the ear-subdeployments-isolated is set to false, then the classes in web.war can access classes
-                    belonging to ejb1.jar and ejb2.jar. Similarly, classes from ejb1.jar can access classes from ejb2.jar
-                    (and vice-versa).
-
-                    *Note that this flag, has no effect on the isolated classloader of the .war file(s). i.e. irrespective
-                    of whether this flag is set to true or false, the .war within a .ear will have a isolated classloader
-                    and other subdeployments within that .ear will not be able to access classes from that .war. This is
-                    as per spec*
-                </xs:documentation>
-        </xs:annotation>
-
-        <xs:restriction base="xs:boolean"/>
-    </xs:simpleType>
-
-    <xs:simpleType name="descriptor-property-replacementType">
-        <xs:annotation>
-            <xs:documentation>
-                Flag indicating whether system property replacement will be performed on a descriptor. This defaults to
-                true, however it is disabled in the default configurations.
-
-                Security Node: System properties etc are resolved in the security context of the application server
-                itself, not the deployment that contains the file. This means that if you are running with a security
-                manager and enable this property, a deployment can potentially access system properties or environment
-                entries that the security manager would have otherwise prevented.
-            </xs:documentation>
-        </xs:annotation>
-
-        <xs:restriction base="xs:boolean"/>
-    </xs:simpleType>
-
-</xs:schema>

jboss-as-7.2.0.Final/docs/schema/jboss-as-ejb3_1_0.xsd

@@ -1,38 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-  ~ JBoss, Home of Professional Open Source.
-  ~ Copyright 2011, Red Hat, Inc., and individual contributors
-  ~ as indicated by the @author tags. See the copyright.txt file in the
-  ~ distribution for a full listing of individual contributors.
-  ~
-  ~ This is free software; you can redistribute it and/or modify it
-  ~ under the terms of the GNU Lesser General Public License as
-  ~ published by the Free Software Foundation; either version 2.1 of
-  ~ the License, or (at your option) any later version.
-  ~
-  ~ This software is distributed in the hope that it will be useful,
-  ~ but WITHOUT ANY WARRANTY; without even the implied warranty of
-  ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-  ~ Lesser General Public License for more details.
-  ~
-  ~ You should have received a copy of the GNU Lesser General Public
-  ~ License along with this software; if not, write to the Free
-  ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
-  ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
-  -->
-
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
-           targetNamespace="urn:jboss:domain:ejb3:1.0"
-           xmlns="urn:jboss:domain:ejb3:1.0"
-           elementFormDefault="qualified"
-           attributeFormDefault="unqualified"
-           version="1.0">
-
-    <!-- The ejb3 subsystem root element -->
-    <xs:element name="subsystem" type="subsystem"/>
-
-    <xs:complexType name="subsystem"/>
-
-
-</xs:schema>

jboss-as-7.2.0.Final/docs/schema/jboss-as-ejb3_1_1.xsd

@@ -1,141 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-  ~ JBoss, Home of Professional Open Source.
-  ~ Copyright 2011, Red Hat, Inc., and individual contributors
-  ~ as indicated by the @author tags. See the copyright.txt file in the
-  ~ distribution for a full listing of individual contributors.
-  ~
-  ~ This is free software; you can redistribute it and/or modify it
-  ~ under the terms of the GNU Lesser General Public License as
-  ~ published by the Free Software Foundation; either version 2.1 of
-  ~ the License, or (at your option) any later version.
-  ~
-  ~ This software is distributed in the hope that it will be useful,
-  ~ but WITHOUT ANY WARRANTY; without even the implied warranty of
-  ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-  ~ Lesser General Public License for more details.
-  ~
-  ~ You should have received a copy of the GNU Lesser General Public
-  ~ License along with this software; if not, write to the Free
-  ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
-  ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
-  -->
-
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
-           targetNamespace="urn:jboss:domain:ejb3:1.1"
-           xmlns="urn:jboss:domain:ejb3:1.1"
-           elementFormDefault="qualified"
-           attributeFormDefault="unqualified"
-           version="1.1">
-
-    <!-- The ejb3 subsystem root element -->
-    <xs:element name="subsystem" type="ejb3-subsystemType"/>
-
-    <xs:complexType name="ejb3-subsystemType">
-        <xs:annotation>
-            <xs:documentation>
-                EJB3 subsystem configurations
-            </xs:documentation>
-        </xs:annotation>
-        <xs:all>
-            <xs:element name="mdb" type="mdbType" minOccurs="0" maxOccurs="1"/>
-            <xs:element name="session-bean" type="session-beanType" minOccurs="0" maxOccurs="1"/>
-            <xs:element name="pools" type="poolsType" minOccurs="0" maxOccurs="1"/>
-            <xs:element name="timer-service" type="timerServiceType" minOccurs="0" maxOccurs="1"/>
-        </xs:all>
-        <xs:attribute name="lite" type="xs:boolean" use="optional"/>
-    </xs:complexType>
-
-    <xs:complexType name="mdbType">
-        <xs:all>
-            <xs:element name="resource-adapter-ref" type="resource-adapter-refType" minOccurs="0" maxOccurs="1"/>
-            <xs:element name="bean-instance-pool-ref" type="bean-instance-pool-refType" minOccurs="0" maxOccurs="1"/>
-        </xs:all>
-    </xs:complexType>
-
-    <xs:complexType name="session-beanType">
-        <xs:all>
-            <xs:element name="stateless" type="stateless-beanType" minOccurs="0" maxOccurs="1"/>
-        </xs:all>
-    </xs:complexType>
-
-    <xs:complexType name="stateless-beanType">
-        <xs:all>
-            <xs:element name="bean-instance-pool-ref" type="bean-instance-pool-refType" minOccurs="0" maxOccurs="1"/>
-        </xs:all>
-    </xs:complexType>
-
-    <xs:complexType name="resource-adapter-refType">
-        <xs:attribute name="resource-adapter-name" type="xs:string" use="required"/>
-    </xs:complexType>
-
-    <xs:complexType name="bean-instance-pool-refType">
-        <xs:attribute name="pool-name" use="required" type="xs:string"/>
-    </xs:complexType>
-
-    <xs:complexType name="poolsType">
-        <xs:all>
-            <xs:element name="bean-instance-pools" type="bean-instance-poolsType" minOccurs="0" maxOccurs="1"/>
-        </xs:all>
-    </xs:complexType>
-
-    <xs:complexType name="bean-instance-poolsType">
-        <xs:choice minOccurs="0" maxOccurs="unbounded">
-            <xs:element name="strict-max-pool" type="strict-max-poolType"/>
-        </xs:choice>
-    </xs:complexType>
-
-    <xs:complexType name="strict-max-poolType">
-        <xs:attribute name="name" type="xs:string" use="required"/>
-        <xs:attribute name="max-pool-size" type="xs:positiveInteger" default="20" use="optional"/>
-        <xs:attribute name="instance-acquisition-timeout" type="xs:positiveInteger" default="5" use="optional"/>
-        <xs:attribute name="instance-acquisition-timeout-unit" type="instance-acquisition-timeout-unitType"
-                      default="MINUTES" use="optional"/>
-    </xs:complexType>
-
-    <xs:simpleType name="instance-acquisition-timeout-unitType">
-        <xs:annotation>
-            <xs:documentation>
-                TimeUnit that are allowed for instance-acquisition-timeout on a pool
-            </xs:documentation>
-        </xs:annotation>
-        <xs:restriction base="xs:token">
-            <xs:enumeration value="HOURS"/>
-            <xs:enumeration value="MINUTES"/>
-            <xs:enumeration value="SECONDS"/>
-            <xs:enumeration value="MILLISECONDS"/>
-        </xs:restriction>
-    </xs:simpleType>
-
-    <xs:complexType name="timerServiceType">
-        <xs:sequence>
-            <xs:element name="thread-pool" type="threadPoolType" minOccurs="0" maxOccurs="1"/>
-            <xs:element name="data-store" type="dataStoreType" minOccurs="0" maxOccurs="1"/>
-        </xs:sequence>
-    </xs:complexType>
-
-    <xs:complexType name="threadPoolType">
-        <xs:attribute name="core-threads" type="xs:int">
-            <xs:annotation>
-                <xs:documentation>
-                    The number of threads that the the thread pool will keep alive. Defaults to 0.
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="max-threads" type="xs:int">
-            <xs:annotation>
-                <xs:documentation>
-                    The maximum number of threads that will be used to run timer service tasks. Defaults to the
-                    number of processes as returned by Runtime.availableProcessors()
-                </xs:documentation>
-            </xs:annotation>
-        </xs:attribute>
-    </xs:complexType>
-
-    <xs:complexType name="dataStoreType">
-        <xs:attribute name="path" type="xs:string" />
-        <xs:attribute name="relative-to" type="xs:string" />
-    </xs:complexType>
-
-</xs:schema>