[
https://issues.apache.org/jira/browse/AXIS2-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13047460#comment-13047460
]
Andreas Veithen commented on AXIS2-5067:
----------------------------------------
Ivan,
The two new test cases fail with the SAAJ reference implementation. You can
check that by adding a @Validated annotation to the test methods; they will
then be executed against the reference implementation before testing the Axis2
implementation.
> content-type header is not generated with SAAJ API
> --------------------------------------------------
>
> Key: AXIS2-5067
> URL: https://issues.apache.org/jira/browse/AXIS2-5067
> Project: Axis2
> Issue Type: Bug
> Components: saaj
> Affects Versions: 1.6.0
> Reporter: Ivan
> Assignee: Andreas Veithen
> Attachments: AXIS2-5067.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
