NetBeans vs. Eclipse RCP: Plug-in mechanism comparison

NetBeans differs from eclipse in how it handles extension points and extensions. Let's look at these differences. Please note that this article is intended only for those who have considerable knowledge of the plug-in mechanisms for these two platforms.

NetBeans Platform:

Defining extension points	Create an interface and place it in a public module package.
Create an extension	Create an implementation of the above interface and register it with the Layer.xml file in the virtual file system.
Read the available extensions	Use the Org.openide.util.Lookup class to obtain an instance of the interface implementation above.

Eclipse RCP:

	Available property types are: Boolean,string,java,resource and identifer. You can add documents to any part of the scenario. Finally, register your extension point to the Plugin.xml file.
	According to the above scenario, the The Plugin.xml file creates a child section where the property is assigned a value. If the property type is Java, you also create the referenced Java class.
	use ORG.ECLI Pse.core.runtime.IExtensionPoint Gets the list of extensions. Gets the list of iconfigurationelement from each extension: Each iconfigurationelement corresponds to an XML tag in the Plugin.xml file.

benefits	disadvantages	advantages	disadvantages
		extension point clearly defines itself: by quickly viewing the jar file, you immediately know what extension points the plug-in provides, and what elements they are composed of.
&nb SP;			 
 	extension and other content areMixed in Layer.xml files: It is difficult to determine which extensions the module is for. The