You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by "Mukul Gandhi (Jira)" <ji...@apache.org> on 2023/12/30 12:18:00 UTC

[jira] [Resolved] (XALANJ-2723) Implementation of xpath 3.1 function fn:deep-equal, for XalanJ's interpretive processor

     [ https://issues.apache.org/jira/browse/XALANJ-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mukul Gandhi resolved XALANJ-2723.
----------------------------------
    Resolution: Fixed

I'm marking this jira issue as resolved, since implementation for this jira issue, has been committed to the XalanJ dev repos's branch xalan-j_xslt3.0.

> Implementation of xpath 3.1 function fn:deep-equal, for XalanJ's interpretive processor
> ---------------------------------------------------------------------------------------
>
>                 Key: XALANJ-2723
>                 URL: https://issues.apache.org/jira/browse/XALANJ-2723
>             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, XPath, XPath-function
>            Reporter: Mukul Gandhi
>            Assignee: Mukul Gandhi
>            Priority: Major
>
> I'm creating this jira issue, to track implementation of xpath 3.1 function fn:deep-equal.
> I've written little bit of code for this, that has been committed to XalanJ dev repos's branch xalan-j_xslt3.0. Few related working test cases for these implementation aspects, have been committed as well to the same XalanJ dev repos's branch.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org