This issue does not seem to be fixed. Generating the wadl with json schema does not solve this specific problem they are two separate things. It is the media type of the "example" that is wrong here and not creating the wadl as json or providing a json schema description of the object.
The format of the example is already rendered as xml in the resourcedoc.xml file before the wadl is generated, if the response type is json, then the example should be json.
- @response.representation.200.qname Root
- @response.representation.200.mediaType application/json
This is what I see when requesting the json schema version of the wadl. I have the describedby tags and I can request the schema for root. Note the example that is also included here that is still xml. We are using xslt to process the wadl and we do currently need the json-schema version, just the correct text representation of the example.
<ns2:representation xmlns:json="http://wadl.dev.java.net/2009/02/json-schema" element="Root" mediaType="application/json" json:describedby="application.wadl/root">
<ns4:code><?xml version="1.0" encoding="UTF-8" standalone="yes"?> <root/> </ns4:code>