Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This configuration is used for logback logging and stores the log files to the  ${PATH_SET_BY_SETUP}. 

Configuration of the web application

The web application is configured in a xml file, which

  • contains the configuration of the context of the web application.
  • is named the same as the war file.
  • resides in the same directory as the war file (deployment with Jetty, Tomcat has a separate directory for context files ).

Image Removed

In the configuration set the context to /jade-history-viewer to make sure the web application is reachable at http://<host>:<port>/jade-history-viewer .

When no context is configured there is still the fallback to the default setting which simply uses a context with the same name as the war file (e.g. jade-history-viewer-1.8.0 or jade-history-viewer-1.8-4236-26901), which

  • contains version information and therefore will get quite confused after some time.
  • changes with each new version(e.g. update of version 1.8.0 to 1.8.1).

Using a context configuration has the following advantages:

  • The (Web) adresse is easier to read.
  • The (Web) adresse doesn´t have to be changed in the bookmarks of clients each time a new version comes out.

jade-history-<version>.xml example for a jetty context configuration

Panel
borderColorgrey
borderWidth1
borderStylesolid

<?xml version="1.0" encoding="ISO-8859-1"?>
<Configure class="org.eclipse.jetty.webapp.WebAppContext">
<Set name="contextPath">/jade-history-viewer</Set>
<Set name="war">/opt/web/jetty_base/webapps/jade-history-viewer-<version>.war</Set>
<Set name="extractWAR">true</Set>
</Configure>