I have run further testing and it looks like the SchemaValidationFeature validates the SOAP body fine and also the SOAP header to some degree. The problem is that within the SOAP header, if a field is mandatory and is left blank, it is not flagged by the SchemaValidationFeature. It seems to pick out mandatory fields being left blank just fine in the SOAP body though. The header is a different xsd from the body xsd. I have checked both xsds and don't see differences that would cause this problem.
Do I need something extra than minOccurs="1" maxOccurs="1" to specify that a field is mandatory?
Hello!
Validate SOAP headers to some degree?!??
That sounds interesting - if you ask me, they are either validated or not validated. I would not trust partial validation.
Yes, if you want to make a field mandatory in an XML schema, you can use minOccurs"1".
Best wishes!
A teeny tiny vulgar attempt to get you to buy our stuff
a bit of art, as a gift, that will fit in a stocking