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
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
Ted Husted wrote:
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.
You mean like JUEL?
The key point is that we don't have to demonstrate all the flexibility
in the examples that we post at the site. People who don't know what
choices to make, will look at our examples, and just follow those.
As to the examples we post, I would like to pick a stack that we can
all support, and use
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
