DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25897>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25897 SchemaGrammar::getElemDecl(elemid) throws Exception if ElemDecl not found instead of doing a GroupElemDecl lookup ------- Additional Comments From [EMAIL PROTECTED] 2004-01-06 16:27 ------- It strikes me that this code is a good deal more broken than stated here. For instance, since fGroupElemDeclPool and fElemDeclPool are not related, it's quite possible to have different element decls with the same ID value in each pool. When you call this method, you'll always get the fElemDeclPool element decl. In fact, the proposed patch will only have any effect when fGroupElemDeclPool happens to have more elements than fElemDeclPool, as far as I can make out; a fix perhaps, but it seems to me that it is dangerous to rely on this code at all. Are you using this in your application directly, or are you noticing some parser behaviour more generally that seems broken? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
