Hi, Is there any way to generate a schema's SCM from within oXygen? http://saxonica.com/documentation/schema-processing/scm.xml Regards, -- Florent Georges http://fgeorges.org/
Hello, The Schema Component Model of an XML Schema can be generated in Oxygen only by creating and running an external tool with a command line based on the |com.saxonica.Validate| class, for example: java -cp ${oxygenInstallDir}\lib\saxon9ee.jar;${oxygenInstallDir} com.saxonica.Validate -scmout:${cfd}\${cfn}_SCM.xml ${cf} This command is applied to the current file (the ${cf} editor variable) which has to contain a schema reference as an xsi:schemaLocation attribute. If the XML file does not contain such a schema reference the command line has to specify the schema explicitly which means it is not generic anymore: java -cp ${oxygenInstallDir}\lib\saxon9ee.jar;${oxygenInstallDir} com.saxonica.Validate -xsd:S:\temp\personal.xsd -scmout:${cfd}\${cfn}_SCM.xml ${cf} Regards, Sorin Florent Georges wrote:
Hi,
Is there any way to generate a schema's SCM from within oXygen?
http://saxonica.com/documentation/schema-processing/scm.xml
Regards,
Sorin Ristache wrote: Hi Sorin,
The Schema Component Model of an XML Schema can be generated in Oxygen only by creating and running an external tool
But Saxon EE is only available for built-in features in oXygen, right? Not through an external tool. Or is it? Regards, -- Florent Georges http://fgeorges.org/
That is correct, the Saxon EE license embedded in Oxygen is available only for built-in features. You need a Saxon EE license file in the classpath of the java command. Regards, Sorin Florent Georges wrote:
Sorin Ristache wrote:
Hi Sorin,
The Schema Component Model of an XML Schema can be generated in Oxygen only by creating and running an external tool
But Saxon EE is only available for built-in features in oXygen, right? Not through an external tool. Or is it?
Regards,
Hi Florent, The Saxon EE license is restricted to usage from within oXygen only. If you put that command in an ant script, add oxygen.jar in the classpath and invoke it only from within oXygen through a transformation scenario then I think it should work. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 6/16/11 3:32 PM, Florent Georges wrote:
Sorin Ristache wrote:
Hi Sorin,
The Schema Component Model of an XML Schema can be generated in Oxygen only by creating and running an external tool
But Saxon EE is only available for built-in features in oXygen, right? Not through an external tool. Or is it?
Regards,
George Cristian Bina wrote: Hi George,
The Saxon EE license is restricted to usage from within oXygen only. If you put that command in an ant script, add oxygen.jar in the classpath and invoke it only from within oXygen through a transformation scenario then I think it should work.
Thanks for the idea. Unfortunately it does not work (I guess you meant saxon9ee.jar instead of oxygen.jar, but anyway I tried both). Regards, -- Florent Georges http://fgeorges.org/
Hi Florent, The workaround George suggested would have worked only if you wanted to use Saxon EE as an <xslt> task with ANT. So I don't think there is another option but to have a license for Saxon EE. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 6/16/2011 7:09 PM, Florent Georges wrote:
George Cristian Bina wrote:
Hi George,
The Saxon EE license is restricted to usage from within oXygen only. If you put that command in an ant script, add oxygen.jar in the classpath and invoke it only from within oXygen through a transformation scenario then I think it should work.
Thanks for the idea. Unfortunately it does not work (I guess you meant saxon9ee.jar instead of oxygen.jar, but anyway I tried both).
Regards,
participants (4)
-
Florent Georges -
George Cristian Bina -
Radu Coravu -
Sorin Ristache