Closed timothypratley closed 6 years ago
Thanks for the issue - I didn't realize that was buried in there. I wonder if there is any difference between this and clojure.instant/parse-timestamp
.
I think practically speaking, the answer is no, just this is in Java. :)
I'll take a look at this when I get a chance.
:) Thank you Alex @puredanger
Hi @puredanger,
I think you are correct that clojure.instant/parse-timestamp
can be used as a replacement; shall I make a pull-request to that effect?
Sorry, we don't take PRs on this project, but I will get to it.
Okidoki thank you :)
as a workaround during java
or jlink
you can --add-modules java.xml.bind
Hi, I am shamelessly checking in to see if you have time to address this... no big deal if not.
Added explicit dep to resolve this in transit-java 0.8.337 (also available via transit-clj 0.8.313).
Thank you Alex!!! :) :+1:
Another solution is to use java.time and kill a dependency
https://github.com/ghadishayban/transit-java/commit/4868bb4aef7db0eabd0aac6855f998aa0aa90eca
When using Java 10 (or 9), transit cannot decode verbose time. such as
~t2018-12-31T00:00:00.000Z
Symptom:
Minimal repro example:
Cause:
com.cognitect.transit.impl/ReaderHandlers.java, line 248 uses
javax.xml.bind.DatatypeConverter.parseDateTime
:Java 10 (and 9) introduces modules, and javax.xml.bind is no longer included by default. https://www.deps.co/blog/how-to-upgrade-clojure-projects-to-use-java-9/
Suggestion:
Use a different method to read the time which is compatible with Java 8 and 10? (to avoid having to use Java flags to enable the javax.xml.bind module).