diff --git a/docs/modules/ROOT/pages/Technical Documentation/Application Development/Class Loaders.adoc b/docs/modules/ROOT/pages/Technical Documentation/Application Development/Class Loaders.adoc
index cc15061d1..d711a64e5 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Application Development/Class Loaders.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Application Development/Class Loaders.adoc
@@ -268,17 +268,17 @@ To disable class loading delegation globally, you can set the system property `f
It's possible to disable class loading delegation directly at the application level. This can be done for both WAR and EAR applications.
[[disabling-classloading-delegation-on-webapps]]
-For *Web* applications, you can include `` element in the `payara-web.xml`/`glassfish-web.xml` deployment descriptors.
+For *Web* applications, you can include `` element in the `payara-web.xml` deployment descriptors.
Here's an example:
[source, xml]
----
-
-
+
+
-
+
----
[[disabling-classloading-delegation-on-ears]]
@@ -300,19 +300,19 @@ Here is an example:
It's possible to configure an extreme isolation level on the class loading delegation for deployed applications. With this extreme isolation behavior, a deployed application can force the server to load only classes and resources from libraries included on the server that belong to *whitelisted packages* defined on its deployment descriptors.
-To configure whitelist packaging you can use the `` element on the `payara-web.xml` / `glassfish-web.xml` (for WAR artifacts) or the `glassfish-application.xml` (for EAR artifacts) deployment descriptors. This element can be included multiple times to whitelist multiple packages.
+To configure whitelist packaging you can use the `` element on the `payara-web.xml` (for WAR artifacts) or the `glassfish-application.xml` (for EAR artifacts) deployment descriptors. This element can be included multiple times to whitelist multiple packages.
Here is an example of whitelisting both the *Google Guava*, *Jackson* and *Faces Config* packages for a WAR application:
[source, xml]
----
-
-
+
+
com.google.guava
com.fasterxml.jackson
com.sun.faces.spi.FacesConfigResourceProvider
-
+
----
The whitelist syntax is simple: Define the name of the package which contains the classes or resources in question. For example writing `com.google` would whitelist all Google libraries included on the server, while writing `com.google.guava` would only whitelist the Google Guava library instead.
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Application Development/Developing Connectors.adoc b/docs/modules/ROOT/pages/Technical Documentation/Application Development/Developing Connectors.adoc
index a4541f203..c599ccf75 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Application Development/Developing Connectors.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Application Development/Developing Connectors.adoc
@@ -218,7 +218,7 @@ To disable connection pooling, set the _Pooling_ attribute to `false`. The defau
[[using-application-scoped-connectors]]
=== Using Application-Scoped Connectors
-You can define an application-scoped connector or other resource for an enterprise application, web module, EJB module, connector module, or application client module by supplying a `payara-resources.xml` or `glassfish-resources.xml` deployment descriptor file. For details, see "xref:Technical Documentation/Payara Server Documentation/Application Deployment/Deploying Applications.adoc#application-scoped-resources[Application-Scoped Resources]" in the Payara Server Application Deployment section.
+You can define an application-scoped connector or other resource for an enterprise application, web module, EJB module, connector module, or application client module by supplying a `payara-resources.xml` deployment descriptor file. For details, see "xref:Technical Documentation/Payara Server Documentation/Application Deployment/Deploying Applications.adoc#application-scoped-resources[Application-Scoped Resources]" in the Payara Server Application Deployment section.
[[inbound-communication-support]]
== Inbound Communication Support
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Application Development/Developing SOAP Webservices.adoc b/docs/modules/ROOT/pages/Technical Documentation/Application Development/Developing SOAP Webservices.adoc
index eae5487cb..37e8dbcfd 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Application Development/Developing SOAP Webservices.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Application Development/Developing SOAP Webservices.adoc
@@ -23,7 +23,7 @@ You deploy a web service endpoint to Payara Server just as you would any servlet
IMPORTANT: For complex services with dependent classes, user specified WSDL files, or other advanced features, auto-deployment of an annotated file is not sufficient.
-The Payara Server deployment descriptor files `glassfish-web.xml`/`payara-web.xml` and `glassfish-ejb-jar.xml` provide optional web service enhancements in the `webservice-endpoint` and `webservice-description` elements, including a `debugging-enabled` sub-element that enables the creation of a test page.
+The Payara Server deployment descriptor files `payara-web.xml` and `glassfish-ejb-jar.xml` provide optional web service enhancements in the `webservice-endpoint` and `webservice-description` elements, including a `debugging-enabled` sub-element that enables the creation of a test page.
The test page feature is enabled by default and described in xref:#the-web-service-uri-wsdl-file-and-test-page[The Web Service URI, WSDL File, and Test Page].
@@ -38,7 +38,7 @@ http://${host}:${port}/${context-root}/${servlet-mapping-url-pattern}
----
The context-root is defined in the `application.xml` or `web.xml` file, and can be overridden in the `glassfish-application.xml` or
-`glassfish-web.xml`/`payara-web.xml` file. The servlet-mapping-url-pattern is defined in the `web.xml` file.
+`payara-web.xml` file. The servlet-mapping-url-pattern is defined in the `web.xml` file.
In the following example, the context-root is `my-ws` and the servlet-mapping-url-pattern is `/simple` for local deployment in the default port:
@@ -68,7 +68,7 @@ You can also test a service using the Administration Console. Open the _Web Serv
WARNING: The tester webpage works only for WS-I compliant web services. This means that the tester servlet does not work for services with WSDL files that use RPC/encoded binding.
The Web Service tester application is enabled by default. You can disable the test page for a web service by setting the value of the
-`debugging-enabled` element in the `glassfish-web.xml`/`payara-web.xml` and `glassfish-ejb-jar.xml` deployment descriptor to `false`.
+`debugging-enabled` element in the `payara-web.xml` and `glassfish-ejb-jar.xml` deployment descriptor to `false`.
[[the-databinding-provider]]
== The Databinding Provider
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Application Development/Developing Web Applications.adoc b/docs/modules/ROOT/pages/Technical Documentation/Application Development/Developing Web Applications.adoc
index 959a22548..d930b1bf1 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Application Development/Developing Web Applications.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Application Development/Developing Web Applications.adoc
@@ -22,7 +22,7 @@ For example, if your servlet returns a stock quote that updates every *5 minutes
Whether to cache results and how to cache them depends on the data involved. For example, it makes no sense to cache the results of a quiz submission, because the input to the servlet is different each time. However, it makes sense to cache a high level report showing demographic data taken from quiz results that is updated once an hour.
-To define how a web application handles response caching, you'll have to modify specific attributes in the `glassfish-web.xml` or `payara-web.xml` deployment descriptor file.
+To define how a web application handles response caching, you'll have to modify specific attributes in the `payara-web.xml` deployment descriptor file.
WARNING: A servlet that uses caching is not portable.
@@ -74,7 +74,7 @@ If you enable caching but do not provide any special configuration for a servlet
[[caching-example]]
==== Caching Example
-Here is an example cache element in the `glassfish-web.xml`/`payara-web.xml` file:
+Here is an example cache element in the `payara-web.xml` file:
[source,xml]
----
@@ -117,14 +117,14 @@ Here is an example cache element in the `glassfish-web.xml`/`payara-web.xml` fil
----
-For more information about the `glassfish-web.xml`/`payara-web.xml` caching settings, see "xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache[cache]" in the Payara Server Application Deployment section.
+For more information about the `payara-web.xml` caching settings, see "xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache[cache]" in the Payara Server Application Deployment section.
[[the-cachekeygenerator-interface]]
==== The CacheKeyGenerator Interface
The built-in default `CacheHelper` implementation allows web applications to customize the key generation. An application component (in a servlet or JSP) can set up a custom `CacheKeyGenerator` implementation as an attribute in the `ServletContext`.
-The name of the context attribute is configurable as the `value` of the `cacheKeyGeneratorAttrName` property in the `default-helper` element of the `glassfish-web.xml`/`payara-web.xml` deployment descriptor.
+The name of the context attribute is configurable as the `value` of the `cacheKeyGeneratorAttrName` property in the `default-helper` element of the `payara-web.xml` deployment descriptor.
For more information, see "xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#default-helper[default-helper]" in the Payara Server Application Deployment section.
@@ -358,7 +358,7 @@ This section describes how to create and manage HTTP sessions that allows users
[[http-sessions-cookies-and-url-rewriting]]
==== HTTP Sessions, Cookies, and URL Rewriting
-To configure whether and how HTTP sessions use cookies and URL rewriting, edit the `session-properties` and `cookie-properties elements in the `glassfish-web.xml` or `payara-web.xml` file for an individual web application. For more details about the properties you can configure, see "xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#session-properties[session-properties]" "xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cookie-properties[cookie-properties]" and in the Payara Server Application Deployment section.
+To configure whether and how HTTP sessions use cookies and URL rewriting, edit the `session-properties` and `cookie-properties elements in the `payara-web.xml` file for an individual web application. For more details about the properties you can configure, see "xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#session-properties[session-properties]" "xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cookie-properties[cookie-properties]" and in the Payara Server Application Deployment section.
For information about configuring default session properties for the
entire web container, see xref:#using-the-default-web.xml-file[Using the `default-web.xml` File].
@@ -377,7 +377,7 @@ The default for the `--keepstate` is `false`. This option is supported only on t
NOTE: This option is not supported and ignored for other targets (clusters and deployment groups included).
-For web applications, this feature is applicable only if in the `payara-web.xml` / `glassfish-web.xml` deployment descriptor files when the `persistence-type` attribute of the `session-manager` element is set to `file`.
+For web applications, this feature is applicable only if in the `payara-web.xml` deployment descriptor files when the `persistence-type` attribute of the `session-manager` element is set to `file`.
If any active web session fails to be preserved or restored, none of the sessions will be available when the redeployment is complete. However, the redeployment continues and a warning is logged.
@@ -454,7 +454,7 @@ correctly rolled back or committed.
A session manager automatically creates new session objects whenever a new session starts. In some circumstances, clients do not join the session, for example, if the session manager uses cookies and the client does not accept cookies.
-The Payara Platform offers these session management options, determined by the `session-manager` element's `persistence-type` attribute in the `glassfish-web.xml`/`payara-web.xml` file:
+The Payara Platform offers these session management options, determined by the `session-manager` element's `persistence-type` attribute in the `payara-web.xml` file:
* xref:#the-memory-persistence-type[The `memory` Persistence Type]
* xref:#the-file-persistence-type[The `file` Persistence Type], which uses a file to store session data
@@ -469,7 +469,7 @@ For more information, see "xref:Technical Documentation/Payara Server Documentat
This persistence type is not designed for a production environment that requires session persistence as it provides no actual session persistence. However, you can configure it so that the session state in memory is written to the file system prior to server shutdown.
-To specify the `memory` persistence type for a specific web application, edit the `glassfish-web.xml` or `payara-web.xml` file as in the following example. The `persistence-type` attribute is optional, but must be set to `memory` if included. This overrides the web container availability settings for the web application.
+To specify the `memory` persistence type for a specific web application, edit the `payara-web.xml` file as in the following example. The `persistence-type` attribute is optional, but must be set to `memory` if included. This overrides the web container availability settings for the web application.
[source,xml]
----
@@ -498,7 +498,7 @@ The store also provides passivation and activation of the session state to help
NOTE: Make sure the `delete` option is set in the `server.policy` file, or expired file-based sessions might not be deleted properly. For more information about `server.policy`, see xref:Technical Documentation/Application Development/Securing Applications.adoc#the-server.policy-file[The`server.policy` File].
-To specify the `file` persistence type for a specific web application, edit the `glassfish-web.xml` or `payara-web.xml` file as in the following example. Note that `persistence-type` must be set to `file`. This overrides the web container availability settings for the web application.
+To specify the `file` persistence type for a specific web application, edit the `payara-web.xml` file as in the following example. Note that `persistence-type` must be set to `file`. This overrides the web container availability settings for the web application.
[source,xml]
----
@@ -668,8 +668,8 @@ This section explains how the server runtime determines the character encoding f
When processing a servlet request, the server uses the following order of precedence, first to last, to determine the request character encoding:
* The `getCharacterEncoding` method.
-* A hidden field in the form, specified by the `form-hint-field` attribute of the `parameter-encoding` element in the `glassfish-web.xml` or `payara-web.xml` deployment descriptor
-* The `default-charset` attribute of the `parameter-encoding` element in the `glassfish-web.xml` or `payara-web.xml` deployment descriptor
+* A hidden field in the form, specified by the `form-hint-field` attribute of the `parameter-encoding` element in the `payara-web.xml` deployment descriptor
+* The `default-charset` attribute of the `parameter-encoding` element in the `payara-web.xml` deployment descriptor
* The default encoding, which is `ISO-8859-1`
For details about the `parameter-encoding` element, see "xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#parameter-encoding[parameter-encoding]" in the Payara Server Application Deployment section.
@@ -768,7 +768,7 @@ A listener class for a web module must implement one the following interfaces:
* `org.apache.catalina.LifecycleListener`
* `org.apache.catalina.InstanceListener`
-In the `glassfish-web.xml`/`payara-web.xml` deployment descriptor, valve and listener properties for a web module look like this:
+In the `payara-web.xml` deployment descriptor, valve and listener properties for a web module look like this:
[source,xml]
----
@@ -816,7 +816,7 @@ NOTE: Not all context definitions are supported by the Payara Platform.
[[enabling-webdav]]
==== Enabling WebDav
-To enable WebDav in Payara Server, you edit the `web.xml` and `glassfish-web.xml`/`payara-web.xml` files as follows.
+To enable WebDav in Payara Server, you edit the `web.xml` and `payara-web.xml` files as follows.
First, enable the WebDav servlet in your `web.xml` file:
@@ -875,7 +875,7 @@ To protect the WebDav servlet so other users can't modify it, you must add a sec
----
-Then define a security role mapping in your `glassfish-web.xml` or `payara-web.xml` deployment descriptor:
+Then define a security role mapping in your `payara-web.xml` deployment descriptor:
[source,xml]
----
@@ -1024,9 +1024,9 @@ An alternate document root (`docroot`) allows a web application to serve request
To specify an alternate document root for a web application or a virtual server, use the `alternatedocroot_n` property, where n is a positive integer greater than zero that allows specifying more than one.
-This property can be a sub-element of a `glassfish-web-app`/`payara-web-app` element in the `glassfish-web.xml`/`payara-web.xml` file or a virtual server property.
+This property can be a sub-element of a `payara-web-app` element in the `payara-web.xml` file or a virtual server property.
-For more information about these elements, see "xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[glassfish-web-app]" in the Payara Server Application Deployment section.
+For more information about this element, see "xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[payara-web-app]" in the Payara Server Application Deployment section.
A virtual server's alternate document roots are considered only if a request does not map to any of the web modules deployed on that virtual server. A web module's alternate document roots are considered only once a request has been mapped to that web module.
@@ -1036,7 +1036,7 @@ If a request matches an alternate document root's URI pattern, it is mapped to t
* Longest path match
* Extension match
-For example, the following properties specify three `glassfish-web.xml`/ `payara-web.xml` document root configurations. The URI pattern of the first alternate document root uses an exact match, whereas the URI patterns of the second and third alternate document roots use extension and longest path prefix matches, respectively:
+For example, the following properties specify three `payara-web.xml` document root configurations. The URI pattern of the first alternate document root uses an exact match, whereas the URI patterns of the second and third alternate document roots use extension and longest path prefix matches, respectively:
[source,xml]
----
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Application Development/Securing Applications.adoc b/docs/modules/ROOT/pages/Technical Documentation/Application Development/Securing Applications.adoc
index 01bf7c57f..2d07e6fd7 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Application Development/Securing Applications.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Application Development/Securing Applications.adoc
@@ -77,7 +77,7 @@ These role names are scoped to the EJB XML deployment descriptors (`ejb-jar.xml`
For an individually deployed web or EJB module, you define roles using `@DeclareRoles` annotations or `role-name` elements in the Jakarta EE deployment descriptor files `web.xml` or `ejb-jar.xml`.
-To map roles to principals and groups, define matching `security-role-mapping` elements in the `glassfish-application.xml`, `glassfish-ejb-jar.xml`, or `glassfish-web.xml`/`payara-web.xml` file for each `role-name` used by the application.
+To map roles to principals and groups, define matching `security-role-mapping` elements in the `glassfish-application.xml`, `glassfish-ejb-jar.xml`, or `payara-web.xml` file for each `role-name` used by the application.
By default, group principal names are mapped to roles of the same name.
Accordingly, the *Default Principal To Role Mapping* setting is enabled by default on the _Security_ page of the Payara Server Administration Console.
@@ -89,7 +89,7 @@ TIP: This default role mapping definition is in effect if you do not define your
Component level security encompasses web components and EJB components.
-A secure web container authenticates users and authorizes access to a servlet or JSP by using the security policy laid out in the servlet XML deployment descriptors (`web.xml`, `glassfish-web.xml` and `payara-web.xml` files).
+A secure web container authenticates users and authorizes access to a servlet or JSP by using the security policy laid out in the servlet XML deployment descriptors (`web.xml`, `payara-web.xml` files).
The EJB container is responsible for authorizing access to a bean method by using the security policy laid out in the EJB XML deployment descriptors (`ejb-jar.xml` and `glassfish-ejb-jar.xml` files).
@@ -117,11 +117,11 @@ Therefore, the *Default Principal To Role Mapping* setting is enabled by default
For applications, you define roles in `@DeclareRoles` annotations or the Jakarta EE deployment descriptor file `application.xml`. You define the corresponding role mappings in the Payara Server deployment descriptor file `glassfish-application.xml`.
-For individually deployed web or EJB modules, you define roles in `@DeclareRoles` annotations or the Jakarta EE deployment descriptor files `web.xml` or `ejb-jar.xml`. You define the corresponding role mappings in the Payara Server deployment descriptor files `glassfish-web.xml`/`payara-web.xml` or `glassfish-ejb-jar.xml`.
+For individually deployed web or EJB modules, you define roles in `@DeclareRoles` annotations or the Jakarta EE deployment descriptor files `web.xml` or `ejb-jar.xml`. You define the corresponding role mappings in the Payara Server deployment descriptor files `payara-web.xml` or `glassfish-ejb-jar.xml`.
For more information regarding Jakarta EE deployment descriptors, see the Jakarta EE Specification. For more information regarding Payara Server deployment descriptors, see "xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#elements-of-the-payara-platform-deployment-descriptors[Elements of the Payara Server Deployment Descriptors]" in the Application Deployment section.
-Each `security-role-mapping` element in the `glassfish-application.xml`, `glassfish-web.xml`/`payara-web.xml`, or `glassfish-ejb-jar.xml` file maps a role name permitted by the application or module to principals and groups.
+Each `security-role-mapping` element in the `glassfish-application.xml`, `payara-web.xml`, or `glassfish-ejb-jar.xml` file maps a role name permitted by the application or module to principals and groups.
For example, a `payara-web.xml` file for an individually deployed web module might contain the following:
@@ -1537,7 +1537,7 @@ You can configure a SAM in one of these ways:
After you install and configure the SAM, you can bind it for use by the container on behalf of one or more of your applications. You have two options in how you bind the SAM, depending on whether you are willing to repackage and redeploy your application:
-* If you are willing to repackage and redeploy, you can bind the SAM using the `glassfish-web.xml` or `payara-web.xml` deployment descriptor file. Set the value of the `httpservlet-security-provider` attribute of the `glassfish-web-app`/`payara-web-app` element to the SAM's configured provider ID, for example, `MySAM`. This option leverages the native `AuthConfigProvider` implementation that ships with Payara Server.
+* If you are willing to repackage and redeploy, you can bind the SAM using the `payara-web.xml` deployment descriptor file. Set the value of the `httpservlet-security-provider` attribute of the `payara-web-app` element to the SAM's configured provider ID, for example, `MySAM`. This option leverages the native `AuthConfigProvider` implementation that ships with Payara Server.
* Another approach is to develop your own `AuthConfigProvider` and register it with the server's `AuthConfigFactory` for use on behalf of your applications. For example, a simple `AuthConfigProvider` can obtain, through its initialization properties, the classname of a SAM to configure on behalf of the applications for which the provider is registered.
@@ -1920,13 +1920,13 @@ After pinging this Servlet, and requesting another Servlet over HTTPS that's pro
[source, xml]
----
-
+
g1
g1
CN=u1
-
+
----
//TODO - Get an updated sample
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Application Development/Using Jakarta Faces Technology.adoc b/docs/modules/ROOT/pages/Technical Documentation/Application Development/Using Jakarta Faces Technology.adoc
index 0689e1444..4277c46b1 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Application Development/Using Jakarta Faces Technology.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Application Development/Using Jakarta Faces Technology.adoc
@@ -82,7 +82,7 @@ As a special case of how the classloader hierarchy can be modified (see xref:Tec
This feature may be useful to switch to a different implementation than the default one included with the server.
-To configure this feature, you need to indicate within the `payara-web.xml` / `glassfish-web.xml` deployment descriptor that the server should use a bundled Jakarta Faces implementation as follows:
+To configure this feature, you need to indicate within the `payara-web.xml` deployment descriptor that the server should use a bundled Jakarta Faces implementation as follows:
[source, xml]
----
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Application Development/Using the Java Naming and Directory Interface.adoc b/docs/modules/ROOT/pages/Technical Documentation/Application Development/Using the Java Naming and Directory Interface.adoc
index 88b79a8fd..c3b773356 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Application Development/Using the Java Naming and Directory Interface.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Application Development/Using the Java Naming and Directory Interface.adoc
@@ -132,7 +132,7 @@ For Jakarta EE components, the code still performs a `java:comp/env` lookup on a
For example, suppose a servlet looks up an EJB reference using `java:comp/env/ejb/Foo`, and the target EJB component has a global JNDI name of `a/b/Foo`.
-The `ejb-ref` element in `glassfish-web.xml` or `payara-web.xml` looks like this:
+The `ejb-ref` element in `payara-web.xml` looks like this:
[source,xml]
----
@@ -208,7 +208,7 @@ Payara Server provides built-in factories for the following types of custom reso
* Java Primitives and String objects
* URLs
-It is possible to create custom resources by using a `payara-resources.xml` or `glassfish-resources.xml` deployment descriptor. To this effect, several `glassfish-resources.xml` template files for these built-in factories and a `README` file are available at `as-install/lib/install/templates/resources/custom/`.
+It is possible to create custom resources by using a `payara-resources.xml` deployment descriptor. To this effect, several `payara-resources.xml` template files for these built-in factories and a `README` file are available at `as-install/lib/install/templates/resources/custom/`.
[[javabeanfactory]]
==== *JavaBeanFactory*
@@ -284,7 +284,7 @@ For the third constructor, define a property named `spec` and assign it the valu
[[using-application-scoped-resources]]
=== Using Application-Scoped Resources
-You can define an application-scoped JNDI resource for an enterprise application, web module, EJB module, connector module, or application client module by supplying a `glassfish-resources.xml` or `payara-resources.xml` deployment descriptor file.
+You can define an application-scoped JNDI resource for an enterprise application, web module, EJB module, connector module, or application client module by supplying a `payara-resources.xml` deployment descriptor file.
For details, see "xref:Technical Documentation/Payara Server Documentation/Application Deployment/Deploying Applications.adoc#application-scoped-resources[Application-Scoped Resources]" in the Application Deployment section.
@@ -308,7 +308,7 @@ JNDI names for EJB components must be unique. For example, appending the applica
+
In this case, `mycompany.pkging.pkgingEJB.MyEJB` would be the JNDI name for an EJB in the module `pkgingEJB.jar`, which is packaged in the `pkging.ear` application.
-These elements are part of the `glassfish-web.xml`/`payara-web.xml`, `glassfish-application-client.xml`, `glassfish-ejb-jar.xml`, and `glassfish-application.xml` deployment descriptor files.
+These elements are part of the `payara-web.xml`, `glassfish-application-client.xml`, `glassfish-ejb-jar.xml`, and `glassfish-application.xml` deployment descriptor files.
For more information about how these elements behave in each of the deployment descriptor files, see "xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#elements-of-the-payara-platform-deployment-descriptors[Elements of the Payara Server Deployment Descriptors]" in the Payara Server Application Deployment section.
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Ecosystem/Connector Suites/Arquillian Containers/Payara Server Managed.adoc b/docs/modules/ROOT/pages/Technical Documentation/Ecosystem/Connector Suites/Arquillian Containers/Payara Server Managed.adoc
index 2f5ba6562..f9602930f 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Ecosystem/Connector Suites/Arquillian Containers/Payara Server Managed.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Ecosystem/Connector Suites/Arquillian Containers/Payara Server Managed.adoc
@@ -140,7 +140,7 @@ If the component is packaged as a regular archive, do not set this option.
|
|===
-The context root that will be used to run the tests is also retrieved automatically from the DAS server. If the deployed application does have a `sun-web.xml`, `glassfish-web.xml` or `payara-web.xml` deployment descriptor, the container will use the name of your deployment without the extension as context root. +
+The context root that will be used to run the tests is also retrieved automatically from the DAS server. If the deployed application does have a `payara-web.xml` deployment descriptor, the container will use the name of your deployment without the extension as context root. +
The same rule is applied for enterprise applications if there is no `application.xml` file. The JAR test-deployments are treated as a web application.
[[examples]]
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Ecosystem/Connector Suites/Arquillian Containers/Payara Server Remote.adoc b/docs/modules/ROOT/pages/Technical Documentation/Ecosystem/Connector Suites/Arquillian Containers/Payara Server Remote.adoc
index 2fd260030..5f76fcd9c 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Ecosystem/Connector Suites/Arquillian Containers/Payara Server Remote.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Ecosystem/Connector Suites/Arquillian Containers/Payara Server Remote.adoc
@@ -110,7 +110,7 @@ If the component is packaged as a regular archive, do not set this option.
|
|===
-The context root that will be used to run the tests is also retrieved automatically from the DAS server. If the deployed application does have a `sun-web.xml`, `glassfish-web.xml` or `payara-web.xml` deployment descriptor, the container will use the name of your deployment without the extension as context root. +
+The context root that will be used to run the tests is also retrieved automatically from the DAS server. If the deployed application does have a `payara-web.xml` deployment descriptor, the container will use the name of your deployment without the extension as context root. +
The same rule is applied for enterprise applications if there is no `application.xml` file. The JAR test-deployments are treated as a web application.
[[examples]]
diff --git a/docs/modules/ROOT/pages/Technical Documentation/MicroProfile/JWT.adoc b/docs/modules/ROOT/pages/Technical Documentation/MicroProfile/JWT.adoc
index 7f9f699c8..9ada880e9 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/MicroProfile/JWT.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/MicroProfile/JWT.adoc
@@ -303,6 +303,6 @@ With `base` being the context where the application is deployed, e.g. `http://ex
[[switch-off-rolesallowed-support]]
== Switching off @RolesAllowed Support
-The out-of-the-box support of `@RolesAllowed` for Jakarta REST Services resources can be switched off by setting the `` tag in `WEB-INF/glassfish-web.xml` to `false`.
+The out-of-the-box support of `@RolesAllowed` for Jakarta REST Services resources can be switched off by setting the `` tag in `WEB-INF/payara-web.xml` to `false`.
For more information see the documentation for the xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#jaxrs-roles-allowed-enabled[jaxrs-roles-allowed-enabled] element.
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Payara Micro Documentation/Payara Micro Configuration and Management/Micro Management/Configuring An Instance.adoc b/docs/modules/ROOT/pages/Technical Documentation/Payara Micro Documentation/Payara Micro Configuration and Management/Micro Management/Configuring An Instance.adoc
index e5ec07da3..6ca0314ea 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Payara Micro Documentation/Payara Micro Configuration and Management/Micro Management/Configuring An Instance.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Payara Micro Documentation/Payara Micro Configuration and Management/Micro Management/Configuring An Instance.adoc
@@ -198,7 +198,7 @@ http://localhost:9080/test
--------------------------
Currently, this is *always* the case; including when a context root is specified
-in a `glassfish-web.xml` deployment descriptor.
+in a `payara-web.xml` deployment descriptor.
If the WAR file is renamed to `ROOT.war` and packaged as an Uber JAR, it will
be deployed to the root context:
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Application Deployment/Deploying Applications.adoc b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Application Deployment/Deploying Applications.adoc
index d45c3bb47..185fe512d 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Application Deployment/Deploying Applications.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Application Deployment/Deploying Applications.adoc
@@ -479,7 +479,7 @@ This listing shows the structure of the deployment plan JAR file for an EAR file
----
$ jar -tvf mydeployplan.jar
420 Thu Mar 13 15:37:48 PST 2003 glassfish-application.xml
-370 Thu Mar 13 15:37:48 PST 2003 RosterClient.war.glassfish-web.xml
+370 Thu Mar 13 15:37:48 PST 2003 RosterClient.war.payara-web.xml
418 Thu Mar 13 15:37:48 PST 2003 roster-ac.jar.glassfish-application-client.xml
1281 Thu Mar 13 15:37:48 PST 2003 roster-ejb.jar.glassfish-ejb-jar.xml
2317 Thu Mar 13 15:37:48 PST 2003 team-ejb.jar.glassfish-ejb-jar.xml
@@ -879,7 +879,7 @@ The domain administration server (DAS) in Payara Server supports the deployment
+
IMPORTANT: Deploying multiple applications using the same context root within a single instance produces an error.
-* *Data Source*. If a web application accesses a `DataSource` that is not specified in a `resource-ref` in `glassfish-web.xml` or `payara-web.xml`, or there is no `glassfish-web.xml` or `payara-web.xml` files, the `resource-ref-name` defined in `web.xml` is used.
+* *Data Source*. If a web application accesses a `DataSource` that is not specified in a `resource-ref` in `payara-web.xml`, or there is no `payara-web.xml` files, the `resource-ref-name` defined in `web.xml` is used.
+
A warning message is logged, recording the JNDI name that was used to look up the resource.
@@ -895,17 +895,17 @@ For information about HTTP session persistence, see the xref:Technical Documenta
* *JSP Precompilation*. You can precompile JSP files during deployment by checking the appropriate box in the Administration Console, or by using the `--precompilejsp` option of the `deploy` subcommand.
+
-You can keep the generated source for JSP files by adding the `keepgenerated` flag to the `jsp-config` element in `glassfish-web.xml` or `payara-web.xml`.
+You can keep the generated source for JSP files by adding the `keepgenerated` flag to the `jsp-config` element in `payara-web.xml`.
+
For example:
+
[source,xml]
----
-
+
-
+
----
+
If you include this property when you deploy the WAR file, the generated source is kept in `domain-dir/generated/jsp/app-name/module-name` for an application, or `domain-dir/generated/jsp/module-name` for an individually-deployed web module.
@@ -969,7 +969,7 @@ The following topics are addressed here:
[[to-deploy-and-configure-a-stand-alone-connector-module]]
=== To Deploy and Configure a Stand-Alone Connector Module
-As an alternative to Step 3 through Step 6, you can define application-scoped resources in the `glassfish-resources.xml` or `payara-resources.xml` deployment descriptor.
+As an alternative to Step 3 through Step 6, you can define application-scoped resources in the `payara-resources.xml` deployment descriptor.
For more information, see xref:Technical Documentation/Payara Server Documentation/Application Deployment/Deploying Applications.adoc#application-scoped-resources[Application-Scoped Resources].
@@ -1144,7 +1144,7 @@ NOTE: If the `--failurefatal` option of `create-lifecycle-module` is set to `tru
== Web Service Deployment Guidelines
NOTE: If you installed the Web Profile, web services are not supported unless the optional Metro Web Services Stack add-on component is downloaded. +
-Without the Metro add-on component, a servlet or EJB component cannot be a web service endpoint, and the `glassfish-web.xml`/`payara-web.xml` and `glassfish-ejb-jar.xml` elements related to web services are ignored.
+Without the Metro add-on component, a servlet or EJB component cannot be a web service endpoint, and the `payara-web.xml` and `glassfish-ejb-jar.xml` elements related to web services are ignored.
The following guidelines apply when deploying a web service in Payara Server:
@@ -1152,7 +1152,7 @@ The following guidelines apply when deploying a web service in Payara Server:
+
If the deployed application or module has a web service endpoint, the endpoint is detected automatically during deployment.
+
-The Payara Server specific deployment descriptor files, `glassfish-web.xml`, `payara-web.xml` and `glassfish-ejb-jar.xml`, provide optional web service enhancements in their xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-endpoint[`webservice-endpoint`] and xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-description[`webservice-description`] elements.
+The Payara Server specific deployment descriptor files, `payara-web.xml` and `glassfish-ejb-jar.xml`, provide optional web service enhancements in their xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-endpoint[`webservice-endpoint`] and xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-description[`webservice-description`] elements.
* *Web Service Management*. Web service management is fully supported in the Administration Console. After the application or module is deployed, click the Web Service component. The table in the right frame lists deployed web service endpoints.
@@ -1187,7 +1187,7 @@ To enable transparent pool reconfiguration, set the `dynamic-reconfiguration-wai
In-progress connection requests must complete before this timeout expires, or they must be retried. New connection requests wait for this timeout to expire before acquiring connections to the reconfigured pool.
If this property exists and has a positive value, it is enabled.
-You can set this property in the `glassfish-resources.xml` or `payara-resources.xml` file. For more information, see the property descriptions under xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#jdbc-connection-pool[`jdbc-connection-pool`].
+You can set this property in the `payara-resources.xml` file. For more information, see the property descriptions under xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#jdbc-connection-pool[`jdbc-connection-pool`].
For JDBC connection pools that are not application-scoped, use the `set` subcommand to set this property. For example, to configure `mypool` on `myserver`, type the following all on one line:
@@ -1220,13 +1220,13 @@ The following resource types can be application-scoped:
* Admin object resources
* Jakarta resources
-*Deployment Descriptor*: An application-scoped resource is defined in the `glassfish-resources.xml` or `payara-resources.xml` deployment descriptor file.
+*Deployment Descriptor*: An application-scoped resource is defined in the `payara-resources.xml` deployment descriptor file.
This file is placed in the `META-INF` directory of the module or application archive.
For web applications or modules, this file is placed in the `WEB-INF` directory.
-If any submodule archives of an enterprise application archive have their own `glassfish-resources.xml` or `payara-resources.xml` files, the resource definitions are scoped to those modules only.
+If any submodule archives of an enterprise application archive have their own `payara-resources.xml` files, the resource definitions are scoped to those modules only.
-For more information about the `glassfish-resources.xml` and `payara-resources.xml` file, see xref:Technical Documentation/Payara Server Documentation/Application Deployment/Deployment Descriptor Files.adoc#the-glassfish-resources.xml-file[Payara Server Deployment Descriptor Files] and xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc[Elements of the Payara Server Deployment Descriptors].
+For more information about the `payara-resources.xml` file, see xref:Technical Documentation/Payara Server Documentation/Application Deployment/Deployment Descriptor Files.adoc#the-glassfish-resources.xml-file[Payara Server Deployment Descriptor Files] and xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc[Elements of the Payara Server Deployment Descriptors].
*Naming*: Application-scoped resource JNDI names begin with `java:app` or `java:module`. If one of these prefixes is not specified in the JNDI name, it is added. For example, application-scoped databases have JNDI names in the following format: `java:app/jdbc/DataSourceName` or `java:module/jdbc/DataSourceName`.
@@ -1234,7 +1234,7 @@ For more information about the `glassfish-resources.xml` and `payara-resources.x
Definitions with the same resource name and type but different attributes or properties are conflicts and cause deployment failure. When an application or module tries to look up a scoped resource that does not belong to it, a naming exception is thrown.
-*Redeployment*: When an application or module is un-deployed, its scoped resources are deleted. During redeployment, resources are destroyed and recreated based on changes in the `glassfish-resources.xml` or `payara-resources.xml` file.
+*Redeployment*: When an application or module is un-deployed, its scoped resources are deleted. During redeployment, resources are destroyed and recreated based on changes in the `payara-resources.xml` file.
To preserve old resource definitions during redeployment, use the `preserveAppScopedResources` property of the `redeploy` (or `deploy --force=true`) subcommand. For example:
@@ -1255,9 +1255,9 @@ For more information, see xref:Technical Documentation/Payara Server Documentati
*Restrictions*. Use of application-scoped resources is subject to the following restrictions:
-* `resource-adapter-config` and `connector-work-security-map` — These can only be specified in the `glassfish-resources.xml` or `payara-resources.xml` file of the corresponding connector module.
+* `resource-adapter-config` and `connector-work-security-map` — These can only be specified in the `payara-resources.xml` file of the corresponding connector module.
+
-In an enterprise application, the `resource-adapter-config` or `connector-work-security-map` for an embedded connector module must be specified in the `glassfish-resources.xml` or `payara-resources.xml` file of the connector module.
+In an enterprise application, the `resource-adapter-config` or `connector-work-security-map` for an embedded connector module must be specified in the `payara-resources.xml` file of the connector module.
+
You cannot specify a `resource-adapter-config` or `connector-work-security-map` in an application for a connector module that is not part of the application.
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Application Deployment/Deployment Descriptor Files.adoc b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Application Deployment/Deployment Descriptor Files.adoc
index 8d973754d..9708df6ed 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Application Deployment/Deployment Descriptor Files.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Application Deployment/Deployment Descriptor Files.adoc
@@ -30,11 +30,8 @@ The following table lists the Payara Platform deployment descriptors and their D
| `glassfish-application_6_0-1.dtd`
| Configures an entire Jakarta EE application (EAR file).
-|
-`glassfish-web.xml`
-
-`payara-web.xml`
-| `glassfish-web-app_3_0-1.dtd`
+|`payara-web.xml`
+|`payara-web-app_4.dtd`
| Configures a web application (WAR file).
| `glassfish-ejb-jar.xml`
@@ -45,11 +42,8 @@ The following table lists the Payara Platform deployment descriptors and their D
| `glassfish-application-client_6_0-1.dtd`
| Configures an Application Client Container (ACC) client (JAR file).
-|
-`glassfish-resources.xml`
-
-`payara-resources.xml`
-| `glassfish-resources_1_5.dtd`
+|`payara-resources.xml`
+| `payara-resources_1_8.dtd`
| Configures application-scoped resources.
| `sun-acc.xml`
@@ -156,18 +150,16 @@ GlassFish Application Server 3.1 Java EE Application 6.0//EN"
----
-[[the-glassfish-web.xml-file]]
-== The `glassfish-web.xml` and `payara-web.xml` Files
-
-The `glassfish-web.xml` file configures a web application (WAR file). It is an original Eclipse GlassFish deployment descriptor.
+[[the-payara-web.xml-file]]
+== The `payara-web.xml` File
-The `payara-web.xml` is a matching Payara Platform variant which is recommended to be used whenever possible.
+The `payara-web.xml` file configures a web application (WAR file).
-Their element hierarchy is as follows:
+Its element hierarchy is as follows:
[source,text]
----
-glassfish-web-app
+payara-web-app
. context-root
. security-role-mapping
. . role-name
@@ -645,12 +637,10 @@ glassfish-application-client
----
-[[the-glassfish-resources.xml-file]]
-== The `glassfish-resources.xml` and `payara-resources.xml` Files
-
-The `glassfish-resources.xml` file configures application-scoped resources. It is an original Eclipse GlassFish deployment descriptor.
+[[the-payara-resources.xml-file]]
+== The `payara-resources.xml` File
-The `payara-resources.xml` is a matching Payara Platform variant that supports additional elements.
+The `payara-resources.xml` file configures application-scoped resources.
Their element hierarchy is as follows:
@@ -953,201 +943,3 @@ alter table PLAYEREJBTEAMEJB add constraint FK_PLAYERS foreign key (TEAMEJB_TEAM
----
-
-//TODO - Assess whether such support should be properly removed in the future
-
-[[weblogic-server-deployment-descriptor-support-in-payara-server]]
-== WebLogic Server Deployment Descriptor Support in Payara Server
-
-Payara Server offers limited support for the `weblogic-application.xml`, `weblogic.xml`, and `weblogic-webservices.xml` deployment descriptor files.
-
-The only element in `weblogic-application.xml` that Payara Server supports is `security`. The equivalent element in the `glassfish-application.xml` file is `security-role-mapping`.
-
-The elements of `weblogic.xml` that Payara Server supports are explained in the following table.
-
-.`weblogic.xml` Support in Payara Server
-
-[cols="2,6",options="header"]
-|===
-| *`weblogic.xml` Element Name* | *Payara Server Support*
-
-| `role-name` under `security-role-assignment`
-| `role-name` under `security-role-mapping` `glassfish-web.xml` equivalent
-
-| `principal-name` under `security-role-assignment`
-| `principal-name` under `security-role-mapping` `glassfish-web.xml` equivalent
-
-| `resource-description`
-| `resource-ref` `glassfish-web.xml` equivalent, but `resource-link` not supported
-
-| `resource-env-description`
-| `resource-env-ref` `glassfish-web.xml` equivalent, but `resource-link` not supported
-
-| `ejb-reference-description`
-| `ejb-ref` `glassfish-web.xml` equivalent
-
-| `service-reference-description`
-|`service-ref` `glassfish-web.xml` equivalent
-
-| `timeout-secs` under `session-descriptor`
-| `timeoutSeconds` property of `session-properties` `glassfish-web.xml` equivalent
-
-| `invalidation-interval-secs` under `session-descriptor`
-| `reapIntervalSeconds` property of `manager-properties` `glassfish-web.xml` equivalent
-
-| `max-in-memory-sessions` under `session-descriptor`
-| `maxSessions` property of `manager-properties` `glassfish-web.xml` equivalent
-
-| `persistent-store-dir` under `session-descriptor`
-| `directory` property of `store-properties` `glassfish-web.xml` equivalent
-
-| `prefer-web-inf-classes` under `container-descriptor`
-| `delegate` attribute of `class-loader` `glassfish-web.xml` equivalent
-
-| `context-root`
-| `context-root` `glassfish-web.xml` equivalent
-
-| `cookies-enabled` under `session-descriptor`
-| Servlet 3.0
-
-| `cookie-name` under `session-descriptor`
-| Servlet 3.0
-
-| `cookie-path` under `session-descriptor`
-| Servlet 3.0
-
-| `cookie-domain` under `session-descriptor`
-| Servlet 3.0
-
-| `cookie-comment` under `session-descriptor`
-| Servlet 3.0
-
-| `cookie-secure` under `session-descriptor`
-| Servlet 3.0
-
-| `cookie-max-age-secs` under `session-descriptor`
-| Servlet 3.0
-
-| `cookie-http-only` under `session-descriptor`
-| Servlet 3.0
-
-| `url-rewriting-enabled` under `session-descriptor`
-| Servlet 3.0
-
-| `persistent-store-cookie-name` under `session-descriptor`
-| Cookie-based persistence is supported
-
-| `keepgenerated` under `jsp-descriptor`
-| keep generated init parameter of `JspServlet`
-
-| `working-dir` under `jsp-descriptor`
-| scratchdir init parameter of `JspServlet`
-
-| `compress-html-template` under `jsp-descriptor`
-| trimSpaces init parameter of `JspServlet`
-
-| `index-directory-enabled` under `container-descriptor`
-| listings init parameter of `DefaultServlet`
-
-| `index-directory-sort-by` under `container-descriptor`
-| sortedBy init parameter of `DefaultServlet`
-
-| `save-sessions-enabled` under `container-descriptor`
-| Same as `asadmin redeploy` `--keepstate=true` or `keep-state` in `glassfish-web.xml`
-
-| `run-as-principal-name` under `servlet-descriptor`
-| `principal-name` under `servlet` `glassfish-web.xml` equivalent
-
-|===
-
-The elements of `weblogic-webservices.xml` that Payara Server supports are explained in the following table.
-
-.`weblogic-webservices.xml` Support in Payara Server
-[cols="3,6",options="header"]
-|===
-| *`weblogic-webservices.xml` Element Name* | *Payara Server Support*
-
-| `webservice-type`
-| Possible values are `JAXRPC` or `JAXWS`. Payara Server does not support JAX-RPC web services with Jakarta Web Services Metadata annotations.
-The use of this element is limited, because the container can find out if the type is JAX-WS or JAX-RPC based on presence of Jakarta Web Services Metadata annotations.
-
-| `wsdl-publish-file`
-| Same as `wsdl-publish-location` in `glassfish-web.xml`
-
-| `service-endpoint-address`
-| Similar to `endpoint-address-uri` in `glassfish-web.xml`, except that `webservice-contextpath` and `webservice-serviceuri` are specified separately
-
-| `j2ee:login-config`
-| Same as `login-config` in `glassfish-web.xml`
-
-| `j2ee:transport-guarantee`
-| Same as `transport-guarantee` in `glassfish-web.xml`
-
-| `exposed` under `wsdl`
-| Accepts `true` or `false`, defaults to `true`. Controls the publishing of WSDL to clients.
-
-| `stream-attachments`
-| Accepts `true` or `false`, defaults to `true`. Only for JAX-WS web services. Configures the JAX-WS runtime to send attachments in streaming fashion.
-
-| `validate-request`
-|Accepts `true` or `false`, defaults to `false`. Only for JAX-WS web services. Configures the JAX-WS runtime to validate that request messages are as the WSDL definitions specify.
-
-| `http-response-buffersize`
-| Property of `ReliabilityMessagingFeature` configuration, similar to `ReliableMessagingFeature.setDestinationBufferQuota()`
-
-| `reliability-config`
-| Partially supported. Sub-elements map to Metro's `ReliabilityMessagingFeature`.
-
-| `inactivity-timeout` under `reliability-config`
-| Maps to `ReliableMessagingFeature.getSequenceInactivityTimeout()`
-
-| `base-retransmission-interval` under `reliability-config`
-| Maps to `ReliableMessagingFeature.``getMessageRetransmissionInterval()`
-
-| `retransmission-exponential-``backoff` under `reliability-config`
-| Maps to `ReliableMessagingFeature.``getRetransmissionBackoffAlgorithm()`. Returns enum values, one of them is `exponential`.
-
-| `acknowledgement-interval` under `reliability-config`
-| Maps to `ReliableMessagingFeature.``getAcknowledgementTransmissionInterval()`
-
-| `sequence-expiration` under `reliability-config`
-| Maps to `ReliableMessagingFeature.``getSequenceInactivityTimeout()`. In WebLogic Server this value applies regardless of activity.
-In Metro it applies only to inactive sequences.
-
-| `buffer-retry-count` under `reliability-config`
-| Maps to `ReliableMessagingFeature.``getMaxMessageRetransmissionCount()`
-
-| `buffer-retry-delay` under `reliability-config`
-| Maps to `ReliableMessagingFeature.``getMessageRetransmissionInterval()`
-|===
-
-[[deployment-descriptor-precedence-order]]
-== Deployment Descriptor Precedence Order
-
-When multiple vendor deployment descriptors are present in the same module (including deployment descriptors of the original *Eclipse GlassFish* and of the old *Sun Application Server*), the descriptors are processed with the following precedence order in default mode:
-
-----
-WebLogic Server > Payara Platform > Eclipse GlassFish Server > Sun Application Server
-----
-
-The default precedence order can be customized and configured via the system properties documented in the following sections.
-
-[[gfdd-over-wlsdd]]
-=== `gfdd.over.wlsdd`
-
-This system property controls the precedence between original GlassFish Server and WebLogic Server deployment descriptors when they are both present.
-
-When the `gfdd.over.wlsdd` property is set to true, the descriptors are processed in this order:
-
-----
-Payara Platform > GlassFish Server > WebLogic Server > Sun Application Server
-----
-
-[[ignore-wlsdd]]
-=== `ignore.wlsdd`
-
-When the `ignore.wlsdd` property is set to true, the WebLogic Server deployment descriptors will be completely ignored and other descriptors will be processed in the following order:
-
-----
-GlassFish Server > Payara Platform > Sun Application Server
-----
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc
index eed476738..cc1040724 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc
@@ -104,7 +104,7 @@ Defines an administered object for an inbound resource adapter.
[[superelements-4]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resources[`resources`] (`glassfish-resources.xml` and `payara-resources.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resources[`resources`] (`payara-resources.xml`)
[[subelements-4]]
=== Subelements
@@ -237,7 +237,7 @@ As a prerequisite to gaining access to any web resources protected by an authori
[[superelements-7]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#login-config[`login-config`] (`glassfish-web.xml` and `payara-web.xml`),
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#login-config[`login-config`] (`payara-web.xml`),
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#as-context[`as-context`] (`glassfish-ejb-jar.xml`)
[[subelements-7]]
@@ -314,7 +314,7 @@ Specifies the user name and password required by the Enterprise Information Syst
[[superelements-9]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#security-map[`security-map`] (`glassfish-resources.xml` and `payara-resources.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#security-map[`security-map`] (`payara-resources.xml`)
[[subelements-9]]
=== Subelements
@@ -465,7 +465,7 @@ Configures caching for web application components.
[[superelements-12]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`)
[[subelements-12]]
=== Subelements
@@ -558,7 +558,7 @@ Specifies a class that implements the com.sun.appserv.web.cache.CacheHelper inte
[[superelements-13]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache[`cache`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache[`cache`] (`payara-web.xml`)
[[subelements-13]]
=== Subelements
@@ -600,7 +600,7 @@ Specifies the `name` of the xref:Technical Documentation/Payara Server Document
[[superelements-14]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache-mapping[`cache-mapping`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache-mapping[`cache-mapping`] (`payara-web.xml`)
[[subelements-14]]
=== Subelements
@@ -633,7 +633,7 @@ Maps a URL pattern or a servlet name to its cacheability constraints.
[[superelements-16]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache[`cache`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache[`cache`] (`payara-web.xml`)
[[subelements-16]]
=== Subelements
@@ -691,7 +691,7 @@ Specifies JAX-RPC property values that can be set on a `javax.xml.rpc.Call` obje
[[superelements-17]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#port-info[`port-info`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#service-ref[`service-ref`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#port-info[`port-info`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#service-ref[`service-ref`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
[[subelements-17]]
=== Subelements
@@ -863,7 +863,7 @@ Configures the class loader for the web module.
[[superelements-25]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`)
[[subelements-23]]
=== Subelements
@@ -949,7 +949,7 @@ For more information about how class delegation can be configured on Payara Serv
[[superelements-223]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`glassfish-web.xml` and `payara-web.xml`),
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`),
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-application[`glassfish-application`] (`glassfish-application.xml`)
[[subelements-214-2]]
@@ -1483,7 +1483,7 @@ Defines a connector connection pool.
[[superelements-39]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resources[`resources`] (`glassfish-resources.xml` and `payara-resources.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resources[`resources`] (`payara-resources.xml`)
[[subelements-37]]
=== Subelements
@@ -1674,7 +1674,7 @@ Defines the connection factory object of a specific connection definition in a c
[[superelements-40]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resources[`resources`] (`glassfish-resources.xml` and `payara-resources.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resources[`resources`] (`payara-resources.xml`)
[[subelements-38]]
=== Subelements
@@ -1779,7 +1779,7 @@ All `constraint-field` constraints must pass for a response to be cached. If the
[[superelements-42]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache-mapping[`cache-mapping`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache-mapping[`cache-mapping`] (`payara-web.xml`)
[[subelements-40]]
=== Subelements
@@ -1837,7 +1837,7 @@ Specifies a value to be matched to the input parameter value. The matching is ca
[[superelements-43]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#constraint-field[`constraint-field`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#constraint-field[`constraint-field`] (`payara-web.xml`)
[[subelements-41]]
=== Subelements
@@ -1883,7 +1883,7 @@ If you are setting up load balancing, web module context roots must be unique wi
=== Superelements
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#web[`web`] (`glassfish-application.xml`),
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`] (`glassfish-web.xml` and `payara-web.xml`),
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`),
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#java-web-start-access[`java-web-start-access`] (`glassfish-application-client.xml`)
[[subelements-42]]
@@ -1902,7 +1902,7 @@ If cookie settings are defined programmatically using `jakarta.servlet.SessionCo
[[superelements-45]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#session-config[`session-config`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#session-config[`session-config`] (`payara-web.xml`)
[[subelements-43]]
=== Subelements
@@ -1995,7 +1995,7 @@ Such object factories implement the `javax.naming.spi.ObjectFactory` interface.
[[superelements-47]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resources[`resources`] (`glassfish-resources.xml` and `payara-resources.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resources[`resources`] (`payara-resources.xml`)
[[subelements-45]]
=== Subelements
@@ -2079,7 +2079,7 @@ Specifies whether the debugging servlet is enabled for this web service endpoint
[[superelements-49]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-endpoint[`webservice-endpoint`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-endpoint[`webservice-endpoint`] (`payara-web.xml`, `glassfish-ejb-jar.xml`)
[[subelements-47]]
=== Subelements
@@ -2109,7 +2109,7 @@ Passes property values to the built-in `default` xref:Technical Documentation/Pa
[[superelements-51]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache[`cache`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache[`cache`] (`payara-web.xml`)
[[subelements-49]]
=== Subelements
@@ -2158,7 +2158,7 @@ If this element is used in conjunction with a JMS Connection Factory resource, t
[[superelements-52]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resource-ref[`resource-ref`] (`glassfish-web.xml` and `payara-web.xml`,
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resource-ref[`resource-ref`] (`payara-web.xml`,
`glassfish-ejb-jar.xml`, `glassfish-application-client.xml`);
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cmp-resource[`cmp-resource`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#mdb-connection-factory[`mdb-connection-factory`]
(`glassfish-ejb-jar.xml`)
@@ -2193,7 +2193,7 @@ Specifies a text description of the containing element.
=== Superelements
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#property-with-attributes[`property` (with attributes)], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#valve[`valve`]
-(`glassfish-web.xml` and `payara-web.xml`); xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#activation-config[`activation-config`],
+(`payara-web.xml`); xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#activation-config[`activation-config`],
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#method[`method`] (`glassfish-ejb-jar.xml`);
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#target-server[`target-server`] (`sun-acc.xml`);
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#admin-object-resource[`admin-object-resource`],
@@ -2202,7 +2202,7 @@ xref:Technical Documentation/Payara Server Documentation/Application Deployment/
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#external-jndi-resource[`external-jndi-resource`],
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#jdbc-connection-pool[`jdbc-connection-pool`], xref:jdbc-resource[`jdbc-resource`],
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#mail-resource[`mail-resource`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#property-with-attributes[`property` (with attributes)],
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resource-adapter-config[`resource-adapter-config`] (`glassfish-resources.xml` and `payara-resources.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resource-adapter-config[`resource-adapter-config`] (`payara-resources.xml`)
[[subelements-51]]
=== Subelements
@@ -2239,7 +2239,7 @@ If this element is not specified, the default is `REQUEST`. See `6.2.5` of the S
[[superelements-55]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache-mapping[`cache-mapping`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache-mapping[`cache-mapping`] (`payara-web.xml`)
[[subelements-53]]
=== Subelements
@@ -2506,7 +2506,7 @@ The `ejb-ref` element is used for the declaration of a reference to an EJB's hom
[[superelements-59]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`] (`glassfish-web.xml` and `payara-web.xml`),
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`),
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#ejb[`ejb`] (`glassfish-ejb-jar.xml`),
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-application-client[`glassfish-application-client`] (`glassfish-application-client.xml`)
@@ -2538,7 +2538,7 @@ Specifies the `ejb-ref-name` in the corresponding Jakarta EE deployment descript
[[superelements-60]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#ejb-ref[`ejb-ref`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#ejb-ref[`ejb-ref`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
[[subelements-58]]
=== Subelements
@@ -2609,7 +2609,7 @@ If the web service endpoint is a servlet that implements only a single endpoint
[[superelements-62]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-endpoint[`webservice-endpoint`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-endpoint[`webservice-endpoint`] (`payara-web.xml`, `glassfish-ejb-jar.xml`)
[[subelements-60]]
=== Subelements
@@ -2834,7 +2834,7 @@ javax.naming.spi.InitialContextFactory interface.
[[superelements-67]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resources[`resources`] (`glassfish-resources.xml` and `payara-resources.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resources[`resources`] (`payara-resources.xml`)
[[subelements-65]]
=== Subelements
@@ -3228,7 +3228,7 @@ asadmin set configs.config.server-config.security-service.activate-default-princ
Except its effect will only limit itself to the application instead of all applications deployed on the server.
-WARNING: When set using this property, this configuration will ALWAYS take effect and if set in the `glassfish-web.xml` or `glassfish-ejb-jar.xml` deployment descriptors, it will be ignored.
+WARNING: When set using this property, this configuration will ALWAYS take effect and if set in the `payara-web.xml` or `glassfish-ejb-jar.xml` deployment descriptors, it will be ignored.
|===
[[glassfish-application-client]]
@@ -3338,12 +3338,12 @@ a| xref:Technical Documentation/Payara Server Documentation/Application Deployme
|===
-[[glassfish-web-app]]
-== `glassfish-web-app` or `payara-web-app`
+[[payara-web-app]]
+== `payara-web-app`
-Defines Payara Server specific configuration for a web module. This is the root element; there can only be one `glassfish-web-app` element in a `glassfish-web.xml` and `payara-web.xml` file.
+Defines Payara Server specific configuration for a web module. This is the root element; there can only be one `payara-web-app` element in a `payara-web.xml` file.
-See xref:Technical Documentation/Payara Server Documentation/Application Deployment/Deployment Descriptor Files.adoc#the-glassfish-web.xml-file[The glassfish-web.xml and payara-web.xml Files].
+See xref:Technical Documentation/Payara Server Documentation/Application Deployment/Deployment Descriptor Files.adoc#the-glassfish-web.xml-file[The payara-web.xml File].
[[superelements-76]]
=== Superelements
@@ -3353,9 +3353,9 @@ none
[[subelements-74]]
=== Subelements
-The following table describes subelements for the `glassfish-web-app` element.
+The following table describes subelements for the `payara-web-app` element.
-.`glassfish-web-app` Subelements
+.`payara-web-app` Subelements
[cols="3,2,6",options="header"]
|===
|Element |Required |Description
@@ -3415,7 +3415,7 @@ a| xref:Technical Documentation/Payara Server Documentation/Application Deployme
a| xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#locale-charset-info[`locale-charset-info`]
|zero or one
-|Deprecated. Use the `parameter-encoding` subelement of `glassfish-web-app` instead.
+|Deprecated. Use the `parameter-encoding` subelement of `payara-web-app` instead.
a| xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#parameter-encoding[`parameter-encoding`]
|zero or one
@@ -3470,9 +3470,9 @@ a| xref:Technical Documentation/Payara Server Documentation/Application Deployme
[[attributes-16]]
=== Attributes
-The following table describes attributes for the `glassfish-web-app` element.
+The following table describes attributes for the `payara-web-app` element.
-.`glassfish-web-app` Attributes
+.`payara-web-app` Attributes
[cols="3,2,6",options="header"]
|===
|Attribute |Default |Description
@@ -3486,9 +3486,9 @@ The following table describes attributes for the `glassfish-web-app` element.
[[properties-7]]
=== Properties
-The following table describes properties for the `glassfish-web-app` element.
+The following table describes properties for the `payara-web-app` element.
-.`glassfish-web-app` Properties
+.`payara-web-app` Properties
[cols="3,2,6",options="header"]
|===
|Property |Default |Description
@@ -3515,11 +3515,11 @@ The URI pattern of the first alternate docroot uses an exact match, whereas the
[source,xml]
----
-
+
-
+
----
The `value` of each alternate docroot has two components: The first component, `from`, specifies the alternate docroot's URI pattern,
@@ -3620,7 +3620,7 @@ Maps an EIS group to a group defined in the Payara Server domain.
[[superelements-77]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#work-security-map[`work-security-map`] (`glassfish-resources.xml` and `payara-resources.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#work-security-map[`work-security-map`] (`payara-resources.xml`)
[[subelements-75]]
=== Subelements
@@ -3651,7 +3651,7 @@ Specifies a group name in the current realm.
[[superelements-78]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#security-role-mapping[`security-role-mapping`] (`glassfish-application.xml`, `glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#security-role-mapping[`security-role-mapping`] (`glassfish-application.xml`, `payara-web.xml`, `glassfish-ejb-jar.xml`)
[[subelements-76]]
=== Subelements
@@ -3666,7 +3666,7 @@ Specifies an HTTP method that is eligible for caching. The default is `GET`.
[[superelements-79]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache-mapping[`cache-mapping`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache-mapping[`cache-mapping`] (`payara-web.xml`)
[[subelements-77]]
=== Subelements
@@ -3681,7 +3681,7 @@ Specifies a URL pattern for idempotent requests.
[[superelements-80]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`)
[[subelements-78]]
=== Subelements
@@ -3806,7 +3806,7 @@ Specifies a method.
[[superelements-86]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#message[`message`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#message[`message`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
[[subelements-82]]
=== Subelements
@@ -3897,7 +3897,7 @@ The out-of-the-box support of `@RolesAllowed` for JAX-RS resources can be switch
[[superelements-228]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app or payara-web-app`] (`glassfish-web-app.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`)
[[subelements-218]]
=== Subelements
@@ -3911,7 +3911,7 @@ Defines the attributes and properties that are required for creating a JDBC conn
[[superelements-88]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resources[`resources`] (`glassfish-resources.xml` and `payara-resources.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resources[`resources`] (`payara-resources.xml`)
[[subelements-84]]
=== Subelements
@@ -4168,7 +4168,7 @@ Defines a JDBC (javax.sql.DataSource) resource.
[[superelements-89]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resources[`resources`] (`glassfish-resources.xml` and `payara-resources.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resources[`resources`] (`payara-resources.xml`)
[[subelements-85]]
=== Subelements
@@ -4264,7 +4264,7 @@ For more information about JMS resources, see "xref:Technical Documentation/Appl
=== Superelements
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#ejb-ref[`ejb-ref`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#message-destination[`message-destination`],
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resource-env-ref[`resource-env-ref`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resource-ref[`resource-ref`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`,
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resource-env-ref[`resource-env-ref`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resource-ref[`resource-ref`] (`payara-web.xml`, `glassfish-ejb-jar.xml`,
`glassfish-application-client.xml`); xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cmp-resource[`cmp-resource`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#ejb[`ejb`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#mdb-connection-factory[`mdb-connection-factory`] (`glassfish-ejb-jar.xml`)
[[subelements-88]]
@@ -4324,7 +4324,7 @@ Specifies JSP configuration information.
[[superelements-94]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`)
[[subelements-90]]
=== Subelements
@@ -4430,7 +4430,7 @@ It is assumed that JSP files have been precompiled, and their corresponding serv
The default value of the compiler property for this element has changed from 1.5 to 1.8, denoting a change from JDK5 to JDK8.
-You can change this to another value by editing the jsp-config element in the glassfish-web.xml file.
+You can change this to another value by editing the jsp-config element in the payara-web.xml file.
[[keep-state]]
== `keep-state`
@@ -4439,7 +4439,7 @@ If set to `true`, retains web sessions, stateful session bean instances, and per
Some changes to an application between redeployments prevent this feature from working properly. For example, do not change the set of instance variables in the SFSB bean class.
-For web applications, this feature is applicable only if in the `glassfish-web-app.xml` file the `persistence-type` attribute of the xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#session-manager[`session-manager`] element is `file`.
+For web applications, this feature is applicable only if in the `payara-web.xml` file the `persistence-type` attribute of the xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#session-manager[`session-manager`] element is `file`.
For stateful session bean instances, the persistence type without high availability is set in the server (the `sfsb-persistence-type` attribute) and must be set to `file`, which is the default and recommended value.
@@ -4451,7 +4451,7 @@ To preserve active state data, Payara Server serializes the data and saves it in
=== Superelements
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-application[`glassfish-application`] (`glassfish-application.xml`),
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`] (`glassfish-web-app.xml`),
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`),
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-ejb-jar[`glassfish-ejb-jar`] (`glassfish-ejb-jar.xml`)
[[subelements-91]]
@@ -4469,7 +4469,7 @@ If this element is not present, the web container uses the Servlet Path (the pat
[[superelements-96]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache-mapping[`cache-mapping`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache-mapping[`cache-mapping`] (`payara-web.xml`)
[[subelements-92]]
=== Subelements
@@ -4546,12 +4546,12 @@ none - contains data
== `locale-charset-info`
Deprecated. For backward compatibility only. Use the xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#parameter-encoding[`parameter-encoding`] subelement of
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`] instead. Specifies information about the application's internationalization settings.
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] instead. Specifies information about the application's internationalization settings.
[[superelements-100]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`)
[[subelements-96]]
=== Subelements
@@ -4597,7 +4597,7 @@ For encodings, see `https://docs.oracle.com/javase/8/docs/technotes/guides/intl/
[[superelements-101]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#locale-charset-info[`locale-charset-info`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#locale-charset-info[`locale-charset-info`] (`payara-web.xml`)
[[subelements-97]]
=== Subelements
@@ -4659,7 +4659,7 @@ Specifies the local part of a QNAME.
[[superelements-102]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#service-qname[`service-qname`],xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#wsdl-port[`wsdl-port`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#service-qname[`service-qname`],xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#wsdl-port[`wsdl-port`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
[[subelements-98]]
=== Subelements
@@ -4742,7 +4742,7 @@ Specifies the authentication configuration for an EJB web service endpoint. Not
[[superelements-106]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-endpoint[`webservice-endpoint`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-endpoint[`webservice-endpoint`] (`payara-web.xml`, `glassfish-ejb-jar.xml`)
[[subelements-101]]
=== Subelements
@@ -4772,7 +4772,7 @@ Defines a Jakarta Mail (`jakarta.mail.Session`) resource.
[[superelements-107]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resources[`resources`] (`glassfish-resources.xml` and `payara-resources.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resources[`resources`] (`payara-resources.xml`)
[[subelements-102]]
=== Subelements
@@ -4849,7 +4849,7 @@ You can set properties for the `mail-resource` element and then get these proper
The Payara Server changes the dash (`-`) character to a period (`.`) in the name of the property, then saves the property to the `MailConfiguration` and Jakarta Mail `Session` objects. If the name of the property doesn't start with `mail-`, the property is ignored.
-For example, to define the property `mail.password` in a Jakarta Mail Session object, first edit `glassfish-resources.xml` and `payara-resources.xml` as follows:
+For example, to define the property `mail.password` in a Jakarta Mail Session object, first edit `payara-resources.xml` as follows:
[source,xml]
----
@@ -4881,7 +4881,7 @@ Specifies session manager properties.
[[superelements-108]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#session-manager[`session-manager`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#session-manager[`session-manager`] (`payara-web.xml`)
[[subelements-103]]
=== Subelements
@@ -5091,7 +5091,7 @@ Specifies the methods or operations to which message security requirements apply
[[superelements-115]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#message-security[`message-security`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#message-security[`message-security`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
[[subelements-108]]
=== Subelements
@@ -5123,7 +5123,7 @@ Use when the message destination reference in the corresponding Jakarta EE deplo
[[superelements-116]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`] (`glassfish-web.xml` and `payara-web.xml`),
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`),
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#enterprise-beans[`enterprise-beans`] (`glassfish-ejb-jar.xml`),
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-application-client[`glassfish-application-client`] (`glassfish-application-client.xml`)
@@ -5155,7 +5155,7 @@ Specifies the name of a logical message destination defined within the correspon
[[superelements-117]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#message-destination[`message-destination`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#message-destination[`message-destination`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
[[subelements-110]]
=== Subelements
@@ -5171,7 +5171,7 @@ Use only when the message destination reference in the corresponding Jakarta EE
[[superelements-118]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`] (`glassfish-web.xml` and `payara-web.xml`),
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`),
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#ejb[`ejb`] (`glassfish-ejb-jar.xml`),
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-application-client[`glassfish-application-client`] (`glassfish-application-client.xml`)
@@ -5203,7 +5203,7 @@ Specifies the name of a physical message destination defined within the correspo
[[superelements-119]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#message-destination-ref[`message-destination-ref`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#message-destination-ref[`message-destination-ref`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
[[subelements-112]]
=== Subelements
@@ -5221,7 +5221,7 @@ Specifies message security requirements.
[[superelements-120]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#message-security-binding[`message-security-binding`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#message-security-binding[`message-security-binding`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
[[subelements-113]]
=== Subelements
@@ -5258,7 +5258,7 @@ Specifies a custom authentication provider binding for a parent xref:Technical D
[[superelements-121]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-endpoint[`webservice-endpoint`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#port-info[`port-info`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-endpoint[`webservice-endpoint`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#port-info[`port-info`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
[[subelements-114]]
=== Subelements
@@ -5407,7 +5407,7 @@ Specifies a method name or `*` (an asterisk) for all methods. If a method is ove
[[superelements-125]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#java-method[`java-method`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`); xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#finder[`finder`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#query-method[`query-method`] , xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#method[`method`] (`glassfish-ejb-jar.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#java-method[`java-method`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`); xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#finder[`finder`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#query-method[`query-method`] , xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#method[`method`] (`glassfish-ejb-jar.xml`)
[[subelements-118]]
=== Subelements
@@ -5429,7 +5429,7 @@ Specifies the fully qualified Java type name of a method parameter.
[[superelements-126]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#method-params[`method-params`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#method-params[`method-params`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
[[subelements-119]]
=== Subelements
@@ -5444,7 +5444,7 @@ Specifies fully qualified Java type names of method parameters.
[[superelements-127]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#java-method[`java-method`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`);
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#java-method[`java-method`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`);
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#query-method[`query-method`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#method[`method`] (`glassfish-ejb-jar.xml`)
[[subelements-120]]
@@ -5471,7 +5471,7 @@ Specifies the name of the entity.
[[superelements-128]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#call-property[`call-property`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#default-resource-principal[`default-resource-principal`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#stub-property[`stub-property`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`); xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#enterprise-beans[`enterprise-beans`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#principal[`principal`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#property-with-subelements[`property` (with subelements)] (`glassfish-ejb-jar.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#call-property[`call-property`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#default-resource-principal[`default-resource-principal`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#stub-property[`stub-property`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`); xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#enterprise-beans[`enterprise-beans`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#principal[`principal`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#property-with-subelements[`property` (with subelements)] (`glassfish-ejb-jar.xml`)
[[subelements-121]]
=== Subelements
@@ -5502,7 +5502,7 @@ Specifies the namespace URI.
[[superelements-130]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#service-qname[`service-qname`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#wsdl-port[`wsdl-port`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#service-qname[`service-qname`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#wsdl-port[`wsdl-port`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
[[subelements-123]]
=== Subelements
@@ -5558,7 +5558,7 @@ Specifies the WSDL name of an operation of a web service.
[[superelements-133]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#message[`message`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#message[`message`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
[[subelements-126]]
=== Subelements
@@ -5570,13 +5570,13 @@ none - contains data
Specifies the default request character encoding and how the web container decodes parameters from forms according to a hidden field value.
-If both the xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`] and xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#locale-charset-info[`locale-charset-info`] elements have `parameter-encoding` subelements, the subelement of `glassfish-web-app` takes precedence.
+If both the xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] and xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#locale-charset-info[`locale-charset-info`] elements have `parameter-encoding` subelements, the subelement of `payara-web-app` takes precedence.
For encodings, see `https://docs.oracle.com/javase/8/docs/technotes/guides/intl/encoding.doc.html`.
[[superelements-134]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#locale-charset-info[`locale-charset-info`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#locale-charset-info[`locale-charset-info`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`)
[[subelements-127]]
=== Subelements
@@ -5643,7 +5643,7 @@ Specifies the password for the principal.
[[superelements-136]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#default-resource-principal[`default-resource-principal`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#default-resource-principal[`default-resource-principal`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
[[subelements-129]]
=== Subelements
@@ -5704,7 +5704,7 @@ Specifies a unique name for a port component within a web or EJB module.
[[superelements-140]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-endpoint[`webservice-endpoint`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-endpoint[`webservice-endpoint`] (`payara-web.xml`, `glassfish-ejb-jar.xml`)
[[subelements-132]]
=== Subelements
@@ -5725,7 +5725,7 @@ If a `service-endpoint-interface` is using container-managed port selection, its
[[superelements-141]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#service-ref[`service-ref`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#service-ref[`service-ref`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
[[subelements-133]]
=== Subelements
@@ -5794,7 +5794,7 @@ Defines a user name on the platform.
=== Superelements
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#ejb[`ejb`] (`glassfish-ejb-jar.xml`);
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#security-map[`security-map`] (`glassfish-resources.xml` and `payara-resources.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#security-map[`security-map`] (`payara-resources.xml`)
[[subelements-135]]
=== Subelements
@@ -5820,7 +5820,7 @@ Maps an EIS principal to a principal defined in the Payara Server domain.
[[superelements-144]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#work-security-map[`work-security-map`] (`glassfish-resources.xml` and `payara-resources.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#work-security-map[`work-security-map`] (`payara-resources.xml`)
[[subelements-136]]
=== Subelements
@@ -5853,7 +5853,7 @@ In an enterprise bean, specifies the principal username that has the `run-as` ro
[[superelements-145]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#security-role-mapping[`security-role-mapping`] (`glassfish-application.xml`, `glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`), xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#servlet[`servlet`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#security-role-mapping[`security-role-mapping`] (`glassfish-application.xml`, `payara-web.xml`, `glassfish-ejb-jar.xml`), xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#servlet[`servlet`] (`payara-web.xml`)
[[subelements-137]]
=== Subelements
@@ -5889,8 +5889,8 @@ xref:Technical Documentation/Payara Server Documentation/Application Deployment/
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#class-loader[`class-loader`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cookie-properties[`cookie-properties`],
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#default-helper[`default-helper`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#manager-properties[`manager-properties`],
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#session-properties[`session-properties`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#store-properties[`store-properties`],
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#valve[`valve`],
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-endpoint[`webservice-endpoint`] (`glassfish-web.xml` and `payara-web.xml`);
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#valve[`valve`],
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-endpoint[`webservice-endpoint`] (`payara-web.xml`);
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#auth-realm[`auth-realm`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#client-container[`client-container`],
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#client-credential[`client-credential`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#log-service[`log-service`],
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#provider-config[`provider-config`] (`sun-acc.xml`);
@@ -5899,8 +5899,8 @@ xref:Technical Documentation/Payara Server Documentation/Application Deployment/
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#connector-resource[`connector-resource`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#custom-resource[`custom-resource`],
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#external-jndi-resource[`external-jndi-resource`],
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#jdbc-connection-pool[`jdbc-connection-pool`], xref:jdbc-resource[`jdbc-resource`],
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#mail-resource[`mail-resource`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resource-adapter-config[`resource-adapter-config`] (`glassfish-resources.xml` and `payara-resources.xml`),
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`/`payara-web-app`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#mail-resource[`mail-resource`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resource-adapter-config[`resource-adapter-config`] (`payara-resources.xml`),
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`)
[[subelements-138]]
=== Subelements
@@ -6178,7 +6178,7 @@ Specifies a field that gives the application component a programmatic way to ref
[[superelements-156]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache-mapping[`cache-mapping`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache-mapping[`cache-mapping`] (`payara-web.xml`)
[[subelements-148]]
=== Subelements
@@ -6314,7 +6314,7 @@ Defines the authentication policy requirements of the application's request proc
[[superelements-162]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#message-security[`message-security`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#message-security[`message-security`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
[[subelements-154]]
=== Subelements
@@ -6362,7 +6362,7 @@ The `res-ref-name` element specifies the name of a resource manager connection f
[[superelements-164]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resource-ref[`resource-ref`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resource-ref[`resource-ref`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
[[subelements-156]]
=== Subelements
@@ -6414,7 +6414,7 @@ Defines a connector (resource adapter) configuration. Stores configuration infor
[[superelements-166]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resources[`resources`] (`glassfish-resources.xml` and `payara-resources.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resources[`resources`] (`payara-resources.xml`)
[[subelements-158]]
=== Subelements
@@ -6486,7 +6486,7 @@ Maps the `res-ref-name` in the corresponding Jakarta EE deployment descriptor fi
[[superelements-168]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`] (`glassfish-web.xml` and `payara-web.xml`),
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`),
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#ejb[`ejb`] (`glassfish-ejb-jar.xml`),
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-application-client[`glassfish-application-client`] (`glassfish-application-client.xml`)
@@ -6529,7 +6529,7 @@ Specifies the `res-ref-name` in the corresponding Jakarta EE deployment descript
[[superelements-169]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resource-env-ref[`resource-env-ref`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resource-env-ref[`resource-env-ref`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
[[subelements-161]]
=== Subelements
@@ -6549,7 +6549,7 @@ When `resource-ref` specifies a JMS connection factory for the Open Message Queu
[[superelements-170]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`] (`glassfish-web.xml` and `payara-web.xml`),
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`),
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#ejb[`ejb`] (`glassfish-ejb-jar.xml`),
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-application-client[`glassfish-application-client`] (`glassfish-application-client.xml`)
@@ -6591,9 +6591,9 @@ a| xref:Technical Documentation/Payara Server Documentation/Application Deployme
[[resources]]
== `resources`
-Defines application-scoped resources for an enterprise application, web module, EJB module, connector module, or application client module. This is the root element; there can only be one `resources` element in a `glassfish-resources.xml` or `payara-resources.xml` file.
+Defines application-scoped resources for an enterprise application, web module, EJB module, connector module, or application client module. This is the root element; there can only be one `resources` element in a `payara-resources.xml` file.
-See xref:Technical Documentation/Payara Server Documentation/Application Deployment/Deployment Descriptor Files.adoc#the-glassfish-resources.xml-file[The glassfish-resources.xml and payara-resources Files].
+See xref:Technical Documentation/Payara Server Documentation/Application Deployment/Deployment Descriptor Files.adoc#the-glassfish-resources.xml-file[The payara-resources File].
NOTE: You must specify a Java Naming and Directory Interface (JNDI) name for each resource. To avoid collisions with names of other enterprise resources in JNDI, and to avoid portability problems, all names in a Payara Server application should begin with the string `java:app/`.
@@ -6695,7 +6695,7 @@ Defines the authentication policy requirements of the application's response pro
[[superelements-173]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#message-security[`message-security`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#message-security[`message-security`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
[[subelements-165]]
=== Subelements
@@ -6726,7 +6726,7 @@ Contains the `role-name` in the `security-role` element of the corresponding Jak
[[superelements-174]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#security-role-mapping[`security-role-mapping`] (`glassfish-application.xml`, `glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#security-role-mapping[`security-role-mapping`] (`glassfish-application.xml`, `payara-web.xml`, `glassfish-ejb-jar.xml`)
[[subelements-166]]
=== Subelements
@@ -6764,7 +6764,7 @@ a| xref:Technical Documentation/Payara Server Documentation/Application Deployme
Modern WAR and EAR files very often include a number of 3rd party JARs. In situations where some JARs require CDI scanning and others may break if scanned, these can now be explicitly included or excluded from such component scanning.
-Both the `glassfish-application.xml` and the `glassfish-web.xml` files support the following directives:
+Both the `glassfish-application.xml` and the `payara-web.xml` files support the following directives:
[source, xml]
----
@@ -6781,7 +6781,7 @@ In the above example, all JARs will be excluded by default, then all JARs beginn
=== Superelements
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-application[`glassfish-application`] (`glassfish-application.xml`),
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`)
[[subelements-167]]
=== Subelements
@@ -6975,7 +6975,7 @@ This is different from a xref:Technical Documentation/Payara Server Documentatio
[[superelements-180]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#connector-connection-pool[`connector-connection-pool`] (`glassfish-resources.xml` and `payara-resources.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#connector-connection-pool[`connector-connection-pool`] (`payara-resources.xml`)
[[subelements-172]]
=== Subelements
@@ -7029,7 +7029,7 @@ To be useful, there must be at least one user in that realm who belongs to that
=== Superelements
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-application[`glassfish-application`] (`glassfish-application.xml`),
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`] (`glassfish-web.xml` and `payara-web.xml`),
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`),
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-ejb-jar[`glassfish-ejb-jar`] (`glassfish-ejb-jar.xml`)
[[subelements-173]]
@@ -7064,7 +7064,7 @@ Specifies the web service reference name relative to `java:comp/env`.
[[superelements-182]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#port-info[`port-info`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#port-info[`port-info`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
[[subelements-174]]
=== Subelements
@@ -7079,7 +7079,7 @@ Specifies the name of the generated service implementation class.
[[superelements-183]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#service-ref[`service-ref`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#service-ref[`service-ref`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
[[subelements-175]]
=== Subelements
@@ -7094,8 +7094,8 @@ Specifies the WSDL service element that is being referred to.
[[superelements-184]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#service-ref[`service-ref`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`);
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-endpoint[`webservice-endpoint`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#service-ref[`service-ref`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`);
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-endpoint[`webservice-endpoint`] (`payara-web.xml`, `glassfish-ejb-jar.xml`)
[[subelements-176]]
=== Subelements
@@ -7129,7 +7129,7 @@ Specifies runtime settings for a web service reference. Runtime information is o
[[superelements-185]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`] (`glassfish-web.xml` and `payara-web.xml`),
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`),
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#ejb[`ejb`] (`glassfish-ejb-jar.xml`),
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-application-client[`glassfish-application-client`] (`glassfish-application-client.xml`)
@@ -7177,7 +7177,7 @@ Specifies the web service reference name relative to `java:comp/env`.
[[superelements-186]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#service-ref[`service-ref`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#service-ref[`service-ref`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
[[subelements-178]]
=== Subelements
@@ -7192,7 +7192,7 @@ Specifies a principal name for a servlet. Used for the `run-as` role defined in
[[superelements-187]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`)
[[subelements-179]]
=== Subelements
@@ -7226,7 +7226,7 @@ Specifies the automatically generated name of the servlet implementation class.
[[superelements-188]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-endpoint[`webservice-endpoint`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-endpoint[`webservice-endpoint`] (`payara-web.xml`, `glassfish-ejb-jar.xml`)
[[subelements-180]]
=== Subelements
@@ -7241,7 +7241,7 @@ Specifies the name of a servlet, which is matched to a `servlet-name` in `web.xm
[[superelements-189]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache-mapping[`cache-mapping`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#servlet[`servlet`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache-mapping[`cache-mapping`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#servlet[`servlet`] (`payara-web.xml`)
[[subelements-181]]
=== Subelements
@@ -7256,7 +7256,7 @@ Specifies session configuration information. Overrides the web container setting
[[superelements-190]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`)
[[subelements-182]]
=== Subelements
@@ -7290,7 +7290,7 @@ Specifies session manager information.
[[superelements-191]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#session-config[`session-config`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#session-config[`session-config`] (`payara-web.xml`)
[[subelements-183]]
=== Subelements
@@ -7335,7 +7335,7 @@ Specifies session properties.
[[superelements-192]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#session-config[`session-config`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#session-config[`session-config`] (`payara-web.xml`)
[[subelements-184]]
=== Subelements
@@ -7448,7 +7448,7 @@ Specifies session persistence (storage) properties.
[[superelements-195]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#session-manager[`session-manager`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#session-manager[`session-manager`] (`payara-web.xml`)
[[subelements-187]]
=== Subelements
@@ -7509,7 +7509,7 @@ Specifies JAX-RPC property values that are set on a `javax.xml.rpc.Stub` object
[[superelements-196]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#port-info[`port-info`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#port-info[`port-info`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
[[subelements-188]]
=== Subelements
@@ -7707,7 +7707,7 @@ Specifies the automatically generated name of a tie implementation class for a p
[[superelements-201]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-endpoint[`webservice-endpoint`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-endpoint[`webservice-endpoint`] (`payara-web.xml`, `glassfish-ejb-jar.xml`)
[[subelements-193]]
=== Subelements
@@ -7723,7 +7723,7 @@ If not specified, the default is the value of the `timeout` attribute of the xre
[[superelements-202]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache-mapping[`cache-mapping`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache-mapping[`cache-mapping`] (`payara-web.xml`)
[[subelements-194]]
=== Subelements
@@ -7799,7 +7799,7 @@ In most cases, a value of `INTEGRAL` or `CONFIDENTIAL` indicates that the use of
[[superelements-204]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-endpoint[`webservice-endpoint`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-endpoint[`webservice-endpoint`] (`payara-web.xml`, `glassfish-ejb-jar.xml`)
[[subelements-196]]
=== Subelements
@@ -7830,7 +7830,7 @@ Specifies a servlet URL pattern for which caching is enabled. See the Servlet 6.
[[superelements-206]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache-mapping[`cache-mapping`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#cache-mapping[`cache-mapping`] (`payara-web.xml`)
[[subelements-198]]
=== Subelements
@@ -7845,7 +7845,7 @@ Contains the group to which the principal belongs.
[[superelements-207]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#security-map[`security-map`] (`glassfish-resources.xml` and `payara-resources.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#security-map[`security-map`] (`payara-resources.xml`)
[[subelements-199]]
=== Subelements
@@ -7875,7 +7875,7 @@ Specifies the value of the entity.
[[superelements-209]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#call-property[`call-property`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#stub-property[`stub-property`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`); xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#property-with-subelements[`property` (with subelements)] (`glassfish-ejb-jar.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#call-property[`call-property`], xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#stub-property[`stub-property`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`); xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#property-with-subelements[`property` (with subelements)] (`glassfish-ejb-jar.xml`)
[[subelements-201]]
=== Subelements
@@ -7891,7 +7891,7 @@ Specifies a custom valve for this web application. You can define a valve for al
[[superelements-210]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`] (`glassfish-web.xml` and `payara-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`)
[[subelements-202]]
Subelements
@@ -8000,7 +8000,7 @@ Contains version information for an application or module. For more information
=== Superelements
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-application[`glassfish-application`] (`glassfish-application.xml`),
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`] (`glassfish-web-app.xml`),
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`),
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-ejb-jar[`glassfish-ejb-jar`] (`glassfish-ejb-jar.xml`),
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-application-client[`glassfish-application-client`] (`glassfish-application-client.xml`)
@@ -8182,7 +8182,7 @@ Specifies a name and optional publish location for a web service.
[[superelements-216]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app`] (`glassfish-web.xml` and `payara-web.xml`),
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`),
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#enterprise-beans[`enterprise-beans`] (`glassfish-ejb-jar.xml`)
[[subelements-208]]
@@ -8213,7 +8213,7 @@ Specifies a unique name for the web service within a web or EJB module.
[[superelements-217]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-description[`webservice-description`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-description[`webservice-description`] (`payara-web.xml`, `glassfish-ejb-jar.xml`)
[[subelements-209]]
=== Subelements
@@ -8228,7 +8228,7 @@ Specifies information about a web service endpoint.
[[superelements-218]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#servlet[`servlet`] (`glassfish-web.xml` and `payara-web.xml`), xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#ejb[`ejb`] (`glassfish-ejb-jar.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#servlet[`servlet`] (`payara-web.xml`), xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#ejb[`ejb`] (`glassfish-ejb-jar.xml`)
[[subelements-210]]
=== Subelements
@@ -8276,7 +8276,7 @@ a| xref:Technical Documentation/Payara Server Documentation/Application Deployme
|zero or one
|Specifies whether the debugging servlet is enabled for this web service endpoint. Allowed values are `true` and `false` (the default).
-a| xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#property-with-attributes[`property` (with attributes)] (`glassfish-web.xml` and `payara-web.xml`) xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#property-with-subelements[`property` (with subelements)] (`glassfish-ejb-jar.xml`)
+a| xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#property-with-attributes[`property` (with attributes)] (`payara-web.xml`) xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#property-with-subelements[`property` (with subelements)] (`glassfish-ejb-jar.xml`)
|zero or more
|Specifies a property, which has a name and a value.
@@ -8295,7 +8295,7 @@ For more information about how extreme class loading isolation works on Payara S
=== Superelements
xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-application[`glassfish-application`] (`glassfish-application.xml`),
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`glassfish-web-app` or `payara-web-app`] (`glassfish-web.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[`payara-web-app`] (`payara-web.xml`)
[[subelements-230]]
=== Subelements
@@ -8311,7 +8311,7 @@ This is different from a xref:Technical Documentation/Payara Server Documentatio
[[superelements-219-2]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resources[`resources`] (`glassfish-resources.xml` and `payara-resources.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#resources[`resources`] (`payara-resources.xml`)
[[subelements-211]]
=== Subelements
@@ -8361,7 +8361,7 @@ Specifies a valid URL pointing to a final WSDL document. If not specified, the W
[[superelements-220]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#service-ref[`service-ref`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#service-ref[`service-ref`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
[[subelements-212]]
=== Subelements
@@ -8391,7 +8391,7 @@ Specifies the WSDL port.
[[superelements-221]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#port-info[`port-info`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#port-info[`port-info`] (`payara-web.xml`, `glassfish-ejb-jar.xml`, `glassfish-application-client.xml`)
[[subelements-213]]
=== Subelements
@@ -8422,7 +8422,7 @@ Any required files are published to this directory, preserving their location re
[[superelements-222]]
=== Superelements
-xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-description[`webservice-description`] (`glassfish-web.xml` and `payara-web.xml`, `glassfish-ejb-jar.xml`)
+xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#webservice-description[`webservice-description`] (`payara-web.xml`, `glassfish-ejb-jar.xml`)
[[subelements-214-1]]
=== Subelements
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/add-resources.adoc b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/add-resources.adoc
index d4f468944..fabd1a54d 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/add-resources.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/add-resources.adoc
@@ -22,7 +22,7 @@ ee Also in this help page.
The `--target` option specifies the target for which you are creating the resources. If this option specifies the domain, the resources are added only to the configuration of the domain administration server (DAS). If this option specifies any other target, the resources are added to the configuration of the DAS and
references are added to the resources from the specified target.
-The xml-file-name operand is the path to the XML file that contains the resources to be created. The `DOCTYPE` must be specified as `http://glassfish.org/dtds/glassfish-resources_1_5.dtd` in the `resources.xml` file.
+The xml-file-name operand is the path to the XML file that contains the resources to be created. The `DOCTYPE` must be specified as `https://docs.payara.fish/schemas/payara-resources_1_8.dtd` in the `resources.xml` file.
This subcommand is supported in remote mode only.
@@ -69,9 +69,9 @@ xml-file-name::
[source,xml]
----
-
+
+
-
+
----
The default value is `true`.
@@ -106,7 +106,7 @@ The default value is `true`.
`securePagesWithPragma`;;
Set this property to `false` to ensure that for all web applications on this virtual server file downloads using SSL work properly in
Internet Explorer. +
- You can set this property for a specific web application. For details, see xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[glassfish-web-app] in Payara Server Application Deployment section.
+ You can set this property for a specific web application. For details, see xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[payara-web-app] in Payara Server Application Deployment section.
`contextXmlDefault`;;
Specifies the location, relative to domain-dir, of the `context.xml`
file for this virtual server, if one is used. For more information
@@ -137,7 +137,7 @@ The default value is `true`.
The `value` of each alternate docroot has two components: The first component, `from`, specifies the alternate docroot's URI pattern,
and the second component, `dir`, specifies the alternate docroot's physical location (directory). Spaces are allowed in the `dir` component. +
- You can set this property for a specific web application. For details, see xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[glassfish-web-app] in Payara Server Application Deployment section.
+ You can set this property for a specific web application. For details, see xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[payara-web-app] in Payara Server Application Deployment section.
`send-error_n`;;
Specifies custom error page mappings for the virtual server, which are inherited by all web applications deployed on the virtual server. A web application can override these custom error page
@@ -182,7 +182,7 @@ value="from=/dummy url-prefix=http://etude"/>
value="org.glassfish.extension.Valve"/>
----
You can set this property for a specific web application. For
- details, see xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[glassfish-web-app] in Payara Server Application Deployment section.
+ details, see xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[payara-web-app] in Payara Server Application Deployment section.
`listener_n`;;
Specifies a fully qualified class name of a custom Catalina listener, where n is a positive integer that allows specification of
@@ -193,7 +193,7 @@ You can set this property for a specific web application. For
----
-You can set this property for a specific web application. For details, see xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[glassfish-web-app] in Payara Server Application Deployment section.
+You can set this property for a specific web application. For details, see xref:Technical Documentation/Payara Server Documentation/Application Deployment/Elements of Deployment Descriptors.adoc#glassfish-web-app[payara-web-app] in Payara Server Application Deployment section.
`docroot`;;
Absolute path to root document directory for server. Deprecated. Replaced with a `virtual-server` attribute, `docroot`, that is
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/deploy-remote-archive.adoc b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/deploy-remote-archive.adoc
index 6083555b2..d4a3a5c79 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/deploy-remote-archive.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/deploy-remote-archive.adoc
@@ -103,7 +103,7 @@ asadmin-options::
`--altdd`::
Deploys the application using a Jakarta EE standard deployment descriptor that resides outside of the application archive. Specify an absolute path or a relative path to the alternate deployment descriptor file. The alternate deployment descriptor overrides the top-level deployment descriptor packaged in the archive. For example, for an EAR, the `--altdd` option overrides `application.xml`. For a standalone module, the `--altdd` option overrides the top-level module descriptor such as `web.xml`.
`--runtimealtdd`::
- Deploys the application using a Payara Server runtime deployment descriptor that resides outside of the application archive. Specify an absolute path or a relative path to the alternate deployment descriptor file. The alternate deployment descriptor overrides the top-level deployment descriptor packaged in the archive. For example, for an EAR, the `--runtimealtdd` option overrides `glassfish-application.xml`. For a standalone module, the `--runtimealtdd` option overrides the top-level module descriptor such as `glassfish-web.xml` or `payara-web.xml`. Applies to Payara Server deployment descriptors only (`glassfish-*.xml`/`payara-*.xml`); the name of the alternate deployment descriptor file must begin with `glassfish-` (or `payara-` in specific cases). Does not apply to `sun-*.xml` deployment descriptors, which are deprecated.
+ Deploys the application using a Payara Server runtime deployment descriptor that resides outside of the application archive. Specify an absolute path or a relative path to the alternate deployment descriptor file. The alternate deployment descriptor overrides the top-level deployment descriptor packaged in the archive. For example, for an EAR, the `--runtimealtdd` option overrides `glassfish-application.xml`. For a standalone module, the `--runtimealtdd` option overrides the top-level module descriptor such as `payara-web.xml`. Applies to Payara Server deployment descriptors only (`glassfish-*.xml`/`payara-*.xml`); the name of the alternate deployment descriptor file must begin with `glassfish-` (or `payara-` in specific cases). Does not apply to `sun-*.xml` deployment descriptors, which are deprecated.
`--deploymentorder`::
Specifies the deployment order of the application. This is useful if the application has dependencies and must be loaded in a certain order at server startup. The deployment order is specified as an integer. The default value is 100. Applications with lower numbers are loaded before applications with higher numbers. For example, an application with a deployment order of 102 is loaded before an application with a deployment order of 110. If a deployment order is not specified, the default value of 100 is assigned. If two applications have the same deployment order, the first application to be deployed is the first application to be loaded at server startup. +
The deployment order is typically specified when the application is first deployed but can also be specified or changed after initial deployment using the `set` subcommand. You can view the deployment order of an application using the `get` subcommand.
@@ -121,7 +121,7 @@ asadmin-options::
This option controls whether web sessions, SFSB instances, and persistently created EJB timers are retained between re-deployments. +
The default is false. This option is supported only on the default server instance, named `server`. It is not supported and ignored for any other target. +
Some changes to an application between re-deployments prevent this feature from working properly. For example, do not change the set of instance variables in the SFSB bean class. +
- For web applications, this feature is applicable only if in the `glassfish-web-app.xml` file the `persistence-type` attribute of the `session-manager` element is `file`. +
+ For web applications, this feature is applicable only if in the `payara-web.xml` file the `persistence-type` attribute of the `session-manager` element is `file`. +
For stateful session bean instances, the persistence type without high availability is set in the server (the `sfsb-persistence-type` attribute) and must be set to `file`, which is the default and recommended value. +
If any active web session, SFSB instance, or EJB timer fails to be preserved or restored, none of these will be available when the redeployment is complete. However, the redeployment continues and a warning is logged. +
To preserve active state data, Payara Server serializes the data and saves it in memory. To restore the data, the class loader of the newly redeployed application deserializes the data that was previously saved.
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/deploy.adoc b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/deploy.adoc
index 18d5b6ef8..954739586 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/deploy.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/deploy.adoc
@@ -101,7 +101,7 @@ asadmin-options::
`--altdd`::
Deploys the application using a Jakarta EE standard deployment descriptor that resides outside of the application archive. Specify an absolute path or a relative path to the alternate deployment descriptor file. The alternate deployment descriptor overrides the top-level deployment descriptor packaged in the archive. For example, for an EAR, the `--altdd` option overrides `application.xml`. For a standalone module, the `--altdd` option overrides the top-level module descriptor such as `web.xml`.
`--runtimealtdd`::
- Deploys the application using a Payara Server runtime deployment descriptor that resides outside of the application archive. Specify an absolute path or a relative path to the alternate deployment descriptor file. The alternate deployment descriptor overrides the top-level deployment descriptor packaged in the archive. For example, for an EAR, the `--runtimealtdd` option overrides `glassfish-application.xml`. For a standalone module, the `--runtimealtdd` option overrides the top-level module descriptor such as `glassfish-web.xml` or `payara-web.xml`. Applies to Payara Server deployment descriptors only (`glassfish-*.xml`/`payara-*.xml`); the name of the alternate deployment descriptor file must begin with `glassfish-` (or `payara-` in specific cases). Does not apply to `sun-*.xml` deployment descriptors, which are deprecated.
+ Deploys the application using a Payara Server runtime deployment descriptor that resides outside of the application archive. Specify an absolute path or a relative path to the alternate deployment descriptor file. The alternate deployment descriptor overrides the top-level deployment descriptor packaged in the archive. For example, for an EAR, the `--runtimealtdd` option overrides `glassfish-application.xml`. For a standalone module, the `--runtimealtdd` option overrides the top-level module descriptor such as `payara-web.xml`. Applies to Payara Server deployment descriptors only (`glassfish-*.xml`/`payara-*.xml`); the name of the alternate deployment descriptor file must begin with `glassfish-` (or `payara-` in specific cases). Does not apply to `sun-*.xml` deployment descriptors, which are deprecated.
`--deploymentorder`::
Specifies the deployment order of the application. This is useful if the application has dependencies and must be loaded in a certain order at server startup. The deployment order is specified as an integer. The default value is 100. Applications with lower numbers are loaded before applications with higher numbers. For example, an application with a deployment order of 102 is loaded before an application with a deployment order of 110. If a deployment order is not specified, the default value of 100 is assigned. If two applications have the same deployment order, the first application to be deployed is the first application to be loaded at server startup. +
The deployment order is typically specified when the application is first deployed but can also be specified or changed after initial deployment using the `set` subcommand. You can view the deployment order of an application using the `get` subcommand.
@@ -119,7 +119,7 @@ asadmin-options::
This option controls whether web sessions, SFSB instances, and persistently created EJB timers are retained between redeployments. +
The default is false. This option is supported only on the default server instance, named `server`. It is not supported and ignored for any other target. +
Some changes to an application between redeployments prevent this feature from working properly. For example, do not change the set of instance variables in the SFSB bean class. +
- For web applications, this feature is applicable only if in the `glassfish-web-app.xml` file the `persistence-type` attribute of the `session-manager` element is `file`. +
+ For web applications, this feature is applicable only if in the `payara-web.xml` file the `persistence-type` attribute of the `session-manager` element is `file`. +
For stateful session bean instances, the persistence type without high availability is set in the server (the `sfsb-persistence-type` attribute) and must be set to `file`, which is the default and recommended value. +
If any active web session, SFSB instance, or EJB timer fails to be preserved or restored, none of these will be available when the redeployment is complete. However, the redeployment continues and a warning is logged. +
To preserve active state data, Payara Server serializes the data and saves it in memory. To restore the data, the class loader of the newly redeployed application deserializes the data that was previously saved.
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/deploydir.adoc b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/deploydir.adoc
index 0de704ab7..af2b6737e 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/deploydir.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/deploydir.adoc
@@ -92,7 +92,7 @@ asadmin-options::
`--altdd`::
Deploys the application using a Jakarta EE standard deployment descriptor that resides outside of the application archive. Specify an absolute path or a relative path to the alternate deployment descriptor file. The alternate deployment descriptor overrides the top-level deployment descriptor packaged in the archive. For example, for an EAR, the `--altdd` option overrides `application.xml`. For a standalone module, the `--altdd` option overrides the top-level module descriptor such as `web.xml`.
`--runtimealtdd`::
- Deploys the application using a Payara Server runtime deployment descriptor that resides outside of the application archive. Specify an absolute path or a relative path to the alternate deployment descriptor file. The alternate deployment descriptor overrides the top-level deployment descriptor packaged in the archive. For example, for an EAR, the `--runtimealtdd` option overrides `glassfish-application.xml`. For a standalone module, the `--runtimealtdd` option overrides the top-level module descriptor such as `glassfish-web.xml` or `payara-web.xml`. Applies to Payara Server deployment descriptors only (`glassfish-*.xml`/`payara-*.xml`); the name of the alternate deployment descriptor file must begin with `glassfish-` (or `payara-` in specific cases). Does not apply to `sun-*.xml` deployment descriptors, which are deprecated.
+ Deploys the application using a Payara Server runtime deployment descriptor that resides outside of the application archive. Specify an absolute path or a relative path to the alternate deployment descriptor file. The alternate deployment descriptor overrides the top-level deployment descriptor packaged in the archive. For example, for an EAR, the `--runtimealtdd` option overrides `glassfish-application.xml`. For a standalone module, the `--runtimealtdd` option overrides the top-level module descriptor such as `payara-web.xml`. Applies to Payara Server deployment descriptors only (`glassfish-*.xml`/`payara-*.xml`); the name of the alternate deployment descriptor file must begin with `glassfish-` (or `payara-` in specific cases). Does not apply to `sun-*.xml` deployment descriptors, which are deprecated.
`--deploymentorder`::
Specifies the deployment order of the application. This is useful if the application has dependencies and must be loaded in a certain order at server startup. The deployment order is specified as an integer. The default value is 100. Applications with lower numbers are loaded before applications with higher numbers. For example, an application with a deployment order of 102 is loaded before an application with a deployment order of 110. If a deployment order is not specified, the default value of 100 is assigned. If two applications have the same deployment order, the first application to be deployed is the first application to be loaded at server startup. +
The deployment order is typically specified when the application is first deployed but can also be specified or changed after initial deployment using the `set` subcommand. You can view the deployment order of an application using the `get` subcommand
@@ -110,7 +110,7 @@ asadmin-options::
This option controls whether web sessions, SFSB instances, and persistently created EJB timers are retained between redeployments. +
The default is false. This option is supported only on the default server instance, named `server`. It is not supported and ignored for any other target. +
Some changes to an application between redeployments prevent this feature from working properly. For example, do not change the set of instance variables in the SFSB bean class. +
- For web applications, this feature is applicable only if in the `glassfish-web-app.xml` file the `persistence-type` attribute of the `session-manager` element is `file`. +
+ For web applications, this feature is applicable only if in the `payara-web.xml` file the `persistence-type` attribute of the `session-manager` element is `file`. +
For stateful session bean instances, the persistence type without high availability is set in the server (the `sfsb-persistence-type` attribute) and must be set to `file`, which is the default and recommended value. +
If any active web session, SFSB instance, or EJB timer fails to be preserved or restored, none of these will be available when the redeployment is complete. However, the redeployment continues and a warning is logged. +
To preserve active state data, Payara Server serializes the data and saves it in memory. To restore the data, the class loader of the newly redeployed application deserializes the data that was previously saved.
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/flush-connection-pool.adoc b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/flush-connection-pool.adoc
index 52221aceb..0b16602cc 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/flush-connection-pool.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/flush-connection-pool.adoc
@@ -22,7 +22,7 @@ This subcommand is supported in remote mode only.
Application Scoped Resources
-The `flush-connection-pool` subcommand can target resources that are scoped to a specific application or module, as defined in the `glassfish-resources.xml` or `payara-resources.xml` for the Payara Server domain.
+The `flush-connection-pool` subcommand can target resources that are scoped to a specific application or module, as defined in the `payara-resources.xml` for the Payara Server domain.
* To reference the `jndi-name` for an application scoped resource, perform the lookup using the `java:app` prefix.
* To reference the `jndi-name` for a module scoped resource, perform the lookup using the `java:module` prefix.
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/ping-connection-pool.adoc b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/ping-connection-pool.adoc
index 6253d132b..0f1d39959 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/ping-connection-pool.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/ping-connection-pool.adoc
@@ -26,7 +26,7 @@ This subcommand is supported in remote mode only.
Application Scoped Resources
The `ping-connection-pool` subcommand can target resources that are scoped to a specific application or module, as defined in the
-`glassfish-resources.xml` or `payara-resources.xml` for the Payara Server domain.
+`payara-resources.xml` for the Payara Server domain.
* To reference the `jndi-name` for an application scoped resource, perform the lookup using the `java:app` prefix.
* To reference the `jndi-name` for a module scoped resource, perform the lookup using the `java:module` prefix.
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/redeploy.adoc b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/redeploy.adoc
index af12a06f2..bb09d6883 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/redeploy.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/redeploy.adoc
@@ -116,7 +116,7 @@ asadmin-options::
descriptor packaged in the archive. For example, for an EAR, the `--altdd` option overrides `application.xml`. For a standalone module,
the `--altdd` option overrides the top-level module descriptor such as `web.xml`.
-`-runtimealtdd`::
- Deploys the application using a Payara Server runtime deployment descriptor that resides outside of the application archive. Specify an absolute path or a relative path to the alternate deployment descriptor file. The alternate deployment descriptor overrides the top-level deployment descriptor packaged in the archive. For example, for an EAR, the `--runtimealtdd` option overrides `glassfish-application.xml`. For a standalone module, the `--runtimealtdd` option overrides the top-level module descriptor such as `glassfish-web.xml` or `payara-web.xml`. Applies to Payara Server deployment descriptors only (`glassfish-*.xml`/`payara-*.xml`); the name of the alternate
+ Deploys the application using a Payara Server runtime deployment descriptor that resides outside of the application archive. Specify an absolute path or a relative path to the alternate deployment descriptor file. The alternate deployment descriptor overrides the top-level deployment descriptor packaged in the archive. For example, for an EAR, the `--runtimealtdd` option overrides `glassfish-application.xml`. For a standalone module, the `--runtimealtdd` option overrides the top-level module descriptor such as `payara-web.xml`. Applies to Payara Server deployment descriptors only (`glassfish-*.xml`/`payara-*.xml`); the name of the alternate
deployment descriptor file must begin with `glassfish-` (or `payara-` in specific cases). Does not apply to `sun-*.xml` deployment descriptors, which are deprecated.
`--deploymentorder`::
Specifies the deployment order of the application. This is useful if the application has dependencies and must be loaded in a certain order
@@ -147,7 +147,7 @@ asadmin-options::
The default is false. This option is supported only on the default server instance, named `server`. It is not supported and ignored for any other target. +
Some changes to an application between redeployments prevent this feature from working properly. For example, do not change the set of
instance variables in the SFSB bean class. +
- For web applications, this feature is applicable only if in the `glassfish-web-app.xml` file the `persistence-type` attribute of the
+ For web applications, this feature is applicable only if in the `payara-web.xml` file the `persistence-type` attribute of the
`session-manager` element is `file`. +
For stateful session bean instances, the persistence type without high availability is set in the server (the `sfsb-persistence-type`
attribute) and must be set to `file`, which is the default and recommended value. +
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/General Administration/Administering HTTP Connectivity.adoc b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/General Administration/Administering HTTP Connectivity.adoc
index 50960a4d0..23dc196eb 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/General Administration/Administering HTTP Connectivity.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/General Administration/Administering HTTP Connectivity.adoc
@@ -1058,13 +1058,13 @@ Defines additional properties for the configuration of a virtual server.
| *setCacheControl* | Comma separated list of Cache-Control response directives (See section 14.9 of: https://www.ietf.org/rfc/rfc2616.txt). | none
| *allowLinking* a| If set to `true`, resources that are symbolic links will be served for all applications deployed to this virtual server.
-Can be overridden for an individual application in the `glassfish-web.xml`/`payara-web.xml` deployment descriptor with:
+Can be overridden for an individual application in the `payara-web.xml` deployment descriptor with:
[source, xml]
----
-
+
-
+
----
NOTE: Setting this property to `true` on Windows systems exposes JSP source code.
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/General Administration/Administering Web Applications.adoc b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/General Administration/Administering Web Applications.adoc
index 64fd8a27b..52772336b 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/General Administration/Administering Web Applications.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/General Administration/Administering Web Applications.adoc
@@ -25,7 +25,7 @@ http://server:port/context-root/servlet-mapping?name=value
| The IP address (or host name) and optional port number. To access the default web module for a virtual server, specify only this URL section. You do not need to specify the context-root or servlet-name unless you also wish to specify name-value parameters.
| context-root
-| For an application, the context root is defined in the `context-root` element of the `application.xml`, `sun-application.xml`, or `sun-web.xml` file. For an individually deployed web module, the context root is specified during deployment. For both applications and individually deployed web modules, the default context root is the name of the WAR file minus the `.war` suffix.
+| For an application, the context root is defined in the `context-root` element of the `application.xml`, `sun-application.xml`, or `payara-web.xml` file. For an individually deployed web module, the context root is specified during deployment. For both applications and individually deployed web modules, the default context root is the name of the WAR file minus the `.war` suffix.
| servlet-mapping
| The `servlet-mapping` as configured in the `web.xml` file.
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/General Administration/Administering the Logging Service.adoc b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/General Administration/Administering the Logging Service.adoc
index abcd5b85e..85ef2e6ab 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/General Administration/Administering the Logging Service.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/General Administration/Administering the Logging Service.adoc
@@ -129,7 +129,7 @@ The following is an example of a log record formatted in the ULF format:
[source, log, subs=attributes+]
----
-[#|2013-04-18T09:27:44.315-0700|INFO|Payara Server {page-version}|jakarta.enterprise.web.core| _ThreadID=15;_ThreadName=RunLevelControllerThread-1366302462682;_TimeMillis=1366302464315;_LevelValue=800;_MessageID=AS-WEB-CORE-00306;| Setting JAAS app name glassfish-web|#]
+[#|2013-04-18T09:27:44.315-0700|INFO|Payara Server {page-version}|jakarta.enterprise.web.core| _ThreadID=15;_ThreadName=RunLevelControllerThread-1366302462682;_TimeMillis=1366302464315;_LevelValue=800;_MessageID=AS-WEB-CORE-00306;| Setting JAAS app name payara-web|#]
----
The Administration Console presents log records in a more readable display. For information about viewing log records using the Administration Console, see xref:Technical Documentation/Payara Server Documentation/General Administration/Administering the Logging Service.adoc#viewing-log-records[Viewing Log Records].
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/General Administration/Configuration Variables Reference.adoc b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/General Administration/Configuration Variables Reference.adoc
index 4dcbf8276..f4d174216 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/General Administration/Configuration Variables Reference.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/General Administration/Configuration Variables Reference.adoc
@@ -79,10 +79,10 @@ Variable references can be used inside text values in the following configuratio
Variable references can be used inside text values also in the following places within deployed applications and modules:
* Package descriptors:
-** web.xml / glassfish-web.xml
+** web.xml / payara-web.xml
** ejb-jar.xml / glassfish-ejb-jar.xml
** application.xml / glassfish-application.xml
-** glassfish-resources.xml
+** payara-resources.xml
* Framework descriptors:
** persistence.xml
** faces-config.xml
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/High Availability/Configuring HA Session Persistence and Failover.adoc b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/High Availability/Configuring HA Session Persistence and Failover.adoc
index b2f9bb845..a929aa7a8 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/High Availability/Configuring HA Session Persistence and Failover.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/High Availability/Configuring HA Session Persistence and Failover.adoc
@@ -196,7 +196,7 @@ See Also
[[configuring-availability-for-individual-web-applications]]
=== Configuring Availability for Individual Web Applications
-To enable and configure availability for an individual web application, edit the application deployment descriptor file (`glassfish-web.xml` or `payara-web.xml`).
+To enable and configure availability for an individual web application, edit the application deployment descriptor file (`payara-web.xml`).
The settings in an application's deployment descriptor override the web container's availability settings.
The `session-manager` element's `persistence-type` attribute determines the type of session persistence an application uses.
@@ -233,7 +233,7 @@ This feature was designed with the more traditional HTTP request/response commun
Another example is when a page includes many static resources, such as `JPG` files.
In these situations, most browsers will optimize the loading of these resources by using multiple parallel connections, each of which is handled by a separate request processing thread. If the application has already established a session, then this will also involve more than one thread at a time accessing a single `HttpSession`.
-The solution in such cases is to use the `relaxVersionSemantics` property in the `glassfish-web.xml` or `payara-web.xml` deployment descriptor file for the application.
+The solution in such cases is to use the `relaxVersionSemantics` property in the `payara-web.xml` deployment descriptor file for the application.
This enables the web container to return for each requesting thread whatever version of the session that is in the active cache regardless of the version number.
diff --git a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Security Guide/Administering Message Security.adoc b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Security Guide/Administering Message Security.adoc
index 7c5573ad2..5c5b88b31 100644
--- a/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Security Guide/Administering Message Security.adoc
+++ b/docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Security Guide/Administering Message Security.adoc
@@ -423,7 +423,7 @@ You can configure a Jakarta Authentication Server Authentication Module (SAM) as
. Create the message security provider by using the xref:Technical Documentation/Payara Server Documentation/Command Reference/create-message-security-provider.adoc#create-message-security-provider[`create-message-security-provider`] subcommand.
. Bind the message security provider for use with your application.
+
-You do this by defining the `httpservlet-security-provider` attribute in the `glassfish-web.xml` or `payara-web.xml` deployment descriptor corresponding to your application.
+You do this by defining the `httpservlet-security-provider` attribute in the `payara-web.xml` deployment descriptor corresponding to your application.
+
Set the value of the attribute to the provider name you assigned to the message security provider. For example, if you use MySAM when you create the message security provider the entry would be `httpservlet-security-provider="MySAM"`.
. Restart the server instance.