I think there's still a lot of ground to cover with Struts-specific tags
that leverage the ActionMappings and other Struts application resources.
Right now, these would be the HTML tags plus logic:forward and
logic:redirect. (Which I personally think should be in HTML anyway,
since they are HTTPD concepts.) At some point, the bean, logic, and
template taglibs should find their way to Jakarta Taglibs, the way
BeanUtils is wandering over to the Commons, which Craig has mentioned
many times.
But the principle would still hold, regardless of where the logic, bean,
and template tags are kept. We might want to keep a lid on the core tags
included with each, and put others into a logic-ext, bean-ext, et
cetera.
Martin Cooper wrote:
>
> We would want to think carefully about including custom tags in such an
> extension scheme. For tags that are truly Struts-specific, this might be
> reasonable. However, even some of the Struts tags are no longer
> Struts-specific, since they are now based on Commons code.
>
> For non-Struts-specific tags, we might want to encourage people to amble on
> over to our neighbour, the Jakarta taglibs project, rather than add them as
> Struts extensions.
