Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.6.2
-
None
-
None
Description
When processing nested xincluded content which has some context other 0, namepace lookup is incorrect which results in fatal errors during a parse like:
The prefix "xi" for element "xi:include" is not bound.
I'm attaching a patch for a new test case of xinclude.Test which demonstrates this problem and another patch which fixes it.