Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 318466 - [History Model] History Model cause interferences with legacy code
Summary: [History Model] History Model cause interferences with legacy code
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 0.7.0   Edit
Hardware: PC Windows XP
: P3 blocker (vote)
Target Milestone: ---   Edit
Assignee: Cedric Dumoulin CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-30 09:30 EDT by Cedric Dumoulin CLA
Modified: 2010-06-30 10:23 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 Cedric Dumoulin CLA 2010-06-30 09:30:01 EDT
I have a big model created few time ago. At one time I have enable the Resource Loading mechanism by opening the corresponding projects. I have never used the control mode on this model.

Today, it seems that:
- I can NOT see my diagram icons in the explorer (but the diagrams are opened).
- If I create a new diagram, I can see its icon
- If I close the Resource Loading mechanism projects and ControlMode, Papyrus can't load my model again (an exception is thrown), and I cannot open the .di file with the di editor. The di contains references to History !!!

For my point of view, the Resource Loading mechanism should be transparent and we should be able to activate/deactivate it. When it is deactivated, we should  be able to load the model anyway.
It looks like the Resource Loading modify something in one of the models, and that this forbid to open the model again ...
The history mechanism should not record data as long as we don't use ControlMode.
Comment 1 Cedric Dumoulin CLA 2010-06-30 10:07:08 EDT
All .di files contain a node History, regardless if the history is used or not.
This come from the /org.eclipse.papyrus.core.resourceloading/src/org/eclipse/papyrus/core/resourceloading/ExampleService.java 
that was here as example and should be removed.
Comment 2 Cedric Dumoulin CLA 2010-06-30 10:21:53 EDT
The problems of extra nodes in .di comes from the History Model: an example class was creating node as example :-(.
The class is removed, and the bug is corrected. 
For older diagrams, it is possible to remove manually extra history nodes from the text editor. It is also necessary to remove the history namespace declaration from the xml root node.

Origin of other problems is not identified and can not be reproduced.