There is a documented restriction that Saxon ignores
any fixed or default value specified in the schema for
an element with a complex type (the specification
allows such values if the content model is mixed).
In fact, however, Saxon crashes with a
NullPointerException while processing a schema that
defines such a fixed or default value.
The bug, along with the documented restriction, will be
removed in the next release.