Even though I argued for it initially, I'm still not 100% sure we want to pull out the tags. Not only is it more confusing to users, but it makes tag extension harder, since plugins can't provide plugin points to other plugins. That means we'd have to keep the majority of the tag infrastructure in core, which gains us little, IMO.
One reason to pull them out is it better facilitates new EL's. With how the tags work right now, they depend on the OGNL EL from a syntax perspective mostly as the API dependency has been abstracted. If you created a JUEL plugin, for example, you'd probably want to rewrite most of the tags to better take advantage of deferred expressions. Anyways, I'm not saying there aren't solutions, just that we need to think about it some more. At this point, I'm not sure the potential cost outweights the benefits. Don On 11/5/07, Ted Husted <[EMAIL PROTECTED]> wrote: > On Nov 4, 2007 9:33 AM, Tom Schneider <[EMAIL PROTECTED]> wrote: > > Speaking of the core taglib, what ARE we going to do with it. There's > > been talk of moving them to a separate plugin, reimplementing them in a > > java, etc. It would be nice to know from a roadmap prespective about > > where the core taglib is headed--I have several plugins that would be > > affected by it. > > My understanding is that we would like to move the existing tags to a > plugin, and create a standard bundle that would include the > tag-plugin, the code-behind plugin, and the core as a single JAR. > > The code-behind plugin will subsume the zero-config and annotations > code, as well as the SmartURls plugin. > > * [s2] Should tags be their own plugin? > * [S2] Plugins gone wild! > > One place to document decisions like this is the STATUS.txt file under SVN. > > * http://svn.apache.org/viewvc/struts/current/STATUS.txt?view=markup > > In terms of the longer-term roadmap, work is being done on a JSP 2 > taglib that won't use the templating system at all. > > Don's also been doing some preliminary refactoring in XWork so that > the expression language can be made pluggable, meaning we would also > be able to plugin something else instead of OGNL. > > -Ted. > > > > > At a minimum, if we're going to keep the ftl template at all, then I > > would recommend we bring in tabletags. (At least the paging and sorting > > tags) Looking at the downloads page for tabletags, there have been over > > 7000 downloads over the last year. That seems significant to me. The > > table tag itself probably needs a little TLC at the moment, but I think > > the other tags are pretty solid. I'm also open to looking at other tags > > that should be brought in--again this is contingent on what we decide to > > do with them pesky tags. > > Tom > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > HTH, Ted <http://www.husted.com/ted/blog/> > > --------------------------------------------------------------------- > 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]
