[
https://issues.apache.org/jira/browse/XALANJ-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mukul Gandhi resolved XALANJ-2658.
----------------------------------
Resolution: Fixed
I'm marking this issue as resolved. We may reopen this jira issue, as per needs
of further enhancements to this XSLT xsl:analyze-string implementation by
XalanJ.
> Implementation of xslt 3.0's xsl:analyze-string instruction, for XalanJ's
> interpretive processor
> ------------------------------------------------------------------------------------------------
>
> Key: XALANJ-2658
> URL: https://issues.apache.org/jira/browse/XALANJ-2658
> 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_analyze_string_test_files.zip
>
>
> I'm creating this jira issue, to track implementation of XSLT 3.0's
> xsl:analyze-string 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:analyze-string use cases. The implementation of
> related XSLT 3.0 function fn:regex-group has also been completed, as part of
> this jira issue's implementation.
> Few relevant working test cases, for this jira issue have been attached as
> zip archive to this jira issue.
> 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]
