Lukas Jungmann

@glassfishrobot Commented pbenedict said: That is an interesting requirement. I've always been in control of my entities so I haven't encountered your dilemma. If the version isn't being exposed to...

@glassfishrobot Commented mkarg said: Yes, in fact our application provides services upon any "unknown" set of entities provided by third parties: We accept JPA QL and we return entities –...

@glassfishrobot Commented neilstockton said: This requirement seems reasonable to me, and is already available in the JDO API. In JDO you can also have a surrogate version (i.e no field...

@glassfishrobot Commented This issue was imported from java.net JIRA JPA_SPEC-74

* **Issue Imported From:** https://github.com/javaee/jpa-spec/issues/163 * **Original Issue Raised By:**@jacekkruger * **Original Issue Assigned To:** Unassigned

@ghost Commented Of all the `java.time` types, it is `Instant` that is designed exactly to represent a point in time, so it should be supported. It is also the only...

* **Issue Imported From:** https://github.com/javaee/jpa-spec/issues/112 * **Original Issue Raised By:**@glassfishrobot * **Original Issue Assigned To:** @ldemichiel

@glassfishrobot Commented Reported by neilstockton

@glassfishrobot Commented neilstockton said: Perhaps this bug ought to be fixed in JPA 2.2 since it is trivial to do?

@glassfishrobot Commented This issue was imported from java.net JIRA JPA_SPEC-112