TimeSpanMap has a dual view for its content:
The underlying storage is based on ordered elements in a
TreeSet (hence guaranteed
log(n) query time) and a chronological comparator.
As spans may have two limit dates, both can be null and all dates are duplicated
as the end and start dates of neighboring spans, what is stored in the
are really the
Transitions, not the
Spans. A side effect is that a
with only one valid entry has a single dummy transition that is not meaningful and
is replaced as soon as a real transition is added.
This dummy transition leaks from the API when calling
As the API implemented as part of issue #883 (closed) adds links that help global navigation
in both directions, for both
Transition views and also allows to go
from time spans to transitions and back,
map.getTransitions() is obsolete and
error prone due to the single dummy transition. This method should be deprecated.