Pulling in an old thread :) I think datetime taglib should be deprecated. I don't think it is interesting enough on top of JSTL to keep alive.
Hen On Mon, Jul 23, 2007 at 2:44 PM, Henri Yandell <flame...@gmail.com> wrote: > Here are the tags in the DateTime taglib: > > * currentTime Gets the current time in milliseconds since Jan 1, 1970 > GMT. > * format Formats a date in milliseconds since Jan 1, 1970 GMT for > output as a date string. > * parse Parses a date string and outputs the time in milliseconds > since Jan 1, 1970 GMT. > * timeZone Create a time zone script variable for use with the parse > or format tags. > > * timeZones Loop through all time zones. > * months Loop through the months of the year. > * weekdays Loop through the days of the week. > * amPms Loop through the am/pm names. > * eras Loop through the era names. > > ----- > > Of the first batch; format and parse are taken of care of in JSTL with > fmt:formatDate and fmt:parseDate. The currentTime tag is effectively > handled by doing: > > <jsp:useBean id="now" class="java.util.Date" /> > > I'm never sure whether it's better to educate people in doing such > things, or if there should be a: > > <un:currentTime var="now"/> > > Probably it's best to just push towards useBean. Also, the timeZone > attribute to the two fmt: tags can take a String as well as an Object, > so presumably that makes that one redundant. > > So the question becomes whether there is any value in the iterator > style tags. I don't see a lot. Any thoughts? I'm tempted to think > 'deprecate' for datetime and bring nothing into Unstandard. > > Hen > --------------------------------------------------------------------- To unsubscribe, e-mail: taglibs-dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: taglibs-dev-h...@jakarta.apache.org