[
https://issues.apache.org/jira/browse/CXF-5728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14006077#comment-14006077
]
Sergey Beryozkin commented on CXF-5728:
---------------------------------------
Right, on one hand we want users or tools see some information about JSON. On
the other hand we have a formal contract which tells users what to expect on
the wire. As such I would not be surprised if someone told me using XML Schema
to describe JSON was a bug, given that plenty of JSON readers exist which do
not deal with JAXB. It is a compromise, we know JSON is not XML but we want to
*optionally* use whatever mechanisms WADL provides to tell the world something
about the JSON structure.
Linking also works for in the wadl to java case if we have a
representation/@element link. Only representation/parameter linking does not
work.
> wadl2java plugin does not create correctly typed parameters
> -----------------------------------------------------------
>
> Key: CXF-5728
> URL: https://issues.apache.org/jira/browse/CXF-5728
> Project: CXF
> Issue Type: Bug
> Components: Tooling
> Affects Versions: 2.7.11
> Reporter: Owen Farrell
> Fix For: 2.7.12
>
> Attachments: myschema.xsd, wadl2JavaTest.wadl
>
>
> When interpreting a WADL with a fully-qualified parameter type, the wadl2java
> plugin converts the parameter to a String in the stubbed interface instead of
> the class generated from the grammar's schema.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
