[oXygen-user] configuring a custom calabash

[Oxygen XML Editor Support]

Hello,


> 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.
Regarding the first problem, that shouldn't have happened unless it's 
trying to write to a folder with no write access (maybe the Oxygen 
installation folder from "Program Files").

> 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.
Unfortunately, none of the options/parameters from the XProc scenario 
can currently be passed to the custom engines. If the command line 
allows it, you will have to do manually do this in the custom engine 
configuration. Only the XProc document is passed: ${xproc}


> 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?
That's meant for developers who would want to integrate their XProc 
engine into Oxygen. AFAIK, Calabash doesn't implement this interface 
(XProcTransformerInterface).


> 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: 
> https://subversion.le-tex.de/common/calabash/lib/ltx-unzip/ltx-config.xml
>
> If someone at syncro soft wants to play around with the custom Calabash, 
> just check it out with svn.
That's only meant to work together with the implemented interface.


I believe you should rather try to use the custom calabash in place of 
the built-in one that Oxygen provides in: Oxygen/lib/xproc/calabash
Make a copy of that folder (place it somewhere else, NOT in 
Oxygen/lib/xproc) and customize the existing engine.xml with what you 
need, update the jars, etc.

Regards,
Adrian

Adrian Buza
oXygen XML Editor and Author Support

Tel: +1-650-352-1250 ext.202
Fax: +40-251-461482
support at oxygenxml.com
http://www.oxygenxml.com


Imsieke, Gerrit, le-tex wrote:
> 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 
> configuration:
>
>                                  <field name="cmd">
>                                      <String>java -cp 
> ${pd}/calabash/resolver/resolver.jar;${pd}/calabash/resolver;${pd}/calabash/calabash.jar;${pd}/calabash/lib;${pd}/calabash/lib/ltx-unzip 
> -Dfile.encoding=UTF8 
> -Dxml.catalog.files=${pdu}/calabash/resolver/catalog.xml 
> -Dxml.catalog.catalog-class-name=org.apache.xml.resolver.Resolver 
> 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>
>                                  </field>
>
> 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: 
> https://subversion.le-tex.de/common/calabash/lib/ltx-unzip/ltx-config.xml
>
> If someone at syncro soft wants to play around with the custom Calabash, 
> just check it out with svn.
>
> Thanks for your help.
>
> Gerrit
>
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at oxygenxml.com
> http://www.oxygenxml.com/mailman/listinfo/oxygen-user
>
>