Project

Profile

Help

Bug #4670

closed

Documentation of Java to XDM conversion is incomplete

Added by Michael Kay over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Documentation
Sprint/Milestone:
-
Start date:
2020-08-05
Due date:
% Done:

100%

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

Description

The class JPConverter, which handles conversion of Java values to XDM, contains code that recognises a number of Java classes and applies custom conversion to them, including:

URI, URL, Date. Instant, LocalDateTime, ZonedDateTime, OffsetDateTime, LocalDate

The documentation at http://www.saxonica.com/documentation/index.html#!extensibility/functions/function-result makes no mention of this.

Moreover, the JAXP information at http://www.saxonica.com/documentation/index.html#!using-xsl/embedding/jaxp-transformation doesn't link to this page to explain that these conversions are applied when using Transformer.setParameter()

In relation to the JAXP XPath API:

(a) At http://www.saxonica.com/documentation/index.html#!xpath-api/jaxp-xpath/context-node there is no mention that the context item does not have to be a node, and that these Java-to-XDM conversion rules are applied

(b) There is no mention that the JAXP VariableResolver can return Java values which are converted to XDM values using these conversion rules.

Please register to edit this issue

Also available in: Atom PDF