[ https://jira.jboss.org/jira/browse/JBWS-2964?page=com.atlassian.jira.plug... ] Jim Ma updated JBWS-2964: ------------------------- Description: When the mimeHeaders value is from another soap message's mimeHeaders , the mimeHeader modification will probably change the referenced mimeHeaders. was: There is code in TCK to create a tmp soapmessage used to dump the outbound soap message: 1 baos = new ByteArrayOutputStream(); 2 msg.writeTo(baos); 3 MessageFactory mf = MessageFactory.newInstance(); 4 SOAPMessage tmpMsg = mf.createMessage(msg.getMimeHeaders(), 5 new ByteArrayInputStream(baos.toString().getBytes())); 6 tmpMsg.removeAllAttachments(); 7 tmpMsg.saveChanges(); Line7 will change the msg's mimeHeaders value . This is not expected. This issue is the cause of two tck failures : com.sun.ts.tests.jaxws.api.javax_xml_ws_handler.LogicalMessageContext.Client.java#ContextPropertiesTest_from_standalone() com.sun.ts.tests.jaxws.api.javax_xml_ws_handler_soap.SOAPMessageContext.Client.java#ContextPropertiesTest_from_standalone() Security: Public (was: JBoss Internal) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira