xop

Building large MTOM/XOP messages with JAX-WS

Hi, I have a question about using MTOM/XOP with JAX-WS. I'm writing a web service which sends large amounts of binary data. The client requests a number of files and the server returns the files in the response. I'm able to get it to build the response correctly so that it correctly implements XOP, but I run into memory-related issues...

WCF: (MTOM) is there any way to change the scheme used in xop:Content reference uris generated by WCF?

WCF uses http://tempuri/1/number for Content-ID uri references when handling streamed MTOM requests. Is there any way how to force WCF to use a different Content-ID references for the xop:Include? Bakcground of the problem: I am building a .NET client for MTOM enabled jax ws java web service that handles streamed large data uploads. ...