Hi Florent,
oXygen allows you to specify extensions at the level of transformation
scenario. Use the "Extensions" button in the transformation scenario
dialog, see
http://www.oxygenxml.com/doc/ug-oxygen/defining-new-transformation-scenario.html#figure-configure-transformation-dialog-xslt
You can also just drop the extensions jars in the oXygen lib folder (in
the case of oXygen standalone, for the Eclipse plugin you need to edit
the plugin.xml to point to your jars). oXygen will automatically load
those jars at startup. There is also a command line property that you
can use to point to jars located in other folders, see
com.oxygenxml.additional.classpath on the page below:
http://www.oxygenxml.com/doc/ug-oxygen/configuring-XSLT-processor-extensions-paths.html
Best Regards,
George
--
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
Florent Georges wrote:
Hi,
Is there any way to alter the built-in XSLT processors? I
have a set of extensions I use often, and I'd like to have a
Saxon processor in oXygen that behaves exactly as the built-in
Saxon 9 B processor. The easiest way would be to be able to
add a JAR file in the classpath of the built-in processor, but
I didn't find a way to do so.
So I created a new processor, with all Saxon 9 B JARs in the
classpath, as well as my extension JAR. That is fine, but
this processor doesn't take into account global preferences,
like XML Catalogs.
Did I miss an easier way to achive my goal? If not, how can
I configure the XML Catalogs support for my custom processor?
(I know how to configure Saxon from the command line, but I'd
like to know how I can get the catalog URIs to use)
Regards,
_______________________________________________
oXygen-user mailing list
[email protected]
http://www.oxygenxml.com/mailman/listinfo/oxygen-user