[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):
Proposal re that last:
Currently, if an exception such as unknown-function is thrown during
dyn:evaluate(), it silently returns an empty nodeset. Uninformative at best.
Can anyone see a good reason not to change that to throw an Exception? The
EXSLT functions are specified as possibly throwing SAXException, so my current
sketch reports it as
{code:java}
(Location of error unknown)org.xml.sax.SAXNotSupportedException: dyn:evaluate()
Could not find function: document{code}
My code does use the localized form of the "Could not find function:" text, for
the obvious I18n reasons... which is why "Could" is capitalized above; I didn't
want to muck with that text. (And why I don't say "in" evaluate)
It might be possible to get the location filled in, but I think that would
require more complicated changes. This is a one-liner.
(Alternative might be to make this a nonfatal warning, but I think this one
merits demanding that the user fix the stylesheet to be compatible with Xalan.)
> document() function returns different values with xalan version 2.7.1. and
> 2.6.0.
> -
>
> Key: XALANJ-2474
> URL: https://issues.apache.org/jira/browse/XALANJ-2474
> Project: XalanJ2
> Issue Type: Bug
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
>Affects Versions: 2.7.1
> Environment: Windows, using command line transform of xalan.
>Reporter: pavankumar
>Priority: Blocker
> Attachments: identitext.xsl, input.xml, jira-xalanj-2474.xml,
> jira-xalanj-2474.xslt, transform.xslt
>
>
> xslt document() function returns duplicate and improper values with 2.7.1.
> where as the same code works with 2.6.0.
> Info : document and evaluate functions are used in xslt and there were other
> slightly inconsistent behaviour also for 2 versions in terms of syntax and
> all. and xlink:href is getting nil values in 2.7.1
> document result contained by path variable line 93 - transform.xsl is the one
> causing problem. and and when printed, it outputs different values with
> different versions.
> Executed using xalan CLI
> C:\>java org.apache.xalan.xslt.Process -IN "C:\input.xml" -XSL
> "C:\transform.xslt" -OUT new.html -PARAM global.result input.xml
> attaching the files.transform.xslt and input.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
[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 surprisingly, it has the same behavior; it just
doesn't like {*}document(){*},
I wonder if *evaluate()* is getting only the *XPath* functions and not those in
scope for XSLT (never mind for XSLT extensions).
> document() function returns different values with xalan version 2.7.1. and
> 2.6.0.
> -
>
> Key: XALANJ-2474
> URL: https://issues.apache.org/jira/browse/XALANJ-2474
> Project: XalanJ2
> Issue Type: Bug
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
>Affects Versions: 2.7.1
> Environment: Windows, using command line transform of xalan.
>Reporter: pavankumar
>Priority: Blocker
> Attachments: identitext.xsl, input.xml, jira-xalanj-2474.xml,
> jira-xalanj-2474.xslt, transform.xslt
>
>
> xslt document() function returns duplicate and improper values with 2.7.1.
> where as the same code works with 2.6.0.
> Info : document and evaluate functions are used in xslt and there were other
> slightly inconsistent behaviour also for 2 versions in terms of syntax and
> all. and xlink:href is getting nil values in 2.7.1
> document result contained by path variable line 93 - transform.xsl is the one
> causing problem. and and when printed, it outputs different values with
> different versions.
> Executed using xalan CLI
> C:\>java org.apache.xalan.xslt.Process -IN "C:\input.xml" -XSL
> "C:\transform.xslt" -OUT new.html -PARAM global.result input.xml
> attaching the files.transform.xslt and input.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
[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/xalan-java/build/serializer.jar
org.apache.xalan.xslt.Process -IN jira-xalanj-2474.xml -XSL
jira-xalanj-2474.xslt -OUT new.html -PARAM global.result
jira-xalanj-2474.xml{code}
I am indeed seeing error-stream output saying, eg,
{code:java}
file:///home/keshlam/git/xalan-test/tests/jira/jira-xalanj-2474.xslt; Line
#118; Column #35; yep.Two sets are not equivalent.
{code}
It appears the evaluate($path) call is not returning a $targetNode which
matches the conditions being placed upon it. Hm.
> document() function returns different values with xalan version 2.7.1. and
> 2.6.0.
> -
>
> Key: XALANJ-2474
> URL: https://issues.apache.org/jira/browse/XALANJ-2474
> Project: XalanJ2
> Issue Type: Bug
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
>Affects Versions: 2.7.1
> Environment: Windows, using command line transform of xalan.
>Reporter: pavankumar
>Priority: Blocker
> Attachments: identitext.xsl, input.xml, jira-xalanj-2474.xml,
> jira-xalanj-2474.xslt, transform.xslt
>
>
> xslt document() function returns duplicate and improper values with 2.7.1.
> where as the same code works with 2.6.0.
> Info : document and evaluate functions are used in xslt and there were other
> slightly inconsistent behaviour also for 2 versions in terms of syntax and
> all. and xlink:href is getting nil values in 2.7.1
> document result contained by path variable line 93 - transform.xsl is the one
> causing problem. and and when printed, it outputs different values with
> different versions.
> Executed using xalan CLI
> C:\>java org.apache.xalan.xslt.Process -IN "C:\input.xml" -XSL
> "C:\transform.xslt" -OUT new.html -PARAM global.result input.xml
> attaching the files.transform.xslt and input.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
[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 decided to test replacing
{code:java}
document($global.result)/{code}
with
{code:java}
/{code}
The results are indeed different. Start of a diff between the two outputs, with
< being with the *document()* call and > being with {*}/{*}:
{code:java}
1,2c1,2
< file:///home/keshlam/git/xalan-test/tests/jira/jira-xalanj-2474.xslt; Line
#101; Column #31;
<
document('jira-xalanj-2474.xml')/*/NetworkElement[Name='FTMYFLXABB0'
---
> file:///home/keshlam/git/xalan-test/tests/jira/jira-xalanj-2474.xslt.simplified;
> Line #101; Column #31;
> /*/NetworkElement[Name='FTMYFLXABB0'
30,32c30,31
< file:///home/keshlam/git/xalan-test/tests/jira/jira-xalanj-2474.xslt; Line
#117; Column #35; yep.Two sets are not equivalent.
< file:///home/keshlam/git/xalan-test/tests/jira/jira-xalanj-2474.xslt; Line
#101; Column #31;
<
document('jira-xalanj-2474.xml')/*/NetworkElement[Name='FTMYFLXA02W'
---
> file:///home/keshlam/git/xalan-test/tests/jira/jira-xalanj-2474.xslt.simplified;
> Line #101; Column #31;
> /*/NetworkElement[Name='FTMYFLXA02W'
60,152c59,60
< file:///home/keshlam/git/xalan-test/tests/jira/jira-xalanj-2474.xslt; Line
#117; Column #35; yep.Two sets are not equivalent.
< file:///home/keshlam/git/xalan-test/tests/jira/jira-xalanj-2474.xslt; Line
#101; Column #31;
<
document('jira-xalanj-2474.xml')/*/NetworkElement[Name='FTMYFLXABB0'
< and Description='Ascend CBX 500'
< and Id='100010'
< and CreationTime=''
< and LastUpdatedTime=''
< and Enabled='EnableType.Enabled'
< and ManagementAddress=''
< and LastDiscovered='2002-05-11 21:21:56.0'
< and FirstDiscoveryFailure=''
< and LastDiscoveryFailure=''
< and NumDiscoveryFailures='0'
< and
NemClass='com.comanage.truesource.nem.naviscore.NavisCoreNem'
< and ContactAddress='Ipv4Address:172.20.254.1'
< and Vendor='Lucent'
< and Model='CBX 500'
< and HardwareVersion='03'
< and SoftwareVersion='04.02.00.00'
< and SerialNumber=''
< and Supplier=''
< and PartNumber=''
< and Clei=''
< and Label=''
< and Credibility='CredibilityLevel.Medium'
< and SlotCount='4'
< and AvailableSlotCount='-1'
<
< and
HostAgent[@xlink:href='nil'] and HostSystem[@xlink:href='nil'] and
Host[@xlink:href='nil']]
<
< file:///home/keshlam/git/xalan-test/tests/jira/jira-xalanj-2474.xslt; Line
#117; Column #35; yep.Two sets are not equivalent.{code}
The question is, is the difference because the document() call is actually
delivering different content, or because the stylesheet is unintentionally
relying upon identity (eg via id()) rather than content equality? The latter
could explain why behavior changed between versions, if the way input documents
are being cached changed.
> document() function returns different values with xalan version 2.7.1. and
> 2.6.0.
> -
>
> Key: XALANJ-2474
> URL: https://issues.apache.org/jira/browse/XALANJ-2474
> Project: XalanJ2
> Issue Type: Bug
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
>Affects Versions: 2.7.1
> Environment: Windows, using command line transform of xalan.
>Reporter: pavankumar
>Priority: Blocker
> Attachments: input.xml, transform.xslt
>
>
> xslt document() function returns duplicate and improper values with 2.7.1.
> where as the same code works with 2.6.0.
> Info : document and evaluate functions are used in xslt and there were other
> slightly inconsistent behaviour also for 2 versions in terms of syntax and
> all. and xlink:href is getting nil values in 2.7.1
> document result contained by path variable line 93 - transform.xsl is the one
> causing problem. and and when printed, it outputs different values with
> different versions.
> Executed using xalan CLI
> C:\>java org.apache.xalan.xslt.Process -IN "C:\input.xml" -XSL
> "C:\transform.xslt" -OUT new.html -PARAM global.result input.xml
> attaching the files.transform.xslt and input.xml
--
This message was sent by Atlassian 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):
Check their usage of generate-ID(). True, XPath says
{code:java}
generate-id(document("foo.xml"))=generate-id(document("foo.xml")){code}
But that is only promised if the two URIs are IDENTICAL STRINGS. After much
argument, the W3C concluded that there is no general way to test that two
relative URIs will evaluate to the same absolute URI, and thus equality
comparison of URIs operates strictly on a string-to-string basis. If the main
document's URI is being absolutized and document()'s isn't, or vice versa, then
different IDs may be generated. (Or may not.) This function is reliable only
for nodes known to be within the same document tree.
As a test, I annotated the *findmatch* template, where one of the
*generate-id()* calls occurs, with
{code:java}
generate-ID(/)=
generate-ID(document($global.result))=
{code}
Sure enough, the output consistently reports two different IDs for the
stylesheet input's document node and that returned by the multiple *document()*
calls, respectively *N1* and {*}N2{*}, as permitted (and arguably
desirable) if their URIs are not completely identical. (In other words, they're
two separate DTM tables, though the second is reused for each *document()* call
with the same URI string.)
I'm not sure yet whether that's the cause of this problem – whether their
stylesheet relied upon the two documents being the same tree – but it's exactly
the kind of edge case that we were chasing down and fixing around that time,
and it's quite possible that previously we were not correctly distinguishing
two different URI strings that had "apparently equivalent" meaning.
If so, then the question may be one of base behaviors – whether the URI as
entered, or the URI as resolved, shall be used by Xalan as the document's
identity. The fact that both were entered as the same relative URI is simply
not enough to imply that.
I know we made some explicit decisions on this issue. Any surviving record of
that discussion would be in the deep archives of xalan-dev.
*CAVEAT: I have not actually confirmed that this is the place where their
stylesheet is failing.* I haven't done a deep analysis of how they are caching
and checking node IDs and whether they ever attempt to use an ID from one
document to reference the other. But it's one likely place to look for a
behavior change between Xalan releases that could affect this stylesheet.
> document() function returns different values with xalan version 2.7.1. and
> 2.6.0.
> -
>
> Key: XALANJ-2474
> URL: https://issues.apache.org/jira/browse/XALANJ-2474
> Project: XalanJ2
> Issue Type: Bug
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
>Affects Versions: 2.7.1
> Environment: Windows, using command line transform of xalan.
>Reporter: pavankumar
>Priority: Blocker
> Attachments: input.xml, transform.xslt
>
>
> xslt document() function returns duplicate and improper values with 2.7.1.
> where as the same code works with 2.6.0.
> Info : document and evaluate functions are used in xslt and there were other
> slightly inconsistent behaviour also for 2 versions in terms of syntax and
> all. and xlink:href is getting nil values in 2.7.1
> document result contained by path variable line 93 - transform.xsl is the one
> causing problem. and and when printed, it outputs different values with
> different versions.
> Executed using xalan CLI
> C:\>java org.apache.xalan.xslt.Process -IN "C:\input.xml" -XSL
> "C:\transform.xslt" -OUT new.html -PARAM global.result input.xml
> attaching the files.transform.xslt and input.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
[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 dump content in an *xsl:message* (identitext.xsl; not fully
polished but if folks think it would be useful for debugging I can add it to
our toolkit) and patched the test to run this over both the input document and
the document(). Modulo errors in that, the two trees appear to have identical
content, as expected.
Next question is, are they loaded with different URIs? I added a printout of
*nodeinfo:systemId()* to my dump, and it shows the same URI for both */* and
{*}document(){*}.
So this +_*may*_+ in fact be a genuine error, assuming that *generate-id()* is
the point of change.
Needs a stripped down test to focus on the precise failure point.
> document() function returns different values with xalan version 2.7.1. and
> 2.6.0.
> -
>
> Key: XALANJ-2474
> URL: https://issues.apache.org/jira/browse/XALANJ-2474
> Project: XalanJ2
> Issue Type: Bug
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
>Affects Versions: 2.7.1
> Environment: Windows, using command line transform of xalan.
>Reporter: pavankumar
>Priority: Blocker
> Attachments: input.xml, transform.xslt
>
>
> xslt document() function returns duplicate and improper values with 2.7.1.
> where as the same code works with 2.6.0.
> Info : document and evaluate functions are used in xslt and there were other
> slightly inconsistent behaviour also for 2 versions in terms of syntax and
> all. and xlink:href is getting nil values in 2.7.1
> document result contained by path variable line 93 - transform.xsl is the one
> causing problem. and and when printed, it outputs different values with
> different versions.
> Executed using xalan CLI
> C:\>java org.apache.xalan.xslt.Process -IN "C:\input.xml" -XSL
> "C:\transform.xslt" -OUT new.html -PARAM global.result input.xml
> attaching the files.transform.xslt and input.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
[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 may be a red herriing. > document() function returns different values with xalan version 2.7.1. and > 2.6.0. > - > > Key: XALANJ-2474 > URL: https://issues.apache.org/jira/browse/XALANJ-2474 > Project: XalanJ2 > Issue Type: Bug > Security Level: No security risk; visible to anyone(Ordinary problems in > Xalan projects. Anybody can view the issue.) >Affects Versions: 2.7.1 > Environment: Windows, using command line transform of xalan. >Reporter: pavankumar >Priority: Blocker > Attachments: input.xml, transform.xslt > > > xslt document() function returns duplicate and improper values with 2.7.1. > where as the same code works with 2.6.0. > Info : document and evaluate functions are used in xslt and there were other > slightly inconsistent behaviour also for 2 versions in terms of syntax and > all. and xlink:href is getting nil values in 2.7.1 > document result contained by path variable line 93 - transform.xsl is the one > causing problem. and and when printed, it outputs different values with > different versions. > Executed using xalan CLI > C:\>java org.apache.xalan.xslt.Process -IN "C:\input.xml" -XSL > "C:\transform.xslt" -OUT new.html -PARAM global.result input.xml > attaching the files.transform.xslt and input.xml -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[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 be able to recover the URIs actually used to
fetch these trees. Note that in general there is no guarantee that the main
document has such a URI; if it was read from a character stream, the *systemId*
may be unknown/empty.
> document() function returns different values with xalan version 2.7.1. and
> 2.6.0.
> -
>
> Key: XALANJ-2474
> URL: https://issues.apache.org/jira/browse/XALANJ-2474
> Project: XalanJ2
> Issue Type: Bug
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
>Affects Versions: 2.7.1
> Environment: Windows, using command line transform of xalan.
>Reporter: pavankumar
>Priority: Blocker
> Attachments: input.xml, transform.xslt
>
>
> xslt document() function returns duplicate and improper values with 2.7.1.
> where as the same code works with 2.6.0.
> Info : document and evaluate functions are used in xslt and there were other
> slightly inconsistent behaviour also for 2 versions in terms of syntax and
> all. and xlink:href is getting nil values in 2.7.1
> document result contained by path variable line 93 - transform.xsl is the one
> causing problem. and and when printed, it outputs different values with
> different versions.
> Executed using xalan CLI
> C:\>java org.apache.xalan.xslt.Process -IN "C:\input.xml" -XSL
> "C:\transform.xslt" -OUT new.html -PARAM global.result input.xml
> attaching the files.transform.xslt and input.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
[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"))=generate-id(document("foo.xml")){code}
But that is true only if exactly the same URI string was used to fetch both.
After an extended debate during the introduction of XML namespaces, we
concluded that we had no reasonable way to compare relative URIs, and until
that can be resolved (if ever), URIs must be tested for equality as literal
strings.
If the command line is expanding the input URI into a string differently from
the way document() does, the short-form URI in the parameter will *NOT* match,
and equivalent nodes will be given different IDs. That may be the change which
precipitated this user's problem; I'm currently betting that it is.
The user really should not rely on generate-id() matching across separately
fetched documents unless they are providing absolute URIs for both.
> document() function returns different values with xalan version 2.7.1. and
> 2.6.0.
> -
>
> Key: XALANJ-2474
> URL: https://issues.apache.org/jira/browse/XALANJ-2474
> Project: XalanJ2
> Issue Type: Bug
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
>Affects Versions: 2.7.1
> Environment: Windows, using command line transform of xalan.
>Reporter: pavankumar
>Priority: Blocker
> Attachments: input.xml, transform.xslt
>
>
> xslt document() function returns duplicate and improper values with 2.7.1.
> where as the same code works with 2.6.0.
> Info : document and evaluate functions are used in xslt and there were other
> slightly inconsistent behaviour also for 2 versions in terms of syntax and
> all. and xlink:href is getting nil values in 2.7.1
> document result contained by path variable line 93 - transform.xsl is the one
> causing problem. and and when printed, it outputs different values with
> different versions.
> Executed using xalan CLI
> C:\>java org.apache.xalan.xslt.Process -IN "C:\input.xml" -XSL
> "C:\transform.xslt" -OUT new.html -PARAM global.result input.xml
> attaching the files.transform.xslt and input.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
[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 to load that file, and the error messages are consistent with the document() call having returned an empty nodeset. Running, and demonstrating the issue being complained about, are different things. -- /_ Joe Kesselman (he/him/his) -/ _) My Alexa skill for New Music/New Sounds fans: / https://www.amazon.com/dp/B09WJ3H657/ () Plaintext Ribbon Campaign /\ Stamp out HTML mail! > document() function returns different values with xalan version 2.7.1. and > 2.6.0. > - > > Key: XALANJ-2474 > URL: https://issues.apache.org/jira/browse/XALANJ-2474 > Project: XalanJ2 > Issue Type: Bug > Security Level: No security risk; visible to anyone(Ordinary problems in > Xalan projects. Anybody can view the issue.) >Affects Versions: 2.7.1 > Environment: Windows, using command line transform of xalan. >Reporter: pavankumar >Priority: Blocker > Attachments: input.xml, transform.xslt > > > xslt document() function returns duplicate and improper values with 2.7.1. > where as the same code works with 2.6.0. > Info : document and evaluate functions are used in xslt and there were other > slightly inconsistent behaviour also for 2 versions in terms of syntax and > all. and xlink:href is getting nil values in 2.7.1 > document result contained by path variable line 93 - transform.xsl is the one > causing problem. and and when printed, it outputs different values with > different versions. > Executed using xalan CLI > C:\>java org.apache.xalan.xslt.Process -IN "C:\input.xml" -XSL > "C:\transform.xslt" -OUT new.html -PARAM global.result input.xml > attaching the files.transform.xslt and input.xml -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[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 and can't be run without that file (or without someone reverse-engineering the testcase to determine what that file was supposed to contain), I'm more than half inclined to close this as "could not reproduce, quite probably obsolete". > document() function returns different values with xalan version 2.7.1. and > 2.6.0. > - > > Key: XALANJ-2474 > URL: https://issues.apache.org/jira/browse/XALANJ-2474 > Project: XalanJ2 > Issue Type: Bug > Security Level: No security risk; visible to anyone(Ordinary problems in > Xalan projects. Anybody can view the issue.) >Affects Versions: 2.7.1 > Environment: Windows, using command line transform of xalan. >Reporter: pavankumar >Priority: Blocker > Attachments: input.xml, transform.xslt > > > xslt document() function returns duplicate and improper values with 2.7.1. > where as the same code works with 2.6.0. > Info : document and evaluate functions are used in xslt and there were other > slightly inconsistent behaviour also for 2 versions in terms of syntax and > all. and xlink:href is getting nil values in 2.7.1 > document result contained by path variable line 93 - transform.xsl is the one > causing problem. and and when printed, it outputs different values with > different versions. > Executed using xalan CLI > C:\>java org.apache.xalan.xslt.Process -IN "C:\input.xml" -XSL > "C:\transform.xslt" -OUT new.html -PARAM global.result input.xml > attaching the files.transform.xslt and input.xml -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
