ntation for the JSTL, but I guess the best we can do is point them to
the PDF specification download.
> -Original Message-
> From: Ted Husted [mailto:husted@;apache.org]
> Sent: Friday, October 18, 2002 7:15 AM
> To: Struts Developers List
> Subject: Re: Suggestions for place
If you can put the high-level usuage documentation ("narrative") in a package.html for
each of the taglibs,
following the example of the other taglibs, I'll can sort out the mechanics of getting
the package description,
Javadoc, and API guide into the documentation/website (somehow).
I'm very
> "Ted" == Ted Husted <[EMAIL PROTECTED]> writes:
Ted> The API part is automatic. There's a stylesheet for the taglibs that lets Ant
do all the work. =:0)
Ted> The other part is the package.html file, which the JavaDoc automatically
bundles in as the "description" portion
Ted> o
The API part is automatic. There's a stylesheet for the taglibs that lets Ant do all
the work. =:0)
The other part is the package.html file, which the JavaDoc automatically bundles in as
the "description" portion
on the cover page for the package
So, for the narrative you mentioned, follow the
You probably want to start with a Developers Guide as we have for the other taglibs.
http://jakarta.apache.org/struts/userGuide/dev_bean.html
-T.
10/17/2002 7:55:15 PM, "Karr, David" <[EMAIL PROTECTED]> wrote:
>I'm planning on putting some information about Struts-EL into the user
>guide. I h
> "Ted" == Ted Husted <[EMAIL PROTECTED]> writes:
Ted> You probably want to start with a Developers Guide as we have for the other
taglibs.
Ted> http://jakarta.apache.org/struts/userGuide/dev_bean.html
Ah, of course. This is the documentation generated from the struts-*.xml
files.
