Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 313988 - Wish: reload model operation
Summary: Wish: reload model operation
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Ansgar Radermacher CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-21 18:09 EDT by Ansgar Radermacher CLA
Modified: 2012-02-23 05:20 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ansgar Radermacher CLA 2010-05-21 18:09:54 EDT
Build Identifier: Build id: 20100506-2000

A reload-model button/automatic operation would be very useful in the context of testing model transformations, since it is currently required to close and re-open a model in order to show the updated contents. This is tedious, in particular if the model that is currently open is not selected in the package explorer and must be located anew. Similar motivation in context of testing model libraries: The importing model in which an element of the library is used, needs to be closed and re-opened as well if changes of the model library should be taken into account.

Ideally (as almost all textual editors do), the editor detects automatically that the underlying file has been changed and offers the user the option (popup dialog) either a reload or replacement of the file with the editor contents. Popup with re-load option should appear as well, if one of the imported model library has changed.
[Simpler re-load button, i.e. without automatic detection has been implemented in latest version of Papyrus 1.12]

Reproducible: Always
Comment 1 Ansgar Radermacher CLA 2010-09-22 05:26:30 EDT
Remark: in addition to a change of the underlying resource of the UML model itself, one of the imported libraries could have changed as well.
[this is also useful in the model transformation context, if an input model references other model libraries that are frequently changed in a testing phase]
Comment 2 Vincent Hémery CLA 2011-09-29 04:50:55 EDT
The automatic reload mechanism has been extended to the situation when an additional resource is modified (this includes controlled sub-models).

In such a case, only the updated model is reloaded, since we know how to perform local reloads (see bug #354220).

For user messages, we do not list resources, but models instead (excluding file extension), since with the one-file feature, unexperienced users no longer see the file extensions.

These modifications have been committed on 0.8.X : 5617
and on trunk : 5620
Comment 3 Ansgar Radermacher CLA 2011-10-07 09:16:45 EDT
The automatic reload of imported models (that worked with Helios) does not work any more.

For imported models (that are read-only), changes should be updated without asking the user, since no data can be lost. Currently the "do you want to update the model contents" dialog is displayed if I update an imported model and go back to the importing model. Worse, answering "yes" to this question does something, but does not re-load the imported model.
Comment 4 Ansgar Radermacher CLA 2012-02-23 05:20:24 EST
As pointed out by Vincent, this bug can be closed due to the additional functionality in the resolution of bug #354220