|
|
Users Guide | Patterns Reference | WebsydianExpress | Search |
|
|
Users Guide | Patterns Reference | WebsydianExpress | Search |
For more information about Websydian Express 1.2 please read Websydian Express 1.2 - What's New.
A new web server component (formerly known as the relay service) for the iSeries platform is included with the Websydian distribution. The Web Server Component for iSeries is based on the CGI standard and can be deployed on IBM iSeries HTTP Server or IBM Apache Web Server for iSeries.
The Web Server Component for iSeries can be used as an alternative to the Servlet Web Server Component which must be deployed on WebSphere.
You can read more in Websydian Web Server Component For iSeries - Deployment.
When setting up the log files for the Servlet Web Server Component or the Websydian Server it is now possible to specify that the log file should roll after a specified period (hourly, daily, weekly, or monthly).
This feature ensures that log files never get too big.
You can read more in Servlet Relay Service Options or Websydian Server Options.
The Servlet Web Server Component has been improved so if an error occurs when a request is sent to the application service, then the Servlet Web Server Component will now use another application service instead of aborting further processing of the request.
This gives a better user experience in case of errors.
For applications deployed on iSeries the max size of a request has been increased from 9999 bytes to 2 GB.
At startup an application service will connect to the Websydian Server to register itself. This requires that the Websydian Server is started before the application services.
To improve the stability in startup scripts, the application service now try to reconnect to the Websydian Server if the first connection attempt fails.
The application service will attempt to connect 3 times and pause in 30 seconds between each connection attempt before it fails to startup.
The handling of character sets in the iSeries and Java variants have been improved making it easier to deploy DWA applications that sends documents using another encoding than the default encoding of the platform. E.g. web services which must return XML documents in both UTF-8 and ISO-8859-1 (Western Latin).
The property file for the Servlet Web Server Component can now be packed in the WAR file. This makes it easier to deploy the Servlet Web Server Component on the web server as it is only necessary to deploy one file (the WAR file) which includes everything.
You can read more in Distributed Websydian Architecture Installation.
The error messages written to the DWA log files (Servlet Web Server Component log and Websydian Server log) have been improved so they more clearly state the most likely cause of the error and how to resolve them.
If an error happens in the Servlet Web Server Component then for security reasons no information about the error will be sent to the browser. Instead an error ID is written to the page, and this error ID can be used to search the Servlet Web Server Component log for the cause of the error.
The Websydian Server is backward compatible with Websydian applications developed with Websydian 5.5 and Websydian 5.6.
This is useful if you have several applications that use the same Websydian Server, and you do not want to upgrade all applications to Websydian 5.7 in one step.
An unreal field value in the WSYAUDIT pattern caused warnings when generating functions at Plex 5.1.
The field value has now been made real.
If the EventHandlerWithValidation function was used with more than 1 view in the WebInput variable, errors in the first view would not be reported if there were not any errors in the last view.
This has now been fixed so if there are errors in the first view these are reported first.
Numerical values are parsed correctly no matter what character is used as decimal separator on the iSeries where the Websydian application is deployed.
The ParameterStore pattern uses the unscoped field name when storing field values. If two scoped fields had the same unscoped name (e.g. Entity1.MyKey and Entity2.MyKey), then the ParameterStore pattern would use the same key to store the two different field values.
This has now been fixed so if a field is scoped the field surrogate is appended to the key used by the ParameterStore pattern.
When the path to the HTML template was generated back slash was used as a path separator. In Java the correct separator to use is a forward slash.
This has now been fixed.
By default the HtmlDropDownGenerator will now load all records when populating a list box.
The two patterns PageGeneratorWithErrorList and RepeatedEventDetection did not work when combined.
This has been solved by introducing a special ErrorPage in the RepeatedEventDetection pattern which is called when an event is activated twice or more.
The InsertRow function did not insert complex elements correctly if the complex element should appear before a simple element.
This has now been fixed.
The functions CreateSchema and CreateWSDL did not execute correctly in a Java environment due to a bug in Plex 5.5.
The CreateSchema and CreateWSDL functions have been modified so they workaround this bug.
Due to a mapping error the SoapGenerator could not correctly parse a response document that contained a Fault element.
Online documentation - Websydian v6.0