Home > Release Notes

4.0.2 (Development Release)

Release Date: March 21, 2007

Bug fixes:

• [01385] XML Import procedure is not transactional on cache layer. If import fails, partial updates done are viewed in EBX.Manager (but persistence layer is clean).

• [01389] It is possible to create a branch or a version with an identifier than contains the space character, however it is not handled correctly in Manager.

• [01395] Archive export/import does include some technical internal adaptations that should not be included.

API:

• Added a method for exporting a EBX.Platform archive that contains a subset of the instances contained in a home. See method ProcedureContext.doExportArchive(ArchiveExportSpec) .

• Added a method for importing a subset of the instances contained in a EBX.Platform archive. See method ProcedureContext.doImportArchive(ArchiveImportSpec) .

• Manager as Component API: It is now possible to call the validation page (either a home validation page or an instance validation page). See method UIAbstractComponentLink.setContextToService(ServiceKey aServiceKey) . 

Known limitations:

• Performance: for large number of tables (in the order of 10,000 tables) and for large number of occurrences (in the order of 10,000,000 occurrences), optimizations are not yet available.

• Merge process: in case of instances' add-add conflict, tables in the source are ignored.

  Workaround: first create instances and merge, then tables may be populated and merged.

• Comparison and Merge: Header informations are not yet included in the comparison user interface nor in the merge process.

  Workaround: for merging header informations, a least one value must be updated on instance.

• Repository locking: it is not yet detected when two Java virtual machines share the same physical repository.

  Workaround: Repositories' administrator must take care that a repository is not refered by two environments.

• Permissions management: a user without the built-in PROVIDER role cannot access on adaptation instances above agreements.

  Workaround: the user must have the built-in PROVIDER role.

• Access right management: a node can be set as ReadWrite even it is not adaptable according to schema definition.

• Manager Components: UI Services can not be addressed through Manager components API.

Home > Release Notes