[jira] [Commented] (XALANJ-2823) implementation of xpath 3.1 partial function applications
"Mukul Gandhi (Jira)" <[email protected]>
| Newsgroups | gmane.text.xml.xalan.devel |
|---|---|
| Message-ID | <[email protected]> |
[ https://issues.apache.org/jira/browse/XALANJ-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18036611#comment-18036611 ]
Mukul Gandhi commented on XALANJ-2823:
--------------------------------------
Thanks Joe, for thoughts. I agree.
I think, it'll be fine, if we can restructure the code within Xalan branch xalan-j_xslt3.0_mvn, with following Java packages,
org.apache.xsl.main
A new factory class here, with a user supplied conditional value to choose XSLT processor version, can invoke either org.apache.xsl.one or org.apache.xsl.three.
org.apache.xsl.one
Putting XSL processor code within branch master with state as of now, here
org.apache.xsl.three
Putting XSL processor code within branch xalan-j_xslt3.0_mvn with state as of now, here
If these suggestions are acceptable, I can try to modify Xalan code within branch xalan-j_xslt3.0_mvn as per this, over the next few days & weeks. After Xalan code repos branch xalan-j_xslt3.0_mvn, is modified as per this and tested appropriately, we can merge the new information within branch xalan-j_xslt3.0_mvn to master.
> implementation of xpath 3.1 partial function applications
> ---------------------------------------------------------
>
> Key: XALANJ-2823
> URL: https://issues.apache.org/jira/browse/XALANJ-2823
> Project: XalanJ2
> Issue Type: Task
> Security Level: No security risk; visible to anyone(Ordinary problems in Xalan projects. Anybody can view the issue.)
> Reporter: Mukul Gandhi
> Assignee: Mukul Gandhi
> Priority: Major
>
> I'm creating this jira issue to track, implementation of XPath 3.1 partial function applications within Xalan-J's XSLT 3.0 dev repos branch.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)