I'm evaluating to migrate my project from the usage of Joda-Time to the java.time package in Java 8. In Joda-Time, I heavily used the Interval class. I could not find anything like this in java.time.
Is there a comparable class?
Add a comment |
4 Answers
Sorry for you, there is no equivalent in JSR-310 to JodaTime-Interval-class. I have doubts if this will ever come, but project lead Stephen Colebourne considers at least to support it in the scope of his external library Threeten-Extra, see this issue.
If you are happy with JodaTime you should keep it. Not everything in JodaTime is ported to Java 8 (Interval is not the only issue).
Update from 2014-12-13:
The situation in Java-8 has not changed, but you might also consider other external libraries beyond Joda-Time. Either Threeten-Extra which now includes a very simple interval class since v0.9 (see the other answer of S. Colebourne here) or my library Time4J which offers the range package since v2.0.
7 Comments
Alexander Myltsev
What are other differences between joda.time and java8.time? Is there a comparison article somewhere?
Meno Hochschild
@AlexanderMyltsev There are many! Once I had given a (very short and out-dated) comparison on my blog in German. If I have time I should write a new one ;-). The technical base of JSR-310 is surely more modern (for example using enums) and the internal implementation details are healthier causing a better performance characteristics. On the other side JSR-310 was and will be never intended to be a complete time library (well, Joda-Time is also by far not complete but offers some more features like intervals, period formatters etc.). An exception are localized weekday nums, better in JSR-310.
Meno Hochschild
@wullxz The class
Duration (and Period, too) is not anchored on a given timeline, that means has no defined start time, just a length. In contrast, an interval always has a start and an end time.Meno Hochschild
@john16384 If you look at my interval implementations mentioned above then you will see that there is much more stuff to explore. For example special interval comparison relationships or specialized formatting capabilities or infinite boundaries or open/closed boundaries or other types like date ranges. Considering all these aspects, the Joda-solution is pretty small, the same valid for Threeten-Extra (rather weak in terms of count of features). Guava range sets and Time4J are much better here.
|
JDK 8 JSR-310 does not have an Interval class. The concept of intervals was descoped to ensure that the rest of the library could be completed.
The ThreeTen-Extra project hosts additional non-JDK date-time classes, and v0.9 includes Interval.
Note: Answer updated 2014-12-10 to include presence of Interval in ThreeTen-Extra.
2 Comments
YoYo
As you state 'could be completed', is that for consideration of time, or for other considerations? I think that the introduction of an
Interval could be confusing, ambiguous, and dangerous. Dangerous because an Interval is still within the frame of the exact dates (it has an end-date and begin-date), which is something that could be easily missed? I think that the omission of Interval made it a cleaner implementation? Period and Duration are to me alternatives without the drama.
JodaStephen
'completed' as in finished in time for Java 8 release date. Interval will not be added in Java 9 either. Really the JDK needs a proper range concept.
Use Range class from Guava.
See https://stackoverflow.com/a/23485533/1214902 for more details.
Comments
Class java.time.Duration may give you similar functionality. In general java 8 time package is very comprehensive and flexible
1 Comment
rve
Duration does not have a begin/end time. Interval does.