Michael Ludwig schrieb:
When passed a URI containing a fragment identifier ("doc#bla"), the
document() function should interpret it according to the document's
ID table, which can be accessed using the id() function.
[example snipped]
Xalan 2.7.1 disregards the fragment identifier and copies the entire
document instead of doing a lookup using the document's ID table.
The XSLT 1.0 specification says:
If the URI reference does contain a fragment identifier, the
function returns a node-set containing the nodes in the tree
identified by the fragment identifier of the URI reference. The
semantics of the fragment identifier is dependent on the media
type of the result of retrieving the URI. If there is an error in
processing the fragment identifier, the XSLT processor may signal
the error; if it does not signal the error, it must recover by
returning an empty node-set.
-- http://www.w3.org/TR/1999/REC-xslt-19991116#document
Should I register this as a Xalan-J bug? Or is it just a missing
feature?
There is only one match for "fragment identifier" in Xalan-J.
https://issues.apache.org/jira/browse/XALANJ
Michael Ludwig
