> Thanks! By the way, DateFormats not being thread-safe is a huge WTF. IMHO the whole Date, Calendar and DateFormat stuff are not really usable (or at least are REALLY error prone). What do you think about implementing first class support for joda-time [1] in tapestry?
Cons: * That would introduce a new dependency on the joda-time library Pros: * provide and easy and proper way to handle time related data to every tapestry user * provide advanced integration with the hibernate ORM framework [3] * be a little ahead of times as the next java time spec is largely based on the joda experience [4] (Will it ever see the light?!) * spring already supports joda (Have a look at [5], but also their validation framework and spring-data-jpa use/support joda) BTW it is true that it is not so difficult to plug joda into your T5 app (and Jumpstart already has an example integration [2]) [1] http://joda-time.sourceforge.net/ [2] http://jumpstart.doublenegative.com.au/jumpstart/examples/jodatime/1 [3] http://usertype.sourceforge.net/ [4] http://jcp.org/en/jsr/detail?id=310 [5] http://static.springsource.org/spring/docs/3.0.x/javadoc-api/index.html?org/springframework/format/datetime/joda/package-summary.html --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
