Saxon 8.2 issue
-
madde001
- Posts: 80
- Joined: Fri Apr 23, 2004 5:24 pm
- Location: Durham, NC, USA
Saxon 8.2 issue
Having trouble getting oXygen to recognize the new release of Saxon (8.2).
Release docs (http://www.saxonica.com/documentation/d ... ation.html) mention that new JAXP 1.3 support in this Saxon release requires separate installation of JAXP 1.3 library for JDK 1.4x, but I am already using JDK 1.5.
Release docs (http://www.saxonica.com/documentation/d ... ation.html) mention that new JAXP 1.3 support in this Saxon release requires separate installation of JAXP 1.3 library for JDK 1.4x, but I am already using JDK 1.5.
-
george
- Site Admin
- Posts: 2096
- Joined: Thu Jan 09, 2003 2:58 pm
Hi John,
Saxon 8.2 was released close to the oXygen 5.1 release and also it contained a lot of problems accoring with the reports on the saxon-help list so we decided against integrating it in oXygen 5.1.
As you know it contains API changes and these changes do not allow getting it to work by overwritting the Saxon 8.1.1 jars that are shipped with oXygen 5.1.
All you can do at this time is to place the jars in some directory and configure an external tool for invoking it. You will have there some macros that will be expanded when the external tool is invoked so you should be able to reuse it.
If you have difficulties getting Saxon 8.2 working through the external tools support let us know.
Best Regards,
George
Saxon 8.2 was released close to the oXygen 5.1 release and also it contained a lot of problems accoring with the reports on the saxon-help list so we decided against integrating it in oXygen 5.1.
As you know it contains API changes and these changes do not allow getting it to work by overwritting the Saxon 8.1.1 jars that are shipped with oXygen 5.1.
All you can do at this time is to place the jars in some directory and configure an external tool for invoking it. You will have there some macros that will be expanded when the external tool is invoked so you should be able to reuse it.
If you have difficulties getting Saxon 8.2 working through the external tools support let us know.
Best Regards,
George
-
madde001
- Posts: 80
- Joined: Fri Apr 23, 2004 5:24 pm
- Location: Durham, NC, USA
George,
That's fine, I'll wait until things stabilize. I thought I'd report this in case it hadn't come up on your radar.
Another thing, though. I was trying out the schema-aware version of Saxon. It seems like the "schema-aware" option to apply validation to the source xml when there is an associated schema (the option that you would turn on from the SaxonSA command line using the -val option), is not turned on when it is called from within oXygen environment.
I infer this, because when I apply a transform using SA to an invalid document that has a schema associated through a <xsi:schemaLocation> element, then SA should report an error and fail the transform if this option is ON. But this doesn't happen; the transform succeeds.
So, when using SA, is there a way from within oXygen to access the setting of this switch so you can turn default validation ON? (A suggestion: a checkbox in the "Edit scenario/XSLT" dialog box when Saxon SA is the selected transformer. Perhaps also a checkbox in the Preferences/XSLT dialog box to turn this switch on/off by default when SA is chosen as the default transformer for XSLT 2.0.)
Thanks,
John
That's fine, I'll wait until things stabilize. I thought I'd report this in case it hadn't come up on your radar.
Another thing, though. I was trying out the schema-aware version of Saxon. It seems like the "schema-aware" option to apply validation to the source xml when there is an associated schema (the option that you would turn on from the SaxonSA command line using the -val option), is not turned on when it is called from within oXygen environment.
I infer this, because when I apply a transform using SA to an invalid document that has a schema associated through a <xsi:schemaLocation> element, then SA should report an error and fail the transform if this option is ON. But this doesn't happen; the transform succeeds.
So, when using SA, is there a way from within oXygen to access the setting of this switch so you can turn default validation ON? (A suggestion: a checkbox in the "Edit scenario/XSLT" dialog box when Saxon SA is the selected transformer. Perhaps also a checkbox in the Preferences/XSLT dialog box to turn this switch on/off by default when SA is chosen as the default transformer for XSLT 2.0.)
Thanks,
John
-
george
- Site Admin
- Posts: 2096
- Joined: Thu Jan 09, 2003 2:58 pm
Hi John,
That is indeed not handled by oXygen. There are also a couple of other options that can be controlled, one is if these errors should be treated as fatal or as warnings.
Further we can go for making a built in behavior of oXygen that should work in all the cases, for instance going for applying the validation and reporting the errors as warnings, not fatal errors or we can integrate all the Saxon SA options in a preferences dialog (we detected about 6 such options).
We would prefer to go with first option, that is always enable validation and treat the errors as warniongs and not as fatal errors, that is the transformation will continue. Do you consider that satisfactory?
We are in process also to see if Saxon allows setting the default values for these options externally, through a system property for instance that can be passed using the -D java switch. Tf this is possible then we have a workaround.
Best Regards,
George
That is indeed not handled by oXygen. There are also a couple of other options that can be controlled, one is if these errors should be treated as fatal or as warnings.
Further we can go for making a built in behavior of oXygen that should work in all the cases, for instance going for applying the validation and reporting the errors as warnings, not fatal errors or we can integrate all the Saxon SA options in a preferences dialog (we detected about 6 such options).
We would prefer to go with first option, that is always enable validation and treat the errors as warniongs and not as fatal errors, that is the transformation will continue. Do you consider that satisfactory?
We are in process also to see if Saxon allows setting the default values for these options externally, through a system property for instance that can be passed using the -D java switch. Tf this is possible then we have a workaround.
Best Regards,
George
-
madde001
- Posts: 80
- Joined: Fri Apr 23, 2004 5:24 pm
- Location: Durham, NC, USA
Hi George,
I've been out of the loop for quite a while, busy on other things. But I'm back again and really enjoying v6.
Were you ever able to get this issue with SaxonSA fixed? I've just monkeyed with it a bit, but it still seems like automatic validation is still not kicking in when transforms are invoked. This is with 8.4SA.
Also, in v6 I'm not seeing my SaxonSA showing up as a choice in the transformer dropdown menu in the Debugger perspective. I do see it in the Transformation Scenario setup dialog.
(It's been awhile and I can't remember--maybe Saxon8 was never working in Debugger perspective?)
John
I've been out of the loop for quite a while, busy on other things. But I'm back again and really enjoying v6.
Were you ever able to get this issue with SaxonSA fixed? I've just monkeyed with it a bit, but it still seems like automatic validation is still not kicking in when transforms are invoked. This is with 8.4SA.
Also, in v6 I'm not seeing my SaxonSA showing up as a choice in the transformer dropdown menu in the Debugger perspective. I do see it in the Transformation Scenario setup dialog.
(It's been awhile and I can't remember--maybe Saxon8 was never working in Debugger perspective?)
John