dkulp wrote:
>
>
> This isn't an Aegis issue I don't think.
>
> First off, can you try 2.2.4? There are a couple MTOM bugs fixed in
> 2.2.4,
> mostly around streaming, but it's possible it affects this.
>
> Next, any chance you can wireshark the transfers for both 2.2.4 and 2.1.3?
> I'd like to see what the differences are. I don't need the whole
> attachment.
> Just the soap message (to see the mtom element) and the headers for the
> attachment parts.
>
> Looking at it, I THINK it might have something to do with the special
> chars
> in:
> urn%3Acws%3Aasset
> (the %3A things)
> At one point, we were not properly encoding them which caused interop
> problems. I'm willing to be 2.1.3 probably has them as urn:cws:asset or
> similar. XFire might not be decoding the cid properly.
>
>
> Thanks!
> Dan
>
I've debugged server and you are right the problem is in special characters.
XFire expects no special symbols in requested attachment ids (e.g.
c89be824-3ac4-48ed-9d91-72072732f42a...@urn:cws:asset) but receives ids with
special symbols (e.g.
c89be824-3ac4-48ed-9d91-72072732f42a...@urn%3acws%3aasset), so it finds
nothing.
Thanks
--
View this message in context:
http://www.nabble.com/Upgrading-from-cfx-2.1.3-to-2.2.3-and-MTOM-issue-tp25988535p26008399.html
Sent from the cxf-user mailing list archive at Nabble.com.
