Description
In the scenario below :
SOAPMessage msg = MessageFactory.newInstance().createMessage();
SOAPPart sp = msg.getSOAPPart();
SOAPEnvelope envelope = sp.getEnvelope();
SOAPBody bdy = envelope.getBody();
SOAPBodyElement sbe = bdy.addBodyElement(envelope.createName("Body1", "ns1", "http://www.helloworld.org"));
sbe.addChildElement(envelope.createName("c1", "ns1", "http://www.helloworld.org")).addTextNode("HelloWorld");
URL url = new File("D:\\opensource\\axis2\\axis2\\axis2-1.5\\modules\\saaj
pom.xml").toURI().toURL();
AttachmentPart attachmentPart = msg.createAttachmentPart(new DataHandler(url));
attachmentPart.setContentType("text/xml");
msg.addAttachmentPart(attachmentPart);
msg.saveChanges();
If we use SOAPMessage.writeTo method to write to the message to an servlet outputstream, those boundary, content-id values are generated on the fly. And for the client applications, there is no way to get the corresponding content-type header.