In the AttachmentSerializer writeHeaders method (CXF 2.2.1) it looks like the
attachmentId is incorrectly substring'd. As it is today the substring
removes the last character of the content id plus the '>'. When the message
is deserialized it can not find the attachment since the content id is
incorrect. 

I have changed the substring line to the following to fix this problem. I
can file a bug report on this, but wanted to make sure I wasn't missing
something.

attachmentId = attachmentId.substring(1, attachmentId.length() - 1);

Thanks,
Chris
-- 
View this message in context: 
http://www.nabble.com/Attachment-serializer-bug-tp23390908p23390908.html
Sent from the cxf-user mailing list archive at Nabble.com.

Reply via email to