[SWS-687] Attachment content id is resetted by spring web service Created: 24/Jan/11  Updated: 04/May/12  Resolved: 06/Oct/11

Status: Closed
Project: Spring Web Services
Component/s: Core
Affects Version/s: 1.5.7
Fix Version/s: 2.0.3

Type: Bug Priority: Major
Reporter: Jaise Thomas Assignee: Arjen Poutsma
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Content id set from the end point or intercepter is being overrided by the spring ws api. Please tell me if this issue is fixed already in another version.

axiomSoapMessage.addAttachment(
"JTT001-CONTENT-007-TXT1", new File("C:\\files
test.xml"));
//Attachment att1= axiomSoapMessage.getAttachment("JTT001-CONTENT-007-TXT1");
//System.out.println("content id of the attachment is working"+att1 != null);

Iterator itr = axiomSoapMessage.getAttachments();
Attachment att2 = null;
while(itr.hasNext())

{ att2 = (Attachment)itr.next(); System.out.println("Content id$$$"+att2.getContentId()); }

soapMessage.getSOAPPart().setContentId("CONTENT-SOAP-01");
if (soapMessage.saveRequired())

{ soapMessage.saveChanges(); }

 Comments   
Comment by Arjen Poutsma [ 06/Oct/11 ]

I can't reproduce this using the code provided. Can you attach a sample project that reproduces this issue, please?

Comment by Arjen Poutsma [ 04/May/12 ]

Closing old issues

Generated at Fri Dec 15 08:06:53 UTC 2017 using JIRA 6.4.14#64029-sha1:ae256fe0fbb912241490ff1cecfb323ea0905ca5.