File Type Integration Tutorial
This tutorial shows you how to write a module that lets the IDE,
or any other application built on the NetBeans Platform, recognize a new file type.
Note: This document uses the NetBeans IDE 6.5 Release. If you
are using NetBeans IDE 6.x, see the 6.1 version
of this document.
Contents
To follow this tutorial, you need the software and resources listed in the following
table.
Introduction to File Type Integration
File types that are recognized in the IDE have their own icons, menu items, and behavior.
The "files" being shown are FileObjects—wrappers
around java.io.File or, in the case of configuration files, typically wrappers around data stored in some other way,
such as inside XML files in modules. What you actually see are Nodes, which provide functionality like actions
and localized names to objects like files. In between Nodes and FileObjects are DataObjects.
A DataObject is like a FileObject, except that it knows what kind of file is being shown, and there are
usually different types of DataObject for files with different extensions and XML files with different namespaces.
Each DataObject is provided by a different module, each implementing support for one or more file types—for example,
the Image module makes it possible to recognize and open .gif and .png files.
A module that recognizes a file type installs a DataLoader—a factory for a file-type-specific DataObject.
When a folder is expanded, the IDE asks each known DataLoader, "Do you know what this is?" The first one that says
"Yes" creates the DataObject for the file. In order to actually display something for each file, the system calls
DataObject.getNodeDelegate() for each DataObject and the Nodes are what you actually see in the IDE.
Below, the diagram on the left shows what each item mentioned above makes available:
In this tutorial, you create a module that installs a DataLoader for imaginary "Abc" files
(.abc file extension). By default, a file with the "abc" extension is treated as any other file that
the IDE does not recognize—it is treated as a text file and, as a result, the IDE provides the same functionality for
Abc files as it does for text files. Once you have created the module, you will be shown how to enhance it
with functionality that will be available to Abc files only. When you complete the development cycle, you can easily let others make use of
your module—the IDE lets you create a binary that you can send to others, who can then install it through the
Update Center.
Creating the Module Project
In this section, we use a wizard to create the source structure that every NetBeans module requires. The
source structure consists of certain folders in specific places and a set of files that are
always needed. For example, every NetBeans module requires a nbproject folder, which holds
the project's metadata, and a layer.xml file, for declarative registration of items
such as toolbar buttons and windows.
- Choose File > New Project (Ctrl-Shift-N). Under Categories, select NetBeans Modules. Under Projects,
select Module and click Next.
- In the Name and Location panel, type AbcFileType in Project Name.
Change the
Project Location to any directory on your computer, such as c:\mymodules. Leave the Standalone Module radiobutton
selected. The panel should now look as follows:
Click Next.
- In the Basic Module Configuration panel, type org.myorg.abcfiletype
as the Code Name Base.
Add spaces to the suggested Module Display Name, so that it is changed to Abc File Type.
Select the "Generate XML Layer" checkbox and
leave the location of the localizing bundle and XML layer as they are,
so that they will be stored in a
package with the name org/myorg/abcfiletype. The panel should now look as follows:
- Click Finish.
The IDE creates the Abc File Type
project. The project contains all of your sources and
project metadata, such as the project's Ant build script. The project
opens in the IDE. You can view its logical structure in the Projects window (Ctrl-1) and its
file structure in the Files window (Ctrl-2). For example, the Projects window should now look as follows:
Recognizing Abc Files
In this section, we use a wizard to create the classes necessary for
recognizing Abc files as being distinct from all other files. As discussed
at the start of this tutorial, we need a data object and a data loader, as
well as a MIME type resolver, and registration entries in the layer.xml file,
to do so. The New File Type wizard will create all of these for us.
- Right-click the project node and
choose New > File Type.
- In the File Recognition panel, do the following:
- Type text/x-abc in the MIME Type edit box.
- Type .abc .ABC in the by Filename Extension edit box.
The File Recognition panel should now look as follows:
Note the following about the fields in the File Recognition panel:
- MIME Type. Specifies the data object's unique MIME type.
- by
Click Next.
- In the Name and Location panel, type Abc as the Class Name Prefix
and browse to any 16x16 pixel image file as the new file type's icon, as shown below.
Note: You can use any icon of a 16x16 pixel dimension. If you like, you can
click on this one and save it locally, and then
specify it in the wizard step above:
- Click Finish.
The Projects window should now look as follows:

Each of the newly generated files is briefly introduced:
- AbcDataObject.java. Wraps a FileObject. DataObjects are produced by DataLoaders.
For more information, see What is a DataObject?.
- AbcResolver.xml. Maps the .abc and .ABC extensions to the MIME type. The AbcDataLoader only
recognizes the MIME type; it does not know about the file extension.
- AbcTemplate.abc. Provides the basis of a file template that is registered
in the layer.xml such that it will be installed in the New File dialog
as a new template.
- AbcDataObjectTest.java. JUnit test class for the DataObject.
In the layer.xml file, you should see the following:
<folder name="Loaders">
<folder name="text">
<folder name="x-abc">
<folder name="Actions">
<file name="org-myorg-abcfiletype-MyAction.shadow">
<attr name="originalFile" stringvalue="Actions/Edit/org-myorg-abcfiletype-MyAction.instance"/>
<attr name="position" intvalue="600"/>
</file>
<file name="org-openide-actions-CopyAction.instance">
<attr name="position" intvalue="100"/>
</file>
<file name="org-openide-actions-CutAction.instance">
<attr name="position" intvalue="200"/>
</file>
<file name="org-openide-actions-DeleteAction.instance">
<attr name="position" intvalue="300"/>
</file>
<file name="org-openide-actions-FileSystemAction.instance">
<attr name="position" intvalue="400"/>
</file>
<file name="org-openide-actions-OpenAction.instance">
<attr name="position" intvalue="500"/>
</file>
<file name="org-openide-actions-PropertiesAction.instance">
<attr name="position" intvalue="700"/>
</file>
<file name="org-openide-actions-RenameAction.instance">
<attr name="position" intvalue="800"/>
</file>
<file name="org-openide-actions-SaveAsTemplateAction.instance">
<attr name="position" intvalue="900"/>
</file>
<file name="org-openide-actions-ToolsAction.instance">
<attr name="position" intvalue="1000"/>
</file>
<file name="sep-1.instance">
<attr name="instanceClass" stringvalue="javax.swing.JSeparator"/>
<attr name="position" intvalue="1100"/>
</file>
<file name="sep-2.instance">
<attr name="instanceClass" stringvalue="javax.swing.JSeparator"/>
<attr name="position" intvalue="1200"/>
</file>
<file name="sep-3.instance">
<attr name="instanceClass" stringvalue="javax.swing.JSeparator"/>
<attr name="position" intvalue="1300"/>
</file>
<file name="sep-4.instance">
<attr name="instanceClass" stringvalue="javax.swing.JSeparator"/>
<attr name="position" intvalue="1400"/>
</file>
</folder>
<folder name="Factories">
<file name="AbcDataLoader.instance">
<attr name="SystemFileSystem.icon" urlvalue="nbresloc:/org/myorg/abcfiletype/Datasource.gif"/>
<attr name="dataObjectClass" stringvalue="org.myorg.abcfiletype.AbcDataObject"/>
<attr name="instanceCreate" methodvalue="org.openide.loaders.DataLoaderPool.factory"/>
<attr name="mimeType" stringvalue="text/x-abc"/>
</file>
</folder>
</folder>
</folder>
</folder>
Installing and Trying Out the Functionality
Let's now install the module and then use the basic
functionality we've created so far.
The IDE uses an Ant build script to build and install your module. The build
script is created for you
when you create the project.
- In the Projects window, right-click the Abc File Type project and choose Run.
A new instance of the IDE starts, installing your module into itself.
- Use the New Project dialog (Ctrl-Shift-N)
to create any kind of application in the IDE.
- Right-click the application node and choose New > Other. In the Other
category, a template is available for working with the new file type:

Complete the wizard and you will have created a template that
can be used for starting off the user's work with the given file type.
If you want to provide default code via the template, add the code to the
AbcTemplate.abc file that the New File Type wizard created for you.
Creating Features for Abc Files
Now that the NetBeans Platform is able to distinguish Abc files from all other types of files,
it is time to add features specifically for these types of files. In this section, we add a menu
item on the right-click contextual menu of the file's node in the explorer windows, such as in
the Projects window, and we enable the file to open into a window, instead of into an editor.
Adding an Action
In this subsection, we use the New Action wizard to create a Java class that
will perform an action for our file type. The wizard will also register the class
in the layer.xml file such that the user will be able to invoke the
action from the right-click contextual menu of the file type's node in an explorer window.
- Right-click the project node and
choose New > Action.
- In the Action Type panel, click Conditionally Enabled. Type AbcDataObject, which
is the name of the data object generated above by the New File Type wizard, as shown below:
Click Next.
- In the GUI Registration panel, select the 'Edit' category in the Category drop-down list.
The Category drop-down list controls where an action is shown in the Keyboard Shortcuts editor in the IDE.
Next, Unselect Global Menu Item and then select File Type Contect Menu Item.
In the Content Type drop-down list, select the MIME type you specified above in the New File Type
wizard, as shown below:
Notice that you can set the position of the menu item and that you
can separate the menu item from the item before it and after it. Click Next.
- In the Name and Location panel, type MyAction as the Class Name
and type My Action as the Display Name. Menu items provided by contextual menus
do not display icons. Therefore, click Finish and MyAction.java is added to the org.myorg.abcfiletype package.
- In the Source Editor, add some code to the action's performAction method:
protected void performAction(Node[] activatedNodes) {
AbcDataObject abcDataObject = activatedNodes[0].getLookup().lookup(AbcDataObject.class);
FileObject f = abcDataObject.getPrimaryFile();
String displayName = FileUtil.getFileDisplayName(f);
String msg = "I am " + displayName + ". Hear me roar!";
NotifyDescriptor nd = new NotifyDescriptor.Message(msg);
DialogDisplayer.getDefault().notify(nd);
}
Press Ctrl-Shift-I. The IDE automatically adds import statements to the top of the class.
Some code
is still underlined in red, to indicate that not all of the required packages are on the classpath.
Right-click the project node, choose Properties, and click Libraries in the Project Properties dialog box.
Click add at the top of the Libraries pane and add the Dialogs API.
In the MyAction.java class, press Ctrl-Shift-I again. The red underlining disappears because
the IDE finds the required packages in the Dialogs API.
- In the Important Files node, expand XML Layer. The two nodes <this layer> and <this layer in context>,
together with their subnodes, make up the System Filesystem Browser. Expand <this layer>, expand Loaders,
continue expanding nodes until you see the Action that you created above.
- Drag-and-drop My Action so that it appears below the Open action, as shown below:
As you can see from the last two steps, the System Filesystem Browser can be used to quickly reorganize
the sequence of the items that are registered in the System Filesystem.
- Run the module again, as you did in the previous section.
- Create an ABC file, using the template shown
in the previous section, and right-click the file's node in one of the
explorer views, such as in the Projects window or Favorites window.
Notice that the Abc file has the icon
you assigned to it in its module and that the list of actions defined in its layer.xml file
is available from the right-click contextual menu:
- Choose the new menu item, the Abc file's name and location are shown:
You now know how to create a new action that appears in the context
menu of a file of the given type, in the Projects window, Files window
or the Favorites window.
Opening the File into a Window
By default, when the user opens a file of the type that we have defined in this tutorial,
the file will open into a basic editor. However, sometimes you may want to create a visual
representation of the file, and let the user drag and drop widgets onto the visual representation.
The first step in creating such a user interface is to let the user open the file into a window.
This subsection shows you how to do that.
- Right-click the project node and
choose New > Window Component. Set "editor" for Window Position
and "Open on Application Start", as shown below:
- Click Next and type "Abc" as the Class Name Prefix:

Click Finish.
- Change the DataObject to use OpenSupport instead of DataEditorSupport,
by changing the DataObject's constructor as follows:
public AbcDataObject(FileObject pf, MultiFileLoader loader)
throws DataObjectExistsException, IOException {
super(pf, loader);
CookieSet cookies = getCookieSet();
//cookies.add((Node.Cookie) DataEditorSupport.create(this, getPrimaryEntry(), cookies));
cookies.add((Node.Cookie) new AbcOpenSupport(getPrimaryEntry()));
}
- Create the OpenSupport class:
class AbcOpenSupport extends OpenSupport implements OpenCookie, CloseCookie {
public AbcOpenSupport(AbcDataObject.Entry entry) {
super(entry);
}
protected CloneableTopComponent createCloneableTopComponent() {
AbcDataObject dobj = (AbcDataObject) entry.getDataObject();
AbcTopComponent tc = new AbcTopComponent();
tc.setDisplayName(dobj.getName());
return tc;
}
}
Tweak the TopComponent to extend CloneableTopComponent,
instead of TopComponent. Set the TopComponent's class modifier, and its
constructor's modifier, to public instead
of private.
Run the module again and then,
when an Abc file is opened, the OpenSupport class handles the
opening, such that it opens the file into the TopComponent instead
of the basic editor that DataEditorSupport provides:

The NetBeans Visual Library Tutorial
provides an example of what you can do
to develop the TopComponent further such that
it will visually display the content of a file
that corresponds to the file type defined in this tutorial.
Creating a Multiview Window
Now that we are able to open a file into a window, let's make the window
more interesting. We'll create a multiview window. The first tab of
a multiview window is typically used to display a visual representation
of the file, while the second tab typically shows the source view. More
than two tabs can also be provided, each tab providing further levels
of detail about the opened file.
- Right-click the project node and choose Properties. In the Project
Properties dialog, choose Libraries, and click Add.
Set a dependency on "MultiView Windows". Click OK and then
click OK again to exit the Project Properties dialog.
For each tab that you want to create in the multiview window, create a class that
implements MultiViewDescription and Serializable.
For
purposes of this tutorial, start by creating a class called
AbcMultiviewDescription1, implementing the specified classes:
public class AbcMultiviewDescription1 implements MultiViewDescription, Serializable {
public int getPersistenceType() {
throw new UnsupportedOperationException("Not supported yet.");
}
public String getDisplayName() {
throw new UnsupportedOperationException("Not supported yet.");
}
public Image getIcon() {
throw new UnsupportedOperationException("Not supported yet.");
}
public HelpCtx getHelpCtx() {
throw new UnsupportedOperationException("Not supported yet.");
}
public String preferredID() {
throw new UnsupportedOperationException("Not supported yet.");
}
public MultiViewElement createElement() {
throw new UnsupportedOperationException("Not supported yet.");
}
}
In the AbcMultiviewDescription1 class above,
the method createElement() returns a MultiViewElement.
What you want to return here is your TopComponent, which
we will do in the next step.
- Rewrite the class signature. To provide a multiview element for
the description in the previous step, we need to extend JPanel
instead of TopComponent and we need to implement
MultiViewElement:
public final class AbcTopComponent extends JPanel implements MultiViewElement {
In the TopComponent, you now need to delete (or comment out) the methods
findInstance(), getPersistenceType(), writeReplace()
and preferredID().
- For the moment, provide very simple
implementations of each of the required methods. Start by defining
a new JToolbar at the top of the TopComponent class:
private JToolBar toolbar = new JToolBar();
Next, implement the methods as follows:
public JComponent getVisualRepresentation() {
return this;
}
public JComponent getToolbarRepresentation() {
return toolbar;
}
public void setMultiViewCallback(MultiViewElementCallback arg0) {
}
public CloseOperationState canCloseElement() {
return null;
}
public Action[] getActions() {
return new Action[]{};
}
public Lookup getLookup() {
return Lookups.singleton(this);
}
public void componentShowing() {
}
public void componentHidden() {
}
public void componentActivated() {
}
public void componentDeactivated() {
}
public UndoRedo getUndoRedo() {
return UndoRedo.NONE;
}
- Now you can redefine the AbcMultiviewDescription1 as follows:
public class AbcMultiviewDescription1 implements MultiViewDescription, Serializable {
public int getPersistenceType() {
return TopComponent.PERSISTENCE_ALWAYS;
}
public String getDisplayName() {
return "Tab 1";
}
public Image getIcon() {
return ImageUtilities.loadImage("/org/myorg/abcfiletype/Datasource.gif");
}
public HelpCtx getHelpCtx() {
return null;
}
public String preferredID() {
return "AbcMultiviewDescription1";
}
public MultiViewElement createElement() {
return new AbcTopComponent();
}
}
- Change the createCloneableTopComponent method in the
OpenSupport class to open your TopComponent
via the MultiViewDescription class you created above:
protected CloneableTopComponent createCloneableTopComponent() {
// Create an array of multiview descriptors:
AbcMultiviewDescription1 firstTab = new AbcMultiviewDescription1();
MultiViewDescription[] descriptionArray = { firstTab };
// Create the multiview window:
CloneableTopComponent tc = MultiViewFactory.createCloneableMultiView(descriptionArray, firstTab, null);
tc.setDisplayName(entry.getDataObject().getName());
return tc;
}
The second argument
in MultiViewFactory.createCloneableMultiView determines which of
the tabs is open by default. Here it is firstTab, the tab defined by
AbcMultiViewDescription1.
Install and open the file again. Now you have a multiview window with one tab:
You now have a single tab in a multiview window. For each additional tab,
create a new MultiviewDescription class, with a new JPanel,
and then instantiate the MultiViewDescription class in the
OpenSupport extension class, as shown above.
Creating a Shareable Module Binary
Now that the module is complete, you can let others use it. To do so, you
need to create a binary "NBM" (NetBeans module) file and distribute it.
- In the Projects window, right-click the Abc File Type project and choose Create NBM.
The NBM file is created and you can view it in the Files window (Ctrl-2):
- Make it available to others via, for example, the
NetBeans Plugin Portal.
The recipient should
use the Plugin Manager (Tools > Plugins) to install it.
Next Steps
For more information about creating and developing NetBeans modules, see the following resources: