Skip navigation links

Java API Reference for Oracle Infrastructure Web Services
11
Release 1 (11.1.1)

E10654-02


oracle.webservices.soap
Interface OracleSOAPMessage


public interface OracleSOAPMessage

Created by IntelliJ IDEA. User: xwen Date: Apr 10, 2007 Time: 3:11:18 PM To change this template use File | Settings | File Templates.


Field Summary
static String MTOM_DOTNET_HEADER_STYLE
          This property can be used to control the Content-Type header of a SOAPMessage which will be serialized into MTOM format.
static String MTOM_THRESHOLD
          This property can be used to control how large a binary needs to be in order to be serialized as a MTOM attachment.

 

Field Detail

MTOM_DOTNET_HEADER_STYLE

static final String MTOM_DOTNET_HEADER_STYLE
This property can be used to control the Content-Type header of a SOAPMessage which will be serialized into MTOM format. By default, a MTOM SOAPMessage could have the following Content-Type header: Content-Type: multipart/related;type="application/xop+xml"; boundary="----=_Part_0_3317565.1173468533317";start="<6290b19511d64a12abfdf530a0894802>"; start-info="application/soap+xml;action=\"http://Ravindra.WCFFileExchangeService.Service/IWCFFileExchangeService/putRawBytes\"" Setting this property to true on the SOAPMessage will caues the Content-Type to look like the Microsoft Dot Net style: Content-Type: multipart/related;type="application/xop+xml"; boundary="----=_Part_0_3317565.1173468533317";start="<6290b19511d64a12abfdf530a0894802>"; start-info="application/soap+xml"; action="http://Ravindra.WCFFileExchangeService.Service/IWCFFileExchangeService/putRawBytes" Default value is false. July 9 08 Gigi Lee: I am changing the default to true. This doesn't seem to be needed as all vendors are doing the Microsoft way. In other words, action should be outside of start-info. I have verified with Axis, JaxwsRI and of course .NET client Where Xiaoping's origional implementation based on is just the sample from the mtom spec.

Type: java.lang.Boolean

See Also:
Constant Field Values

MTOM_THRESHOLD

static final String MTOM_THRESHOLD
This property can be used to control how large a binary needs to be in order to be serialized as a MTOM attachment. Because of the overhead associated with MIME part headers, it is sometimes more efficient to serialize the binary into a Base64 text node instead of carrying it as a MTOM attachment, espeically when the binary is small in size. The value of this property should be an integer or it String equilvalent. Its unit is byte. For example, if we have a value of 1024, only binary of this size or larger will be carried as a MTOM attachment. Its default value is 0, meaning that all binaries, regardless of their sizes, will be serialized into attachments if configured for MTOM serialization.
See Also:
Constant Field Values

Skip navigation links

Copyright © 2006, 2009 Oracle. All Rights Reserved.