Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 405586 - It should not be possible to create new elements on a read only resource, even in the cache.
Summary: It should not be possible to create new elements on a read only resource, eve...
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 1.0.0   Edit
Hardware: All All
: P2 major (vote)
Target Milestone: M6   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 323802
Blocks:
  Show dependency tree
 
Reported: 2013-04-12 09:59 EDT by Samuel Rochet CLA
Modified: 2014-03-24 05:16 EDT (History)
3 users (show)

See Also:

Attachments
Example Screenshot (250.03 KB, image/png)
2014-01-14 04:49 EST, Ronan Bar CLA 		no flags Details
View All 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 Samuel Rochet CLA 2013-04-12 09:59:18 EDT 
It should not be possible to create new elements on a read only resource, even in the cache.
Currently we can create new diagrams (only the diagram, no graphical elements inside). We can also apply profiles and stereotypes on read only elements. In both cases, the request to pass the resource in write mode is done only when the user tries to save its model. This behavior induces risks of inconsistencies between resources.
The request for passing a resource in write mode should be done immediately after the user action  and the cache model should be modified only if the user accepts this request.
Comment 1 Samuel Rochet CLA 2013-04-22 11:02:23 EDT 
This problem concerns also tables.
Comment 2 Patrick Tessier CLA 2013-04-29 05:33:10 EDT 
The possibility that we can create diagram on read only resource, it is normal, because it is only references.
But it is not normal, that we can create element (diagram, or model explorer) in read only resource. it is a regression.

So I change the bug to major.
Comment 3 Sébastien Gérard CLA 2013-06-12 13:34:50 EDT 
Camille,

I guess we can close this task, isn't?

thanks,
cheers.... Sébastien.
Comment 4 Ronan Bar CLA 2014-01-14 04:49:16 EST 
Created attachment 238954 [details]
Example Screenshot
Comment 5 Ronan Bar CLA 2014-01-14 04:49:32 EST 
Hi,
This bug is still valid. If I have a model with a class diagram. On the diagram I have a class A and I have dragged and dropped a "read-only" element, such as Real, from the UML Primitive Types package. I can now create a dependency from the Real element to A. All looks fine in the diagram but the Real element in the UML Primitive Types of course has not be changed. Upon reloading the diagram I will see the the operation did not work. See sreenshot.
Comment 6 Camille Letavernier CLA 2014-02-27 07:18:27 EST 
Papyrus doesn't provide a true read-only mode yet; nothing more than a few graphical hints.

Bug 323802 is focused on providing a real read-only feature; it should be finished soon.
Comment 7 Ronan Bar CLA 2014-03-18 18:13:47 EDT 
Really nice fix in M6. The tooltip shows this sort of relationship is no longer possible. Confirmed fixed.
Comment 8 Camille Letavernier CLA 2014-03-24 05:16:17 EDT 
> Confirmed fixed.

I close the task