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=9761>. 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=9761 Schema Validation not working with multiple namespaces [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2002-09-06 18:43 ------- Hi. If you change all the elementFormDefault="unqualified" to "qualified" in these three schemas, there's a very good chance your instance will validate (haven't checked). There's no question though that the reason it doesn't validate as-is is that the <person> element is bound to the http://company.org namespace; and yet, since it's a local declaration in a complexType in company.xsd, it is definitely in the null namespace. To make things work as- is, you'll need to bind http://company.org to an explicit prefix and use that on the <Company> element, leaving the rest unprefixed. Note that Name etc. are also local elements, so those prefixes need to be removed. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
