Web Resource Override

From DOC

Standard JEE web resources are all packaged within the tolvenWEB.war file (part of the tolven.ear file). In Tolven, the overall structure of applications are controlled by dynamic metatdata that is independent of the software distributed by Tolven. This metadata calls upon resources (web page snippets, css, etc) that are normally defined within the Tolven core. If you wish to extend or override any of these resources, define the server runtime property:

tolven.web.resources=file:///usr/local/tolven-config/web/
or 
tolven.web.resources=file:///c:/tolven-config/web/

This directs the web server to look in the specified location before looking within the core web resources.

As described in the previous section, this attribute can also be overridden for different listing (local) IP addresses. Therefore, users connecting to Tolven via different IP addresses may see different page renderings and behavior.

The resource search occurs in this order:

Step	Propert Used	Example
IP-specific override	tolven.web.resources.<localAddr>	tolven.web.resources.1.2.3.4=file:///c:/tolven-config/specialWeb/
general override	tolven.web.resources	tolven.web.resources=file:///c:/tolven-config/web/
core resource	internal

The directory path specified prepends the requested resource. For example, using the configuration above, when Tolven looks up the login page resource, it looks for /web/private/login.xhtml. If a user connects to Tolven on IP address 1.2.3.4, and a file called

c:/tolven-config/specialWeb/private/login.xhtml

exists, it will be used.

If not, or if a user connected to Tolven on a different IP address and,

c:/tolven-config/web/private/login.xhtml

exists, then it will be used. Otherwise the internal resource will be used.