Hi David

Please see [1]. I've added 3 extra properties:
- applicationTitle (String, can be used to set a
wadl/application/wadl:doc/@title)
- namespacePrefix (String, can be used to override the default prefix if needed)
- ignoreForwardSlash (boolean) - if the stylesheet adds '/' itself
when concatenating path values then setting this value to false will
help.

You can just link to a customized WADLGenerator bean from
jaxrs:providers section

Thanks, Sergey

[1] 
https://cwiki.apache.org/confluence/display/CXF20DOC/JAXRS+Services+Description#JAXRSServicesDescription-CustomWADLproviders

On Wed, Apr 20, 2011 at 11:17 PM, KARR, DAVID (ATTSI) <[email protected]> wrote:
>> -----Original Message-----
>> From: KARR, DAVID (ATTSI)
>> Sent: Wednesday, April 20, 2011 2:59 PM
>> To: [email protected]
>> Subject: How to properly set "title" in generated WADL
>>
>> My controller class has a @Description annotation with both "title" and
>> "value" properties.
>>
>> Here is an abbreviated excerpt from the generated WADL:
>> ------------------
>>   <resources base="http://myuri";>
>>     <resource path="mypath">
>>       <doc title="mytitle">mydescription</doc>
>> ------------------
>>
>> This all seems reasonable.  I'm trying to use a spreadsheet that
>> generates docs from a WADL, from <
>> https://github.com/mnot/wadl_stylesheets>.  It mostly works, but it's
>> not getting my title value.  This is possibly just a XSLT bug in the
>> spreadsheet, or perhaps there are different interpretations of where
>> the title should go.
>
> Ok, I think I see one issue.  This stylesheet is checking for the "doc" 
> element in the "application" element, but CXF's @Description annotation on 
> the controller results in putting the title and description in the "resource" 
> element.
>
> It sounds like any documentation at the "application" level wouldn't be in 
> the Controller, it would have to be in the "jaxrs:server" element, at least.
>



-- 
Sergey Beryozkin

Application Integration Division of Talend
http://sberyozkin.blogspot.com

Reply via email to