Reporting of Imported/Included XSLT Component in Error Messages

I have a complext XSLT made up of many parts. In running it from inside Oxygen using Saxon 9, I was getting an error message but the message was reported against a line number in the top-level style sheet. When I run the same script outside Oxygen the error messages is associated with the correct component file (not the top-level). Is this a limitation in Oxygen's integration with Saxon or a bug? The message in this case was a run-time error reporting that a template's parameter was not set by the caller and the default was not consistent with the declared data type of the parameter. Thanks, Eliot -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 610.631.6770 www.reallysi.com www.rsuitecms.com

Hello, The error message displayed in the Errors panel at the bottom of the oXygen window contains the file location and the line and column received from Saxon. If the error points to a different file outside oXygen then it is an oXygen bug. Can you post sample files for reproducing the problem? Thank you, Sorin Eliot Kimber wrote:
I have a complext XSLT made up of many parts.
In running it from inside Oxygen using Saxon 9, I was getting an error message but the message was reported against a line number in the top-level style sheet.
When I run the same script outside Oxygen the error messages is associated with the correct component file (not the top-level).
Is this a limitation in Oxygen's integration with Saxon or a bug?
The message in this case was a run-time error reporting that a template's parameter was not set by the caller and the default was not consistent with the declared data type of the parameter.
Thanks,
Eliot

Sorin Ristache wrote:
Hello,
The error message displayed in the Errors panel at the bottom of the oXygen window contains the file location and the line and column received from Saxon. If the error points to a different file outside oXygen then it is an oXygen bug. Can you post sample files for reproducing the problem?
I'll see what I can do. I think the problem is specifically in the case where a function is called in a match expression. Unfortunately, the style sheet where I noticed the problem is a monster that would be hard to make into a focused test case. Cheers, Eliot -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 610.631.6770 www.reallysi.com www.rsuitecms.com
participants (2)
-
Eliot Kimber
-
Sorin Ristache