Re: Extracting taglibs

You can indeed use Velocity+Tiles: http://jakarta.apache.org/velocity/tools/javadoc/org/apache/velocity/tools/struts/TilesTool.html Also, while ya'll are pulling out the taglibs (hooray!!), i would like to just mention that there are some things in the TagUtils class that are useful to other view

Re: Extracting taglibs

On Tue, 21 Dec 2004 21:06:19 -0800, Craig McClanahan <[EMAIL PROTECTED]> wrote: > On Tue, 21 Dec 2004 20:45:03 -0800, Don Brown <[EMAIL PROTECTED]> wrote: > > > I agree as well. This lets us follow a consistent approach to > > subprojects, where they may (and probably should) link to Struts core,

Re: Extracting taglibs

:) Actually, in the extraction I performed so far, I did just that and moved TilesPreProcessor into the o.a.s.tiles.commands package. There was one other class, o.a.s.actions.RedeployableActionServlet that I moved into o.a.s.tiles since it was full of references to TilesRequestProcessor. Don

Re: Extracting taglibs

--- Don Brown <[EMAIL PROTECTED]> wrote: > FWIW, so far, I extracted tiles and taglib into their own projects, and > got both core and taglib compiling (haven't tried tiles yet). It took > the steps I described earlier as well as moving some methods from > TagUtils back into ResponseUtils. O

Re: Extracting taglibs

At 6:09 AM -0600 12/22/04, Vic wrote: Joe Germuska wrote: I do think that Struts shouldn't depend on subprojects. -1. core should not depdend on any subprojects I think. Not today, 1st day or repackaging but eventualy. I also think subprojects should be set up to depend on a struts.jar ... and n

Re: Extracting taglibs

Joe Germuska wrote: I do think that Struts shouldn't depend on subprojects. -1. core should not depdend on any subprojects I think. Not today, 1st day or repackaging but eventualy. I also think subprojects should be set up to depend on a struts.jar ... and not the code. -- RiA-SoA w/JDNC

Re: Extracting taglibs

At 10:24 PM -0800 12/21/04, Don Brown wrote: FWIW, so far, I extracted tiles and taglib into their own projects, and got both core and taglib compiling (haven't tried tiles yet). It took the steps I described earlier as well as moving some methods from TagUtils back into ResponseUtils. Of cours

Re: Extracting taglibs

FWIW, so far, I extracted tiles and taglib into their own projects, and got both core and taglib compiling (haven't tried tiles yet). It took the steps I described earlier as well as moving some methods from TagUtils back into ResponseUtils. Of course, if ResponseUtils has been dreprecated lo

Re: Extracting taglibs

This would be Tony the Tiger GRRREeattt! Jack On Tue, 21 Dec 2004 21:06:19 -0800, Craig McClanahan <[EMAIL PROTECTED]> wrote: > On Tue, 21 Dec 2004 20:45:03 -0800, Don Brown <[EMAIL PROTECTED]> wrote: > > > I agree as well. This lets us follow a consistent approach to > > subprojec

Re: Extracting taglibs

On Tue, 21 Dec 2004 20:45:03 -0800, Don Brown <[EMAIL PROTECTED]> wrote: > I agree as well. This lets us follow a consistent approach to > subprojects, where they may (and probably should) link to Struts core, > but Struts core should not depend on them. I hope this can actually be accomplished

Re: Extracting taglibs

Martin Cooper wrote: On Tue, 21 Dec 2004 20:25:55 -0800, Craig McClanahan <[EMAIL PROTECTED]> wrote: I think a separate subproject for Tiles (including the code and the tags) probably makes the most sense. +1 If we don't mind the dependency back onto Struts, then this could also include the Strut

Re: Extracting taglibs

I agree with making Tiles into its own Struts subproject including its taglibs. This would also make it easier if people wanted Tiles to be its own project again in the future. David --- Craig McClanahan <[EMAIL PROTECTED]> wrote: > I think a separate subproject for Tiles (including the code a

Re: Extracting taglibs

On Tue, 21 Dec 2004 20:25:55 -0800, Craig McClanahan <[EMAIL PROTECTED]> wrote: > I think a separate subproject for Tiles (including the code and the > tags) probably makes the most sense. +1 > If we don't mind the dependency > back onto Struts, then this could also include the Struts PlugIn that

Re: Extracting taglibs

I think a separate subproject for Tiles (including the code and the tags) probably makes the most sense. If we don't mind the dependency back onto Struts, then this could also include the Struts PlugIn that is currently used to configure it -- although it would probably be better that this class s

Re: Extracting taglibs

It has been discussed, I believe, to separate Tiles from Struts, but no one seemed to know where it would go. jakarta-commons doesn't want taglibs, and for some reason I don't remember, the taglibs project wasn't accepted. It would be kinda funny, though, since Tiles used to be its own projec

Re: Extracting taglibs

Actually, I'd tend to agree with that. It makes more sense than separating Tiles and the Tiles taglibs - don't think you'd use the former without the latter. Maybe ... but I don't. On Tue, 21 Dec 2004 20:35:53 -0500, Deadman, Hal <[EMAIL PROTECTED]> wrote: > Haven't look into this much but it w

RE: Extracting taglibs

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:[EMAI