Haven't look into this much but it would seem better to have a completely separate tiles sub-project that struts core would use. Don't JSF and Spring currently use tiles and have to include struts.jar when all they really want is tiles?
> -----Original Message----- > From: Don Brown [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 21, 2004 7:51 PM > To: Struts Developers List > Subject: Extracting taglibs > > My basic assumption in approaching taglibs extraction into its own > subproject is it can reference Struts classes, but Struts classes > shouldn't reference it. > > If that is correct, here are the changes I see happening to extract > taglibs: > > 1. Move o.a.s.taglib out into its own subproject src tree > 2. Remove methods in RequestUtils that delegate to TagUtils. They are > marked as deprecated anyways and explicitly say they will be removed > after 1.2. > 3. Move properties in o.a.s.taglib.html.Constants that are referred to > in Struts core code into o.a.s.Globals. (cancel and token keys) > 4. Move o.a.s.taglib.tiles to o.a.s.tiles.taglib This one I'm not sure > about. Should/can tiles be used w/o its jsp taglibs? If not, then it > should stay in core w/ tiles. Otherwise, it could be moved out too. > > That should be it, as far as I can tell. taglibs are already pretty > well isolated from the rest of Struts which will make the extraction > pretty straightforward. > > I'd like to get this done before Christmas (25th) if there are no > objections. > > Don > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
