Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 398693 - [CDO] Model repository connection management
Summary: [CDO] Model repository connection management
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 0.10.0   Edit
Hardware: PC Mac OS X
: P2 enhancement (vote)
Target Milestone: M6   Edit
Assignee: Christian Damus CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 290952
  Show dependency tree
 
Reported: 2013-01-21 17:46 EST by Christian Damus CLA
Modified: 2013-03-11 16:17 EDT (History)
0 users

See Also:
give.a.damus: kepler+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Damus CLA 2013-01-21 17:46:17 EST 
For persistence of Papyrus models in CDO repositories, a user interface and API will be required for the management of connections and browsing of model resources.

This feature comprises two parts:

  - a "repository connection manager" API for Papyrus internally to track
    connections to CDO repositories, with views and transactions on those
    repositories

  - a Model Repositories UI view that presents available repositories, and for
    those that are connected, a browser tree showing the shared models that they
    contain.   This would be the primary launch point for creating models and
    opening editors on models in the CDO repositories
Comment 1 Christian Damus CLA 2013-01-21 17:47:36 EST 
I'll take this on.  I have prototypes of an IPapyrusRepositoryManager API and a Model Repositories view in progress.
Comment 2 Christian Damus CLA 2013-01-31 18:04:35 EST 
r9995 on cdo_kepler branch:

Committed initial implementation of a model repository connection management API and Model Repositories view:

  - IPapyrusRepositoryManager and IPapyrusRepository encapsulate the
    CDO container and session concepts, in a private container that doesn't
    interact with the rest of the CDO UI (thus avoiding deadlocks and other
    potential problems)

The Model Repositories view supports creation, connection, disconnection, and removal of repositories connected via TCP or HTTP protocol (more to be added).  CDO's username/password authentication scheme is supported for CDO servers that implement it.  Information about the user's repositories is stored in an EMF model in the workspace metadata area, persisted across workbench sessions.  Repositories are not automatically connected on workbench start and Papyrus editors opened on models in a repository are likewise not re-opened on start-up.

Includes JUnit test coverage of the repository connection management API, using CDO repositories instantiated in memory (using mem store and JVM connector).
Comment 3 Christian Damus CLA 2013-03-11 16:17:12 EDT 
Additional improvements have been merged to trunk in r10489, including:

  * rename models
  * drag-and-drop to move folders and models in a repository
  * drag-and-drop from Project Explorer to Model Repositories view
    to launch the Model Import Wizard
  * drag-and-drop from the Model Repositories view to the Project
    Explorer to launch the Model Export wizard, with path mappings
    data-filled for convenience