...
NXML is deprecated in favor of XAL
To run your application in NXML compatibility mode, set this property in the nexaweb-client.xml.
| Code Block |
|---|
<application-type>NXML</application-type> |
XAL does not support NFC
If your application relies heavily on NFC, do not migrate to XAL. XAL does not have an equilvalent set of typesafe wrappers available in 4.5.
...
The following option flags have been added to the nexaweb-client.xml configuration file. See below for details on each one.
| Code Block |
|---|
<ensure-pre-4-dot-2-mco-string-argument-compatibility>
<ensure-pre-4-dot-2-macro-compatibility>
<ensure-pre-4-dot-2-resolution-syntax-compatibility> |
Resolution Syntax
Using {...} as a text node or attribute is now interpreted as text resolution. In an attribute or text node { and } must be escaped as \{ and \} respectively. \ should be escaped as \\. The resolution can be turned off with the client.xml parameter
| Code Block |
|---|
<ensure-pre-4-dot-2-resolution-syntax-compatibility> |
For more details on text resolution (open).
...
To disable the new escaping syntax set
| Code Block |
|---|
<ensure-pre-4-dot-2-mco-string-argument-compatibility> |
to false in client.xml.
Macros
If you were using macros prior to Nexaweb's 4.2 release and those macros contained any of the MessageFormat special characters, you may wish to disable the MessageFormat functionality to ensure that your macros continue to function as before. This can be done by changing the
| Code Block |
|---|
<ensure-pre-4-dot-2-macro-compatibility> |
value to true in your nexaweb-client.xml file:
| Code Block |
|---|
|
<ensure-pre-4-dot-2-macro-compatibility>
true
| Code Block |
|---|
</ensure-pre-4-dot-2-macro-compatibility> |
...
An example of this is the single quote character within macro calls. This means that
| Code Block |
|---|
<xu:replace select="id('panel1')"> |
becomes
| Code Block |
|---|
...
<xu:replace select="id(''panel1'')"> |
Other Changes
The attribute fontColorDisabled will now inherit from parent to children.
...
Where the following XUpdate statement used to operate on the UI Document:
| Code Block |
|---|
<xu:modifications xmlns:xu="http://nexaweb.com/xupdate"> |
the new syntax is:
| Code Block |
|---|
<xu:modifications document="nxml" xmlns:xu="http://nexaweb.com/xupdate"> |
For a dataset named "MyDoc" the old syntax was:
...
| Code Block |
|---|
<xu:modifications dataset="MyDoc" xmlns:xu="http://nexaweb.com/xupdate"> |
the new sytax is:
...
| Code Block |
|---|
<xu:modifications document="MyDoc" xmlns:xu="http://nexaweb.com/xupdate"> |
If the document attribute is not present, the "nxml" document is used by default.
...