You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 48bd451
Browse filesBrowse the repository at this point in the historyBrowse files
<h3id="JettyRemoteDeployer-Downloadingtheremotedeployer">Downloading the remote deployer</h3>
593
593
<p>Two versions of the Jetty remote deployer WAR are available on the <ahref="Downloads.html">Cargo downloads</a> page (scroll down to the <strong>Tools</strong> section):</p>
594
594
<ul>
595
-
<li><code>cargo-jetty-11-onwards-deployer</code>: The Deployer Web application for the Jetty remote containers, which must have been deployed to Jetty before using the CARGO remote deployer. Designed to work with Jetty 11.x onwards (Jetty from Eclipse.org, implementing Jakarta EE)</li>
596
-
<li><code>cargo-jetty-10-deployer</code>: The Deployer Web application for the Jetty remote containers, which must have been deployed to Jetty before using the CARGO remote deployer. Designed to work with Jetty 10.x (Jetty from Eclipse.org)</li>
597
-
<li><code>cargo-jetty-7-to-jetty-9-deployer</code>: The Deployer Web application for the Jetty remote containers, which must have been deployed to Jetty before using the CARGO remote deployer. Designed to work with Jetty 7.x to Jetty 9.x (Jetty from Eclipse.org)</li>
598
-
<li><code>cargo-jetty-6-and-earlier-deployer</code>: The Deployer Web application for the Jetty remote containers, which must have been deployed to Jetty before using the CARGO remote deployer. Designed to work with Jetty 6.x and earlier (Jetty from Mortbay.org)</li>
595
+
<li>
596
+
<p><code>cargo-jetty-12-deployer</code>: The Deployer Web application for the Jetty remote containers, which must have been deployed to Jetty before using the Codehaus Cargo remote deployer. Designed to work with Jetty 12.1.x (Jetty from Eclipse.org, implementing Java EE and various Jakarta EE versions at the same time), it is sadly <u>not compatible with Jetty 12.0.x</u>.</p>
597
+
</li>
598
+
<li>
599
+
<p><code>cargo-jetty-11-deployer</code>: The Deployer Web application for the Jetty remote containers, which must have been deployed to Jetty before using the Codehaus Cargo remote deployer. Designed to work with Jetty 11.x (Jetty from Eclipse.org, implementing Jakarta EE)</p>
600
+
</li>
601
+
<li>
602
+
<p><code>cargo-jetty-10-deployer</code>: The Deployer Web application for the Jetty remote containers, which must have been deployed to Jetty before using the Codehaus Cargo remote deployer. Designed to work with Jetty 10.x (Jetty from Eclipse.org)</p>
603
+
</li>
604
+
<li>
605
+
<p><code>cargo-jetty-7-to-jetty-9-deployer</code>: The Deployer Web application for the Jetty remote containers, which must have been deployed to Jetty before using the Codehaus Cargo remote deployer. Designed to work with Jetty 7.x to Jetty 9.x (Jetty from Eclipse.org)</p>
606
+
</li>
607
+
<li>
608
+
<p><code>cargo-jetty-6-and-earlier-deployer</code>: The Deployer Web application for the Jetty remote containers, which must have been deployed to Jetty before using the Codehaus Cargo remote deployer. Designed to work with Jetty 6.x and earlier (Jetty from Mortbay.org)</p>
609
+
</li>
599
610
</ul>
600
611
<p>Please make sure to download and install the correct flavour for your Jetty version.</p>
<p>Define a security realm, which can be per-webapp (i.e., by adding a <code>jetty-web.xml</code> file to the WAR) or global (i.e., for all applications deployed on that Jetty server). You can learn more about both methods on the Jetty documentation: <ahref="http://www.eclipse.org/jetty/documentation/current/configuring-security-authentication.html#d0e5513">http://www.eclipse.org/jetty/documentation/current/configuring-security-authentication.html#d0e5513</a></p>
626
649
</li>
627
650
</ol>
628
-
<p>To try the security settings, you can try to visit the <code>/cargo-jetty-deployer</code> context on your server, for example <ahref="http://production27:8080/cargo-jetty-deployer">http://production27:8080/cargo-jetty-deployer</a>, using any Web browser. If security is configured well, it should:</p>
651
+
<p>To try the security settings, you can try to visit the <code>/cargo-jetty-deployer</code> context (on Jetty 12.x, the <code>/cargo-jetty-deployer-eeXX</code> context where XX is the Jetty EE version and multiple EE versions being active at the same time is supported) on your server, for example <ahref="http://production27:8080/cargo-jetty-deployer">http://production27:8080/cargo-jetty-deployer</a>, using any Web browser. If security is configured well, it should:</p>
629
652
<ul>
630
-
<li>Ask for a login and password</li>
631
-
<li>Ask again if the login is not valid</li>
632
-
<li>If the login is valid, show a page saying: <code>Command / is unknown</code></li>
653
+
<li>
654
+
<p>Ask for a login and password</p>
655
+
</li>
656
+
<li>
657
+
<p>Ask again if the login is not valid</p>
658
+
</li>
659
+
<li>
660
+
<p>If the login is valid, show a page saying: <code>Command / is unknown</code></p>
<p><strong>Unexpected end of file from server and maxIdleTime parameter</strong></p>
715
752
<p>By default, Jetty sets the <code>maxIdleTime</code> parameter in the <code>etc/jetty.xml</code> file 30 seconds. This means that if the actual deployment takes more than 30 seconds, you might get error messages like:</p>
0 commit comments