Hi,<= /p>

I got the issue now, s= orry for delay.

The problem is that if= you use WSDL or Java first approaches, you say CXF where inject a referenc= e to sending binary data:

-&n= bsp; for WSDL using= <element name=3D"attachinfo" type=3D"xsd:base64Binary&qu= ot; xmime:expectedContentTypes=3D"application/octet-stream"/><= o:p>

-&n= bsp; for java using= annotation:

&nb= sp; @XmlMimeType("application/octet-stream")

&nb= sp; protected DataHandler imageData;

In case of using Dispa= tch interface and SOAPMessage, user is responsible to build complete SOAP m= essage and, as a result, to insert <xop:Include href> element.

Currently CXF has no i= nformation where this element should be added in SOAPMessage body.

I think that could be = a useful extension to provide additional property for example in form of XP= ath and automate that for SOAPMessage as well.

Patch is welcome.=

Regards,

Andrei.

From: Gumudavelli, Alekhya [mailto:Alekhya.Gumudavelli@in.p= ega.com]
Sent: Dienstag, 18. Februar 2014 13:53
To: Andrei Shakirin; users@cxf.apache.org
Subject: RE: Query on CXF dispatch client with MTOM
Importance: High

Hi Andr= ei,

Any upd= ate on this. I raised a JIRA item on the same last week. Could someone plea= se look into it.

https://issues.apache.o= rg/jira/browse/CXF-5560

Let me = know if you need more details on the issue.

&n= bsp;

Regards= ,

Alekhya=

&n= bsp;

From: Gumudavelli, Alekhya
Sent: Thursday, February 13, 2014 11:42 AM
To: Andrei Shakirin; users@c= xf.apache.org
Subject: RE: Query on CXF dispatch client with MTOM

Hi,

<= /span>

I am at= taching the client and service that I am using. MTOMClient.java is a = standalone Java program that I wrote to connect to a service that I got fro= m CXF samples apache-cxf-3.0.0-milestone1.rar

( apach= e-cxf-3.0.0-milestone1\samples\mtom ). links.txt is the file I = am trying to send as an MTOM attachment.

<= /span>

I am al= so attaching MTOMClientBase64.java. It sends a base64 encoded data of the a= ttachment.

<= /span>

Regards= ,

Alekhya=

<= /span>

From: Andrei Shakirin [mailto:ashakirin@talend.com]
Sent: Wednesday, February 12, 2014 9:43 PM
To: users@cxf.apache.org=
Cc: Gumudavelli, Alekhya
Subject: RE: Query on CXF dispatch client with MTOM

Hi,

Interesting. Any chanc= e to create a small test case to reproduce that?

Regards,

Andrei.

From: Gumudavelli, Alekhya [= mailto:Alekhya.Gumudavelli= @in.pega.com]
Sent: Mittwoch, 12. Februar 2014 14:26
To: Andrei Shakirin; us= ers@cxf.apache.org=
Subject: RE: Query on CXF dispatch client with MTOM

Hi,

I don&#= 8217;t find any difference between my client code and https://svn.apache.org/repos/asf/cxf/branches/2.7.x-fixes/sy= stests/jaxws/src/test/java/org/apache/cxf/systest/swa/ClientServerSwaTest.j= ava except that I am doing an additional setting MTOMEnabled property to true.=

<= /span>

Can you= give me any MTOM specific sample test (not just SWA). I would like to try = that out directly. I had searched in cxf/systest/ repository but could not = find any. I see that all MTOM tests in the repo use stubs and not dispatch API.

<= /span>

Or can = you point me to the internal CXF code / class that takes care of adding <= ;xop include> element. I would like to debug and understand why is it no= t xop’ing it.

We are = revamping our entire stack to use CXF and this issue is hindering us from i= mplementing MTOM with CXF, one of the important features for clients.

<= /span>

Thanks = much for the quick responses Andrei!

<= /span>

Alekhya=

<= /span>

From: Andrei Shakirin [mailto:ashakirin@talend.com]
Sent: Tuesday, February 11, 2014 11:06 PM
To: users@cxf.apache.or= g
Cc: Gumudavelli, Alekhya
Subject: RE: Query on CXF dispatch client with MTOM

Hi,

It is quite difficult = to say what exactly wrong without your test case.

Could you run the syst= em test I referenced in last mail and try to find the difference between te= st and your code?

Regards,

Andrei.

From: Gumudavelli, Alekhya [= mailto:Alekhya.Gumudavelli= @in.pega.com]
Sent: Dienstag, 11. Februar 2014 12:54
To: Andrei Shakirin; us= ers@cxf.apache.org=
Subject: RE: Query on CXF dispatch client with MTOM

Hi Andr= ei,

I am do= ing exactly the way you are referring. The service is not able to recognize= attachment.

<= /span>

Below i= s my service method . It fails to process attachment as the parameter ̶= 0;attachinfo” does not hold the attachment we have sent. This works w= ell if I manually insert <attachinfo> element by linking it with content-id.=

<= /span>

public = void testDataHandler(Holder<String> name, Holder<DataHandler>= ; attachinfo) {<= /o:p>

&= nbsp; &nbs= p; if(attachinfo.value=3D=3Dnull)

&nb= sp; = ; {System.out.println("attachin= fo.value is null"); //This gets executed

&nbs= p; = return;}

&= nbsp; &nbs= p; InputStream mtomIn =3D attachinfo.value.getInputStream();

&= nbsp; &nb= sp;ByteArrayOutputStream out =3D new ByteArrayOutputStream();

and so on…. = &nb= sp;

Also, i= n the below line we can use any random name to set content id. Isn’t = it?

<= /span> &nb= sp; att.setContentId("<attach1=3Dc187f5da-fa5d-4ab9= -81db-33c2bb855201@apache.org>");=

Could you please help = me out with this issue

Below is the screensho= t of my request in TCP mon –

3D"cid:image001.jpg@01CF28AC.70954370"

<= /span>

Regards= ,

Alekhya=

<= /span>

From: Andrei Shakirin [mailto:ashakirin@talend.com]
Sent: Monday, February 10, 2014 9:57 PM
To: users@cxf.apache.or= g
Cc: Gumudavelli, Alekhya
Subject: RE: Query on CXF dispatch client with MTOM

Hi,

I do not think that yo= u should add MTOM <include> manually.

It should be enough to= activate MTOM and add attachment part in following way:

&nbs= p; DataHandler dh1 =3D new DataHandler(new ByteArrayDataS= ource(bigBytes, "text/plain"));

&nbs= p; AttachmentPart att =3D msg.createAttachmentPart(dh1);<= /span>

&nbs= p; att.setContentId("<attach1=3Dc= 187f5da-fa5d-4ab9-81db-33c2bb855201@apache.org>");

&nbs= p; msg.addAttachmentPart(att);

See the testSwaTypesWi= thDispatchAPI() in https://svn.apache.org/repos/asf/cxf/branches/2.7.x-fixes/sy= stests/jaxws/src/test/java/org/apache/cxf/systest/swa/ClientServerSwaTest.j= ava for details.

Regards,

Andrei.

From: Gumudavelli, Alekhya [= mailto:Alekhya.Gumudavelli= @in.pega.com]
Sent: Montag, 10. Februar 2014 08:36
To: Andrei Shakirin
Cc: users@cxf.apache.or= g
Subject: Query on CXF dispatch client with MTOM

Hi Andrei= , team

I am writ= ing a CXF client with MTOM by using dynamic dispatch style of service invoc= ation. I understand that dynamic dispatch requires request message to be co= nstructed manually.

But I wou= ld like to avoid manual insertion of <inc:include href> XOP element i= n the SOAP message to enable MTOM.

I am curr= ently doing the following steps to generate a CXF mtom client

1. Enable MTOM using

((SOAPBinding)binding).setMTOMEnabled();

2.       Construct SOAP request me= ssage programmatically

SOAPMessage request =3D = MessageFactory.newInstance().createMessage();

//= create attachment and add it to request

AttachmentPart attach =3D request.createAttachmentPart(new DataHandler(new FileDataSource("F:\\CXF3\\CXF3\\s= rc\\me.bmp")));

&= nbsp;   attach.setContentId(= "image");

request.addAttachmentPar= t(attach);

SOAPElement operation =3D body.addChildElement("testDataHandler"= , "typ",<= /span>

&= nbsp;          "<= span style=3D"font-size:10.0pt;font-family:"Courier New"">http://= cxf.apache.org/mime/types");

&= nbsp;
/= *Here, I am creating the SOAP body with appropriate nodes needed for MTOM -= <inc:include href=3D”image”. . . */

<= /span>

SOAPElement value1 =3D operation.addChildElement("attachinfo",= "tns","http://cxf.apache.org/mime/types");

SOAPElement xop =3D= value1.addChildElement("Include","inc","http://www.w3.org/2004/08/= xop/include");<= /b>

xop.addAttribute(QN= ame.valueOf("href"),"cid:image<= /a>");

Generated request message :
<soap:= Envelope xmlns:soap=3D"http://schemas.xmlsoap.org/soap/envelope/"= ; xmlns:typ=3D"http://cxf.apache.org/mime/types">
&nb= sp; <soapenv:Header xmlns:soapenv=3D"http://schemas.xmlsoap.org/soap/e= nvelope/"/>

&nb= sp; <soap:Body>

&nb= sp; <typ:testDataHandler>

<tns:attachinfo xmlns:tns=3D"= htt= p://cxf.apache.org/mime/types"><inc:Include xmlns:inc=3D"http://www.w3.org/2004/08/xop/include" href=3D"cid:image"/>= </= tns:attachinfo= >
</typ:testDataHandler>

</soap= :Body>

</soap= :Envelope>

The above= request works well. However, manual inclusion of DOM elements like this do= es not appear clean and maintainable. Could you tell me how else can we ach= ieve this to generate the request d= ynamically?

<= /span>

I have th= e same issue with SWA CXF dispatch client where I am including <cid:image> node programmatically which I want to avoi= d.

<= /span>

Thanks,

Alekhya G= umudavelli