[
https://issues.apache.org/jira/browse/CXF-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13858787#comment-13858787
]
Sergey Beryozkin commented on CXF-5353:
---------------------------------------
Hi Francesco
I think if you get WADLGenerator initialized with a CXF bus reference (via the
constructor) then the jar can be placed elsewhere, say in WEB-INF/javadocs, the
default CXF bus id is 'cxf'.
I can see UserService keeping Descriptions targeting METHOD and RETURN, which
is exactly what JavaDocs handler will target as well. Descriptions would be
preferred, so if you'd like to get JavaDocs preferred instead then drop
Descriptions, or perhaps, change Description target, for example, Description
would target REQUEST and RESPONSE.
We can make it a bit more flexible, for example, we can make JavaDocs targeting
RESPONSE instead of RETURN if preferred, but lets see first if it can produces
something at all,
Cheers, Sergey
> WADLGenerator needs to support existing JavaDocs when possible
> --------------------------------------------------------------
>
> Key: CXF-5353
> URL: https://issues.apache.org/jira/browse/CXF-5353
> Project: CXF
> Issue Type: Improvement
> Reporter: Sergey Beryozkin
>
> CXF @Description annotations targeting a given resource method (method itself
> and its in and response parameters) will often duplicate what the existing
> JavaDocs have already documented.
> WADLGenerator needs to do the best effort in trying to incorporate JavaDocs
> into the generated document.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
