GWC_JS_LOOKUP

Configure the GWC_JS_LOOKUP_PATH element to specify the location of your customized Genero Web Client for JavaScript (GWC-JS) front-end.

Syntax

<GWC_JS_LOOKUP_PATH>gwc_js_userdir;docroot</GWC_JS_LOOKUP_PATH>

The GWC_JS_LOOKUP_PATH allows for multiple directory paths to be specified. The separator between resource paths is a semi-colon (;).

Usage

You use this element to specify the path to the GWC-JS. Examples are shown of how to specify this using the GWC_JS_LOOKUP_PATH and with dispatcher overrides.

Usage example

<GWC-JS-LOOKUP-PATH>$(res.path.gwcjs.user);$(res.path.docroot)</GWC-JS-LOOKUP-PATH>

In this example, the GAS first searches the directory specified by the resource res.path.gwcjs.user. This resource is not defined in the GAS configuration file by default, however it can be set as required at runtime.

If the specified customization folder is not found, the GAS then looks for the GWC-JS directory at the default location defined by the resource res.path.docroot, which is defined by default in the GAS configuration file as $FGLASDIR/web.

Note: The GAS provides a dedicated URL as the document root where your customized GWC-JS directory is located (see ua/w/ in Application URIs).

If the directory is found, the requested file is sent. If the file does not exist, no additional searching is performed. This is to avoid the risk of mixing up files in other GWC-JS versions that may be located in various directories in these paths.

Set GWC_JS_LOOKUP_PATH at runtime

httpdispatch -E res.path.gwcjs.user=<directory-of-your-choice>

This example sets the location of your customized GWC-JS files with the dispatcher switch (-E) by creating or overwriting the res.path.gwcjs.user resource with the path to the directory holding the customization folder.

Child elements

There are no child elements.

Parent elements

This element is a child of the following element: INTERFACE_TO_CONNECTOR