Currently I am using the tiles, bean, html, and logic taglibs, and am about to start using nested. If these will eventually be phased out then I am very happy to move to other taglibs. It would be very nice if there was some kind of documentation on how the current libraries match with the alternatives: e.g. which struts tags are replaceable with current JSTL tags and which are not. This would help me and others like me, in making the transition early and avoiding the pain of more major work later by replacing as many tag uses as possible now.
Any comments? Alan Craig R. McClanahan writes: > > * For my own efforts, I'm going to de-emphasize improvements > and enhancements to the Struts tag libraries at all, and > encourage people to use the standardized successors (JSTL > now, and JSF when it's done). We should definitely do bugfixes > on the existing libraries after 1.1, but I don't see a good > reason to invest the necessary effort to disconnect > them when standarized (as well as more powerful) solutions > exist. Other committers might see this differently, of course. > > * There is very little code in RequestUtils that is not > Struts-specific, so it wouldn't make a particularly good > candidate for commons. You might recall that several > Commons packages did originally come from Struts (beanutils, > digester, resources, validator), so the factoring of what was > horizontally reusable is, IMHO, pretty much done. > > We're also, of course, incorporating commons packages that were > originated by others but are useful to us (collections, dbcp/pool, > fileupload, logging) as well, rather than reinventing those wheels. > > My personal efforts on the future of Struts are going to be focused on > enhancing the fundamental architecture of the controller, and looking at > things like hierarchical modules, more general command patterns for > Actions, scriptable multi-request dialogs, and things like that. > > > Craig -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
