Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 334076 - Values of 'extends' and 'implements' for an attribute of type 'java' are not validated.
Summary: Values of 'extends' and 'implements' for an attribute of type 'java' are not ...
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-12 07:35 EST by Deepak Azad CLA
Modified: 2019-06-18 20:17 EDT (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 Deepak Azad CLA 2011-01-12 07:35:14 EST 
E.g. in the following extension point 'prefenceClass' and 'class' attributes are of type Java, but PDE does not report an error if the classes specified for these do not extend/implement the class/interface specified in the extension definition.

----------------------------------------------------------------------------
    <extension point="org.eclipse.ui.workbench.texteditor.spellingEngine">
        <engine
              preferencesClass="org.eclipse.jdt.internal.ui.preferences.SpellingPreferenceBlock"
              label="%defaultSpellingEngine.label"
              class="org.eclipse.jdt.internal.ui.text.spelling.DefaultSpellingEngine"
              default="true"
              id="org.eclipse.jdt.internal.ui.text.spelling.DefaultSpellingEngine">
        </engine>
    </extension>
----------------------------------------------------------------------------
Comment 1 Dani Megert CLA 2011-06-10 05:29:08 EDT 
This is an ugly hole in our story: people spend time to specify their extension point but in the end it will not be verified/checked.
Comment 2 Eclipse Genie CLA 2019-06-18 20:17:46 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.