Hi, Any chance to see stack trace from the server side? If you observe wire traffic between client and service, how response looks like? Has it empty body?
Regards, Andrei. > -----Original Message----- > From: bimjoeipa [mailto:[email protected]] > Sent: Freitag, 6. Juni 2014 09:15 > To: [email protected] > Subject: Empty response when SoapFault is thrown with WS-Policy > > Hi, > > We're using JBoss EAP 6.2.2 which uses ~CXF 2.7.7, and we have a JAX-WS > webservice that throws a SoapFault. When that happens we get a Internal > Server Error 500, but with an empty response, ie the SoapFault doesn't come > back. However when we remove the @Policy annotations (or the policy > references from the WSDL), the SoapFault body comes back fine. > > I tested this against: > org.apache.cxf.systest.wssec.examples.common.DoubleItPortTypeImpl and > added a throw new RuntimeException, and the some fault came back properly, > so it doesn't look like the problem happens in every case. > > Does anyone have any ideas why having WS-Policy on a web service could > cause the Soap Fault's to be suppressed? > > We tried ramping up the logging to FINE in JBoss, but it didn't reveal > anything > obvious. > > Thanks, > > Joel > > > > -- > View this message in context: http://cxf.547215.n5.nabble.com/Empty- > response-when-SoapFault-is-thrown-with-WS-Policy-tp5744804.html > Sent from the cxf-user mailing list archive at Nabble.com.
