You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
store both files in /db/apps/test NOTE: you cannot use eXide to store the HTML file because the CDATA node will be swallowed.
rest or XML-RPC (I used xst) will work though (as does when uploading it within a XAR).
(see [BUG] HTML is modified when saved eXide#593)
Describe the bug
When traversing node-trees with CDATA the exist.log is littered with
Even though the node type
4
is known (it's a CDATA node).UPDATE
Turns out that this issue also causes an NPE when attempting to get the name of the CDATA section:
Expected behavior
The log not to be littered with false errors.
In memory CDATA section returns an empty string, that should happen for stored ones as well.
To Reproduce
With a simple main module that traverses a node-tree using
typeswitch
(traverse.xq).And an HTML file with a CDATA node (has-cdata.html).
/db/apps/test
NOTE: you cannot use eXide to store the HTML file because the CDATA node will be swallowed.
rest or XML-RPC (I used xst) will work though (as does when uploading it within a XAR).
(see [BUG] HTML is modified when saved eXide#593)
curl http://localhost:8080/exist/apps/test/traverse.xq
exist.log
it should now contain three consecutive error message withUnknown node type: 4
Context (please always complete the following information)
Build: eXist-6.2.0
Java: 1.8.0_362 (Azul Systems, Inc.)
OS: Mac OS X 12.6.3 (aarch64)
Additional context
conf.xml
? noneThe text was updated successfully, but these errors were encountered: