[
https://issues.apache.org/jira/browse/CXF-6491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626896#comment-14626896
]
Sergey Beryozkin commented on CXF-6491:
---------------------------------------
Both xml and json representations refer to the same element and the code blocks
representations with duplicate elements, if you change the order of reps and
put the JSON one first then XML one will not be printed if a method per
representation is required, otherwise you'd have a compilation error because
two identical Java method elements would be created.
When you have say a POST method with two reps, then unless a method 'id' is
set, it is "post" + a given rep element name, a media type does not contribute
to the uniqueness of the generated method name.
I think the clean solution is to have two WADL POST methods with different ids,
say, postXml and postJson, with one having only XML reps, the other one - only
JSON reps
> wadl2java produces incorrect Consumes 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)
