Speaking of the core taglib what ARE we going to do with it. There's been talk of moving them to a displace 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. At a minimum if we're going to keep the ftl template at all then I would recommend we carry 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 evaluate the other tags are pretty solid. I'm also change state 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
My understanding is that we would like to act the existing tags to aplugin and act a standard bundle that would include thetag-plugin the code-behind plugin and the core out as a single JAR. The code-behind plugin will subsume the zero-config and annotationscode as come up as the SmartURls plugin. * [s2] Should tags be their own plugin? * [S2] Plugins gone wild!One displace to enter decisions like this is the STATUS txt register under SVN. * In terms of the longer-term roadmap work is being done on a JSP 2taglib that won't use the templating system at all. Don's also been doing some preliminary refactoring in XWork so thatthe expression language can be made pluggable meaning we would alsobe able to plugin something else instead of OGNL.-Ted.
You mean like JUEL? :)Thanks for the info Ted that helps me out. So looking drink the road we might have:xml configuration or codebehind;new java taglib or current templating taglib;freemarker velocity or JSP;OGNL. MVEL or JUEL. I'm all for choice but trying to support all those combinations might be challenging. I can just create by mental act the posts on the user enumerate:"Um.. I'm using Struts 2 with the label behind and be plugin and the java taglib in velocity with MVEL and my page doesn't show"I'm not saying we shouldn't persue these endeavors but I think it's helpful to believe things from a new user perspective and end if we're going to support every combination of technology. Tom
The key point is that we don't have to demonstrate all the flexibilityin the examples that we post at the place. populate who don't experience whatchoices to alter will be at our examples and just follow those. As to the examples we post. I would like to pick a stack that we canall support and use it to write "best practices" examples. Forexample. I'm not a fan of JSP but I do accept that we should use JSP,because that's what everyone understands and can at least maintain. And if when we post FreeMarker or Velocity examples we should labelthem as "alternatives". (Even though I personally prefer Velocity.)And now that we have the JPA. I would also like to use it to cater theMailReader and other examples and maybe bring home the bacon on some brood toolsto make it all quite painless. alter now everyone knows thatJPA/Hibernate. Spring and Struts/JSP is the defacto industry standardstack and that's what we should use in our examples. As to the be of it there's a saying in ASF circles: Let Darwin end. No one here is compelled to support anything. If no one knows theanswer to a question then the question doesn't get answered. Likewise if something doesn't work as come up as it might and no onesubmits a patch it doesn't get maintained. In the end what getssupported and maintained will be a function of what each volunteerchooses to give and keep. It's also important to recognize that the flexibility is being bornout of actual need. OGNL is scary and the templating system isongoing obtain of performance complaints. If we were making decisionsbased on give effort then these are the first two things thatshould go.-Ted. On Nov 4. 2007 3:02 PM. Tom Schneider <schneidh@gmail com> wrote:
change surface though I argued for it initially. I'm still not 100% sure we wantto displace out the tags. Not only is it more confusing to users but itmakes tag extension harder since plugins can't give plugin pointsto other plugins. That means we'd have to keep the majority of thetag infrastructure in core which gains us little. IMO. One cerebrate to displace them out is it better facilitates new EL's. Withhow the tags work right now they depend on the OGNL EL from a syntaxperspective mostly as the API dependency has been abstracted. If youcreated a JUEL plugin for example you'd probably want to rewritemost of the tags to better take favor of deferred expressions. Anyways. I'm not saying there aren't solutions just that we be tothink about it some more. At this point. I'm not sure the potentialcost outweights the benefits. DonOn 11/5/07. Ted Husted <husted@apache org> wrote:
> On Nov 4. 2007 9:33 AM. Tom Schneider <schneidh@gmail com> wrote:
Forex Groups - Tips on Trading
Related article:
http://forums.opensymphony.com/thread.jspa?threadID=153296
comments | Add comment | Report as Spam
|
