I'm using the dynamic client and even thought I set: requestContext.put (Message.MTOM_ENABLED, "false") the attachment goes thru looking like MTOM. Our code uses whatever wsdl the user enters so I can't add @XmlInlineBinaryData annotation to the field
Roger -----Original Message----- From: Daniel Kulp [mailto:[email protected]] Sent: Tuesday, October 27, 2015 7:22 AM To: [email protected] Cc: Daransky, Peter <[email protected]>; Berger, Franz <[email protected]> Subject: Re: Inline attachments sent as MTOM You can turn off MTOM, but that would force inline for everything. The other option would be to add @XmlInlineBinaryData annotation to the field to force that one to be inlined and not affect the others. Dan > On Oct 26, 2015, at 9:33 PM, Talkov, Roger <[email protected]> wrote: > > I have a Request Object with an attachment field of byte [], I expect the > attachment to go across as Inline data base 64 encoded, code snippet below. > > @XmlElement(required = true) > protected byte[] inputBinary; > > but it appears to be sent as an MTOM attachment: > > LoggingOutInterceptor: Outbound Message > --------------------------- > ID: 1 > Address: http://vwgarwin01:8080/testWS/testws > Encoding: UTF-8 > Http-Method: POST > Content-Type: multipart/related; type="text/xml"; > boundary="uuid:76ef1055-95fd-466a-b973-af39492ca798"; > start="<[email protected]>"; start-info="text/xml" > Headers: {Accept=[*/*], SOAPAction=[""]} > Payload: --uuid:76ef1055-95fd-466a-b973-af39492ca798 > Content-Type: text/xml; charset=UTF-8 > Content-Transfer-Encoding: binary > Content-ID: <[email protected]> > > <soap:Envelope > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";><soap:Body><ns3 > :echoRequest4 xmlns:ns1="http://schemas.xmlsoap.org/soap/encoding/"; > xmlns:ns3="http://www.automic.com/wsdl/test";><input>test > input</input><inputBoolean>false</inputBoolean><inputBinary><xop:Inclu > de xmlns:xop="http://www.w3.org/2004/08/xop/include"; > href="cid:[email protected]"/></in > putBinary><inputFloat>0.0</inputFloat><inputDouble>0.0</inputDouble><i > nputInteger>0</inputInteger><inputLong>0</inputLong><inputShort>0</inp > utShort><inputByte>0</inputByte><inputUnsignedInt>0</inputUnsignedInt> > <inputUnsignedLong>0</inputUnsignedLong><inputUnsignedShort>0</inputUn > signedShort><inputUnsignedByte>0</inputUnsignedByte><inputAnyURI>http: > //dummy</inputAnyURI><inputQName > xmlns:prefix="namespaceURI">prefix:localPart</inputQName></ns3:echoReq > uest4></soap:Body></soap:Envelope> > --uuid:76ef1055-95fd-466a-b973-af39492ca798 > Content-Type: application/octet-stream > Content-Transfer-Encoding: binary > Content-ID: <[email protected]> > > binary test > --uuid:76ef1055-95fd-466a-b973-af39492ca798— > > Is there any way I can have it go out as inline data? > > > Roger Talkov > Senior Software Engineer > [email protected] > +14256332568 > +14256332568 > > Come join us at Automic World 2015 > The Scottsdale Resort at McCormick Ranch > > > > Twitter: #AutomicWorld > Event Email: [email protected] > This email (including any attachments) may contain information which is > privileged, confidential, or protected. If you are not the intended > recipient, note that any disclosure, copying, distribution, or use of the > contents of this message and attached files is prohibited. If you have > received this email in error, please notify the sender and delete this email > and any attached files. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com This email (including any attachments) may contain information which is privileged, confidential, or protected. If you are not the intended recipient, note that any disclosure, copying, distribution, or use of the contents of this message and attached files is prohibited. If you have received this email in error, please notify the sender and delete this email and any attached files.
