This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 431699 - workbench.xmi have no menu and trimbar Contributions from Application.e4xmi if RCP kills.
Summary: workbench.xmi have no menu and trimbar Contributions from Application.e4xmi i...
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.4   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 4.4 M7   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-01 07:41 EDT by Sumit Singh CLA
Modified: 2014-04-03 04:31 EDT (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 Sumit Singh CLA 2014-04-01 07:41:21 EDT
I'm working on RCP application based on compatibility layer.
In my application I have one main Application.e4xmi and multiple fragment.e4xmi.
Case 1: If I run my application and close it and during close I'm saving the workspace then next time when I'll open it without cleaning the workspace then its work properly.

Case 2: If Application is running and you kill it through task manager or simply by eclipse terminate( if you are running it through eclipse). then next time when you open it you will not see the menus which are contributed by Application.e4xmi

Observation 1: By using live edition I'm seeing that all the menus and trimbars which are contributed by Application.e4xmi are not available in the application.

But other menus which are contributed by fragment.e4xmi are there.

Observation 2: By comparing the ".metadata/plugins/org.eclipse.e4.workbench/workspace.xmi" before and after UI messed Up. I found that In messed up workspace.xmi there is no entry for menuContributions which are contributed by Application.e4xmi.

I can use "-persistState false" or "clearPersistedState" but I want my application to open as it was close so this option will not help to my application.

Is any thing I'm missing and what is went wrong if application is killed.? And even same thing I'm observing with eclipse IDE as well.
Comment 1 Paul Webster CLA 2014-04-01 09:25:11 EDT
First off, if you are using an Application.e4xmi then you are *not* using the compatibility layer.

But this is a failure scenario.  You killed the app in the middle of it running.  We don't guarantee the state of the workbench.e4xmi, and provide -clean and -clearPersistedState to allow you to recover from that.

PW
Comment 2 Sumit Singh CLA 2014-04-02 02:20:43 EDT
Hi Paul,

Yes, But by using -clean and -clearPersistedState we can not store last State.
Comment 3 Paul Webster CLA 2014-04-02 09:49:10 EDT
It's a recovery mechanism, not something to be put in the .ini file.

i.e. if there's a crash, the customer should start up at least once with those options.

If your app is crashing regularly, that's another problem.

PW
Comment 4 Sumit Singh CLA 2014-04-03 01:21:46 EDT
Thanks Paul.

So what i do with this bug, Should close it or you will do it?.
Comment 5 Lars Vogel CLA 2014-04-03 04:30:01 EDT
(In reply to sumit singh from comment #4)
> Thanks Paul.
> 
> So what i do with this bug, Should close it or you will do it?.

Thanks. I mark this one as WORKSFORME.