[jira] [Resolved] (XALANJ-2844) xpath 3.1 schema awareness implementation
"Mukul Gandhi (Jira)" <[email protected]> Sat, 16 May 2026 05:29:00 +0000 (UTC)
| Newsgroups | gmane.text.xml.xalan.devel |
|---|---|
| Message-ID | <[email protected]> |
[ https://issues.apache.org/jira/browse/XALANJ-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mukul Gandhi resolved XALANJ-2844.
----------------------------------
Resolution: Fixed
I'm resolving this jira issue as fixed, since implementation for this jira issue has been committed to Xalan Java xslt 3.0 development branch.
> xpath 3.1 schema awareness implementation
> -----------------------------------------
>
> Key: XALANJ-2844
> URL: https://issues.apache.org/jira/browse/XALANJ-2844
> 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
> Affects Versions: xslt3.0_alpha1
> Reporter: Mukul Gandhi
> Assignee: Mukul Gandhi
> Priority: Major
>
> We've implemented XPath 3.1 native schema awareness implementation within Xalan Java xslt 3.0 development branch. I'm creating this jira issue to track implementation of this Xalan Java xslt 3.0 feature.
> As of now, following XPath 3.1 schema awareness features are available, within Xalan Java xslt 3.0 implementation:
> 1) Xalan Java command-line utility org.apache.xalan.xslt.Process has been modified to add an option -xsval for schema awareness feature. This works when, this command-line utility is invoked with option -flavor d2d (i.e, an XML DOM is provided as input to XSL transformation).
> 2) Xalan Java xslt 3.0 implementation of XPath 3.1 operators +, -, *, idiv, div and mod have been modified to make use of XPath 3.1 schema awareness.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)