Custom Saxon processor and global preferences
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, -- Florent Georges http://www.fgeorges.org/
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.... 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... 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,
George Cristian Bina wrote: Hi George,
oXygen allows you to specify extensions at the level of transformation scenario.
Yes, but when you often use a simple extension, this is easier to add its JAR each time to the classpath, instead that modifying each scenario... But I didn't know about com.oxygenxml.additional.classpath and ${oxygenHome}/lib/. Sounds like exactly fitting my needs (just have to test at home.) Thanks for your prompt answer! -- Florent Georges http://www.fgeorges.org/
Florent Georges wrote:
But I didn't know about com.oxygenxml.additional.classpath and ${oxygenHome}/lib/. Sounds like exactly fitting my needs (just have to test at home.)
I confirm that works nice! Even the calls to Java extension functions (through the pseudo namespace "java:...") is recognized in the editor (this is not pointed out as an error anymore, as the processor used for this job has its classpath modified too.) On Mac OS X, I have to use the shell script now (to add the system property) so I don't have the nice icon anymore. But I do not really care :-) Thanks George, -- Florent Georges http://www.fgeorges.org/
On 12/8/08 8:34 PM, "Florent Georges" <lists@fgeorges.org> wrote:
Florent Georges wrote:
But I didn't know about com.oxygenxml.additional.classpath and ${oxygenHome}/lib/. Sounds like exactly fitting my needs (just have to test at home.)
I confirm that works nice! Even the calls to Java extension functions (through the pseudo namespace "java:...") is recognized in the editor (this is not pointed out as an error anymore, as the processor used for this job has its classpath modified too.)
On Mac OS X, I have to use the shell script now (to add the system property) so I don't have the nice icon anymore. But I do not really care :-)
You can modify the Info.plist file in the Oxygen app resource to add the appropriate Java parameters you need. Cheers, E. ---- Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc. email: ekimber@reallysi.com <mailto:ekimber@reallysi.com> office: 610.631.6770 | cell: 512.554.9368 2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403 www.reallysi.com <http://www.reallysi.com> | http://blog.reallysi.com <http://blog.reallysi.com> | www.rsuitecms.com <http://www.rsuitecms.com>
Eliot Kimber wrote:
You can modify the Info.plist file in the Oxygen app resource to add the appropriate Java parameters you need.
That works great! Thank you. Yes, I am really, really new to Mac OS X :-) -- Florent Georges http://www.fgeorges.org/
On 9 déc. 08, at 04:03, Florent Georges wrote:
That works great! Thank you. Yes, I am really, really new to Mac OS X :-)
Or you can change the environment.plist file located in the .MacOSX folder, inside your home directory. Jacques -- Mac OS X Server à votre service, seconde édition (Leopard) est disponible au "Monde en Tique" <http://www.lmet.fr>".
participants (4)
-
Eliot Kimber -
Florent Georges -
George Cristian Bina -
Jacques Foucry