Page 1 of 1

Using IAltovaXMLFactory with JAXP

Posted: Tue Jun 28, 2011 6:43 am
by wise1372
Altova has there XML processor/reporting tool available. In the past it was freely available and it is now available for a reason price. How can I use this tool for the JAXP processor? It provides the XML factory method the options screen suggest. What settings and value do I need to use to be able to use this processor for XSLT transformations in Oxygen?

Re: Using IAltovaXMLFactory with JAXP

Posted: Tue Jun 28, 2011 9:35 am
by sorin_ristache
Hello,

You can configure it as a JAXP processor only if it is implemented in Java, otherwise you can run it from Oxygen only as an external XSLT processor by configuring a command line for calling it.

If it is a Java tool (you have a jar file with the Java classes) just go to menu Preferences -> XML -> XSLT-FO-XQuery -> XSLT, set the complete class name of the transformer factory class in the text field, copy the jar file to the lib folder as instructed on the XSLT preferences panel and restart Oxygen. Your JAXP transformer will be used in a transformation scenario when you select the value JAXP in the Transformer combo box.

If it is not a Java tool you have to configure it as an external XSLT processor. You will set the new processor in a transformation scenario in the same way as for a JAXP processor, that is by selecting it in the Transformer combo box of the scenario edit dialog box.


Regards,
Sorin

Re: Using IAltovaXMLFactory with JAXP

Posted: Tue Jun 28, 2011 10:25 pm
by wise1372
Sorin,

Thank you for your reply I was unable to get the Java Jar model working even though Oxygen supports it. I did get the External engine working. The one question I have is it possible to pass the parameters through for a style sheet to the external engine?

Re: Using IAltovaXMLFactory with JAXP

Posted: Wed Jun 29, 2011 5:16 pm
by adrian
Hi,

Unfortunately for external engines there is currently no way to pass the parameters from the transformation scenario to the engine. You have to manually add them to the external engine command line.

We do have this request logged on our issue tracking tool and it will be implemented in a future version of Oxygen.


In this case the JAXP implementation would be preferable as Oxygen can pass XSLT parameters to it.

Regards,
Adrian