[jira] [Updated] (XALANJ-2661) Implementation of xpath 3.1 function fn:string-join(), for XalanJ's interpretive processor

[ https://issues.apache.org/jira/browse/XALANJ-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Gandhi updated XALANJ-2661: - Attachment: fn_string_join_test_files.zip > Implementation of xpath 3.1 function fn:string-j

[jira] [Created] (XALANJ-2661) Implementation of xpath 3.1 function fn:string-join(), for XalanJ's interpretive processor

Mukul Gandhi created XALANJ-2661: Summary: Implementation of xpath 3.1 function fn:string-join(), for XalanJ's interpretive processor Key: XALANJ-2661 URL: https://issues.apache.org/jira/browse/XALANJ-2661

[jira] [Updated] (XALANJ-2645) Implementation of XPath 3.1 functions fn:matches() and fn:replace(), for XalanJ interpretive processor

[ https://issues.apache.org/jira/browse/XALANJ-2645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Gandhi updated XALANJ-2645: - Summary: Implementation of XPath 3.1 functions fn:matches() and fn:replace(), for XalanJ

[jira] [Created] (XALANJ-2665) Implementation of xpath 3.1 function fn:index-of for XalanJ's interpretive processor

Mukul Gandhi created XALANJ-2665: Summary: Implementation of xpath 3.1 function fn:index-of for XalanJ's interpretive processor Key: XALANJ-2665 URL: https://issues.apache.org/jira/browse/XALANJ-2665

[jira] [Resolved] (XALANJ-2665) Implementation of xpath 3.1 function fn:index-of for XalanJ's interpretive processor

[ https://issues.apache.org/jira/browse/XALANJ-2665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Gandhi resolved XALANJ-2665. -- Resolution: Fixed I'm marking this jira issue as resolved, since implementation for this jira

[jira] [Created] (XALANJ-2683) Implementation of xpath 3.1 component extraction functions on durations, for XalanJ's interpretive processor

Mukul Gandhi created XALANJ-2683: Summary: Implementation of xpath 3.1 component extraction functions on durations, for XalanJ's interpretive processor Key: XALANJ-2683 URL: https://issues.apache.org/jira/browse

[jira] [Resolved] (XALANJ-2683) Implementation of xpath 3.1 component extraction functions on durations, for XalanJ's interpretive processor

[ https://issues.apache.org/jira/browse/XALANJ-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Gandhi resolved XALANJ-2683. -- Resolution: Fixed I'm marking this jira issue as resolved, since implementation for this jira

[jira] [Created] (XALANJ-2681) Implementation of xpath 3.1 sequence constructor, using comma operator, for XalanJ's interpretive processor

Mukul Gandhi created XALANJ-2681: Summary: Implementation of xpath 3.1 sequence constructor, using comma operator, for XalanJ's interpretive processor Key: XALANJ-2681 URL: https://issues.apache.org/jira/browse

[jira] [Resolved] (XALANJ-2681) Implementation of xpath 3.1 sequence constructor, using comma operator, for XalanJ's interpretive processor

[ https://issues.apache.org/jira/browse/XALANJ-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Gandhi resolved XALANJ-2681. -- Resolution: Fixed I'm marking this jira issue as resolved, since implementation for this jira

[jira] [Updated] (XALANJ-2673) Implementation of xpath 3.1's "function item" inline function expressions processing, for XalanJ's interpretive processor

[ https://issues.apache.org/jira/browse/XALANJ-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Gandhi updated XALANJ-2673: - Description: I'm creating this jira issue, to track implementation of XPath 3.1's "fun

[jira] [Updated] (XALANJ-2673) Implementation of xpath 3.1's function item "inline function expression" processing, "built-in higher order functions" and "dynamic function calls", for XalanJ's interpr

[ https://issues.apache.org/jira/browse/XALANJ-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Gandhi updated XALANJ-2673: - Summary: Implementation of xpath 3.1's function item "inline function expression"

[jira] [Updated] (XALANJ-2673) Implementation of xpath 3.1's function item "inline function expression" processing, "built-in higher order functions" and "dynamic function calls", for XalanJ's interpr

[ https://issues.apache.org/jira/browse/XALANJ-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Gandhi updated XALANJ-2673: - Description: I'm creating this jira issue, to track implementation of XPath 3.1's function

[jira] [Updated] (XALANJ-2673) Implementation of xpath 3.1's "function item" inline function expressions processing, for XalanJ's interpretive processor

[ https://issues.apache.org/jira/browse/XALANJ-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Gandhi updated XALANJ-2673: - Description: I'm creating this jira issue, to track implementation of XPath 3.1's "fun

[jira] [Updated] (XALANJ-2673) Implementation of xpath 3.1's function item "inline function expression" processing, implementation of "built-in higher order functions" and "dynamic function calls", fo

[ https://issues.apache.org/jira/browse/XALANJ-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Gandhi updated XALANJ-2673: - Summary: Implementation of xpath 3.1's function item "inline function expression"

[jira] [Created] (XALANJ-2684) Implementation of xpath 3.1 node comparison operators 'is', '<<', '>>', for XalanJ's interpretive processor

Mukul Gandhi created XALANJ-2684: Summary: Implementation of xpath 3.1 node comparison operators 'is', '<<', '>>', for XalanJ's interpretive processor Key: XALANJ-2684 URL: https://issues.apache.org

[jira] [Resolved] (XALANJ-2684) Implementation of xpath 3.1 node comparison operators 'is', '<<', '>>', for XalanJ's interpretive processor

[ https://issues.apache.org/jira/browse/XALANJ-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Gandhi resolved XALANJ-2684. -- Resolution: Fixed I'm marking this jira issue as resolved, since implementation for this jira

[jira] [Resolved] (XALANJ-2685) Implementation of xpath 3.1 simple map operator '!', for XalanJ's interpretive processor

[ https://issues.apache.org/jira/browse/XALANJ-2685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Gandhi resolved XALANJ-2685. -- Resolution: Fixed I'm marking this jira issue as resolved, since implementation for this jira

[jira] [Created] (XALANJ-2685) Implementation of xpath 3.1 simple map operator '!', for XalanJ's interpretive processor

Mukul Gandhi created XALANJ-2685: Summary: Implementation of xpath 3.1 simple map operator '!', for XalanJ's interpretive processor Key: XALANJ-2685 URL: https://issues.apache.org/jira/browse/XALANJ-2685

[jira] [Updated] (XALANJ-2684) Implementation of xpath 3.1 node comparison operators "is", "<<", ">>", for XalanJ's interpretive processor

[ https://issues.apache.org/jira/browse/XALANJ-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Gandhi updated XALANJ-2684: - Summary: Implementation of xpath 3.1 node comparison operators "is", "<<&

[jira] [Updated] (XALANJ-2684) Implementation of xpath 3.1 node comparison operators 'is', '<<', '>>', for XalanJ's interpretive processor

[ https://issues.apache.org/jira/browse/XALANJ-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Gandhi updated XALANJ-2684: - Description: I'm creating this jira issue, to track implementation of xpath 3.1 node

[jira] [Created] (XALANJ-2682) Implementation of xpath 3.1 string concatenation operator "||", for XalanJ's interpretive processor

Mukul Gandhi created XALANJ-2682: Summary: Implementation of xpath 3.1 string concatenation operator "||", for XalanJ's interpretive processor Key: XALANJ-2682 URL: https://issues.apache.org/jira/bro

[jira] [Resolved] (XALANJ-2682) Implementation of xpath 3.1 string concatenation operator "||", for XalanJ's interpretive processor

[ https://issues.apache.org/jira/browse/XALANJ-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Gandhi resolved XALANJ-2682. -- Resolution: Fixed I'm marking this jira issue as resolved, since implementation for this jira

[jira] [Comment Edited] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735363#comment-17735363 ] Joe Kesselman edited comment on XALANJ-2474 at 6/20/23 5:27 PM: FWIW, I

[jira] [Comment Edited] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735363#comment-17735363 ] Joe Kesselman edited comment on XALANJ-2474 at 6/20/23 5:28 PM: FWIW, I

[jira] [Comment Edited] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735363#comment-17735363 ] Joe Kesselman edited comment on XALANJ-2474 at 6/20/23 5:28 PM: FWIW, I

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735419#comment-17735419 ] Joe Kesselman commented on XALANJ-2474: --- Hm. Actually, we never get to the point of calling

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17733368#comment-17733368 ] Vladimir Sitnikov commented on XALANJ-2474: --- [~kesh...@alum.mit.edu] , are you sure you pass

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17733364#comment-17733364 ] Joe Kesselman commented on XALANJ-2474: --- Read the stylesheets and look more carefully at the error

[jira] [Comment Edited] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17733368#comment-17733368 ] Vladimir Sitnikov edited comment on XALANJ-2474 at 6/16/23 7:26 AM

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17733372#comment-17733372 ] Joe Kesselman commented on XALANJ-2474: --- ... ah. I did miss the -param . Thanks, let me take

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17733256#comment-17733256 ] Joe Kesselman commented on XALANJ-2474: --- The test as provided is incomplete; it depends

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17733328#comment-17733328 ] Vladimir Sitnikov commented on XALANJ-2474: --- What do you mean "it depends on a resul

[jira] [Updated] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Kesselman updated XALANJ-2474: -- Attachment: jira-xalanj-2474.xml jira-xalanj-2474.xslt > document() funct

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17736235#comment-17736235 ] Joe Kesselman commented on XALANJ-2474: --- Note that the test demonstrates that *evaluate

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17736233#comment-17736233 ] Joe Kesselman commented on XALANJ-2474: --- Simplified and renamed testcase attached. If we fix

[jira] [Updated] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Kesselman updated XALANJ-2474: -- Attachment: identitext.xsl > document() function returns different values with xalan vers

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17736228#comment-17736228 ] Joe Kesselman commented on XALANJ-2474: --- Just in case, I tried the EXSLT *dyn:evaluate

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17736255#comment-17736255 ] Joe Kesselman commented on XALANJ-2474: --- Confirmed that calling ** to make the explicit document's

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17736269#comment-17736269 ] Joe Kesselman commented on XALANJ-2474: --- Confirmed XPathParser.getFunctionToken("doc

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17736258#comment-17736258 ] Joe Kesselman commented on XALANJ-2474: --- xalan:evaluate now redirects to EXSLT dyn:evaluate

[jira] [Comment Edited] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17736543#comment-17736543 ] Joe Kesselman edited comment on XALANJ-2474 at 6/24/23 10:40 PM: - When

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17736342#comment-17736342 ] Joe Kesselman commented on XALANJ-2474: --- Current suspicion is that the reason behavior changed

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17736513#comment-17736513 ] Joe Kesselman commented on XALANJ-2474: --- (Note that this also points out a failure in error

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17736543#comment-17736543 ] Joe Kesselman commented on XALANJ-2474: --- When XPaths are invoked from the stylesheet

[jira] [Resolved] (XALANJ-2669) Implementation of xpath 3.1's value comparison operators eq, ne, lt, le, gt, ge, for XalanJ's interpretive processor

[ https://issues.apache.org/jira/browse/XALANJ-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Gandhi resolved XALANJ-2669. -- Resolution: Fixed I'm marking this jira issue as resolved, since implementation for this jira

[jira] [Created] (XALANJ-2669) Implementation of xpath 3.1's value comparison operators eq, ne, lt, le, gt, ge, for XalanJ's interpretive processor

Mukul Gandhi created XALANJ-2669: Summary: Implementation of xpath 3.1's value comparison operators eq, ne, lt, le, gt, ge, for XalanJ's interpretive processor Key: XALANJ-2669 URL: https://issues.apache.org/jira

[jira] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474 ] Joe Kesselman deleted comment on XALANJ-2474: --- was (Author: JIRAUSER285361): Just in case, I tried the EXSLT *dyn:evaluate()* as a replacement for {*}xalan:evaluate(){*}. Not too

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735047#comment-17735047 ] Joe Kesselman commented on XALANJ-2474: --- If we continue down this path, the Xalan *NodeInfo

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17734357#comment-17734357 ] Joe Kesselman commented on XALANJ-2474: --- Since in this case the document() call is being used

[jira] [Created] (XALANJ-2672) Suggestion: avoid adding @author tag to javadoc, or document its use

Vladimir Sitnikov created XALANJ-2672: - Summary: Suggestion: avoid adding @author tag to javadoc, or document its use Key: XALANJ-2672 URL: https://issues.apache.org/jira/browse/XALANJ-2672

[jira] [Commented] (XALANJ-2671) Source code history lost in "clearing all contents" + "updating master branch, to have same contents as..." commits

[ https://issues.apache.org/jira/browse/XALANJ-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17739302#comment-17739302 ] Stanimir Stamenkov commented on XALANJ-2671: See this suggestion I've just created: * https

[jira] [Commented] (XALANJ-2671) Source code history lost in "clearing all contents" + "updating master branch, to have same contents as..." commits

[ https://issues.apache.org/jira/browse/XALANJ-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17739305#comment-17739305 ] Vladimir Sitnikov commented on XALANJ-2671: --- It does encourage bad practices though

[jira] [Commented] (XALANJ-2672) Suggestion: avoid adding @author tag to javadoc, or document its use

[ https://issues.apache.org/jira/browse/XALANJ-2672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17739297#comment-17739297 ] Gary D. Gregory commented on XALANJ-2672: - In general @author tags are discouraged Apache wide

[jira] [Commented] (XALANJ-2672) Suggestion: avoid adding @author tag to javadoc, or document its use

[ https://issues.apache.org/jira/browse/XALANJ-2672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17739301#comment-17739301 ] Mukul Gandhi commented on XALANJ-2672: -- @Gary, if there's an ASF wide mandatory requirement

[jira] [Commented] (XALANJ-2672) Suggestion: avoid adding @author tag to javadoc, or document its use

[ https://issues.apache.org/jira/browse/XALANJ-2672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17739310#comment-17739310 ] Gary D. Gregory commented on XALANJ-2672: - I'm sure it's not a requirement, but I recall seeing

[jira] [Commented] (XALANJ-2672) Suggestion: avoid adding @author tag to javadoc, or document its use

[ https://issues.apache.org/jira/browse/XALANJ-2672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17739311#comment-17739311 ] Mukul Gandhi commented on XALANJ-2672: -- @Gary, thanks for the thoughts about this topic. I shall

[jira] [Commented] (XALANJ-2671) Source code history lost in "clearing all contents" + "updating master branch, to have same contents as..." commits

[ https://issues.apache.org/jira/browse/XALANJ-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17739306#comment-17739306 ] Stanimir Stamenkov commented on XALANJ-2671: bq. It does encourage bad practices though

[jira] [Created] (XALANJ-2671) Source code history lost in "clearing all contents" + "updating master branch, to have same contents as..." commits

URL: https://issues.apache.org/jira/browse/XALANJ-2671 Project: XalanJ2 Issue Type: Bug Security Level: No security risk; visible to anyone (Ordinary problems in Xalan projects. Anybody can view the issue.) Reporter: Vladimir Sitnikov Assignee: Gary

[jira] [Created] (XALANJ-2673) Implementation of xpath 3.1's "function item" inline function expressions processing, for XalanJ's interpretive processor

apache.org/jira/browse/XALANJ-2673 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

[jira] [Resolved] (XALANJ-2673) Implementation of xpath 3.1's "function item" inline function expressions processing, for XalanJ's interpretive processor

[ https://issues.apache.org/jira/browse/XALANJ-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Gandhi resolved XALANJ-2673. -- Resolution: Fixed I'm marking this jira issue as resolved, since implementation for this jira

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737309#comment-17737309 ] Joe Kesselman commented on XALANJ-2474: --- Proposal re that last: Currently, if an exception

[jira] [Created] (XALANJ-2670) when's the last time we reviewed _all_ the testcases?

Joe Kesselman created XALANJ-2670: - Summary: when's the last time we reviewed _all_ the testcases? Key: XALANJ-2670 URL: https://issues.apache.org/jira/browse/XALANJ-2670 Project: XalanJ2

[jira] [Updated] (XALANJ-2670) when's the last time we reviewed _all_ the testcases?

[ https://issues.apache.org/jira/browse/XALANJ-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Kesselman updated XALANJ-2670: -- Description: We should confirm that there's an open issue for any test we know we're failing

[jira] [Commented] (XALANJ-2024) Axis name: preceding-sibling:: does not seem to work

[ https://issues.apache.org/jira/browse/XALANJ-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737858#comment-17737858 ] Joe Kesselman commented on XALANJ-2024: --- Attached files, with syntax errors (bad comment

[jira] [Updated] (XALANJ-2024) Axis name: preceding-sibling:: does not seem to work

[ https://issues.apache.org/jira/browse/XALANJ-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Kesselman updated XALANJ-2024: -- Attachment: jira-xalanj-2024.xsl jira-xalanj-2024.xml > Axis name: preced

[jira] [Comment Edited] (XALANJ-2024) Axis name: preceding-sibling:: does not seem to work

[ https://issues.apache.org/jira/browse/XALANJ-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737860#comment-17737860 ] Joe Kesselman edited comment on XALANJ-2024 at 6/27/23 8:05 PM: I'm

[jira] (XALANJ-2024) Axis name: preceding-sibling:: does not seem to work

[ https://issues.apache.org/jira/browse/XALANJ-2024 ] Joe Kesselman deleted comment on XALANJ-2024: --- was (Author: JIRAUSER285361): Note that the _text_ of the test says following-sibling. and the problem author themselves commented

[jira] [Comment Edited] (XALANJ-2024) Axis name: preceding-sibling:: does not seem to work

[ https://issues.apache.org/jira/browse/XALANJ-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737860#comment-17737860 ] Joe Kesselman edited comment on XALANJ-2024 at 6/27/23 7:48 PM: I'm

[jira] [Commented] (XALANJ-2024) Axis name: preceding-sibling:: does not seem to work

[ https://issues.apache.org/jira/browse/XALANJ-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737895#comment-17737895 ] Joe Kesselman commented on XALANJ-2024: --- If I rewrite the selection as {code:java} {code} I *do

[jira] [Commented] (XALANJ-2024) Axis name: preceding-sibling:: does not seem to work

[ https://issues.apache.org/jira/browse/XALANJ-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737860#comment-17737860 ] Joe Kesselman commented on XALANJ-2024: --- I'm not seeing the problem, outside of the fact

[jira] [Comment Edited] (XALANJ-2024) Axis name: preceding-sibling:: does not seem to work

[ https://issues.apache.org/jira/browse/XALANJ-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737860#comment-17737860 ] Joe Kesselman edited comment on XALANJ-2024 at 6/27/23 8:10 PM: Note

[jira] [Commented] (XALANJ-2024) Axis name: preceding-sibling:: does not seem to work

[ https://issues.apache.org/jira/browse/XALANJ-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737903#comment-17737903 ] Joe Kesselman commented on XALANJ-2024: --- (The reason the user's path "worked" wh

[jira] [Commented] (XALANJ-2537) The SAX exception occurs in Tansformer.transform() for a very large xml string as input.

[ https://issues.apache.org/jira/browse/XALANJ-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737909#comment-17737909 ] Joe Kesselman commented on XALANJ-2537: --- Handling huge documents is a problem for any XSLT

[jira] [Comment Edited] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17733372#comment-17733372 ] Joe Kesselman edited comment on XALANJ-2474 at 6/16/23 3:12 PM: ... ah

[jira] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474 ] Joe Kesselman deleted comment on XALANJ-2474: --- was (Author: JIRAUSER285361): Read the stylesheets and look more carefully at the error messages. It does complain about not being able

[jira] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474 ] Joe Kesselman deleted comment on XALANJ-2474: --- was (Author: JIRAUSER285361): The test as provided is incomplete; it depends on a result.xml not posted. Since this issue is 15 years old

[jira] [Resolved] (XALANJ-2667) Implementation of xslt 3.0's xsl:iterate instruction, for XalanJ's interpretive processor

[ https://issues.apache.org/jira/browse/XALANJ-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Gandhi resolved XALANJ-2667. -- Resolution: Fixed I'm marking this jira issue as resolved, since implementation for this jira

[jira] [Created] (XALANJ-2667) Implementation of xslt 3.0's xsl:iterate instruction, for XalanJ's interpretive processor

Mukul Gandhi created XALANJ-2667: Summary: Implementation of xslt 3.0's xsl:iterate instruction, for XalanJ's interpretive processor Key: XALANJ-2667 URL: https://issues.apache.org/jira/browse/XALANJ-2667

[jira] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474 ] Joe Kesselman deleted comment on XALANJ-2474: --- was (Author: JIRAUSER285361): OK, after downloading, renaming, and executing as {code:java}  java -cp ~/git/xalan-java/build/xalan.jar:~/git

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17736910#comment-17736910 ] Joe Kesselman commented on XALANJ-2474: --- User claims this worked in 2.6.0. Taking a quick look

[jira] [Comment Edited] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17736910#comment-17736910 ] Joe Kesselman edited comment on XALANJ-2474 at 6/25/23 7:14 PM: User

[jira] [Comment Edited] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17736910#comment-17736910 ] Joe Kesselman edited comment on XALANJ-2474 at 6/25/23 7:16 PM: User

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17736913#comment-17736913 ] Gary D. Gregory commented on XALANJ-2474: - I don’t think we need to provide this kind

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17736925#comment-17736925 ] Joe Kesselman commented on XALANJ-2474: --- And we should probably have better ever reporting for bad

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17736924#comment-17736924 ] Joe Kesselman commented on XALANJ-2474: --- Agreed, not necessary. The EXSLT evaluate operation only

[jira] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474 ] Joe Kesselman deleted comment on XALANJ-2474: --- was (Author: JIRAUSER285361): If we continue down this path, the Xalan *NodeInfo* extension functions, specifically {*}systemId(){*}, may

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735363#comment-17735363 ] Joe Kesselman commented on XALANJ-2474: --- FWIW, I rattled off a basic "render XML as

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735942#comment-17735942 ] Joe Kesselman commented on XALANJ-2474: --- Simplifying this down drastically, and using my

[jira] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474 ] Joe Kesselman deleted comment on XALANJ-2474: --- was (Author: JIRAUSER285361): Hm. Actually, we never get to the point of calling java:put, since findMatch never succeeds, so generate-ID

[jira] [Comment Edited] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735942#comment-17735942 ] Joe Kesselman edited comment on XALANJ-2474 at 6/22/23 12:55 AM

[jira] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474 ] Joe Kesselman deleted comment on XALANJ-2474: --- was (Author: JIRAUSER285361): FWIW, I rattled off a basic "render XML as text by recreating syntax" stylesheet so I can du

[jira] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474 ] Joe Kesselman deleted comment on XALANJ-2474: --- was (Author: JIRAUSER285361): Check their usage of generate-ID(). True, XPath says {code:java} generate-id(document("foo.xml"))=g

[jira] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474 ] Joe Kesselman deleted comment on XALANJ-2474: --- was (Author: JIRAUSER285361): Since in this case the document() call is being used to retrieve the same file as the input document, I

[jira] [Comment Edited] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735942#comment-17735942 ] Joe Kesselman edited comment on XALANJ-2474 at 6/22/23 4:58 AM

[jira] [Comment Edited] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735942#comment-17735942 ] Joe Kesselman edited comment on XALANJ-2474 at 6/22/23 5:00 AM

[jira] [Comment Edited] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17734357#comment-17734357 ] Joe Kesselman edited comment on XALANJ-2474 at 6/19/23 8:17 PM: Since

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17734469#comment-17734469 ] Joe Kesselman commented on XALANJ-2474: --- They are using generate-id(). XSLT 1.0 promises

[jira] [Commented] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17733695#comment-17733695 ] Joe Kesselman commented on XALANJ-2474: --- OK, after downloading, renaming, and executing

[jira] [Comment Edited] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17733695#comment-17733695 ] Joe Kesselman edited comment on XALANJ-2474 at 6/17/23 6:18 AM: OK

[jira] (XALANJ-2474) document() function returns different values with xalan version 2.7.1. and 2.6.0.

[ https://issues.apache.org/jira/browse/XALANJ-2474 ] Joe Kesselman deleted comment on XALANJ-2474: --- was (Author: JIRAUSER285361): They are using generate-id(). XSLT 1.0 promises that {code:java} generate-id(document("foo.xml"))=g

<    3   4   5   6   7   8   9   10   11   12   >