Actions
Bug #2725
closed
xml-to-json() problems
Start date:
2016-04-25
Due date:
% Done:
100%
Estimated time:
Legacy ID:
Applies to branch:
9.7, trunk
Fix Committed on Branch:
9.7, trunk
Fixed in Maintenance Release:
Platforms:
Description
(1) xml-to-json crashes if the input contains a <j:number> element containing an invalid number.
(2) if the input has escaped=yes, escape sequences in the original (for example \u0061) are not retained unless they represent characters for which JSON requires escaping. The specification says that valid JSON escape sequences in the input should be retained in the output.
Updated by O'Neil Delpratt about 8 years ago
- Category set to XPath conformance
- Status changed from New to In Progress
- Assignee set to Michael Kay
- Priority changed from Low to Normal
- Applies to branch 9.7 added
Updated by Michael Kay about 8 years ago
- Status changed from In Progress to Resolved
- Applies to branch 9.8 added
- Fix Committed on Branch 9.7, 9.8 added
Fixed on the 9.7 and 9.8 branches. Many new test cases added to XSLT3 and QT3 test suites.
Updated by O'Neil Delpratt almost 8 years ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in Maintenance Release 9.7.0.5 added
Bug fix applied in the Saxon 9.7.0.5 maintenance release.
Updated by O'Neil Delpratt almost 7 years ago
- Applies to branch trunk added
- Applies to branch deleted (
9.8)
Updated by O'Neil Delpratt almost 7 years ago
- Fix Committed on Branch trunk added
- Fix Committed on Branch deleted (
9.8)
Please register to edit this issue
Actions
.