[
https://issues.apache.org/jira/browse/XALANJ-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471438
]
Henry Zongaro commented on XALANJ-2363:
---------------------------------------
Let me expand on my previous comment. The fn:replace function is defined in
the new W3C XQuery 1.0 and XPath 2.0 Functions and Operators Recommendation,[1]
but Xalan-J implements XSLT and XPath 1.0, and the replace function did not
exist in the first version of the XSLT and XPath.
There is an EXSLT str:replace function, and though Xalan-J implements some of
the EXSLT string functions, it doesn't implement str:replace. I was guessing
that that was really the replace function that you meant.
Another possibility is that the replace function was defined by some other W3C
Recommendation that extends the set of XPath functions. Is that the case? If
so, a component other the Xalan-J is supplying the flawed implementation.
[1] http://www.w3.org/TR/xquery-operators/#func-replace
> function replace() does not conform to specifications
> -----------------------------------------------------
>
> Key: XALANJ-2363
> URL: https://issues.apache.org/jira/browse/XALANJ-2363
> Project: XalanJ2
> Issue Type: Bug
> Components: XPath-function
> Affects Versions: 2.7
> Environment: Windows 2000; IBM RAD 6
> Reporter: Henk Spaan
> Fix For: The Latest Development Code
>
>
> The function call:
> replace('xyzxyzxyz', 'x', 'aaa')
> will return 'ayzayzayz' in version 2.7.0.
> According to the W3C specifications the result should be 'aaayzaaayzaaayz'.
> Now, it seems to be nothing more than a copy of 'translate'.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
