Para registrar um modelo XSLT em um plug-in existente para modelos:
<extension
point="com.ibm.ccl.erf.ui.services.IntegratingClient"
point="com.ibm.xtools.publish.ui.xsltReportsextension"
</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>
point="com.ibm.xtools.publish.ui.xsltReportsextension"
</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>
point="com.ibm.xtools.publish.ui.xsltReportsextension"
</extension>
<category
id="<category ID>"
name="<category display name>"
</category>
Se você utilizar a definição de categoria padrão, não inclua uma definição de categoria. Require-Bundle: org.eclipse.core.runtime,
com.ibm.ccl.erf.ui.services,
com.ibm.xtools.publish.ui
Você deve garantir que o arquivo XSL seja validado e que localize todos os arquivos XSL dos quais ele depende.