MTOM/XOP behavior in WL 10

Question

Hi!
I'm using BEA Workshop for WebLogic v. 10.1.
I want to use MTOM/XOP for sending and receiving binary data, but it doesn't seem to work as I expect.
I can only make it work if the binary data is at the top level in the request or response message.
If I'm using binary data at a lower level it doesn't become an attachment.
I haven't been able to find any documentation that can explain if is this is according to the standard,
if it's a limitation in the WebLogic implementation or if it's related to my use of XmlBeans for binding.
To clarify, I would like to define my types in e.g the following way:
<complexType name="PDFFile">
     <sequence>
          <element name="filename" type="string"/>
          <element name="printDate" type="date"/>
          <element name="contents" type="base64Binary"
               xmime:expectedContentTypes="application/pdf"/>
     </sequence>
</complexType>
<complexType name="BudgetPrint">
     <sequence>
          <element name="customerID" type="string"/>
          <element name="printID" type="string"/>
          <element name="print" type="tns:PDFFile"/>
     </sequence>
</complexType>
The in my JWS file I can have the following:
package com.my.service;
import ...
import weblogic.jws.Policy;
@WebService
@Policy(uri="policy:Mtom.xml", attachToWsdl=true)
public class BudgetService {
     @WebMethod
     public void saveBudgetPrint(BudgetPrint print) {
     @WebMethod
     public BudgetPrint getBudgetPrint(String customerID, String printID) {
This results in the following in the generated WSDL file (the above types have been removed to shorten it):
<?xml version='1.0' encoding='UTF-8'?>
<s2:definitions name="BudgetServiceServiceDefinitions" targetNamespace="http://com/my/service" xmlns="" xmlns:s0="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:s1="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:s2="http://schemas.xmlsoap.org/wsdl/" xmlns:s3="http://com/my/service" xmlns:s4="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy">
<s0:Policy s1:Id="policy:Mtom">
<wsoma:OptimizedMimeSerialization xmlns:wsoma="http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization"/>
</s0:Policy>
<wsp:UsingPolicy s2:Required="true"/>
<s2:types>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://com/my/service" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://my.com/types"/>
<xs:element name="saveBudgetPrint">
<xs:complexType>
<xs:sequence>
<xs:element name="print" type="typ:BudgetPrint" xmlns:typ="http://my.com/types"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="saveBudgetPrintResponse">
<xs:complexType>
<xs:sequence/>
</xs:complexType>
</xs:element>
<xs:element name="getBudgetPrint">
<xs:complexType>
<xs:sequence>
<xs:element name="customerID" type="xs:string"/>
<xs:element name="printID" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="getBudgetPrintResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="BudgetPrint" type="typ:BudgetPrint" xmlns:typ="http://my.com/types"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
</s2:types>
<s2:message name="saveBudgetPrint">
<s2:part element="s3:saveBudgetPrint" name="parameters"/>
</s2:message>
<s2:message name="saveBudgetPrintResponse">
<s2:part element="s3:saveBudgetPrintResponse" name="parameters"/>
</s2:message>
<s2:message name="getBudgetPrint">
<s2:part element="s3:getBudgetPrint" name="parameters"/>
</s2:message>
<s2:message name="getBudgetPrintResponse">
<s2:part element="s3:getBudgetPrintResponse" name="parameters"/>
</s2:message>
<s2:portType name="BudgetService">
<s2:operation name="saveBudgetPrint" parameterOrder="parameters">
<s2:input message="s3:saveBudgetPrint"/>
<s2:output message="s3:saveBudgetPrintResponse"/>
</s2:operation>
<s2:operation name="getBudgetPrint" parameterOrder="parameters">
<s2:input message="s3:getBudgetPrint"/>
<s2:output message="s3:getBudgetPrintResponse"/>
</s2:operation>
</s2:portType>
<s2:binding name="BudgetServiceServiceSoapBinding" type="s3:BudgetService">
<s4:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsp:Policy>
<wsp:PolicyReference URI="#policy:Mtom"/>
</wsp:Policy>
<s2:operation name="saveBudgetPrint">
<s4:operation soapAction="" style="document"/>
<s2:input>
<s4:body parts="parameters" use="literal"/>
</s2:input>
<s2:output>
<s4:body use="literal"/>
</s2:output>
</s2:operation>
<s2:operation name="getBudgetPrint">
<s4:operation soapAction="" style="document"/>
<s2:input>
<s4:body parts="parameters" use="literal"/>
</s2:input>
<s2:output>
<s4:body parts="parameters" use="literal"/>
</s2:output>
</s2:operation>
</s2:binding>
<s2:service name="BudgetServiceService">
<s2:port binding="s3:BudgetServiceServiceSoapBinding" name="BudgetServiceSoapPort">
<s4:address location="http://localhost:7001/MyService/BudgetService"/>
</s2:port>
</s2:service>
</s2:definitions>
When I monitor the HTTP requests I can observe that the binary data isn't attachments.
If I instead define my web methods as follows:
     @WebMethod
     public void saveBudgetPrintContents(String customerID, String printID, String filename, Calendar printDate, byte[] contents) {
     @WebMethod
     public byte[] getBudgetPrintContents(String customerID, String printID) {
it works as expected and the binary data is attachments.
The WSDL file is now:
<?xml version='1.0' encoding='UTF-8'?>
<s2:definitions name="BudgetServiceServiceDefinitions" targetNamespace="http://com/my/service" xmlns="" xmlns:s0="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:s1="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:s2="http://schemas.xmlsoap.org/wsdl/" xmlns:s3="http://com/my/service" xmlns:s4="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy">
<s0:Policy s1:Id="policy:Mtom">
<wsoma:OptimizedMimeSerialization xmlns:wsoma="http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization"/>
</s0:Policy>
<wsp:UsingPolicy s2:Required="true"/>
<s2:types>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="java:com.my.service" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="base64Binary_literal" type="xs:base64Binary"/>
</xs:schema>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://com/my/service" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://my.com/types"/>
<xs:element name="saveBudgetPrintContents">
<xs:complexType>
<xs:sequence>
<xs:element name="customerID" type="xs:string"/>
<xs:element name="printID" type="xs:string"/>
<xs:element name="filename" type="xs:string"/>
<xs:element name="printDate" type="xs:dateTime"/>
<xs:element name="contents" type="xs:base64Binary"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="saveBudgetPrintContentsResponse">
<xs:complexType>
<xs:sequence/>
</xs:complexType>
</xs:element>
<xs:element name="getBudgetPrintContents">
<xs:complexType>
<xs:sequence>
<xs:element name="customerID" type="xs:string"/>
<xs:element name="printID" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="getBudgetPrintContentsResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="return" type="xs:base64Binary"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
</s2:types>
<s2:message name="saveBudgetPrintContents">
<s2:part element="s3:saveBudgetPrintContents" name="parameters"/>
</s2:message>
<s2:message name="saveBudgetPrintContentsResponse">
<s2:part element="s3:saveBudgetPrintContentsResponse" name="parameters"/>
</s2:message>
<s2:message name="getBudgetPrintContents">
<s2:part element="s3:getBudgetPrintContents" name="parameters"/>
</s2:message>
<s2:message name="getBudgetPrintContentsResponse">
<s2:part element="s3:getBudgetPrintContentsResponse" name="parameters"/>
</s2:message>
<s2:portType name="BudgetService">
<s2:operation name="saveBudgetPrintContents" parameterOrder="parameters">
<s2:input message="s3:saveBudgetPrintContents"/>
<s2:output message="s3:saveBudgetPrintContentsResponse"/>
</s2:operation>
<s2:operation name="getBudgetPrintContents" parameterOrder="parameters">
<s2:input message="s3:getBudgetPrintContents"/>
<s2:output message="s3:getBudgetPrintContentsResponse"/>
</s2:operation>
</s2:portType>
<s2:binding name="BudgetServiceServiceSoapBinding" type="s3:BudgetService">
<s4:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsp:Policy>
<wsp:PolicyReference URI="#policy:Mtom"/>
</wsp:Policy>
<s2:operation name="saveBudgetPrintContents">
<s4:operation soapAction="" style="document"/>
<s2:input>
<s4:body parts="parameters" use="literal"/>
</s2:input>
<s2:output>
<s4:body use="literal"/>
</s2:output>
</s2:operation>
<s2:operation name="getBudgetPrintContents">
<s4:operation soapAction="" style="document"/>
<s2:input>
<s4:body parts="parameters" use="literal"/>
</s2:input>
<s2:output>
<s4:body parts="parameters" use="literal"/>
</s2:output>
</s2:operation>
</s2:binding>
<s2:service name="BudgetServiceService">
<s2:port binding="s3:BudgetServiceServiceSoapBinding" name="BudgetServiceSoapPort">
<s4:address location="http://localhost:7001/MyService/BudgetService"/>
</s2:port>
</s2:service>
</s2:definitions>
As you can see the binary data is now at the top level.
Could somebody please enlighten me on this?
Is it by the standard, a limitation in WL or is there another explanation?
With the current behavior I'm tempted to just use good old attachments.
/John.
Edited by johnlindgreen at 10/24/2007 4:44 AM
Edited by johnlindgreen at 10/24/2007 4:45 AM
Edited by johnlindgreen at 10/24/2007 4:46 AM
Edited by johnlindgreen at 10/24/2007 4:46 AM

Answer 1

Sorry for the delay response. This is a known issue that MTOM is enabled only the binary data is at the top level in WLS 10.1.
But it has already support complex type MTOM encoded in WLS 10.3. Please download at [url http://commerce.bea.com/products/weblogicplatform/weblogic_prod_fam.jsp]here
Edited by jliao at 11/14/2007 5:46 AM