On Thu, Jan 16, 2014 at 3:12 AM, Henri Yandell <flame...@gmail.com> wrote: > +1 to that vision. > > I'll ditch the current Extended code. > <snip/>
Yup. I agree to below as well. -Rahul > Hen > > > On Tue, Jan 14, 2014 at 8:47 AM, Jeremy Boynes <jboy...@apache.org> wrote: > >> On Jan 13, 2014, at 9:51 PM, Henri Yandell <flame...@gmail.com> wrote: >> >> > Any thoughts Jeremy on our containing tags outside of the Standard >> > implementation? >> > >> > I was pondering folding the Extended one (which contains two very tiny >> > tags) into the Standard taglib, or if you don't see any likelihood for >> > adding new ones, just removing it. >> >> If anything, I think I would rather go in the other direction, breaking >> Standard down into individual taglibs. I think there are a number of users >> who primarily rely only on core & fn in their applications, using other >> libraries for the functionality in fmt, sql, and xml. It would be nice to >> be able to consume them that way. Splitting them up would also allow >> specific libraries to be optimized through tag plugins or by Jasper itself. >> >> Those other libraries have also not really kept up with the times. For >> example, fmt is heavily coupled to native Java L10N which I think still >> lags behind icu4j and hasn’t added basics like named placeholders, sql has >> been superseded by frameworks like JPA but even the basic JDBC support >> could take advantage of “new" things like @Resource injection, and we’ve >> added a hard dependency on Xalan to address xml performance and the spec >> still hasn’t touched new features like XPath 2 or XQuery. >> >> “Extended” is a vague name so I would be in favor of just dropping it and >> replacing it with more specific libraries e.g. localization, xpath, json or >> whatever we decide to work on. >> >> Cheers >> Jeremy >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
