The CXF response message is correct. That incoming message really isn't. I'm really surprised that works. MTOM, by definition, puts stuff on the wire using XOP. See the example at: http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.express.iseries.doc/info/iseriesexp/ae/cwbs_xop.html
From a validation standpoint, that's technically a bug in JAXB. :-( We've worked around it a bit in CXF 2.1.4 that I'm running final tests on now. Dan On Tue February 3 2009 12:15:38 pm Heemskerk, Marcel (M.) wrote: > I defined a WSDL with a request with an attachement <xsd:element > name="UploadedZippedCsvFile" type="xsd:base64Binary" > xmime:expectedContentTypes="application/zip"/> with namespace > xmlns:xmime="http://www.w3.org/2005/05/xmlmime"; > > CXF/JAXB generates this into a DataHandler for this element. The JAXWS > properties have "mtom-enabled" to "true". > With for example SOAPUI i send a request with attachement > <UploadedZippedCsvFile>cid:1205859071240</UploadedZippedCsvFile> with > the mime attachement below the XML, this works fine. > > However... When using the same element in the response, CXF wraps the > cid:xxxx string into a <xop> element. The response XML doesn't even > validate! > > How do i correct this? > > Greetings, > Marcel Heemskerk > > > > > === ( sorry for previous unfinished message ) === -- Daniel Kulp [email protected] http://www.dankulp.com/blog
