[
https://issues.apache.org/jira/browse/CXF-6491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14621317#comment-14621317
]
Pat Lynch commented on CXF-6491:
--------------------------------
For the sake of sanity would it make sense to start by limiting the multiple
representations to either in or out but not both? Of course I'm speaking from
our perspective where this happens to be our current practice. We usually
return a 204 (no content) response from a POST/PUT.
> wadl2java produces incorrect Comsumes annotation for multiple representations
> on POST methods
> ---------------------------------------------------------------------------------------------
>
> Key: CXF-6491
> URL: https://issues.apache.org/jira/browse/CXF-6491
> Project: CXF
> Issue Type: Bug
> Components: Tooling
> Affects Versions: 3.0.2, 3.0.5, 3.1.1
> Environment: CentOS 6.6, Java
> java version "1.7.0_71"
> OpenJDK Runtime Environment (rhel-2.5.3.2.el6_6-x86_64 u71-b14)
> OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
> Reporter: Pat Lynch
> Assignee: Sergey Beryozkin
> Fix For: 3.0.6, 3.1.2
>
> Attachments: PlcmHohoResource.java, plcm-hoho-v2.xsd,
> plcm-hoho-v3.xsd, plcm-hoho.wadl, plcm-hoho.xsd
>
>
> The wadl2java tool, with the supportMultipleXmlReps option, generates the
> wrong @Consumes annotation values for each of the POST methods that have
> multiple representations. The annotation for all of the methods contains all
> of the media types instead of the single media type that is appropriate for
> the specific method.
> I've tested the versions listed in the affected versions field, but it likely
> applies to other versions as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
