- Each SchemaInfo should have its own NamespaceScope (pre-populated with the...
- Each SchemaInfo should have its own NamespaceScope (pre-populated with the content of the including grammar) instead of pointing to a stack of the NamespaceScope of the topmost grammar (otherwise, if A includes B and then C, C sees the namespace prefixes declared by B) - SchemaGrammar should not be used to store the transient NamespaceScope objects - The stack of NamespaceScope is updated by each DOMElement that has attributes declaring new namespace prefixes (XERCESC-1592) git-svn-id: https://svn.apache.org/repos/asf/xerces/c/trunk@526239 13f79535-47bb-0310-9956-ffa450edef68
Showing
- src/xercesc/dom/impl/DOMXPathExpressionImpl.cpp 1 addition, 1 deletionsrc/xercesc/dom/impl/DOMXPathExpressionImpl.cpp
- src/xercesc/validators/schema/NamespaceScope.cpp 48 additions, 4 deletionssrc/xercesc/validators/schema/NamespaceScope.cpp
- src/xercesc/validators/schema/NamespaceScope.hpp 3 additions, 14 deletionssrc/xercesc/validators/schema/NamespaceScope.hpp
- src/xercesc/validators/schema/SchemaGrammar.cpp 1 addition, 5 deletionssrc/xercesc/validators/schema/SchemaGrammar.cpp
- src/xercesc/validators/schema/SchemaGrammar.hpp 0 additions, 16 deletionssrc/xercesc/validators/schema/SchemaGrammar.hpp
- src/xercesc/validators/schema/SchemaInfo.cpp 6 additions, 3 deletionssrc/xercesc/validators/schema/SchemaInfo.cpp
- src/xercesc/validators/schema/SchemaInfo.hpp 6 additions, 6 deletionssrc/xercesc/validators/schema/SchemaInfo.hpp
- src/xercesc/validators/schema/TraverseSchema.cpp 131 additions, 71 deletionssrc/xercesc/validators/schema/TraverseSchema.cpp
- src/xercesc/validators/schema/TraverseSchema.hpp 3 additions, 9 deletionssrc/xercesc/validators/schema/TraverseSchema.hpp
Loading
Please register or sign in to comment