calumet integration no longer working in the latest version?

[PaulHermans]

In OxygenXML 12, I get
SystemID:
C:\Users\Paul\Untitled1.xpl
# which is the file generated by the xpl template
Engine name: Calumet XProc
Severity: error
Description: java.lang.AbstractMethodError

In OxygenXML 11.2, I get the output ('Hello World!') as expected.

[Mircea]

Hi Paul,

Since 12.0 we performed some API changes and the Calumet conector is no longer compatible.
You can download a conector based on Calumet 1.0.11 here.

Regards,
Mircea

[mstoef]

Hi Paul,

Since 12.0 we performed some API changes and the Calumet conector is no longer compatible.
You can download a conector based on Calumet 1.0.11 here.

Regards,
Mircea

Does this mean Calumet is still non-compatible? I have installed v. 1.0.12 and set up integration. Again, the default xpl 'Hellow World' works fine, but if I use an xpl sample based on one from the Pawson tutorial below, I get either a 'null stream' error (SAMPLE1), or an XC0050 (SAMPLE2).

m./


SAMPLE1:
<p:declare-step xmlns:p="http://www.w3.org/ns/xproc"
xmlns:c="http://www.w3.org/ns/xproc-step" version="1.0">
<p:input port="source">
<p:document href="file:///Users/jstor/localApps/xproc/doc.xml"/>
</p:input>
<!-- <p:identity/>
<p:store href="file:///Users/jstor/localApps/xproc/opx1.xml"/>-->
<p:output port="result"/>
<p:identity/>
</p:declare-step>

SAMPLE2:
<?xml version="1.0" encoding="UTF-8"?>
<p:declare-step xmlns:p="http://www.w3.org/ns/xproc"
xmlns:c="http://www.w3.org/ns/xproc-step" version="1.0">
<p:input port="source">
<p:document href="file:///Users/jstor/localApps/xproc/doc.xml"/>
</p:input>
<p:identity/>
<p:store href="file:///Users/jstor/localApps/xproc/opx1.xml"/>

</p:declare-step>

[Mircea]

Hello,

The 1.0.12 Calumet integration works fine with the 12.0 version of oXygen.
The problems you encounter are raised from the URI-handling capabilities of Calumet.
This means the filepaths you provide are somehow incorect. I tried the same saples you provided (of course with different filepaths) and the samples worked succesfully.
The dynamic error XC0050 is thrown if the URI scheme is not supported or the step cannot store to the specified location, while the 'null stream' error speaks for itself.

Regards,
Mircea

[mstoef]

Well, I am able to run both samples via the Calabash processor without any trouble. Is there something specific about the Calumet implementation that might explain the difference?

[mstoef]

It looks like I have a problem obtaining or writing files to disk. Any clues?

[Mircea]

It seems indeed to be a problem on Mac. We are investigating this, and we will keep you informed.

[mstoef]

I wasn't sure if this was a problem in Oxygen or Calumet. I posted the same issue to the Calumet message board, and they gave this response:

https://community.emc.com/message/521808#521808

[george]

Thanks for updating us on this.
I was about to contact Vojtech as in the end we got the stacktrace below that indicates indeed an issue in Calumet. I am happy to hear that the issue has already been fixed in Calumet.

Code: Select all

ro.sync.xml.transformer.xproc.XProcTransformer - java.lang.NullPointerException: <null> stream

java.lang.NullPointerException: <null> stream

    at com.emc.documentum.xml.xproc.util.impl.XProcSerializationUtil.serialize(XProcSerializationUtil.java:82)

    at com.emc.documentum.xml.xproc.util.impl.XProcSerializationUtil.serialize(XProcSerializationUtil.java:127)

    at com.emc.documentum.xml.xproc.util.impl.XProcUtilImpl.serialize(XProcUtilImpl.java:52)

    at com.emc.documentum.xml.xproc.plugin.oxygen.XProcTransformerImpl.serialize(XProcTransformerImpl.java:318)

    at com.emc.documentum.xml.xproc.plugin.oxygen.XProcTransformerImpl.serialize(XProcTransformerImpl.java:298)

    at com.emc.documentum.xml.xproc.plugin.oxygen.XProcTransformerImpl.processOutput(XProcTransformerImpl.java:255)

    at com.emc.documentum.xml.xproc.plugin.oxygen.XProcTransformerImpl.transform(XProcTransformerImpl.java:124)

    at ro.sync.xml.transformer.xproc.XProcTransformer$2.run(XProcTransformer.java:470)

    at java.lang.Thread.run(Thread.java:680)

Best Regards,
George