Files
sailing-analytics/java/com.sap.sailing.server.gateway.interfaces
Axel Uhl 641a3f4258 bug6288: use TimePoint instead of long millis in LiveContentCheckResult and SailingServer.getLiveContent
Change SailingServer.getLiveContent(long) to accept a TimePoint and refactor
LiveContentCheckResult to hold a TimePoint (checkedAt) rather than a long
(checkedAtMillis), matching how TimePoint is used elsewhere in the
SailingService[Write] API. Also adds Javadoc to getLiveContent.

Serialization:
- GWT RPC now writes/reads the TimePoint as an object (TimePoint is
  GWT-serializable and already used across the RPC boundary).
- JSON keeps the long millisecond value (or null) on the wire under the
  unchanged checkedAtMillis key; the deserializer wraps it back into a
  TimePoint via TimePoint.of(...).

Regenerated serialVersionUID for the changed field layout of
LiveContentCheckResult.

Assisted-By: Claude (claude-4.8-opus)
2026-09-14 23:30:19 +02:00
..