Community
Participate
Working Groups
The Kepler release implemented connection of Papyrus to existing CDO model repositories. This does not account for the need to create, configure, and delete those repositories. The following capabilities are required of a repository administration UI: * create new repository: specifying the server, back-end store type, and properties (which depend on the store type but may include such things as table mapping strategies, auditing/branching, etc.) * delete repository * configure users, roles, groups, permissions (a more abstract interface than editing the raw security model resource) For repository creation and deletion, the implementation is expected to have variability according to back-end data store. The scope of this initial implementation will be limited to the H2 embedded RDBMS back-end only. Also, modification of the properties of an existing repository and migration of data from one repository to another are not in scope. Much or all of this work is expected to be contributed to the CDO project; appropriate enhancements will be linked to this bugzilla item, which serves at least for visibility/traceability of the needs of the Papyrus user community.
Linked the CDO enhancements that will provide the functionality required herein.
Fixed in git master. Most of the enhancements are implemented in CDO (see the linked bugzilla items) but a few integration bits are implemented in Papyrus: commit 26194d2: From the results of the query for Papyrus model resources in the repo to populate the Model Repositories view, filter out resources (Papyrus Models) that are in folders that the logged-in user does not have permission to read. commit aafe5e0: Integrate the new CDO "Change Password" and "Manage Security" functions into the context menu in the Model Repositories View. Also ensure that certain actions for creating and deleting objects/models in the repository are only enabled as appropriate to the user's permissions on those objects, containing folders, etc. commit fc7dc3d: Integrate model repository administration functions: respond to events from CDO indicating the creation or deletion of repositories in the CDO Administration view, prompting the user to add/remove them (as appropriate) in the Model Repositories View.
Updating target milestone to reflect actual delivery.
