Precisely which version are you using--2.0.what? If it's too old, best to upgrade first. Also, what happens if you try a Metro client[1]--do you get the same problem or does the problem go away? That would help narrow down the problem to SOAP client or web service provider, or developer error or web service stack error.
HTH, Glen [1] http://www.jroller.com/gmazza/date/20071102 Evan Huang wrote: > > Hi > > I've sent a mail about the content id issue a couple of days ago, I > wonder if there is any information for this issue, it really bothers us > so much. > Here is the original mail: > > I am working on getting an CXF 2.0 client to work with a Java service > written using > Metro 1.2, > I have been trying to get an CXF 2.0 client to receive an MTOM response > back from my service to receive a mms, > but the content-id has been lost in the soap message > > here is part of the soap message(attachment) > > ------=_Part_1_22176987.1215509803675 > Content-Type: application/smil > > <smil xmlns="http://www.w3.org/2001/SMIL20/Language";> > <body> > <par dur="3s"> > <text src="cid:text.txt"/> > </par> > <par dur="5s"> > cid:ericsson_logo.gif > </par> > </body> > </smil> > > > ------=_Part_1_22176987.1215509803675-- > > as we can see, the content-id is missing > > the client is generate by wsdl2java, standard saaj interfaces are used, > I add a SOAPHandler in the handlerChain of the binding to process the > inbound attachment in the soap message, but when I check the soap > message, I found that the content id has already been lost > > > Best Regards > Evan > > -- View this message in context: http://www.nabble.com/miss-content-id-in-soap-message-attachment-using-CXF-client-and-Metro-server-tp18395374p18396432.html Sent from the cxf-user mailing list archive at Nabble.com.
