From 102a9628af0df8095ef2a28b9d7170dfb956f448 Mon Sep 17 00:00:00 2001 From: alitokmen Date: Sun, 27 Aug 2023 22:50:31 +0200 Subject: [PATCH] Update outgoing links for JBoss and JSR-88 container features --- cargo/JBoss+Remote+Deployer.html | 2 +- cargo/JSR88.html | 26 ++++++++------------------ 2 files changed, 9 insertions(+), 19 deletions(-) diff --git a/cargo/JBoss+Remote+Deployer.html b/cargo/JBoss+Remote+Deployer.html index 17184be2f9..474db8c895 100644 --- a/cargo/JBoss+Remote+Deployer.html +++ b/cargo/JBoss+Remote+Deployer.html @@ -487,7 +487,7 @@

JBoss 5.0.x, 5.1.x, -

That is a known bug, documented in http://community.jboss.org/wiki/WhydoIgetasocketconnectionerrorwhenusingremoteJBossAS and the solution presented on that document is to use a cron job as the root user to fix the file when it gets broken.

+

That is a known bug, documented in https://developer.jboss.org/docs/DOC-16380, and the solution presented on that document is to use a cron job as the root user to fix the file when it gets broken.

First, create the correct version of /etc/hosts and save it somewhere, such as /etc/hosts.fixed, and populate it with the following contents (replace myhost with the hostname of your computer, as reported by the hostname command, and the correct IP assignment, as reported by ipconfig):

diff --git a/cargo/JSR88.html b/cargo/JSR88.html index 0d4ff04452..6489c7edd0 100644 --- a/cargo/JSR88.html +++ b/cargo/JSR88.html @@ -301,26 +301,16 @@

Explanation

-

GlassFish 3.x to 5.x and Payara

-
-

GlassFish 6.x and remote deployment

-
-

The GlassFish 6.x container doesn't have any remote deployers yet, as GlassFish 6.0 lacks JSR-88 support and it is unclear whether this will be included in a future release.

-

Until then, please follow the remote deployment instructions for GlassFish 6.x.

-
-
-
-

Remote deployment to recent Payara versions

-
-

Recent versions of Payara might have issues getting deployables uploaded via JSR-88, resulting in errors such as:

-
-
- 
Distributing failed: Action failed Deploying application to target server failed; File not found
-
-
-

If you encounter such errors, please follow the remote deployment instructions for recent Payara versions.

+

GlassFish 6.x onwards, as well as newer versions of Payara

+

The GlassFish 6.x container doesn't have any remote deployers yet, as GlassFish 6.0 lacks JSR-88 support and it is unclear whether this will be included in a future release. Until then, please follow the remote deployment instructions for GlassFish 6.x.

+

Recent versions of Payara might have issues getting deployables uploaded via JSR-88, resulting in errors such as:

+
+
+ 
Distributing failed: Action failed Deploying application to target server failed; File not found
+

If you encounter such errors, please follow the remote deployment instructions for recent Payara versions.

+

GlassFish 3.x to 5.x and Payara

The GlassFish 3.x, GlassFish 4.x, GlassFish 5.x and Payara remote containers use the JSR-88 API. For the connection to succeed, the following JARs need to be in the container classpath or in the current Java Thread's context classloader:

  • deployment-client.jar and its dependencies - for GlassFish 3.x, these seem to be: