Issue Details (XML | Word | Printable)

Key: XALANJ-2292
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Henry Zongaro
Reporter: Henry Zongaro
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
XalanJ2

XSLTC doesn't handle xsl:param passed as second argument to key function correctly

Created: 17/Apr/06 08:50 PM   Updated: 11/Dec/07 04:57 PM
Return to search "STDCXX HP aCC issues"
Component/s: None
Affects Version/s: 2.7
Fix Version/s: 2.7.1

Time Tracking:
Not Specified

File Attachments:
  Size
XML File Licensed for inclusion in ASF works j2292.out 2006-04-17 08:56 PM Henry Zongaro 0.4 kB
XML File Licensed for inclusion in ASF works j2292.xml 2006-04-17 08:56 PM Henry Zongaro 0.3 kB
XML File Licensed for inclusion in ASF works j2292.xsl 2006-04-17 08:56 PM Henry Zongaro 0.7 kB

Reviewer: Christine Li
Resolution Date: 08/Jun/06 03:30 AM


 Description  « Hide
If the second argument to the XSLT key function is a template parameter, XSLTC always converts it to a string. However, the value could be a node set, in which case the result of the function should be the union of applying the function to the string values of all the nodes in the node set. Converting the node set to a string only gets the result for the first node in the node set.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Henry Zongaro added a comment - 17/Apr/06 08:56 PM
Attaching stylesheet (j2292.xsl), input document (j2292.xml) and expected output (j2292.out).

Henry Zongaro added a comment - 10/May/06 01:58 AM
Patch for XALANJ-2295 includes a fix for this problem.

Henry Zongaro added a comment - 08/Jun/06 03:30 AM
Applied patch attached to XALANJ-2295 to source repository.

Brian Minchau added a comment - 11/Dec/07 03:16 PM
This issue is no longer relevant for 2.7.1, it is fixed in 2.7.1.
Changing the affected version to 2.7.

Brian Minchau added a comment - 11/Dec/07 04:57 PM
Would the originator of this issue please verify that this issue is fixed in the 2.7.1 release, by adding a comment to this issue, so that we can close this issue.

A lack of response by February 1, 2008 will be taken as consent that we can close this resolved issue.

Regards,
Brian Minchau