Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 357254 - [General] Strange behavior when saving a model with read-only resources
Summary: [General] Strange behavior when saving a model with read-only resources
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 0.10.0   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 357250
Blocks:
  Show dependency tree
 
Reported: 2011-09-09 11:37 EDT by Vincent Hémery CLA
Modified: 2015-04-24 09:07 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent Hémery CLA 2011-09-09 11:37:06 EDT
When a resource is read-only, it can be directly opened by Papyrus as a main model, or loaded in a model as additional resource (like in the cases of Profiles and Sub-models).

When saving a model set with such read-only resources, the behavior is incorrect.


1. All main model's resources (notation, di, uml) are saved, and if one of them is read-only, the save crashes with no error message, leaving the user with a partially saved set of files. Hence, these files are probably corrupted and the user has no explanation of why the model has not been saved.

2. All additional resources are saved, only if they are not read-only and are workspace files. But if they have been modified (see bug #357250), they are ignored during saving, there is no warning and the user just does not know that these are different from what is visible in the editor. In such a case, the solution of bug #357250 should be applied to at least warn the user, and eventually restore correct file in editor.
Comment 1 Camille Letavernier CLA 2013-09-09 12:11:57 EDT
Read-Only mode is still not properly supported in 0.10.0, especially w.r.t. workspace libraries
Comment 2 Camille Letavernier CLA 2015-04-24 09:07:25 EDT
I can't reproduce this issue anymore

I close the task