Message-ID: <1658296438.171.1406130595046.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_170_1674310497.1406130595045" ------=_Part_170_1674310497.1406130595045 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
In some cases, it is necessary to enrich your container configuration wi=
th extra files. This can be done using Cargo's
ion, accessible via the Cargo APIs.
The advantage of using this option is that it can replace configuration properties in your =
files: simply use, for example,
@cargo.servlet.port@ to have i=
t replaced with the port on which the Servlet/JSP container is listening to=
You might for example want to add the advanced login configuration to yo= ur JBoss instance.
To define a central
jetty-env.xml file and reuse it la=
ter from your WARs, you can proceed as follows:
As explained on the top of this page, use a standalone local container (i.e.= , not an embedded configuration)
Make sure the property
cargo.jetty.createContextXml) is set to&nb=
false; so that CARGO doesn't create a
l file for your WAR's deployable but rather copies it from the sourc=
e to the configuration home folder.
For each deployable, make sure the deployable is defined as an expan= ded WAR; as explained on the Static deployment of expanded WAR page.
Finally, for each deployable, add the following to your local contai= ner's configuration:
webapp-context is the Web application'=
webappssubdirectory of the J= etty configuration
jetty-env.x= mlfile into that WAR's WEB-INF directory
As a reference, please find below the full configuration for Jetty 7.x:<= /p>