You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating a SOAP Attachment its 'Content-ID: ' header returns as 'Content-Id:' (with small 'd' letter and without a space after ':')
This issue cause interoperability problems with some clients that expects all headers with a space after semicolon and expects standart headers as they described in ws-i.org Attachment profile 1.0
I think its because this code in class
com.sun.xml.ws.encoding.MimeCodec :
public ContentType encode(Packet packet, OutputStream out) throws IOException {
...
if(cid != null && cid.length() >0 && cid.charAt(0) != '<')
cid = '<' + cid + '>';
writeln("Content-Id:" + cid, out);
writeln("Content-Type: " + att.getContentType(), out);
...
}
When creating a SOAP Attachment its 'Content-ID: ' header returns as 'Content-Id:' (with small 'd' letter and without a space after ':')
This issue cause interoperability problems with some clients that expects all headers with a space after semicolon and expects standart headers as they described in ws-i.org Attachment profile 1.0
I think its because this code in class
com.sun.xml.ws.encoding.MimeCodec :
public ContentType encode(Packet packet, OutputStream out) throws IOException {
...
if(cid != null && cid.length() >0 && cid.charAt(0) != '<')
cid = '<' + cid + '>';
writeln("Content-Id:" + cid, out);
writeln("Content-Type: " + att.getContentType(), out);
...
}
Source: javaee/metro-jax-ws#1203
Author: Dukekz
The text was updated successfully, but these errors were encountered: