Hi, I still have this problem... Doesn't anyone have an idea? At least I would appreciate a hint if it's rather a bug of servicemix-jsr181 or XFire.
Thanks André André Szdzuy wrote: > > Hi, > I am providing a web service based on servicemix-jsr181 and a POJO. My > operation has a parameter "TARFILE" of type DataHandler and I have MTOM > enabled. The parameter part of the WSDL generated by servicemix-jsr181 > looks like this: > > <xsd:element minOccurs="0" name="TARFILE" nillable="true" > type="xsd:base64Binary"/> > > If I import the WSDL with some other SOAP tool like SoapUI and generate a > SOAP request from it the parameter TARFILE is considered to contain a > base64 string and not a reference to an attachment as I actually want. > SoapUI's behaviour is correct, I would say, because the WSDL doesn't > contain any hint that MTOM and attachments should be used. > > When I adjust the WSDL manually by replacing "xsd:base64Binary" by > "xmime:base64Binary" with xmlns:xmime="http://www.w3.org/2005/05/xmlmime"; > then SoapUI generates the correct SOAP request from it! > > Can I configure the WSDL generation so that it puts "xmime:base64Binary" > into the WSDL? Or is it a bug in servicemix-jsr181 or even XFire? > > Thanks for your help... > > André > > -- View this message in context: http://www.nabble.com/wrong-WSDL-generated-for-MTOM-attachments-tf4354339s12049.html#a12776613 Sent from the ServiceMix - User mailing list archive at Nabble.com.
