Over a million developers have joined DZone.

@MimeLocation, @MimeRegistration and @MimeRegistrations added

· Java Zone

Discover how AppDynamics steps in to upgrade your performance game and prevent your enterprise from these top 10 Java performance problems, brought to you in partnership with AppDynamics.

This is how code completion providers are registered in NetBeans IDE 7.0, take note of the @MimeRegistration annotation (which comes from the Mime Lookup API) on the class:

import javax.swing.text.Document;
import javax.swing.text.JTextComponent;
import org.netbeans.api.editor.mimelookup.MimeRegistration;
import org.netbeans.spi.editor.completion.CompletionProvider;
import org.netbeans.spi.editor.completion.CompletionResultSet;
import org.netbeans.spi.editor.completion.CompletionTask;
import org.netbeans.spi.editor.completion.support.AsyncCompletionQuery;
import org.netbeans.spi.editor.completion.support.AsyncCompletionTask;

@MimeRegistration(mimeType = "text/html", service = CompletionProvider.class)
public class DemoCompletionProvider implements CompletionProvider {

    public CompletionTask createTask(int i, JTextComponent jTextComponent) {
        return new AsyncCompletionTask(new AsyncCompletionQuery() {
            protected void query(CompletionResultSet resultSet, Document doc, int caretOffset) {
                throw new UnsupportedOperationException("Not supported yet.");

    public int getAutoQueryTypes(JTextComponent jTextComponent, String string) {
        return 0;


When you compile the module that contains the class above, you'll have a file named "generated-layer.xml" in "build/classes/META-INF", with this content:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE filesystem PUBLIC "-//NetBeans//DTD Filesystem 1.2//EN"
    <folder name="Editors">
        <folder name="text">
            <folder name="html">
                <folder name="CompletionProviders">
                    <file name="org-demo-DemoCompletionProvider.instance">


Sometimes one implementation can be used in different contexts, i.e., in different editors, in which case you would annotate like this instead:

    @MimeRegistration(mimeType="text/html", service=CompletionProvider.class),
    @MimeRegistration(mimeType="text/x-java", service=CompletionProvider.class)
public class DemoCompletionProvider implements CompletionProvider {


Therefore, you will no longer need to manually register editor service providers manually in the layer file anymore. In the case of completion providers, that's all possible because the CompletionProvider class has this annotation:

public interface CompletionProvider {


The above is just an example. Anything else that is registered per MIME type in the "Editors" folder can now be registered as shown above. As shown above, you can use the same approach when requiring contributors to register implementations per MIME type in the "Editors" folder.

For details, see this issue:https://netbeans.org/bugzilla/show_bug.cgi?id=190606


The Java Zone is brought to you in partnership with AppDynamics. AppDynamics helps you gain the fundamentals behind application performance, and implement best practices so you can proactively analyze and act on performance problems as they arise, and more specifically with your Java applications. Start a Free Trial.


{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}