Project

Profile

Help

Bug #1516

closed

Class cast exception occurs when trying to use a JavaScript DOM document node within XSLT

Added by Philip Fearon almost 12 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Sprint/Milestone:
Start date:
2012-05-04
Due date:
% Done:

100%

Estimated time:
Platforms:

Description

If a DOM document node is returned as the result of a JavaScript call made within XSLT, the document node is not wrapped properly - causing a class cast extension.

This issue manifests itself when calling any user-defined or browser client function, the workaround in most cases would be to use a wrapper JavaScript function that returned the top-level element instead of the document node.

Actions #1

Updated by Philip Fearon almost 12 years ago

  • Status changed from New to Resolved
Actions #2

Updated by Philip Fearon almost 12 years ago

  • Sprint/Milestone set to Release 1.0
Actions #3

Updated by Philip Fearon almost 12 years ago

  • % Done changed from 0 to 100
Actions #4

Updated by O'Neil Delpratt about 11 years ago

  • Status changed from Resolved to Closed
  • Sprint/Milestone changed from Release 1.0 to Release 1.1
  • Found in version changed from Beta 0.2 to 1.0
  • Fixed in version set to 1.1

Bug fixed for Saxon-CE version 1.1 release

Please register to edit this issue

Also available in: Atom PDF