[
https://issues.apache.org/jira/browse/CXF-2717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Beryozkin reopened CXF-2717:
-----------------------------------
Assignee: Sergey Beryozkin
> Some Content-Transfer-Encoding values are not supported for multiparts
> ----------------------------------------------------------------------
>
> Key: CXF-2717
> URL: https://issues.apache.org/jira/browse/CXF-2717
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Affects Versions: 2.2.5
> Reporter: Andreas Sahlbach
> Assignee: Sergey Beryozkin
> Fix For: 2.3
>
>
> In the JAX-RS documentation I've read the following:
> {quote}
> When handling complex multipart/form-data submissions (such as those
> containing files) MultipartBody (and Attachment) need to be used directly. In
> simpler cases, when every form part can be captured by String, the following
> code will suffice :
> @POST
> @Consumes("multipart/form-data")
> public void addForm1(@FormParam("name") String title, @FormParam("id") Long
> id) throws Exception {
> ...
> {quote}
> This is either a bug in CXF or a misleading documentation (at least for
> slow-minded non-native speaker like me). The big difference between
> @FormParam and @Multipart is, that @FormParam _always_ expects url-encoded
> data. So sending "A+B" using Multipart in e.g. 8-bit encoding or binary
> encoding delivers "A B" to @FormData annotated Strings but "A+B" to
> @Multipart annotated Strings.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
