Craig,
What are your thoughts about morphing the current XML/XSL scheme of
generating TLD's to XDoclet's struts-config and taglib capability?
Centralizing all the TLD information into the actual source code of each tag
could avoid a lot of potential mismatch issues. It would take some work,
but I think it would be possible, to create new XDoclet's that could
generate the documentation for the tags as well as the TLD's themselves.
Thanks,
Erik
----- Original Message -----
From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: "Martin Gee" <[EMAIL PROTECTED]>
Sent: Wednesday, October 17, 2001 8:14 PM
Subject: Re: Generating doc/*.xml files from javadocs
...
> The XML files are themselves the source files. However, they are used to
> generate two different kinds of things:
>
> * The "struts-*.xml" files are used to generate BOTH the TLD files
> that you include in your application AND the "Tag Library Reference"
> pages in the struts-documentation webapp (HTML format).
>
> * The remaining XML files are used to generate the rest of the
> struts-documentation stuff only (HTML format).
>
> In the former case, this magic comes courtesy of using two different XSLT
> stylesheets that take the same input, but generate different output.
>
> You can look at the Ant build script (build.xml) for how this is done in
> Struts. The Jakarta Taglibs project <http://jakarta.apache.org/taglibs>
> has a similar-but-different approach that accomplishes the same thing, but
> again starts from XML files as the source, not the destination.
