[oXygen-user] configuring a custom calabash

Imsieke, Gerrit, le-tex gerrit.imsieke at le-tex.de
Mon Mar 18 02:13:20 CDT 2013

I’m running oXygen 14.2 on Windows 7 64bit.

I tried to configure a customized calabash. There’s a calabash.bat file, 
https://subversion.le-tex.de/common/calabash/calabash.bat, that I 
checked out locally and specified as a custom processor, but I also 
tried to give the Java invocation explicitly, as seen in my project 

                                 <field name="cmd">
                                     <String>java -cp 
com.xmlcalabash.drivers.Main -E 
org.apache.xml.resolver.tools.CatalogResolver -U 
org.apache.xml.resolver.tools.CatalogResolver -c 
${pdu}/calabash/lib/ltx-unzip/ltx-config.xml </String>

The first problem that I ran into was that Windows gave an access denied 
error. I knew that it was Windows because it was in German while my 
oXygen installation is in English.

This will become important to overcome later because the custom Calabash 
needs to run on users’ computers. They don’t have admin privileges.

So I ran oXygen as admin. Then it ran in principle, but the (command 
line?) options – input and output ports, the pipeline, and options – 
that I configured in the transformation scenario apparently weren’t 
passed to the script. The output was only the usage information of my 
custom calabash.

In the help I read an entry called “Integration of an External XProc 
Engine”. I don’t know whether that is relevant to my problem. Do I 
really have to implement 
ro.sync.xml.transformer.xproc.api.XProcTransformerInterface myself? 
What’s the purpose of being able to configure an external script / Java 
invocation as XProc engine?

When I think about configuring an engine.xml file for my purposes, I’m 
unsure how to map Calabash’s -c option, where I specify an option to use 
our configuration file that maps a step name to a class that implements 
an extension.

The config file is here: 

If someone at syncro soft wants to play around with the custom Calabash, 
just check it out with svn.

Thanks for your help.


More information about the oXygen-user mailing list