Bug 184246 - Eclipse workbench editor registry confusion for *.jsdl extensions
Summary: Eclipse workbench editor registry confusion for *.jsdl extensions
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Geclipse (show other bugs)
Version: unspecified   Edit
Hardware: All Linux
: P3 trivial (vote)
Target Milestone: ---   Edit
Assignee: Mathias Stümpert CLA
QA Contact:
URL:
Whiteboard:
Keywords: contributed
Depends on:
Blocks:
 
Reported: 2007-04-26 11:22 EDT by Nicholas Loulloudes CLA
Modified: 2014-01-09 16:18 EST (History)
0 users

See Also:


Attachments
This patch solves the above problem. (868 bytes, patch)
2007-04-26 11:43 EDT, Nicholas Loulloudes CLA
aog-ecl: iplog+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Nicholas Loulloudes CLA 2007-04-26 11:22:35 EDT
Hello,

It has been noticed that double clicking a *.jsdl file does not open the JSDL Multi-Page Editor.

This is caused by a confusion imposed on the Eclipse workbench editor registry due to a double entry for *.jsdl extensions in plugin.xml of eu.geclipse.ui

The first entry is for  class="eu.geclipse.ui.editors.JobDescriptionEditor" and the second entry for class="eu.geclipse.ui.editors.JsdlMultiPageEditor".

As it can be observed the JobDescription editor is only a raw source editor of the Jsdl file...which is already included in the JSDL MultiPage Editor.


I recommend removing the first entry since the standard JSDL editor from now on will be the JSDL Multi Page Editor.
Comment 1 Nicholas Loulloudes CLA 2007-04-26 11:43:28 EDT
Created attachment 65054 [details]
This patch solves the above problem.

Entry for JobDescriptionEditor has been removed.
Comment 2 Harald Kornmayer CLA 2007-04-26 11:46:24 EDT
Mathias 
Can you check the patch! 
I fully support the ideas of Nicholas! 
We need only one JSDL editor!

Harald 
Comment 3 Harald Kornmayer CLA 2007-04-26 12:10:03 EDT
I patched the source according to Nicholas recommendation. 
I tested it manually, and it works as expected. 
I commited the code to the SVN repository. 

Comment 4 Harald Kornmayer CLA 2007-04-26 12:10:38 EDT
close the bug
Comment 5 Ariel Garcia CLA 2009-05-03 09:19:55 EDT
Comment on attachment 65054 [details]
This patch solves the above problem.

Applied by Harald