FISH-10296 FISH-11137 Document New Deployment Property and System Property

docs/modules/ROOT/pages/Technical Documentation/Application Development/Class Loaders.adoc

@@ -141,6 +141,9 @@ This command accepts the `--type` argument, which accepts the following options:
 `common`:: The library is installed as a common library into the `lib` directory in the Payara Server domain
 `ext`:: The library is installed as an "extension" library into the `lib/ext` directory in the Payara Server domain
 `app`:: the library is installed as an application library into the `lib/applibs` directory in the Payara Server domain
+ifeval::["{page-site-edition}" == "community"]
+`war`:: the library is installed as a WAR library into the `lib/warlibs` direcotyr in the Payara Server domain
+endif::[]
 
 [[common-libraries]]
 ==== Common Libraries
@@ -194,6 +197,16 @@ If multiple applications or modules refer to the same libraries, classes in thos
 NOTE: If you see an access control error message when you try to use a library, you may need to grant permission to the library in the
 `server.policy` file. For more information, see xref:Technical Documentation/Application Development/Securing Applications.adoc#changing-permissions-for-an-application[Changing Permissions for an Application].
 
+ifeval::["{page-site-edition}" == "community"]
+[[War-libraries]]
+==== WAR Libraries
+
+Libraries stored in this directory allows a developer to create and deploy skinny WARs, as the libraries stored in this directory are subject to additional annotation and extension scanning & processing for CDI, EJB, Servlet, and more.
+Unlike common and application libraries (those stored in `domain_dir/lib` and `domain_dir/lib/applibs` respectively), warlibs are cached and don't dynamically update if the files within the directory are modified.
+
+These libraries are only used by applications which are deployed with the `warlibs` property set to `true`. See the xref:Technical Documentation/Command Reference/deploy.adoc#changing-permissions-for-an-application[deploy command documentation].
+endif::[]
+
 [[packaging-the-client-jar-for-one-application-in-another-application]]
 === Packaging the Client JAR for One Application in Another Application
 

docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/add-library.adoc

@@ -50,6 +50,10 @@ Adds the library files to the Common class loader directory, `domain-dir/lib`. T
 Adds the library files to the Java optional package directory, `domain-dir/lib/ext`.
 `app`;;
 Adds the library files to the application-specific class loader directory, `domain-dir/lib/applibs`.
+ifeval::["{page-site-edition}" == "community"]
+`war`;;
+Adds the library files to the war-packaged class loader directory, `domain-dir/lib/warlibs`.
+endif::[]
 +
 For more information about these directories, see
 xref:Technical Documentation/Application Development/Class Loaders.adoc#class-loaders[Class Loaders] in the Payara Server Application Development section.

docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/Command Reference/deploy.adoc

@@ -169,6 +169,13 @@ asadmin-options::
   `allowFacesCdiInitialisation={false|true}`;;
     If set to true, enables scanning for Jakarta Faces content in the application, and if detected, forcing an attempt to initialise CDI and Weld even if bean discovery is set to "none". Default is false.
 
+ifeval::["{page-site-edition}" == "community"]
+  `warlibs={false|true}`;;
+      If set to true, enables an application to make use of shared libraries installed to `domain_dir/lib/warlibs`. Default is `false`. +
+      Libraries stored in this directory allows a developer to create and deploy skinny WARs, as the libraries stored in this directory are subject to additional annotation and extension scanning & processing for CDI, EJB, Servlet, and more.
+      Unlike common and application libraries (those stored in `domain_dir/lib` and `domain_dir/lib/applibs` respectively), warlibs are cached and don't dynamically update if the files within the directory are modified.
+endif::[]
+
 Other available properties are determined by the implementation of the component that is being redeployed. +
 For components packaged as OSGi bundles (`--type=osgi`), the `deploy` subcommand accepts properties arguments to wrap a WAR file as a WAB (Web Application Bundle) at the time of deployment. The subcommand looks for a key named `UriScheme` and, if present, uses the key as a URL stream handler to decorate the input stream. Other properties are used in the decoration process. For example, the Payara Server OSGi web container registers a URL stream handler named `webbundle`, which is used to wrap a plain WAR file as a WAB. For more information about usage, see the example in this help page.
 

docs/modules/ROOT/pages/Technical Documentation/Payara Server Documentation/General Administration/General Runtime Administration.adoc

@@ -610,6 +610,20 @@ This option is intended to make member partitioning work consistently for highly
 +
 CAUTION: Use this option with extreme care
 
+//Conditional block, only rendered for the Community Edition
+ifeval::["{page-site-edition}" == "community"]
+`fish.payara.ear-combined-cdi-deployment`::
+This option defines whether or not to restrict CDI scanning when multiple WARs exist within an EAR.
++
+The CDI scanning behaviour for WARs and libraries contained with an EAR changed, to allow split CDI bean deployments.
++
+This option is intended to allow a user to revert the CDI scanning behaviour to how it operated in prior versions.
++
+The behaviour in prior versions aligned with `false`.
++
+Default is undefined (`true`)
+endif::[]
+
 //TODO - Not sure what this feature is for and how it works or it is properly supported.
 
 [[using-configuration-modularity]]