te')); return $arr; } /* 遍历用户所有主题 * @param $uid 用户ID * @param int $page 页数 * @param int $pagesize 每页记录条数 * @param bool $desc 排序方式 TRUE降序 FALSE升序 * @param string $key 返回的数组用那一列的值作为 key * @param array $col 查询哪些列 */ function thread_tid_find_by_uid($uid, $page = 1, $pagesize = 1000, $desc = TRUE, $key = 'tid', $col = array()) { if (empty($uid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('uid' => $uid), array('tid' => $orderby), $page, $pagesize, $key, $col); return $arr; } // 遍历栏目下tid 支持数组 $fid = array(1,2,3) function thread_tid_find_by_fid($fid, $page = 1, $pagesize = 1000, $desc = TRUE) { if (empty($fid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('fid' => $fid), array('tid' => $orderby), $page, $pagesize, 'tid', array('tid', 'verify_date')); return $arr; } function thread_tid_delete($tid) { if (empty($tid)) return FALSE; $r = thread_tid__delete(array('tid' => $tid)); return $r; } function thread_tid_count() { $n = thread_tid__count(); return $n; } // 统计用户主题数 大数量下严谨使用非主键统计 function thread_uid_count($uid) { $n = thread_tid__count(array('uid' => $uid)); return $n; } // 统计栏目主题数 大数量下严谨使用非主键统计 function thread_fid_count($fid) { $n = thread_tid__count(array('fid' => $fid)); return $n; } ?>jax rs - Format of java.sql.Timestamp in JSON has changed - Stack Overflow
最新消息:雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客

jax rs - Format of java.sql.Timestamp in JSON has changed - Stack Overflow

programmeradmin3浏览0评论

When upgrading a rest service from JEE7 to jakarta.jakartaee-api (v 10.0.0) there is an unwanted change in format of java.sql.Timestamp timestamps. The timestamps used to be like this

{"timestamp": 1568281963809}

but now they are like this

{"timestamp": "2019-09-12T10:52:43.808Z[UTC]"}

In the java code the json response is generated simply like this:

return Response.ok(someDto).build();

The parameter someDto is a java object that has many fields including some Timestamps. The json is otherwise just fine, but the timestamps have this wrong string format. The clients that are calling the rest interface do not like the formatted string at all as they are expecting an integer value.

What is the best and easiest way to change the format back as it was? It should be the default?

发布评论

评论列表(0)

  1. 暂无评论