4.7.8
Release Date: January 28, 2010
DataModel API
Introspection API has been completed:
The method
SchemaNode.getCategory()
has been added. It returns
the category
that is defined in schema.
For more information, see SchemaNode.getCategory()
Workflow
New field in history table
A new field has been added in history table: print stack trace. When an unexpected error occurs, this field contains print stack trace of the associated exception. This field is filled only if the error messages are not explicit.
Bug Fixes
Core Cache
-
[2341] Schema validation does not verify the length of table's pathes.
The ddl (cf ddl.sql) is limited to 255 characters for table path but it is not verifiyed when setuping a schema.
-
[2345] In EBX.Manager, an exception is thrown when a filter is applied on a table with an "osd:select" attribute.
When a filter is applied on a table and when this table has an 'osd:select' attribute, the following exception is thrown :
PathAccessException[The specified node is neither an adaptation terminal node, nor a descendant of a terminal: /root/table1[*]/linkToTable2.]
-
[2365] Adaptation tree is not loaded as expected.
In a multi-processor environment, an adaptation tree can be loaded with wrong child-to-parent relationships. As a result, a single and large adaptation tree may result in severall smaller trees.
Data Model & DMA
-
[2374] Tables are not correctly handled when they are defined on reusable types
When a reusable type is defined as a table, its primary keys are not visible in the hierarchy tree. Futhermore they cannot be selected as a target of a foreign key constraint.
J2EE Integration
-
[2339] EBX.Platform does not run under IBM WebSphere 7.
Besause of a library conflict, EBX.Platform cannot be run under IBM java runtime environment 1.6.0.
User Interface
-
[2329] Ajax tree can freeze if several Ajax requests are sent concurrently.
Expand and collapse events responses must embed the target line ID so that ajax tree can manage responses independently from a current line.
Main concerned tres are: adaptation trees, hierarchies and Workflow work list.
-
[2370] In EBX.Manager, in 'All user sessions' page, 'login' column content is erroneous.
The login displayed for each row of the table is always the current user's login.
-
[2371] EBX.Manager "max adaptation node quantity" parameter is not used as expected.
EBX.Manager "max adaptation node quantity" parameter is designed to handle the way EBX.Manager display sub-nodes (show sub-nodes or display a navigation link to sub-nodes).
Users & Permissions
-
[2373] Distributor (only) profile may update adaptation if it has a role that support it.
If a distributor only user is involved in a role that is owner of an agreement or an adaptation above agreement, he may update this agreement or the adaptation above agreement.