Xalan and LibXML doesn't support using functions #75

New Issue

augustyd · 2023-02-24T12:21:22+01:00

augustyd commented

2023-02-24 12:21:22 +01:00

When trying to use function like String(11) which should return 11, Xalan and LibXML try to treat fucntion lika a node.
Xalan: Can not convert #STRING to a NodeList!
LibXML: Type 'str' cannot be serialized.

When trying to use function like String(11) which should return 11, Xalan and LibXML try to treat fucntion lika a node. Xalan: Can not convert #STRING to a NodeList! LibXML: Type 'str' cannot be serialized.

bema added the

bug

XPath

labels 2023-02-28 10:07:36 +01:00

boguckib added this to the Release 11.1 milestone 2023-02-28 15:10:48 +01:00

bema self-assigned this 2023-03-01 10:49:24 +01:00

bema commented

2023-03-01 11:04:50 +01:00

ACKTUALLY (xD) both of these engines support functions, except ones that doesn't rely on given XML data, like:

string(.11)

XPath query such as:

/l:library/l:bookList/b:book[contains(b:title, "o")]

will work.

Of course, this is something that still needs fixing, but situation isn't as bad as title suggests.

ACKTUALLY (xD) both of these engines support functions, except ones that doesn't rely on given XML data, like: ``` string(.11) ``` XPath query such as: ``` /l:library/l:bookList/b:book[contains(b:title, "o")] ``` will work. Of course, this is something that still needs fixing, but situation isn't as bad as title suggests.

bema changed title from ~~Xalan and LibXML doesn't support using fuctions~~ to Xalan and LibXML doesn't support using functions

2023-03-01 12:53:09 +01:00

bema referenced this issue

2023-03-02 11:06:26 +01:00

Partial fix for #75 - fixes problem in libXML #92

bema referenced this issue from a commit

2023-03-02 11:08:03 +01:00

Partial fix for #75 - fixes problem in libXML (#92)

bema referenced this issue from a commit

2023-03-02 11:57:56 +01:00

Fixed #75

bema referenced a pull request that will close this issue