Dan, I was looking at the docco and it says that you need to add the xmime:expectedContentTypes attribute to your WSDL to make MTOM work, as well as enabling the run time support, but the MTOM demo does not use this and simply generates byte[]. Which is correct? Or does it matter as long as the runtime support is turned on? Cheers, Eric
> -----Original Message----- > From: Dan Diephouse [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 15, 2007 4:45 PM > To: [email protected] > Subject: Re: SOAP w/ Attachments > > Yes it works on all soap versions. You can enable it simply > by setting the "mtom-enabled" property to "true" somewhere > (i.e. on the service/endpoint/etc - > endpoint.put("mtom-enabled", Boolean.TRUE);) > > - Dan > > On 5/15/07, Johnson, Eric <[EMAIL PROTECTED]> wrote: > > > > Does MTOM work for both SOAP 1.1 and SOAP 1.2? Can MTOM be enabled > > through configuring the SOAP binding rather JAX-WS? > > > > > -----Original Message----- > > > From: Dan Diephouse [mailto:[EMAIL PROTECTED] > > > Sent: Monday, May 14, 2007 2:28 PM > > > To: [email protected] > > > Subject: Re: SOAP w/ Attachments > > > > > > On 5/14/07, Johnson, Eric <[EMAIL PROTECTED]> wrote: > > > > > > > > Does either of the SOAP bindings support sending binary > attachments? > > > > > > > > > > We support MTOM: > > > http://cwiki.apache.org/CXF20DOC/mtom-attachments.html > > > > > > There is also minimal support for SwA (according to the > > > AttachmentsProfile), but that is basically worthless because any > > > soap stack that does SwA AP also does MTOM: > > > > > > http://netzooid.com/blog/2007/01/04/the-ws-i-attachmentsprofil > > e-is-a-sham/ > > > > > > - Dan > > > > > > -- > > > Dan Diephouse > > > Envoi Solutions > > > http://envoisolutions.com | http://netzooid.com/blog > > > > > > > > > -- > Dan Diephouse > Envoi Solutions > http://envoisolutions.com | http://netzooid.com/blog >
