You still haven't told me if you are using Aegis or JAXB, but now I'm pretty confident it's JAXB.
Give me a JIRA and I'll just make it work like this all the time, no need for you to customize a perfectly reasonable idea of this form. If there's some reason not to, I'll post customization advice onto the JIRA. On Thu, Apr 2, 2009 at 4:50 PM, jp4 <[email protected]> wrote: > > A generic fault is returned... Something like this... But I would like to > throw an application defined Fault like SchemaValidationFault. > > <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> > <soap:Body> > <soap:Fault> > <faultcode>soap:Client</faultcode> > <faultstring>Unmarshalling Error: cvc-complex-type.2.4.b: The > content of element 'hear:GetHeartBeatRequest' is not complete. One of > '{" > http://www.foo.com/enterpriseservices/heartbeatservices/heartbeatservices_1_0_0 > ":Token}' > is expected.</faultstring> > </soap:Fault> > </soap:Body> > </soap:Envelope> > > > bimargulies wrote: > > > > Don't we already make a fault? Which data binding are you using. > > > > On Thu, Apr 2, 2009 at 2:21 PM, jp4 <[email protected]> > wrote: > > > >> > >> I am able to configure my web services with schema validation enabled. > >> The > >> next step is to catch any schema validation errors and throw a fault > that > >> adheres to the contract. > >> > >> Can anyone tell me how I can go about this? Essentially, I'd like to > >> wrap > >> the spring bean that performs schema validation, catch a schema > >> validation > >> exception and throw a fault. > >> > >> Any help would be greatly appreciated. > >> > >> Thanks, > >> > >> John > >> -- > >> View this message in context: > >> http://www.nabble.com/Custom-Schema-Validator-tp22854150p22854150.html > >> Sent from the cxf-user mailing list archive at Nabble.com. > >> > >> > > > > > > -- > View this message in context: > http://www.nabble.com/Custom-Schema-Validator-tp22854150p22856723.html > Sent from the cxf-user mailing list archive at Nabble.com. > >
