[
https://issues.apache.org/jira/browse/XALANJ-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mukul Gandhi updated XALANJ-2646:
---------------------------------
Description:
I'm creating this jira issue, to track implementation of XSLT 3.0's
xsl:for-each-group instruction, for XalanJ's interpretive processor.
I've done little bit of implementation for this, that seems to work fine for
various primary XSLT 3.0 xsl:for-each-group use cases. The XSLT 3.0 structural
implementation for xsl:for-each-group, implementing the XSLT element
xsl:for-each-group, and functions fn:current-group(), fn:current-grouping-key()
have been completed. xsl:for-each-group's attributes "group-by" and
"group-adjacent" have been implemented. Currently, xsl:for-each-group's
grouping keys (i.e, value of xslt 3.0 function fn:current-grouping-key() for a
group) can have values typed as string, number or boolean (any other XPath
typed value for xslt 3.0's grouping keys is converted to a string value).
The codebase changes for these mentioned XSLT 3.0 implementation aspects, have
been committed to xalan-java repo's branch xalan-j_xslt3.0.
was:
I'm creating this jira issue, to track implementation of XSLT 3.0's
xsl:for-each-group instruction, for XalanJ's interpretive processor.
I've done little bit of implementation for this, that seems to work fine for
various primary XSLT 3.0 xsl:for-each-group use cases. The XSLT 3.0 structural
implementation for xsl:for-each-group, implementing the XSLT element
xsl:for-each-group, and functions fn:current-group(), fn:current-grouping-key()
have been completed. xsl:for-each-group's attributes "group-by" and
"group-adjacent" have been implemented. Currently, xsl:for-each-group's
grouping keys (i.e, value of xslt 3.0 function fn:current-grouping-key() for a
group) can have values typed as string, number or boolean (any other XPath data
type for xslt 3.0's grouping keys is converted to a string value).
The codebase changes for these mentioned XSLT 3.0 implementation aspects, have
been committed to xalan-java repo's branch xalan-j_xslt3.0.
> Implementation of xslt 3.0's xsl:for-each-group instruction, for XalanJ's
> interpretive processor
> ------------------------------------------------------------------------------------------------
>
> Key: XALANJ-2646
> URL: https://issues.apache.org/jira/browse/XALANJ-2646
> Project: XalanJ2
> Issue Type: New Feature
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
> Components: Xalan-interpretive
> Reporter: Mukul Gandhi
> Assignee: Mukul Gandhi
> Priority: Major
> Attachments: xsl3_for_each_group_test_files.zip
>
>
> I'm creating this jira issue, to track implementation of XSLT 3.0's
> xsl:for-each-group instruction, for XalanJ's interpretive processor.
> I've done little bit of implementation for this, that seems to work fine for
> various primary XSLT 3.0 xsl:for-each-group use cases. The XSLT 3.0
> structural implementation for xsl:for-each-group, implementing the XSLT
> element xsl:for-each-group, and functions fn:current-group(),
> fn:current-grouping-key() have been completed. xsl:for-each-group's
> attributes "group-by" and "group-adjacent" have been implemented. Currently,
> xsl:for-each-group's grouping keys (i.e, value of xslt 3.0 function
> fn:current-grouping-key() for a group) can have values typed as string,
> number or boolean (any other XPath typed value for xslt 3.0's grouping keys
> is converted to a string value).
> The codebase changes for these mentioned XSLT 3.0 implementation aspects,
> have been committed to xalan-java repo's branch xalan-j_xslt3.0.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
