> For the writing side, yea. Basically, when the validation fails, we check > the event to see if the failure was during the the validating of the lat MTOM > element, and if so, tell jaxb to ignore it and continue. > > On the incoming side, I don't think we had to do anything. JAXB handles the > MTOM stuff prior to making the calls to the validator to actually validate it. > Thus, by the time the validator sees it, the Include is "gone". >
Ok, I think I see what's happening. JAXB code is dealing with the "cid" of MTOM attachments and altering the incoming XML before it gets handed off to the validator (jaxb/attachment/JAXBAttachmentUnmarshaller.java/AttachmentUnmarshaller). Hence, by the time the Xml gets validated against the XSD, the whole mtom/base64 issue has already been solved in the Xml and it's valid against the XSD.
