# jsr310

JSR 310 is a Java date and time API providing classes and functionality for representing and manipulating dates, times, durations, formatting, parsing, and calendar systems.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Microsoft's Canada Timezone Troubles Leave Admins Fixing Calendars, Pretending They're In Bogota

DevFeed: [Microsoft's Canada Timezone Troubles Leave Admins Fixing Calendars, Pretending They're In Bogota](<https://devfeed.tech/articles/microsoft-s-canada-timezone-troubles-leave-admins-fixing-calendars-pretending-they-re-in-bogota-112566.md>)

Original publisher: [Read original article](<https://news.slashdot.org/story/26/11/02/1538237/microsofts-canada-timezone-troubles-leave-admins-fixing-calendars-pretending-theyre-in-bogota>)

Author: BeauHD

Published: 2026-11-02T18:00:00Z

Content type: news

Language: en

Sources: [Slashdot](<https://devfeed.tech/sources/slashdot.md>)

Topics: [microsoft 365](<https://devfeed.tech/topics/microsoft-365.md>), [jsr310](<https://devfeed.tech/topics/jsr310.md>)

Tags: [calendar](<https://devfeed.tech/tags/calendar.md>), [canada](<https://devfeed.tech/tags/canada.md>), [exchange-online](<https://devfeed.tech/tags/exchange-online.md>), [fabric](<https://devfeed.tech/tags/fabric.md>), [meetings](<https://devfeed.tech/tags/meetings.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [outlook](<https://devfeed.tech/tags/outlook.md>), [power-automate](<https://devfeed.tech/tags/power-automate.md>), [powershell](<https://devfeed.tech/tags/powershell.md>), [schedules](<https://devfeed.tech/tags/schedules.md>), [sharepoint](<https://devfeed.tech/tags/sharepoint.md>), [time-zones](<https://devfeed.tech/tags/time-zones.md>), [timezone](<https://devfeed.tech/tags/timezone.md>)

### AI overview

After parts of Canada stopped changing clocks on November 1, Microsoft reported time-zone problems across several products. Outlook users must change their calendar time zone and update upcoming events; only meeting organizers can change meetings involving others. Changing the zone resets previously moved occurrences in recurring meetings, which must be recreated. Microsoft said a PowerShell cmdlet for non-recurring meetings was expected later that week; its recurring-meeting fix was still in development with no ETA. Temporary Power Automate and Fabric workarounds use other locations, varying by product and province. SharePoint On-Prem was slated to receive the correct zones November 10, while a Power Pages service fix for dates displayed an hour off had a December 12 milestone.

### Source excerpt

Microsoft is scrambling to fix time-zone problems across Outlook, Power Automate, Fabric, SharePoint and other products after parts of Canada stopped observing seasonal clock changes on November 1. "The company has confirmed problems across a chunk of its software estate, leaving some customers facing incorrect times, broken schedules and a collection of workarounds while Redmond catches up," reports The Register. From the report: Outlook users have been left with the most homework. Switching to the new Canadian time zones won't automatically update existing calendar entries, meaning that meetings scheduled after November 1 are potentially an hour out of whack. Microsoft advises users to change their Outlook calendar time zone, then update upcoming events and meetings to use it. For meetings involving other people, only the organizer can make the change. Recurring meetings come with an additional treat: changing the time zone resets any previously moved occurrences, which then have to be recreated. Anyone with a calendar full of recurring meetings may wish to put the kettle on first. Microsoft is working on an Exchange Online PowerShell cmdlet to remediate non-recurring meetings, but according to its guidance, that's not due until later this week. A fix for recurring meetings remains "in development," with an ETA yet to be confirmed. Things get stranger with Power Automate and Fabric, where Microsoft's temporary fix involves pretending you're somewhere else entirely. Depending on the product and province, that could mean Saskatchewan, Arizona or, for Manitobans, Bogota. Because apparently time zones weren't confusing enough already. SharePoint On-Prem customers, meanwhile, have to wait until November 10 for the correct time zones to arrive, while Power Pages users could see server-formatted dates appear an hour out until a service fix lands. Microsoft's current milestone for that is December 12. Read more of this story at Slashdot.

## Java Time (JSR-310) enhancements in Java SE 9

DevFeed: [Java Time (JSR-310) enhancements in Java SE 9](<https://devfeed.tech/articles/java-time-jsr-310-enhancements-in-java-se-9-21993.md>)

Original publisher: [Read original article](<http://blog.joda.org/2017/02/java-time-jsr-310-enhancements-java-9.html>)

Author: Stephen Colebourne (noreply@blogger.com)

Published: 2017-02-07T14:47:00Z

Content type: article

Language: en

Sources: [Stephen Colebourne](<https://devfeed.tech/sources/stephen-colebourne.md>)

Topics: [jsr310](<https://devfeed.tech/topics/jsr310.md>)

Tags: [added](<https://devfeed.tech/tags/added.md>), [api](<https://devfeed.tech/tags/api.md>), [clock](<https://devfeed.tech/tags/clock.md>), [conversion](<https://devfeed.tech/tags/conversion.md>), [days](<https://devfeed.tech/tags/days.md>), [enhancement](<https://devfeed.tech/tags/enhancement.md>), [instant](<https://devfeed.tech/tags/instant.md>), [java](<https://devfeed.tech/tags/java.md>), [java-se](<https://devfeed.tech/tags/java-se.md>), [java9](<https://devfeed.tech/tags/java9.md>), [jdk](<https://devfeed.tech/tags/jdk.md>), [jsr310](<https://devfeed.tech/tags/jsr310.md>), [localdate](<https://devfeed.tech/tags/localdate.md>), [minutes](<https://devfeed.tech/tags/minutes.md>), [optimize](<https://devfeed.tech/tags/optimize.md>), [optimized](<https://devfeed.tech/tags/optimized.md>), [performance](<https://devfeed.tech/tags/performance.md>), [precision](<https://devfeed.tech/tags/precision.md>), [returning](<https://devfeed.tech/tags/returning.md>), [stream](<https://devfeed.tech/tags/stream.md>), [time](<https://devfeed.tech/tags/time.md>), [use-cases](<https://devfeed.tech/tags/use-cases.md>)

### AI overview

Java SE 9's java.time updates add date streaming, duration operations, and more direct conversions to epoch seconds. Clock.systemUTC() gains precision according to the operating system clock; Clock.tickMillis(ZoneId) preserves Java SE 8-style millisecond ticks when needed. DateTimeFormatter gains modified Julian day and generic time-zone patterns, supports more offset forms, and improves adjacent-value parsing. The excerpt also describes performance optimizations for clocks, zone lookups, and LocalDate.plusDays. It identifies these as selected enhancements among 117 targeted issues, many of which were Javadoc fixes.

### Source excerpt

The java.time.* API (JSR-310) was added to Java SE 8, but what has been going on since then? Java Time in Java SE 9 There are currently 117 java time issues targetted into Java SE 9. Most of these are not especially interesting, with a lot of mistakes in the Javadoc that needed fixing. What follows are some of the interesting ones: Main enhancements: JDK-8146218 - Add LocalDate.datesUntil method producing Stream. Adds two new methods - LocalDate.datesUntil(LocalDate) and LocalDate.datesUntil(LocalDate,Period) - returning a stream of dates. JDK-8068730 - Increase precision of Clock.systemUTC(). The clock in Java - System.currentTimeMillis() - has ticked in milliseconds since Java was first released. With Java SE 9, users of Clock will see higher precision, depending on the available clock of the operating system. JDK-8071919 - Clock.tickMillis(ZoneId zone) method. With the system clock now returning higher precision, a new method was added - Clock.tickMillis(ZoneId) - that chops off the extra precision to restrore the millisecond ticking behaviour of Java SE 8. JDK-8030864 - Add efficient getDateTimeMillis method to java.time. This adds two methods named epochSecond to Chronology that have no object creation to convert date-time fields to an epoch-second. JDK-8142936 - Duration methods for days, hours, minutes, seconds, etc. The Java SE 8 API of Duration turned out to be incomplete for certain use cases. This change adds a slew of new methods that allow parts of the duration to be reliably returned. JDK-8148849 - Truncating Duration. Adds a method Duration.truncatedTo(TemporalUnit) to allow truncation, similar to the existing method on Instant. JDK-8032510 - Add Duration.dividedBy(Duration). A new method to allow a duration to be divided by another duration. JDK-8133079 - LocalDate and LocalTime ofInstant() factory methods. Add new factory methods in LocalDate and LocalTime to simplify conversion from Instant. JDK-8143413 - Add toEpochSecond methods for efficient acc