Versions Compared

Key

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

New Features

SOA Integration through Data Services

"Integrate with enterprise data"

...

See the documentation on data services.


Data Validation

"Validate user input without code"

...

See the documentation on data validation.

Headless Client Operation

"Dual mode deployment options; back-office integration"

...

See the documentation on headless client.

New Logging Features

"Improve logging flexibility"

...

  1. Syntax for configuring logs in nexaweb-client.xml is now uniform with the syntax in nexaweb-server.xml
  2. APIs have been extended to enable custom log consumer development
  3. Two default log consumers are now available for the client
    • ConsoleLogConsumer - outputs log messages to the client console
    • DialogLogConsumer - outputs error and exceptionmessages to a dialog box

Support for Drop Shadows

Drop shadows available for user interface elements; see the dropShadowOffset and dropShadowColor attributes in the XML UI documentation.

See the documentation for more.

Client Side XML Processing

"Improve UI responsiveness"

...

See the documentation for more.

Updated Default Stylesheet

The default style sheet has been updated.

To access the previous style sheet, download from the Nexaweb compatibility repository.

Release Notes and Known Issues

Differences from Nexaweb Java Client

...

  1. NFC will not work with XAL; it will continue to work for NXML. This will be addressed in future releases
  2. Scrollbar as a separate component, this will likely be dropped permanently in both technologies; scrollPane is supported
  3. Slider
  4. cardPane
  5. Drag and Drop functionality (may have limited support in the release)
  6. Validation framework
  7. Tab order
  8. Keyboard navigation - later releases will have better support

Troubleshooting

XInclude


If an xInclude seems to be failing, run through this checklist of potential problems

...

IIS does not recognize files with a .xal file extension and does not send them by default. This can be worked around by setting a mime type for XAL text/xml; another workaround is to rename the files with a .xml extension. This behavior does not exist on any application servers or on Apache web server.

IE 6 Performance

There is a known issue with poor IE 6 performance.  This is being resolved with progressive versions of the Nexaweb Platform, however Microsoft has also released a patch for it.

...