In my testing of Xerces 1.4 while reusing the validator, I've discovered that there are times when undeclared attributes get faulted into the name pools and get stuck there. I can parse a file once, and I'll get an undeclared attribute error and then I'll parse it again and I don't get the message. There was some code added to scanStartTag in XMLScanner.c to deal with this, but the code looks wrong to me. It sets the XMLAttDef::JustFaultIn creation reason if NOT reusing the validator. It also "resets the CreateReason to avoid redundant error", but the error isn't redundant if the validator is being reused. The code was also not placed in the parallel scanStartTagNS code, so the exact behavior depends on if the parser is doing namespaces or not. Chris --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
