Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 315354 - Automatically generate extension point reader class
Summary: Automatically generate extension point reader class
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.0   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-02 04:13 EDT by Jacek Pospychala CLA
Modified: 2019-09-09 02:24 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jacek Pospychala CLA 2010-06-02 04:13:43 EDT
hi,
every time I'm playing with new extension point (say every 2-3 months), the biggest pain is to figure out how to read the registry using extension registry API.
I mean problems like:
- which of Platform.getExtensionRegistry().get* methods should be used
- jumping back and forth betwen extension point schema and the handler class to correctly read all the arguments, etc.
- should I use registry tracer, to make the code more flexible (honestly, I never did that, after finishing basic ext.point reader)

Because all this things are pretty straightforward and repeatable, it would be really nice to have a generator producing all above code. Such generator could be accessible somewhere from the extension point schema editor. The produced code could use all the latest and greatest API. Probably such generated code would still need some manual modifications to integrate with ready stuff, but that's not a big issue.
Comment 1 Eclipse Webmaster CLA 2019-09-06 15:36:11 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.
Comment 2 Julian Honnen CLA 2019-09-09 02:24:31 EDT
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.