cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <dk...@apache.org>
Subject Re: Force MTOM Fault
Date Sat, 27 Feb 2010 03:13:15 GMT

You MAY be able to add the AttachmentOutInterceptor to the FaultOut chain as 
well.   I think it's normally just on the Out chain cause, as Glen said, it 
shouldn't be required for faults.

Dan



On Thu February 25 2010 12:10:38 pm digibeb wrote:
> Hi,
> 
> I use CXF to provide web service and one of my class is MTOM enabled :
> 
> 	<jaxws:endpoint id="MyService"
> 		implementor="beb.ws.provider.impl.MyService"
> 		address="/MyService">
> 		<jaxws:properties>
> 			<entry key="mtom-enabled" value="true" />
> 		</jaxws:properties>
> 	</jaxws:endpoint>
> 
> All the soap response received from this web service has the following
> content-type "application/xop+xml"
> 
> The problem is when i throw exception in my web method.
> An exception is sent and transformed as Soap Fault but the soap response
> doesn't have anymore MTOM content-type "application/xop+xml" but
> "text/xml;charset=UTF-8"
> 
> The client which consume my webservice is coded in .NET (WSE 3) and display
> an error because it expect "application/xop+xml" instead of
> "text/xml;charset=UTF-8"
> 
> There is a solution with interceptor or something like that?
> 
> Thanks in advance

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

Mime
View raw message