Project

Profile

Help

Bug #2058

closed

No location information for xsl:message if evaluation of error-code fails

Added by Johannes Harth about 10 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Diagnostics
Sprint/Milestone:
-
Start date:
2014-04-23
Due date:
% Done:

0%

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

Description

Call 'te.setLocator(this);' directly after creation of the exception to ensure it's set every time


Files

Actions #1

Updated by Michael Kay about 10 years ago

Thanks for offering this. Technically, it looks fine.

Sorry to be tedious, but could you please confirm that you are submitting this code to be released under the Mozilla Public License and that you have authority (e.g. from your employer) to submit it?

(In future, for a small change like this, there's less admin hassle if you just describe the change that's needed rather than submitting code; we have to review it line-by-line anyway to assess whether test cases are needed).

Actions #2

Updated by Johannes Harth about 10 years ago

I am the author of the attached patch file and I do confirm that I release this code under the Mozilla Public License.

Hopefully this formal statement satisfies the necessary administration hassle.

I am also fine if you do not apply the patch but just take it as a guide and write you on solution.

In the case that this would mean less hassle for you and it would speed up the implementation process, go for it!

Actions #3

Updated by Michael Kay about 10 years ago

  • Tracker changed from Patch to Bug
  • Subject changed from Always set SourceLocator for all TerminationExceptions to No location information for xsl:message if evaluation of error-code fails
  • Category set to Diagnostics
  • Status changed from New to Resolved
  • Assignee set to Michael Kay
  • Priority changed from Low to Normal

Many thanks.

Actions #4

Updated by O'Neil Delpratt over 9 years ago

  • Status changed from Resolved to Closed

Bug fixed in the Saxon maintenance release 9.5.1.6

Please register to edit this issue

Also available in: Atom PDF