The argument is sound but, [hypothetically, have not looked really...]
one *may* still be able to split the taglib into a generic part and some
other part that is more tied to the framework.
- eduard/o
Ted Husted wrote:
>
> Morgan Delagrange wrote:
> > Right now, I'm inclined to create a new tag library in
> > Taglibs that mimics portions of the Struts tags. I
> > think the duplication is justifiable. Ideally this
> > would not be necessary, but I think that the Struts
> > tags are just too, well, Struts-ish for developers who
> > are not working inside that framework. (This is not a
> > criticism, just an observation!) And of course, any
> > new approaches we develop in scopes (e.g. I don't see
> > any init parameter support in the Struts tags) can be
> > picked up by Struts too.
>
> That seems like a sensible approach, Morgan. Here's a clip from a Struts
> FAQ I'm drafting.
>
> "Why aren't the Struts tags maintained as part of the Jakarta Taglibs
> project?
>
> "A few of the Struts tags could be maintained outside of the framework,
> but most accept parameters that are in someway tied to the rest of
> Struts, especially references to the Controller's action mappings. This
> is an important feature, since it allows the view to be developed using
> logical forwards, which could be maintained by another team. Ironically,
> for the view to be "loosely coupled" to the Controller, most of the view
> tags need to be tightly coupled to the framework."
>
> -- Ted Husted, Husted dot Com, Fairport NY USA.
> -- Custom Software ~ Technical Services.
> -- Tel 716 737-3463.
> -- http://www.husted.com/about/struts/
