Bug 78484 - [implementation] Extension-point "documentProviders" should allow to register for content types
Summary: [implementation] Extension-point "documentProviders" should allow to register...
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-12 04:26 EST by Dani Megert CLA
Modified: 2019-09-06 16:13 EDT (History)
1 user (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 Dani Megert CLA 2004-11-12 04:26:56 EST 
3.1 M3

The extension-point "documentProviders" should allow to register a document
provider for content types.
Comment 1 Andrew Arapov CLA 2009-03-17 08:10:52 EDT 
Hello! I wonder, if there is any resolution about this problem?

I'm trying to register my own DocumentProvider, doing this:

    <extension
          point="org.eclipse.ui.editors.documentProviders">
       <provider
             class="ru.mbtc.sae.jseditor.StringStorageDocumentProvider"
             inputTypes="org.eclipse.ui.IStorageEditorInput"
             id="ru.mbtc.sae.jseditor.StringStorageDocumentProvider">
       </provider>
    </extension>

public class StringStorageDocumentProvider extends StorageDocumentProvider {

    @Override
    protected void doSaveDocument(IProgressMonitor monitor, Object element, IDocument document, boolean overwrite) throws CoreException {
        ...do something...
    }
}

But there isn't any effect of this - provider for my IEditorInput, which implements IStorageEditorInput:

public class SimpleEditorInput implements IStorageEditorInput {
  ... 
}

is StorageDocumentProvider.

What do I wrong?
Thanks.
Comment 2 Dani Megert CLA 2009-03-17 09:09:23 EDT 
Your comment is completely unrelated to this bug and rather a question that belongs to the newsgroup.
Comment 3 Andrew Arapov CLA 2009-03-17 09:11:10 EDT 
(In reply to comment #2)
> Your comment is completely unrelated to this bug and rather a question that
> belongs to the newsgroup.
> 

Yes, I'm very sorry for my inattention. Please, could you delete my previous and this comment?
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:13: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.