Validataing incoming SOAP messages with Glassfish V2
I have a problem with implementing WS using NB 6 and Glassfish v2. We can send any wrong xml message to WS endpoint (SOAP over HTTP) and it is passed to lower framework layers instead of throwing some schema validation fault. In case of other app servers we used to get schema validation as soon as wrong message arrived. It is a serious problem for us, as some of our consumers are quite inadvanced and they build WS clients using string concatenation, not WS frameworks :( and they consume a lot of troubles when they get some lower level exceptions. I guess it has something in common with FI and processing optimization, but I need your help to switch validation on as it is more important at this point than performance.