dmatej
commented
5 months ago I believe you cannot mix java.util.Date (rather obsoleted type) and Java Time api. Replace the java.util.Date time you used with the java.time.LocalDate.
Open black-pwq opened 5 months ago
dmatej
commented
5 months ago I believe you cannot mix java.util.Date (rather obsoleted type) and Java Time api. Replace the java.util.Date time you used with the java.time.LocalDate.
pzygielo
commented
5 months ago Not exactly this:
But it perhaps could be discussed with yasson project.
black-pwq
commented
5 months ago I believe you cannot mix java.util.Date (rather obsoleted type) and Java Time api. Replace the java.util.Date time you used with the java.time.LocalDate.
@dmatej Thanks for you suggestion. And I agree that java.util.Date is not the perfect object for time-related conversion (I use it mainly for compatibility reason). However, in my tests, format like "2020-12-12T17:17" will be deserialized to a Date object leaving the seconds field to be zero. I failed to find what are the accepted ISO 8601 formats in JSON-B spec. I am new to Jakarta EE and glassfish, if I miss something, please tell me. Thanks!
OndroMih
commented
5 months ago Looking at Yasson code, it looks like Yasson only tries to parse Date+Time (https://github.com/eclipse-ee4j/yasson/blob/master/src/main/java/org/eclipse/yasson/internal/deserializer/types/DateDeserializer.java#L47) and does respect what the spec says in https://jakarta.ee/specifications/jsonb/3.0/jakarta-jsonb-spec-3.0#java-util-date-calendar-gregoriancalendar:
The serialization format of java.util.Date, Calendar, GregorianCalendar instances with no time information is ISO_DATE.
If time information is present, the format is ISO_DATE_TIME.This should be fixed in Yasson. I'll see if I can fix it there.
OndroMih
commented
5 months ago By the way, @black-pwq , until this is fixed, you can use a Jakarta REST provider to change the default date format. If you want to change the date format only for this specific REST method, it's also possible using reflection in the provider, like this:
@Provider
public class JSONConfigurator implements ContextResolver<Jsonb> {
@Context
private ResourceInfo ri;
@Override
public Jsonb getContext(Class<?> type) {
// Configures JSON-B mapper to use
JsonbConfig config = new JsonbConfig();
/* Uses injected context ResourceInfo to check whether
the resource method to be executed is on the TestResource class and has @Path("test") annotation.
Only for that method it will configure JSON Binding to use a ISO_DATE format
*/
if (TestResource.class.isAssignableFrom(ri.getResourceClass())
&& ri.getResourceMethod().isAnnotationPresent(Path.class)) {
String path = ri.getResourceMethod().getAnnotation(Path.class).value();
if ("test".equals(path)) {
config.withDateFormat("yyyy-MM-dd[XXX]", null);
}
}
return JsonbBuilder.create(config);
}
}There's an issue for this already raised in Yasson project: https://github.com/eclipse-ee4j/yasson/issues/487
OndroMih
commented
1 month ago I raised a pull request in Yasson: https://github.com/eclipse-ee4j/yasson/pull/648
@black-pwq , @pzygielo , please review it and let me know if you think UTC should be used instead of the local timezone.
Environment Details
Problem Description
JAX-RS runtime don't bind string like "2024-12-12" to java.util.Date. Here's example that don't work:
ISO 8601 date only string should be supported as stated in JSON-B 3.0:
The above example reports:
Steps to reproduce
Register an endpoint like the above one, and make a POST to it.