To register an XSLT template in an existing plug-in for templates:
<extension point="com.ibm.ccl.erf.ui.services.IntegratingClient" </extension>
<extension point="com.ibm.ccl.erf.ui.services.IntegratingClient" <client class="com.ibm.xtools.publish.ui.internal.XSL_UML2XML_IntegratingClient" description="" display_name="" report_file_extensions="*.xslt;*.xsl" reporting_system="XSLT" uid="com.ibm.xtools.publish.uml2"> </client> </extension>
<extension point="com.ibm.ccl.erf.ui.services.IntegratingClient"> <client class="com.ibm.xtools.publish.ui.internal.XSL_UML2XML_IntegratingClient" description="" display_name="" report_file_extensions="*.xslt;*.xsl" reporting_system="XSLT" uid="com.ibm.xtools.publish.uml2"> <report_design_definitions> <resource_info> categoryID="mycategoryID" description="%report1_description" display_name="%report1.name" path="<path to template>/<file>.xslt" type="FILE" </resource_info> </report_design_definitions> </client> </extension>
<category id="<category ID>" name="<category display name>" </category>If you use the default category definition, do not include a category definition.
Require-Bundle: org.eclipse.core.runtime, com.ibm.ccl.erf.ui.services, com.ibm.xtools.publish.ui
You must ensure that the XSL file validates and can locate all the XSL files that it depends on.
The changes take effect when you restart Eclipse.