commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (JELLY-11) The Tag Reference should understand tags like JellySwing
Date Fri, 10 Sep 2004 05:54:43 GMT
The following comment has been added to this issue:

     Author: Hans Gilde
    Created: Thu, 9 Sep 2004 10:53 PM
Ok, I think this is important. I see two choices:

Each TagLib has its own package. That package has an XML file describing the tags. The JavaDoc
overlays this XML info with any info that it finds in individual class files. Thus, classes
are free to define themselves in terms of their bean properties but extra tags can be defined
in XML.

Or, we could add JavaDoc @tags to specify more than one tag in a Java file. This way, tags
like ComponentTag will define all its tags via something like @jellyTag.

Or, we could let each tag lib get introspected by the documentation tool and be allowed to
just specify all it's tags.

Maybe the tags are output first to XML and bundled with the tag lib JAR. The XML can later
be processed into HTML for a big doc of all libs.

Just throwing out all the crazy ideas first. I like 1 or 2, more likely 2.
View this comment:

View the issue:

Here is an overview of the issue:
        Key: JELLY-11
    Summary: The Tag Reference should understand tags like JellySwing
       Type: Improvement

     Status: Open
   Priority: Major

    Project: jelly
   Fix Fors:

   Assignee: james strachan
   Reporter: james strachan

    Created: Wed, 30 Oct 2002 6:00 AM
    Updated: Thu, 9 Sep 2004 10:53 PM

Right now only statically defined Tag implementations are detected with the doclet that makes
the Tag Reference for Jelly...

It would rock if we could instantiate each tag library and somehow introspect it to find its
attributes for the reference. 

e.g. the JellySwing tags typicaly map to a Swing component like JFrame, JTable and so on.
Then each tag supports each property on the underlying bean.

if we could represent this in the Tag Reference it would make them much easier to use!

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message