Application configuration

Add noNamespaceSchemaLocation attribute in external application configuration file

All external application configuration files must be updated by adding the noNamespaceSchemaLocation attribute. When defining external application files, the "noNamespaceSchemaLocation" attribute should have this value:

  • For web applications: xsi:noNamespaceSchemaLocation="http://www.4js.com/ns/gas/2.11/cfextwa.xsd"
  • For web services applications:xsi:noNamespaceSchemaLocation="http://www.4js.com/ns/gas/2.11/cfextws.xsd"

For example, consider the following examples of the Edit.xcf web application configuration file:

The old Edit.xcf: 
01  <?xml version="1.0" encoding="UTF-8"?>
02  <APPLICATION Parent="defaultgwc">
03    <EXECUTION>
04      <PATH>$(res.path.fgldir.demo)/Widgets</PATH>
05    </EXECUTION>
06  </APPLICATION>
The new Edit.xcf: 
01  <?xml version="1.0" encoding="UTF-8"?>
02  <APPLICATION Parent="defaultgwc"
03      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
04      xsi:noNamespaceSchemaLocation="http://www.4js.com/ns/gas/2.11/cfextwa.xsd">
05    <EXECUTION>
06      <PATH>$(res.path.fgldir.demo)/Widgets</PATH>
07    </EXECUTION>
08  </APPLICATION>
If this attribute is missing, the corresponding application will fail to start, and the following message will be written to the log file:
Can't find 'noNamespaceSchemaLocation' attribute in external
 application file '/home/f4gl/gwc/app/Edit.xcf'.

Output drivers for Internet Explorer

Specific output drivers DUA_AJAX_HTML and DUA_PAGE_HTML have been added to support certain features (such as the Canvas widget) on Internet Explorer. As a result, all customized snippets specified for DUA_AJAX will also need to be specified for DUA_AJAX_HTML.

The original CardStep1.xcf:
01  <?xml version="1.0" encoding="UTF-8"?>
02  <APPLICATION Parent="defaultgwc"
03    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
04    xsi:noNamespaceSchemaLocation="http://www.4js.com/ns/gas/2.11/cfextwa.xsd">
05    <EXECUTION>
06      <PATH>$(res.path.demo.app)/card/src</PATH>
07      <MODULE>card.42r</MODULE>
08    </EXECUTION>
09    <OUTPUT>
10    <MAP Id="DUA_AJAX">
11      <THEME>
12        <SNIPPET Id="Image" Style="Picture">
           $(res.path.demo.app)/card/tpl/set1/Image.xhtml</SNIPPET>
13      </THEME> 
14    </MAP>
15    </OUTPUT>
16  </APPLICATION>
The new CardStep1.xcf:
01  <?xml version="1.0" encoding="UTF-8"?>
02  <APPLICATION Parent="defaultgwc"
03    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
04    xsi:noNamespaceSchemaLocation="http://www.4js.com/ns/gas/2.11/cfextwa.xsd">
05    <EXECUTION>
06      <PATH>$(res.path.demo.app)/card/src</PATH>
07      <MODULE>card.42r</MODULE>
08    </EXECUTION>
09    <OUTPUT>
10    <MAP Id="DUA_AJAX">
11      <THEME>
12        <SNIPPET Id="Image" 
           Style="Picture">$(res.path.demo.app)/card/tpl/set1/Image.xhtml
          </SNIPPET>
13      </THEME> 
14    </MAP>
15    <MAP Id="DUA_AJAX_HTML">
16      <THEME>
17        <SNIPPET Id="Image"
           Style="Picture">$(res.path.demo.app)/card/tpl/set1/Image.xhtml
        </SNIPPET>
18      </THEME> 
19    </MAP>
20    </OUTPUT>
21  </APPLICATION>

Likewise, all customized snippets specified for DUA_PAGE will also need to be specified for DUA_PAGE_HTML.

To change output drivers default behaviors, see Automatic Discovery of User Agent topic in the Genero Application Server User Guide version 2.20.

URL parameters

By default, parameters in the URL are not taken into account. They are not transmitted to the DVM. Only the parameters defined in the configuration files are transmitted.

To use URL parameters, in the EXECUTION tag, you have to set AllowUrlParameters to TRUE.

Caution! Parameters are transmitted to the DVM in this order: configured parameters in PARAMETERS tag followed by the URL parameters.