Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesTo deploy a WAR at a chosen Tomcat URL, either rename the archive to match the context path or define a Context descriptor. For example, orders.war deploys at /orders, ROOT.war becomes the root application at /, and foo#bar.war represents /foo/bar. Use a per-host Context XML when the WAR must keep its filename, lives outside the Host appBase, or needs an explicit external docBase.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
What a Tomcat context path controls
A Tomcat Context represents one web application. Catalina chooses a Context by matching the longest request-URI prefix against the configured Context paths. The empty Context path is the default application, so a root deployment handles requests beginning at / while a Context at /orders handles requests beginning with that prefix.
As an Amazon Associate I earn from qualifying purchases.
The path is independent of the WAR’s internal Java package names. It is the URL prefix Tomcat uses when routing requests to that application. If an application is deployed from orders.war, its expected URL is normally http://host:port/orders/; changing the context path changes that prefix without requiring a different application archive.
Choose the deployment method
| Method | How the path is selected | Must the WAR filename change? | Where the application is defined | Best use |
|---|---|---|---|---|
| Filename-based auto-deployment | Tomcat derives the path from the basename during deployOnStartup or autoDeploy. |
Yes, unless the existing basename already produces the desired path. | The Host appBase, commonly webapps. |
Simple drop-in deployments. |
| Per-host Context XML | The descriptor’s path attribute selects the URL prefix. |
No. | $CATALINA_BASE/conf/[enginename]/[hostname]/, with an optional external docBase. |
Stable names, external WARs, and explicit configuration. |
| Embedded Context XML | The packaged descriptor can describe the application, subject to Host policy and deployment rules. | Not necessarily, but it cannot rename a filename-derived auto-deployment. | META-INF/context.xml inside the application. |
Application-packaged settings where the Host permits them. |
server.xml Context |
The Context element in the server configuration supplies the path and deployment settings. | No. | server.xml. |
Environments that intentionally manage Contexts centrally. |
| Tomcat Manager | An explicit path parameter sets the path; without one, the WAR filename without .war is used. |
No when a path is supplied. | Manager deployment request and the resulting Context. | Remote or administrative deployments. |
Per-host XML takes precedence over a packaged META-INF/context.xml. The Host’s deployXML and copyXML settings also determine which descriptor sources Tomcat will honor.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
Method 1: set the path by renaming the WAR
Filename deployment is the shortest route when automatic deployment is enabled. Tomcat removes the .war extension and uses the remaining basename as the Context path.
Deploy at a single-level path
- Stop or undeploy the existing application if its old Context is still present. This prevents an old exploded directory or Context from continuing to serve the previous URL.
- Rename the archive to the desired basename. For a URL prefix of
/orders, renamebuild.wartoorders.war. - Copy
orders.warinto the Host’sappBase, commonly thewebappsdirectory. - With
autoDeployordeployOnStartupenabled, Tomcat deploys the archive as the/ordersContext. - Request the application using the intended prefix, such as
http://host:port/orders/, and check the Catalina log or Manager application for the deployed Context and startup result.
Deploy as the root application
Use the exact basename ROOT.war to select the empty Context path. The application then serves at the host root, for example http://host:port/, rather than under /ROOT. Remove or undeploy any previous root application before deploying the replacement; otherwise stale exploded content can make it appear that the new archive was ignored.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Deploy at a nested path
Tomcat encodes a multi-level Context path in the filename with a hash character. The path /foo/bar is represented by foo#bar.war. Copy that file to the Host appBase with automatic deployment enabled, then verify the URL prefix at /foo/bar.
The filename method is operationally simple, but it couples the public URL to the archive basename. It also does not provide a way to keep a generic build name while selecting a different path.
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
Method 2: define a per-host Context descriptor
A per-host descriptor gives the path an explicit value and can point to a WAR outside the Host’s appBase. Create one XML descriptor in the Host-specific configuration directory:
<Context path="/orders" docBase="/srv/apps/orders.war" />How to use the descriptor
- Identify the Engine and Host names used by the server.
- Create the descriptor in
$CATALINA_BASE/conf/[enginename]/[hostname]/, using the filename and Host configuration that correspond to the intended deployment. - Set
pathto the desired URL prefix, such as/orders. Use the empty path only when you are deliberately defining the root application. - Set
docBaseto the external WAR or directory, for example/srv/apps/orders.war. - Deploy or restart according to the server’s normal configuration process, then check the Context name and startup result in Manager or the Catalina log.
The per-host descriptor overrides a packaged descriptor. This makes it the appropriate place to enforce an operational path when an application contains its own META-INF/context.xml.
Using docBase safely
docBase identifies the directory or WAR that supplies the application. Tomcat restricts when docBase may be set for an application located in the Host’s appBase; do not assume that adding an arbitrary docBase to an appBase-local deployment is valid. An external path, such as /srv/apps/orders.war, is the clear use case for a per-host descriptor.
If the external location is changed through a symlink, a simple Context reload is not sufficient. The Context reference requires a restart or an undeploy followed by a redeploy for symlink changes to take effect.
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
Embedded META-INF/context.xml: what it can and cannot do
A WAR may contain a Context descriptor at META-INF/context.xml. That file is one of Tomcat’s supported descriptor locations, but it is not a universal method for renaming a WAR deployed by filename. When the Host derives deployment from the archive basename, the context path may not be defined in the embedded descriptor. In practical terms, placing path="/orders" inside a WAR named build.war does not reliably turn that filename-derived deployment into /orders.
Use the filename itself for automatic appBase deployment, or move the path definition to a per-host descriptor or server.xml. If a packaged descriptor seems to be ignored, inspect the Host’s deployXML setting.
Method 3: deploy through Tomcat Manager
Tomcat Manager can deploy either a WAR or a directory. If no path parameter is supplied, Manager uses the directory name or the WAR filename without the .war extension as the Context path. Thus a file named orders.war becomes /orders when deployed without an explicit path.
Supplying a Context XML
A Manager deployment can use a Context XML that defines path and docBase. However, if the deployment request also supplies a WAR or directory URL, that explicitly supplied application takes precedence over the XML’s docBase. Make sure the URL and descriptor point to the artifact you actually intend to deploy.
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
Manager checks after deployment
- Confirm that the Manager application lists the expected Context path, including the leading slash or the empty root path.
- Open the application at the selected prefix rather than at the original WAR filename.
- Review Catalina logs for deployment errors, duplicate Contexts, or a failed startup.
- Undeploy the old Context before reusing its path if stale content remains.
Manager behavior and available deployment fields can vary with the Tomcat release and server configuration, so verify the procedure against the version you operate.
Context descriptor locations and precedence
Tomcat recognizes three principal places for Context definitions:
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →- Packaged:
META-INF/context.xmlinside the application. - Per-host: an XML file under
$CATALINA_BASE/conf/[enginename]/[hostname]/. - Central: a Context element in
server.xml.
For a given application, the per-host descriptor takes precedence over the packaged descriptor. This precedence lets an administrator override application-supplied settings without rebuilding the WAR. A Context declared in server.xml is managed centrally and follows the server configuration’s restart requirements.
Deployment policy: deployXML and copyXML
deployXML=false
When the Host has deployXML=false, Tomcat ignores packaged Context descriptors. A WAR can still be deployed, but settings that exist only in its META-INF/context.xml will not be applied. Put the required Context definition in the per-host configuration directory or in server.xml instead.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
Both deployXML and copyXML set to false
With both options disabled, only Contexts declared in server.xml deploy. Changes to those Contexts require a server restart. This is a deliberate administrative policy, not a symptom of a malformed WAR.
Why the WAR still opens under its old filename
The old archive or exploded directory is still deployed
Tomcat may still have the former Context or an exploded directory created from the old basename. Stop or undeploy that application, remove stale exploded content according to your deployment procedure, and deploy the archive again under the intended name.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Automatic deployment is disabled
The filename method depends on autoDeploy or deployOnStartup. If neither deployment path is active, copying or renaming a WAR will not create the new Context automatically; use an explicit Context definition or the administrative deployment mechanism enabled for the server.
The embedded descriptor was expected to rename the application
Filename-derived deployment takes precedence for the path. Rename the archive, create a per-host descriptor, or define the Context centrally instead of relying on META-INF/context.xml to change the URL.
The Host is ignoring packaged XML
Check deployXML. A value of false intentionally disables packaged descriptors. If copyXML is also false, move the definition to server.xml and restart when changing it.
The request uses the wrong prefix
Check the exact mapping: orders.war is /orders, ROOT.war is the empty root path, and foo#bar.war is /foo/bar. Context matching uses the longest URI prefix, so a more-specific Context can receive a request instead of a shorter one.
Recommended Free Tools
Verification checklist
- Write down the intended URL prefix, including whether it is the root path, a single segment, or a nested path.
- Confirm the selected deployment method and its prerequisites: automatic deployment for filename mapping, a valid per-host descriptor for explicit mapping, or an enabled Manager deployment.
- Check the actual archive basename and remove the
.warextension when predicting the automatic path. - For nested paths, verify that each slash is represented by the filename encoding, such as
foo#bar.warfor/foo/bar. - Inspect Manager and Catalina logs for the Context name and startup result.
- Request the application at the intended prefix and confirm that the old prefix no longer serves the application.
- If a descriptor is ignored, inspect Host
deployXML,copyXML, descriptor precedence, and whether the Context is declared only inserver.xml. - When changing an external symlink target, restart or undeploy and redeploy; do not rely on a reload alone.
Practical decision guide
- Choose filename mapping when you control the archive name, the WAR belongs in the Host
appBase, and the desired path can follow Tomcat’s basename rules. - Choose a per-host descriptor when the WAR must retain a build-oriented name, resides outside
appBase, or needs an explicit externaldocBase. - Choose Manager when deployment is performed administratively and you need to provide a path or artifact URL at deployment time.
- Choose
server.xmlonly when Contexts are intentionally managed centrally and restart-based configuration changes are acceptable.
The dependable rule is to make the path explicit in the mechanism that owns deployment: the filename for automatic appBase deployment, a per-host or central Context for administrator-controlled mapping, or Manager’s path parameter for an administrative deployment request.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
