Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 184605

Summary:

InvalidThreadAccess in Manifest editor when reacting to model changes

Product:

[Eclipse Project] PDE

Reporter:

Leif Frenzel <himself>

Component:

Assignee:

PDE-UI-Inbox <pde-ui-inbox>

Status:

CLOSED WONTFIX

QA Contact:

Severity:

normal

Priority:

Version:

3.3

Target Milestone:

---

Hardware:

OS:

Windows XP

See Also:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=520352

Whiteboard:

stalebug

Attachments:

Description	Flags
Minimal project to reproduce	none
Logfile with exception stacktrace	none

Description Leif Frenzel

2007-04-28 12:50:28 EDT

Build ID: I20070323-1616

Steps To Reproduce:
Using 3.3 M6 Eclipse SDK

To reproduce:

Implement an extension wizard, by contributing to org.eclipse.pde.ui.newExtension, and implement model changes
by calling the model object passed to IExtensionWizard#init( IProject, IPluginModelBase ). Perform the model changes from a job that runs not in the UI thread. Then an InvalidThreadAccess exception is thrown by the editor.

I think the editor, when listening to model changes, should take care of reacting in the UI thread. With the current 
situation, clients are forced to do model manipulation in UI code (instead of in the core, where it would belong :-)

More information:
I'm attaching a minimal project to reproduce the problem. Run the runtime workbench, create a new plugin project, open the Extensions tab on the manifest editor, select Add > Extension Wizards > Other > Problematic Wizard > Next > Finish. A message box appears, and an error message is written to the log.

I'm also attaching the stacktrace.

Comment 1 Leif Frenzel

2007-04-28 12:51:06 EDT

Created attachment 65328 [details]
Minimal project to reproduce

Comment 2 Leif Frenzel

2007-04-28 12:53:25 EDT

Created attachment 65329 [details]
Logfile with exception stacktrace

Comment 3 Eclipse Genie

2019-09-19 14:32:08 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.