Home > ReleaseNotes

4.3.2 fix 001

Release Date: March 19, 2008

 

Bug Fixes

 
  • [01678] Table content does not support a read concurrent access when an archive's import is made.
  • [01686] Optimize and Refactor - Mutualize common values procedure does nothing on tables without non-key columns.
  • [01688] Data Services - Count operation should return an integer but WSDL declares a string type.
  • [01689] Data Services - Validation operation may return empty validationReport but WSDL does not define a minOccurs=0

4.3.2

Release Date: March 17, 2008

 

Backward compatibility

 
  1. The API has changed for optimize and refactor handling. The methods in ProcedureContext have been moved into a new framework.
 

Bug Fixes

 
  • [01654] "Optimize and Refactor" procedure does nothing on table contents.
  • [01667] In advanced component for facet enumeration, if the programmatic enumeration throws an exception when trying to display an empty string, the user interface crashes.
  • [01668] Advanced component for facet enumeration does not support osd:tableRef's container attribute.
  • [01669] Accented characters are poorly managed in XML history files.
  • [01672] If EBX.platform startup process includes dynamic creation of persistence tables, WAS DB2 datasource implementation will return a null ResultSet (forbidden according to JDBC spec).
  • [01676] Invalid XML characters cause data loading failure (for instance: ascii #17).
  • [01679] Character ascii #14 causes data loading failure.
  • [01680] Persistent home lock does not record lock time (from timestamp) and lock comment.
  • [01682] In EBX.Manager, constraint documentation link to target node (e.g. a table node for a table reference) is missing if target node label contains a '&' character.
  • [01683] Invalid XML characters in complex node cause data loading failure.
  • [01684] Invalid XML characters in node with maxOccurs > 1 cause data loading failure.
  • [01685] Table column access may not be restricted as expected if several permissions match user profile.
 

Invalid XML characters

 
  • If an input via EBX.Manager contains invalid XML characters, an error is raised and a message is returned.
  • If a value with invalid XML characters is set via EBX.API, an exception is thrown.
 

Data Services

 

Note: Data Services is no more in Beta Version.

Bug Fixes

 
  • Lists of complex nodes are now generated in the WSDL.
  • The WSDL now matches exactly the response to a select operation.
  • Fault description is not present into WSDL
  • minOccurs is not handled in WSDL
  • Some attributes in select operation are not compliant with the generated WSDL
  • Attribute xml:lang was in wrong format (en_US instead of en-US) in schema declaration
  • Operations documentation was not WSDL compliant

Enhancements

 
  • Declaration of WSSE header added to the WSDL.
  • Add HTTP Basic Authentication Support
  • WSDL documentation has been changed so as to be fully WS-I Compliant.
  • Branch & Version names generated follow the naming convention of the Manager.

Home > ReleaseNotes