[
https://issues.apache.org/jira/browse/CXF-5728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989689#comment-13989689
]
Sergey Beryozkin commented on CXF-5728:
---------------------------------------
Well, XML Schema is for describing XML payloads. What if a user says
"text/plain" and links to the grammar ? XMl Schema does not have a notion of
the rootless sequences, etc. So what we are talking about is making WADL more
useful for describing JSON sequences - and primarily those one which are backed
up by JAXB-aware JSON providers.
WADL auto-generator supports linking application/json data to grammars exactly
for this reason: making WADL more useful, despite the mismatch between the XML
Schema 'view of the world' and that of JSON's. This is why I'm open to
supporting linking the generated types even if it is "application/json" - but
it will be an optional feature.
Now, re the use of representation parameters. Why do you prefer to use it this
way as opposed to linking directly from the representation element, example, to
a schema element representing a collection ?
> 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)
