Project

Profile

Help

Bug #1459

closed

When type-checking fails within an Attribute Value Template (AVT) the error message is unclear about the cause.

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

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

100%

Estimated time:
Platforms:

Description

For common type-checking errors within an AVT, an XPath Exception code is supplied in the Saxon-CE log, but there's no explanation of the meaning of this code. Also, the location reported is not specific enough.

Actions #1

Updated by Philip Fearon about 12 years ago

  • Status changed from New to Resolved

More details is now included with the error message. No specifix change has been made to improve the granularity of the reported location - but Saxon-CE now has a trace capability which can provide more detail if the error location isn't obvious. The approach should be to switch tracing on (?logLevel = FINEST), and re-run the XSLT, the trace (in the browser development console) will stop at the error location.

Actions #2

Updated by Philip Fearon almost 12 years ago

  • Fixed in version set to Beta 0.2
Actions #3

Updated by Philip Fearon almost 12 years ago

  • Sprint/Milestone set to Beta 0.2
Actions #4

Updated by O'Neil Delpratt about 11 years ago

  • Status changed from Resolved to Closed
  • Fixed in version changed from Beta 0.2 to 1.0

Fixed in Saxon-CE version 1.0

Actions #5

Updated by O'Neil Delpratt about 11 years ago

  • Sprint/Milestone changed from Beta 0.2 to Release 1.0
  • % Done changed from 0 to 100

Please register to edit this issue

Also available in: Atom PDF