The PDE wizards and editors that manipulate plug-ins and fragments are nearly the same. However, you must be aware of some important differences.
We start by creating a new fragment project.
On the first page of the New Fragment Project wizard, type the project name "com.example.german". Accept the default values and press Next. The "Fragment Content" page has three additional fields from the plug-in creation wizard: parent plug-in id, parent plug-in version, and version match rule.
Since we are writing a fragment for a specific plug-in, we can use the Browse button to select "com.example.xyz" in the plug-in selection dialog. Using the dialog, we could have also chosen any external plug-in.
Once the project is created, it opens the fragment manifest editor.
It is almost identical to plug-in manifest editor with the following exceptions:
We will add a similar action set as in the plug-in example, but this time in German.
System.out.println("Hallo, PDE welt!");
When you run the fragment using the "Run" tool bar button, the run-time platform instance should have the "Deutsche Aktionsmenge" action set available. (Use Window->Customize Perspective...->Other to get to the list of action sets). When you activate the action set, the "Beispiel Menu" menu should appear on the tool bar. When you select its menu item, you should see "Hallo, PDE welt!" in the Console. The runtime platform didn't see the German fragment directly. Instead, its plug-in registry resolved fragment references in such a way that the fragment's action set appeared to the platform as though it came directly from the XYZ Plug-in.