Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 331132 - [Core] resource update is harmful in case of profiles
Summary: [Core] resource update is harmful in case of profiles
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 0.7.1   Edit
Hardware: PC Linux
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Ansgar Radermacher CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-25 10:07 EST by Ansgar Radermacher CLA
Modified: 2012-02-23 05:15 EST (History)
4 users (show)

See Also:

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 Ansgar Radermacher CLA 2010-11-25 10:07:05 EST 
If a resource that is referenced by an editor is updated, Papyrus tries to unload the resource (for triggering a reload when demanded). While this procedure works well in general, it is harmful if an applied profile is unloaded.
Comment 1 Ansgar Radermacher CLA 2010-11-25 17:46:57 EST 
I commited a fix which

- Transforms resource update mechanism into a service (thanks, Cedric)
- Moves the service from core to uml.service.types (since modified service needs uml2 dependency)
- Added check, if modified resource is a profile (don't unload in this case)

It seems to work fine, but it's not clear for me whether the org.eclipse.papyrus.service.types plugin is the "right" one.

Another issue: non-UML diagrams (that deactivate the uml.service.types plugin) would have no update support at all.
=> Possible? Define a UML-unaware update service in a common plugin, refine the update service in a UML specific profile. Please comment
Comment 2 Ansgar Radermacher CLA 2010-11-26 17:14:46 EST 
Moved service to org.eclipse.papyrus.diagram.common (proposed by Remi Schnekenburger)
Comment 3 Ansgar Radermacher CLA 2012-02-23 05:15:58 EST 
Fix already applied in nov. 2010