I have another question on soap fault. I could see the root cause returning from the soap fault from my Sun JAX-WS service, but I am not seeing it in the CXF implementation. Is there a way for CXF to return the root cause of the soap fault to a client? Here's the example response from my test.
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> <soap:Header/> <soap:Body> <soap:Fault> <faultcode> soap:Server </faultcode> <faultstring> java.lang.RuntimeException: Mock up exception </faultstring> <detail> <ns1:ServiceException xmlns:ns1="urn:expd.com:service:calculation"/> </detail> </soap:Fault> </soap:Body> </soap:Envelope> Thanks, Kiffin dkulp wrote: > > On Fri February 12 2010 3:06:52 pm kiffin wrote: >> Hi. I am porting a Sun JAX-WS service to CXF. Sun has a system property - >> com.sun.xml.ws.transport.http.client.HttpTransportPipe.dum - which dumps >> the request/response message on the console. Does CXF have an equivalent >> property to dump the request/response message on the console? > > OK. Didn't know about that specific property. Sun seems to have several > properties like that which CXF would respond to, but that one isn't one. > I'll add it. > > With 2.2.6, you can chose one of: > > Boolean.getBoolean("org.apache.cxf.logging.enabled"); > Boolean.getBoolean("com.sun.xml.ws.transport.local.LocalTransportPipe.dump"); > Boolean.getBoolean("com.sun.xml.ws.util.pipe.StandaloneTubeAssembler.dump"); > Boolean.getBoolean("com.sun.xml.ws.transport.http.HttpAdapter.dump"); > > It wouldn't go to the console. It would go the java.util.logging, but by > default, that would go to the console. > > -- > Daniel Kulp > [email protected] > http://www.dankulp.com/blog > > -- View this message in context: http://old.nabble.com/com.sun.xml.ws.transport.http.client.HttpTransportPipe.dump-tp27568694p27570187.html Sent from the cxf-user mailing list archive at Nabble.com.
