Hi,
Did you try with these properties on your JAX-WS provider?
<jaxws:properties>
<entry key="mtom-enabled" value="true"/>
<entry key="attachment-directory" value="/path/attach"/>
<entry key="attachment-memory-threshold" value="2000000"/>
</jaxws:properties>
Regards.
Xilai
-----Original Message-----
From: zsolt.szloboda [mailto:[email protected]]
Sent: Saturday, June 21, 2014 7:19 PM
To: [email protected]
Subject: JAX-WS Provider with attachment streaming
I would like to implement a JAX-WS Provider, that receives large MTOM
attachments. I would like to prevent the attachments from being cached in
memory; I would like to stream them to a temporary file (or the JAX-WS
implementation to stream them to a temporary file).
Theoretically I could get the MTOM attachmments with
SOAPMessage#getAttachments(), or with
WebServiceContext#getMessageContext()#get(INBOUND_MESSAGE_ATTACHMENTS), and
stream them into a temporary file.
The problem is that I've found no way to get the SOAP Part itself without the
attachments resolved (in memory). I've tried the PAYLOAD/MESSAGE annotations,
Source/SOAPMessage parameters, but no luck, the memory always gets filled with
the attachments.
Does anyone have an idea, or experience about this problem?
--
View this message in context:
http://cxf.547215.n5.nabble.com/JAX-WS-Provider-with-attachment-streaming-tp5745444.html
Sent from the cxf-user mailing list archive at Nabble.com.
