I believe this is actually related to: https://issues.apache.org/jira/browse/CXF-1536
Basically, we keep parsing up until we get all the data we need, then pretty much ignore the rest. Dan On Wednesday 13 August 2008 1:09:53 am jian wu wrote: > Hi, > > I'm migrating WS from XFire 1.2.6 to CXF 2.1.1 using JAX-WS Front-end with > Aegis data binding. > > For XFire, we had a negative test case with the following invalid SOAP > Message returning "soap:Server" Fault, which is fine as long as it is > fault: > > Request:==================================================== > <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:web="http://webservices.com";> > <soapenv:Header/> > <soapenv:Body> > <web:getCustomerByCustomerId> > <web:in0>624972813</web:in0> > <!-- WRONG, start a new elment instead of end element --> > <web:getCustomerByCustomerId> > </soapenv:Body> > </soapenv:Envelope> > > Response: ================================================ > <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > <soap:Body> > <soap:Fault> > <faultcode>soap:Server</faultcode> > <faultstring>Index: 1, Size: 1</faultstring> > </soap:Fault> > </soap:Body> > </soap:Envelope> > > But this invalid request was passing through without problem with CXF. > Is there a way to turn on some simple validation with Aegis Binding? > Any build-in Interceptor we can leverage? > > Or I have to switch to JAXB Binding with Schema Validation Enabled option, > which obviously has impact on performance? > > Any tips or suggestions would be really appreciated! > > Thanks a lot! > > Jian -- Daniel Kulp [EMAIL PROTECTED] http://www.dankulp.com/blog
