[jira] [Commented] (HTTPCLIENT-317) HTTP Client doesn't support multipart/related content-type
[ https://issues.apache.org/jira/browse/HTTPCLIENT-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749884#comment-13749884 ] Oleg Kalnichevski commented on HTTPCLIENT-317: -- Fixed in SVN trunk and targeted for inclusion in 4.3. Oleg > HTTP Client doesn't support multipart/related content-type > -- > > Key: HTTPCLIENT-317 > URL: https://issues.apache.org/jira/browse/HTTPCLIENT-317 > Project: HttpComponents HttpClient > Issue Type: Improvement > Components: HttpMime >Affects Versions: 2.0 Final > Environment: Operating System: Windows XP > Platform: PC >Reporter: peter >Priority: Minor > Fix For: 4.0 Beta 2 > > > It is not possible to sent data easely as a multipart/related content-type > (as > discribed in rfc 2387) using Http Client. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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]
[jira] [Commented] (HTTPCLIENT-317) HTTP Client doesn't support multipart/related content-type
[ https://issues.apache.org/jira/browse/HTTPCLIENT-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749697#comment-13749697 ] Eugene Fedotov commented on HTTPCLIENT-317: --- Though the MinimalField *class* is public, its *constructor* is still package private. > HTTP Client doesn't support multipart/related content-type > -- > > Key: HTTPCLIENT-317 > URL: https://issues.apache.org/jira/browse/HTTPCLIENT-317 > Project: HttpComponents HttpClient > Issue Type: Improvement > Components: HttpMime >Affects Versions: 2.0 Final > Environment: Operating System: Windows XP > Platform: PC >Reporter: peter >Priority: Minor > Fix For: 4.0 Beta 2 > > > It is not possible to sent data easely as a multipart/related content-type > (as > discribed in rfc 2387) using Http Client. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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]
[jira] Commented: (HTTPCLIENT-317) HTTP Client doesn't support multipart/related content-type
[ https://issues.apache.org/jira/browse/HTTPCLIENT-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830192#action_12830192 ] Oleg Kalnichevski commented on HTTPCLIENT-317: -- MinimalField is a public class. I do not see why this class should be added to HttpMime. Oleg > HTTP Client doesn't support multipart/related content-type > -- > > Key: HTTPCLIENT-317 > URL: https://issues.apache.org/jira/browse/HTTPCLIENT-317 > Project: HttpComponents HttpClient > Issue Type: Improvement > Components: HttpMime >Affects Versions: 2.0 Final > Environment: Operating System: Windows XP > Platform: PC >Reporter: peter >Priority: Minor > Fix For: 4.0 Beta 2 > > > It is not possible to sent data easely as a multipart/related content-type > (as > discribed in rfc 2387) using Http Client. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] Commented: (HTTPCLIENT-317) HTTP Client doesn't support multipart/related content-type
[
https://issues.apache.org/jira/browse/HTTPCLIENT-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829675#action_12829675
]
Peter Klotz commented on HTTPCLIENT-317:
OK, I fixed the problem with a new sub-class for FormBodyPart that adds the
Content-ID header called SOAPBodyPart
I only would need someone to commit this, as one cannot use MinimalField
outside the httpcomponent package, for whatever reason.
---
package org.apache.http.entity.mime;
import org.apache.http.annotation.NotThreadSafe;
import org.apache.http.entity.mime.content.ContentBody;
import org.apache.james.mime4j.descriptor.ContentDescriptor;
/**
* An extension of the mime4j standard {...@link BodyPart} class that
* automatically populates the header with standard fields based
* on the content description of the enclosed body.
*
*
* @since 4.0
*/
@NotThreadSafe // Entity is @NotThreadSafe
public class SOAPBodyPart extends FormBodyPart {
public SOAPBodyPart(final String name, final ContentBody body) {
super(name, body);
generateContentID(body);
}
protected void generateContentID(final ContentDescriptor desc)
{
StringBuilder buf = new StringBuilder();
buf.append("<").append(getName()).append(">");
getHeader().addField(new MinimalField("Content-ID", buf.toString()));
}
}
> HTTP Client doesn't support multipart/related content-type
> --
>
> Key: HTTPCLIENT-317
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-317
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpMime
>Affects Versions: 2.0 Final
> Environment: Operating System: Windows XP
> Platform: PC
>Reporter: peter
>Priority: Minor
> Fix For: 4.0 Beta 2
>
>
> It is not possible to sent data easely as a multipart/related content-type
> (as
> discribed in rfc 2387) using Http Client.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
[jira] Commented: (HTTPCLIENT-317) HTTP Client doesn't support multipart/related content-type
[ https://issues.apache.org/jira/browse/HTTPCLIENT-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829662#action_12829662 ] Peter Klotz commented on HTTPCLIENT-317: It would be fixed in HttpMime, could you please explain how? Because if I even look into HttpMime 4.1 alpha2 in trunk there is nothing that generates the Content-ID header in the parts with HttpMultipartMode.STRICT only Content-Type, Content-Disposition and Content-Transfer-Encoding. But Content-ID is NEEDED e.g. in Servicemix as target. so the above mentioned problem is still open in the latest version but the workaround only would work in 3.1 (legacy) > HTTP Client doesn't support multipart/related content-type > -- > > Key: HTTPCLIENT-317 > URL: https://issues.apache.org/jira/browse/HTTPCLIENT-317 > Project: HttpComponents HttpClient > Issue Type: Improvement > Components: HttpMime >Affects Versions: 2.0 Final > Environment: Operating System: Windows XP > Platform: PC >Reporter: peter >Priority: Minor > Fix For: 4.0 Beta 2 > > > It is not possible to sent data easely as a multipart/related content-type > (as > discribed in rfc 2387) using Http Client. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
