Thanks to Dan, we got attachments working and the initial result, at least,
shows no OutOfMemory exceptions!
The solution was a little different than he described in the code excerpt,
since it was the WSS4JOutInterceptor (not the "In" interceptor) and we had
the client configuration in Java, but it was enough to point us in the right
direction. Here's the relevant change that can be matched up with our code
already posted:
WSS4JOutInterceptor wssOut = new WSS4JOutInterceptor(outProps);
wssOut.setAllowMTOM(true);
cxfEndpoint.getOutInterceptors().add(wssOut);
Thanks again. Your response saved us a lot of time.
Regards,
Steve
dkulp wrote:
>
>
> By default, the WSS4JOutInterceptor turns off MTOM since the attachments
> would
> not be signed/encrypted. Basically, it takes the "secure" route.
>
> You can tell it to not do that by:
>
> <bean class="org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor">
>
> <constructor-arg>
> ....
> </contructor-arg>
> <property name="allowMTOM" value="true"/>
> ....
>
> Dan
>
> --
> Daniel Kulp
> [email protected]
> http://dankulp.com/blog
>
>
--
View this message in context:
http://old.nabble.com/Out-of-memory-when-sending-files-%28MTOM%2C-inlining%2C-JDK-1.6%29-tp28394078p28412640.html
Sent from the cxf-user mailing list archive at Nabble.com.
