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=7950>. 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=7950 Empty complex type with mixed="true" allows non-whitespace characters. [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2002-04-11 10:15 ------- I think you missed the line just above the one you pointed out. <SNIP> 1 If the <restriction> alternative is chosen, then the appropriate case among the following: 1.1 If one of the following is true 1.1.1 There is no <group>, <all>, <choice> or <sequence> among the [children]; ... ,then empty; 1.2 otherwise a pair consisting of 1.2.1 the appropriate case among the following: 1.2.1.1 If the mixed [attribute] is present on <complexContent>, then mixed if its �actual value� is true, otherwise elementOnly; 1.2.1.2 If the mixed [attribute] is present on <complexType> and its �actual value� is true, then mixed; ... </SNIP> Your sample falls under 1.2.1.2, so it's content type is mixed. Hence it's not a bug. Kazumi, I'm closing this bug. If you think there's some other problem feel free to reopen it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
