Project

Profile

Help

Bug #1644

closed

"FORG0006: Effective boolean value is not defined" for a TEI transformation with byteCodeGeneration ON

Added by Alex Jitianu about 12 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Low
Category:
Byte code generation
Sprint/Milestone:
-
Start date:
2012-11-13
Due date:
% Done:

100%

Estimated time:
Legacy ID:
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:
Platforms:

Description

Hi,

We stumbled upon the following exception while running a TEI (Text Encoding Initiative) transformation with Saxon 9.4.0.6 EE with byte code generation ON:

Error on line 1338 of RngToRnc.xsl:
  FORG0006: Effective boolean value is not defined
Transformation failed: Run-time errors were reported

To reproduce it you first have to download the TEI stylesheets v6.19 available at http://sourceforge.net/projects/tei/files/Stylesheets/. After that, just run a transformation on the attached XML file using as XSL: tei-xsl-6.19/xml/tei/stylesheet/odds2/odd2lite.xsl. The transformation will fail with the above error message.

The transformation succeeds when byte code generation is disabled. I'm sorry I didn't succeeded in creating a smaller example to reproduce the issue.


Files

tei_error.xml (1.32 MB) tei_error.xml Alex Jitianu, 2012-11-13 16:01
Actions #1

Updated by O'Neil Delpratt about 12 years ago

  • Category set to Byte code generation
  • Assignee set to O'Neil Delpratt

Thanks for reporting this bug. We are now investigating it

Actions #2

Updated by O'Neil Delpratt about 12 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Bug fixed and committed to subversion. The fix will be available in the next maintenance release.

The problem in bytecode was that the code generated for computing EBV on a xs:anyURI was incorrect.

A workaround would be to wrap the call to namespace-uri(.) in a xs:string, i.e. on line 1338.

Actions #3

Updated by O'Neil Delpratt over 11 years ago

  • Status changed from Resolved to Closed
  • Fixed in version set to 9.4.0.7

Bug closed. Fixed in Saxon maintenance release 9.4.0.7

Please register to edit this issue

Also available in: Atom PDF