Actually that's incorrect. I had this same discussion with Juergen for Spring Framework bug SPR-10767. First, the default value in the XSD does not apply if <exclude-unlisted-classes> is omitted. It only applies if <exclude-unlisted-classes> is present but empty.

However, the 1.0 XSD was incorrect. The spec says that the default is true (which is the only thing that can possibly make sense if the file contains <exclude-unlisted-classes /> ... that would NEVER mean "don't exclude unlisted classes"). The XSD does not comply with the spec. Therefore, this change is correct as-is.