"Craig R. McClanahan" wrote: > What about the stuff that's shared across multiple taglibs > (org.apache.struts.util.*, org.apache.struts.action.*, and so on)? I > haven't checked them all, but I'd be surprised if *any* of the tag > libraries can stand on their own without needing the proposed > struts-core.jar anyway. > > IMHO, having more smaller pieces makes life harder, not easier -- it's one > of the few negatives for using commons-*.jar instead of the old stuff that > was all right there waiting for you in struts.jar.
True, but I think it's important that we start paving the way for a future where there are several different presentation devices -- JSTL, JavaServer Faces, Velocity templates, the Struts taglibs -- which all have equal access to the framework components. Personally, I still think it would be worthwhile to try and break the build into a struts-core.jar and a struts-taglibs.jar, as the first step of a refactoring. The struts-taglibs.jar may retain a dependency on the struts-core.jar, and maybe that will never go away. But as we work on a migration path for the JSTL, and expand on our support for other devices, like Velocity Templates, it seems helpful to me to start thinking of the taglibs as one of several presentation options supported by Struts. -- Ted Husted, Husted dot Com, Fairport NY USA. -- Building Java web applications with Struts. -- Tel +1 585 737-3463. -- Web http://www.husted.com/struts/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
