Managing a new plugin for a new media-type needs parameterizations both on the Componize server to declare the media-type and on the DITA-OT Server for deploying the plugin.
<bean id="my.ooxml.mediaType" parent="io.mediaType.factory.abstract"> <property name="name" value="application/vnd.openxmlformats-officedocument.wordprocessingml" /> <property name="label" value="Microsoft Word (OpenXML)" /> </bean>
<bean id="my.ditaot.docx.pipelineDefinition" parent="ditaot.pipelineDefinition.abstract"> <property name="resultMediaType" ref="my.ooxml.mediaType" /> <property name="options"> <map> <entry key="transtype" value="docx" /> </map> </property> </bean>
<bean id="my.alfrescoPipelineDefinition.ditaot.docx" parent="alfresco.pipeline.definition.abstract"> <property name="id" value="my.ditaot-docx" /> <property name="pipelineDefinition" ref="my.ditaot.docx.pipelineDefinition" /> </bean>
my.ditaot-docx.title=DOCX my.ditaot-docx.description=DOCX
Note: You will also be able to provide or override the title and description of your pipeline by setting properties on the XML Pipeline Configuration file itself, using Alfresco Share Interface.
<?xml version="1.0" encoding="UTF-8"?> <pipelineConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="cpnz:pipeline:xsd:pipeline-configuration.xsd"> <pipeline>my.ditaot-docx</pipeline> <options> ... </options> <catalogs> ... </catalogs> </pipelineConfiguration>