#189 fix misuse of StructuralBadDocumentError

[Peter A. Bigot]

While #188 may not be in scope for PyXB, the exception it produces should be fixed so that it reveals the invalid content.

[Peter A. Bigot]

• status changed from new to closed

• resolution set to fixed

  commit 8f235ba58264f3cb61d8a695e86aab6e099a59be
  Author: Peter A. Bigot pab@pabigot.com
  Date: Mon Apr 15 10:52:39 2013 -0500

  trac/189: fix misuse of StructuralBadDocumentError
  
  One raise site to StructuralBadDocument was replaced by raise
  NonPluralAppendError, as it should be a ValidationError not a
  BadDocumentError.
  
  The problematic call site is only entered when validation is disabled, so it
  is appropriate to raise an exception that is not a ValidationError.
  StructuralBadDocument has been modified to provide access to the container
  and the value that could not be identified without validation.
  
  The reference in the originating trac/188 to inability to invoke details()
  on the exception is irrelevant as only ValidationErrors support details().