I just made some more changes to this that will hopefully work a bit better.
Basically, rather than remove the attributes from the Element, I stick an error handler onto the Schema validator to ignore the errors related to the mustUnderstand and Actor/Role attributes that SOAP clients may stick on the headers. Thus, if your schema does have them, JAXB should then be able to read them and populate the values but they won't generate validation errors if they are there. Can you give that a try to see if that then works for your use case? Dan On Feb 18, 2013, at 10:12 AM, Jesus Castillo <[email protected]> wrote: > Hi Dan, > > For now, I disabled the validation of the attribute as a workaround until a > final solution is found. > > However, as this attribute is part of the schema defining the custom header, > I expect to retrieve it > too. In a perfect world, you shouldn't remove this attribute at all as this > is or should be part of the > custom schema if needed. So, if you are to remove it, I think this solution > should be the exception > and not the rule. > > Rgds, > > Jesus. > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/CXF-4819-breaking-validation-of-mustUnderstand-attribute-tp5723289p5723304.html > Sent from the cxf-user mailing list archive at Nabble.com. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
