[dbdoclet] Re: upgrade dbdoclet to jdk 1.5

Hello Klaus,
> The dbdoclet port to Java 1.5 seems to be insidpensable to me.
> http://java.sun.com/j2se/1.5.0/docs/guide/javadoc/doclet/transition-1.5docletapi.html
> says how.
> Annotations will become more and more importand, and so will their
> JavaDoc documentation.
> See for example MMBI http://jsesoft-mmbi.sourceforge.net (a little
> tool of mine which
> instruments arbitrary objects as JMX ModelMBeans).
>
> On the other hand, it's not only Java that changes regularly: it is
> DocBook as well.
> And other formats are around (e.g. maven's xdoc, see
> http://maven.apache.org )
> In my opinion, it would be nice to have a JavaDocInspector, which
> traverses the
> JavaDoc of a class with the help of the DocLet API and calls
> respective handler
> functions for all JavaDoc elements (ClassDoc, MethodDoc, ConstructorDoc,
> ParamTag, ...) encountered. By the help of subclassing, attaching a
> strategy, or
> even plug-in (see http://jpf.sourceforge.net) these handler functions
> can be customized
> for producing different DocBook for different situationa, or even
> other XML or
> non-XML formats. The above mentioned MMBI project does similar things
> (provides a ReflectionInspector which traverses the reflection tree
> and calls respective
> handler functions for all class members found, attaches a strategy
> which generates
> JMX ModelMbean information which is customizable by annotations). And it
> works nice.
my idea is to use DocBook itself for that purpose. If you create DocBook
XML using the dbdoclet strict style,
you can use the resulting DocBook XML as source for your own XSLT
transformation. It should be possible to
create your destination format from the given information. If not, I
should improve the quality of the generated
DocBook XML :-). Some weeks ago I had the idea to use an internal XML
format with XSLT to control
the generation of different DocBook flavours, but I ended up in
implementing a second DocBook XML. Perhaps
I was doing something wrong, but I think DocBook XML is already an
excellent source for custom transformations.

If you need a JavaDocInspector nevertheless, you can create your own
style class. Have a look at the Style*.java classes
in the package org.dbdoclet.doclet.docbook.

Regards
Michael
-- 
-------------------------------------
Dipl.-Ing. (FH) Michael Fuchs
Phone: 0 81 61/ 14 41 66
Fax: 0 81 61/ 14 05 21
E-Mail: michael.fuchs@xxxxxxxxxxxxxxx
Homepage: http://www.dbdoclet.org

Other related posts: