If you have a DateTime object which represents a value in the month, then it’s pretty straightforward. You get the dayOfMonth property from that DateTime object and get the maximum value of the property. Here is a sample function: public static int daysOfMonth(int year, int month) { DateTime dateTime = new DateTime(year, month, 14, 12, … Read more
I also ran into this problem. Jon Skeet’s suspicions were correct, the problem is that the time zones are being loaded really inefficiently, opening a jar file and then reading the manifest to try to get this information. However, simply calling DateTimeZone.setProvider([custom provider instance …]) is not sufficient because, for reasons that don’t make sense … Read more
You need to normalize the period because if you construct it with the total number of seconds, then that’s the only value it has. Normalizing it will break it down into the total number of days, minutes, seconds, etc. Edit by ripper234 – Adding a TL;DR version: PeriodFormat.getDefault().print(period) For example: public static void main(String[] args) … Read more
I’ve had almost entirely positive experiences with Joda Time. My one problem was when trying to construct my own time zone (for legitimate reasons, I assure you 🙂 I got some very weird exceptions, and the documentation wasn’t very good for that particular use case. However, for the most part it’s been a joy to … Read more
You can use class LocalDateTime LocalDateTime dt = new LocalDateTime(t.getTime()); and convert LocalDateTime to DateTime DateTime dt = new LocalDateTime(timestamp.getTime()).toDateTime(DateTimeZone.UTC); Joda DateTime treats any time in millis like “millis since 1970y in current time zone”. So, when you create DateTime instance, it is created with current time zone.
Joda-Time uses the ISO standard Monday to Sunday week. It does not have the ability to obtain the first day of week, nor to return the day of week index based on any day other than the standard Monday. Finally, weeks are always calculated wrt ISO rules.
A distinct paucity of documentation, means it might be helpful for me to write down the steps required for integration. Make sure your libraries are up to date. You’ll need : [assuming you already have hibernate4] Latest version of joda-time <dependency> <groupId>joda-time</groupId> <artifactId>joda-time</artifactId> <version>2.0</version> </dependency> and usertype lib <dependency> <groupId>org.jadira.usertype</groupId> <artifactId>usertype.core</artifactId> <version>3.0.0.CR1</version> </dependency> Then use … Read more
JodaTime To convert JodaTime’s org.joda.time.LocalDate to java.util.Date, do Date date = localDate.toDateTimeAtStartOfDay().toDate(); To convert JodaTime’s org.joda.time.LocalDateTime to java.util.Date, do Date date = localDateTime.toDate(); JavaTime To convert Java8’s java.time.LocalDate to java.util.Date, do Date date = Date.from(localDate.atStartOfDay().atZone(ZoneId.systemDefault()).toInstant()); To convert Java8’s java.time.LocalDateTime to java.util.Date, do Date date = Date.from(localDateTime.atZone(ZoneId.systemDefault()).toInstant()); You might be tempted to shorten it with LocalDateTime#toInstant(ZoneOffset), … Read more
Yes, it is: DateTimeFormat is thread-safe and immutable, and the formatters it returns are as well. and so is the Java 8 version Implementation Requirements: This class is immutable and thread-safe.
You can convert a Joda DateTime to a long (millis since the epoch) first, and then create a Timestamp from that. DateTime dateTime = new DateTime(); Timestamp timeStamp = new Timestamp(dateTime.getMillis());