On Wednesday, December 07, 2011 12:37:44 PM eamiller83 wrote: > After further debugging it seems like it may be the xml validation during > marshalling that is causing issues. I changed the schema to make the field > that I was having problems with not be required. I also added a print > statement in the client to alert me to the event that the field was empty or > incorrect...it never was. So it seems like the validator is falsely > detecting that the required field is not filled in. Again this seems to be > a concurrency issue as I only see this when multiple clients are hitting > the server at once. So in theory I can solve this problem by turning off > validation, but that is not the desirable solution. Any thoughts?
No idea really. :-( According to the javadocs, the Schema objects that we pass to JAXB are thread safe and immutable. The JAXB marshaller is created per response. Thus, it SHOULD be OK. Not really sure how to approach this. Maybe grab a newer JDK (if possible) to see if there are bugs fixed in the newer validators? Maybe throwing the latest xerces jar in to see if that helps? Honestly, I'm not sure. There is a JIRA logged: https://issues.apache.org/jira/browse/CXF-3813 to split the validation settings between incoming and outgoing so you can validate incoming messages (that you don't control) and not log outgoing message (you can assume you generate proper messages so don't validate). Might be worth some time to pursue that if you are interested. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
