Hi,
I am providing a web service based on servicemix-jsr181 (which uses XFire) 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 XFire 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 XFire?
Thanks for your help...
André
if( self == top ) { Nabble.writeReturnToLink( 'Return to thread' );
} else if( Nabble.prev ) Nabble.writeReturnToLink(Nabble.prev);
---------------------------------
Die etwas anderen Infos rund um das Thema Reisen. BE A BETTER WELTENBUMMLER!
