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

Mukul Gandhi updated XALANJ-2697:
---------------------------------
    Summary: xpath 3.1 sequence type expression implementation, and their use 
with xslt instructions xsl:variable, xsl:template, xsl:param, xsl:with-param 
using an attribute "as"  (was: Implementation of xpath 3.1 sequence type 
expressions, and their use with xslt 3.0 instructions xsl:variable, 
xsl:template, xsl:param, xsl:with-param using an attribute "as", for XalanJ's 
interpretive processor)

> xpath 3.1 sequence type expression implementation, and their use with xslt 
> instructions xsl:variable, xsl:template, xsl:param, xsl:with-param using an 
> attribute "as"
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: XALANJ-2697
>                 URL: https://issues.apache.org/jira/browse/XALANJ-2697
>             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: transformation, Xalan-interpretive, XPath
>            Reporter: Mukul Gandhi
>            Assignee: Mukul Gandhi
>            Priority: Major
>             Fix For: xslt3.0_alpha1
>
>
> I'm creating this jira issue, to track implementation of xpath 3.1 sequence 
> type expressions, and their use with xslt 3.0 instructions xsl:variable, 
> xsl:template, xsl:param, xsl:with-param using an attribute "as".
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to