DITA-OT ancient plugins and their way of defining extension points

[cant0r]

Hi all,

I was redirected here from the groups.io DITA-OT Users group, but I actually come with a different technical question since I managed to overcome the original one.

To begin with, I'm currently an intern at my company, I don't really have a deep understanding of dita-ot yet I just started a week ago,  and I was tasked with upgrading their dita-ot installation from 1.5.2 to 3.5.2. We use dita-ot under a CCMS for validation/publishing as I understand it.

The updating process actually goes really well since I spent the last few days getting to know the system itself(high level, I've only looked at dost.jar on the source level) but I'm having problem moving our custom content-model related plugins to 3.5.2.

These plugins define extension-points which are used by other plugins but when I run the new Ant script called `dita.bat` with the `install` parameter to integrate the plugins the whole thing falls apart because the system thinks a certain extension-point is undefined even though it is! Well, according to the current documentation everything is perfect syntactically.

I believe this is caused by the order in which the system installs the plugins.

Is it possible to explicitly state the order of installation of the plugins?

Or could you please point me in the right direction?

The affected XMLs and the script output look like this, if you require more information about this please tell me:

PLUGIN A (it uses said problematic extension-point)

plugin.xml

...

<plugin>

<feature extension="html.xsl.library.catalog.relative" value="xslcatalog.xml" type="file"/>

</plugin>

PLUGIN B (it defines the extension point)

catalog_template.xml

...

<catalog>

<uri name="....

....

<dita:extension
                   id="html.xsl.library.catalog.relative"
                   behavior="org.dita.dost.platform.InsertActionRelative"/>

</catalog>

And after `dita install -d` I receive the following, <plugin> is of course PLUGIN A:

Error: Plug-in <plugin> uses an undefined extension point html.xsl.library.catalog.relative

[Radu Coravu]

Hi,

Your pluginB should also have a plugin.xml, do you advertise the extension point there? Like:

       <extension-point id=" html.xsl.library.catalog.relative" name="...."/>

?

Regards,

Radu

--
You received this message because you are subscribed to the Google Groups "DITA-OT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dita-ot-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/dita-ot-users/1b65b03e-89d9-4945-92f3-4594c9808f0an%40googlegroups.com.

[cant0r]

Hi Radu,

Thank you for your answer. I missed that advertising thing, is advertising ext points necessary because dita-ot operates in strict mode by default?

Regards,

cant0r 

[Radu Coravu]

Hi,

You may be right, I'm not sure.

There is a migration guide in the DITA OT docs. The migration to DITA OT 1.7 seems indeed to refer to the strict integration mode:

https://www.dita-ot.org/dev/topics/migrating-to-1.7.html#ariaid-title1

Regards,

Radu

To view this discussion on the web, visit https://groups.google.com/d/msgid/dita-ot-users/b28157e1-67da-4f2a-be40-7d3a3078d9afn%40googlegroups.com.