WSDL with SOAP Binding and Attachement

Question

Hello
I'm trying to define a WSDL-Definition which defines a operation called getFile() which returns a file as a SOAP attachement. I created the follwing file which I can verify without any problems. However if I try to compile it with wscompile (wscompile -gen:server -mapping build/mapping.xml -d build -nd build -classpath . config.xml) I get the follwing error:
error: output message of binding operation "getFile" does not have a SOAP body extension
When I remove the line
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
wscompile generates the classes but gives the following warnings:
warning: ignoring port "FileDistributorIFPort": not a SOAP port
warning: Service "FileDistributorService" does not contain any usable ports
Which is somehow clear because I did not define the soap binding.
Any ideas what I can do so I can transmit a file via SOAP using attachements?
Here's the file
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="FileDistributorService"
targetNamespace="urn:Foo"
xmlns:tns="urn:Foo"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
<types>
<xsd:schema targetNamespace="urn:Foo"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
<xsd:element name="getFile">
<xsd:complexType>
<xsd:all>
<xsd:element name="mySymbol" type="xsd:string"/>
</xsd:all>
</xsd:complexType>
</xsd:element>
<xsd:element name="getFileResponse">
<xsd:complexType>
<xsd:all>
<xsd:element name="result" type="float"/>
</xsd:all>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="ArrayOfBinary">
<xsd:complexContent>
<xsd:restriction base="soapenc:Array">
<xsd:attribute ref="soapenc:arrayType"
wsdl:arrayType="xsd:binary[]"/>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
</xsd:schema>
</types>
<message name="m1">
<part name="body" element="tns:getFile"/>
</message>
<message name="m2">
<part name="body" element="tns:getFileResponse"/>
<part name="file" type="tns:ArrayOfBinary"/>
</message>
<portType name="pt1">
<operation name="getFile">
<input message="tns:m1"/>
<output message="tns:m2"/>
</operation>
</portType>
<binding name="b1" type="tns:pt1">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
<operation name="getFile">
<soap:operation soapAction="getFile"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<mime:multipartRelated>
<mime:part>
<soap:body parts="body" use="literal"/>
</mime:part>
<mime:part>
<mime:content part="file" type="tns:ArrayOfBinary"/>
</mime:part>
</mime:multipartRelated>
</output>
</operation>
</binding>
<service name="FileDistributorService">
<port name="FileDistributorIFPort" binding="tns:b1">
<soap:address location="http://localhost:8080/fxm/FileDistributorImpl"/>
</port>
</service>
</definitions>
Thanks a lot!
Oliver

Answer 1

Not very sure, but i suspect that there is an error here in your WSDL :
<mime:multipartRelated>
<mime:part>
<soap:body parts="body" use="literal"/>
</mime:part>
<mime:part>
<mime:content part="file" type="tns:ArrayOfBinary"/>The type attribute should be a valid Mime Type.
Quoting from the WSDL Specification
The type attribute contains the MIME type string. A type value has two portions, separated by a slash (/), either of which may be a wildcard (*). Not specifying the type attribute indicates that all MIME types are acceptable.
Why not try the following instead of the last line above
<mime:content part="file" type="*/*"/>