[
https://issues.apache.org/jira/browse/CXF-5479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13958667#comment-13958667
]
Sergey Beryozkin commented on CXF-5479:
---------------------------------------
Hi Freeman
I guess we are talking about using Doclet API, see a link to it from here:
http://stackoverflow.com/questions/13024881/how-to-extract-javadoc-comments-from-the-source-files
So when generating WADL with the plugin we should be able to register a
DocumentationProvider that can utilize Doclet API.
IMHO EclipseJDT is not what we need, the existing JavaDocs provider that we
ship more or less does the same thing I guess, it parses HTML and attempts to
make it portable across different Java versions.
I think it is not the right way to follow. Perhaps we can split the process, I
don't know, get this plugin run in two phases, one will accumulate JavaDocs
only and will build some internal map (example: ClassA - JavaDocs for ClassA,
etc), save it to some temp file if needed to get it persisted and then when
building the actual WADL it will have DocumentationProvider that will use the
earlier created map to map JavaDocs pieces to WADL docs...
Cheers, Sergey
> Create a Maven plugin for generating WADL at build time
> -------------------------------------------------------
>
> Key: CXF-5479
> URL: https://issues.apache.org/jira/browse/CXF-5479
> Project: CXF
> Issue Type: New Feature
> Components: JAX-RS
> Reporter: Sergey Beryozkin
> Assignee: Freeman Fang
> Attachments: CXF-5479.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
