bundles/org.eclipse.wst.sse.core/plugin.xml

<?xml version="1.0" encoding="UTF-8"?>
<?eclipse version="3.0"?>
<plugin>


	<!-- deprecated -->
	<extension-point
		id="adaptOnCreateFactory"
		name="%Adapt_On_Create_Factory_Extension.name" />
	<extension-point
		id="documentTypes"
		name="%Document_Types_Extension.name" />
	<extension-point
		id="embeddedTypeHandler"
		name="%JSP_Embedded_Content_Type_Handler_Extension.name" />
	<extension-point
		id="contentTypeFactoryContribution"
		name="%Content_Type_Factory_Contribution_Extension.name" />
	<!-- I commented out ... clients should just use the normal platform way of registering these 
		adapterFactories. At worst, they'd need a small plugin with 'startup' specified ... but that's 
		better than us getting hit with the performance impact (of loading plugins and pre-reqs, etc.). 
		<extension-point id="uriResolverAdapterFactory" name="Resource Adapter Factory for Creating URIResolvers"/>
	-->
	<extension-point
		id="cssprofile"
		name="%CSS_Profile_Extension.name" />
	<extension-point
		id="commentElementHandler"
		name="%Comment_Element_Handler_Extension.name" />

	<!-- this plug-in provides support for this extension point -->
	<extension-point
		id="modelHandler"
		name="%Model_Handler_Extension.name" />
	<extension-point
		id="formatProcessors"
		name="%Format_Processors_Extension_Point.name"
		schema="schema/formatProcessors.exsd" />

	<!-- not for use by clients (internal)-->
	<extension-point
		id="taskscanner"
		name="%Task_Scanner_Extension_Point.name" />

	<!-- define our task marker type -->
	<extension
		id="task"
		name="%Structured_Sources_Task_Extension.name"
		point="org.eclipse.core.resources.markers">
		<super type="org.eclipse.core.resources.taskmarker" />
		<persistent value="true" />
	</extension>

	<!-- Make sure default preference values are set at runtime -->
	<extension point="org.eclipse.core.runtime.preferences">
		<initializer
			class="org.eclipse.wst.sse.core.internal.preferences.PreferenceInitializer" />
	</extension>

</plugin>