Lukas Jungmann

well, there are more to this. If one looks at the content of the EclipseLink, there are components which do not make much sense for pure-jpa implementation - SDO is...

@keilw this was archived but we found an issue which needs to be fixed, so we unarchived this and will archive it (and port all changes to ee4j) once its...

wrt test - take a look at [jpa/eclipselink.jpa.testapps](https://github.com/eclipse-ee4j/eclipselink/tree/master/jpa/eclipselink.jpa.testapps) and try to find an existing test this could be added to - `jpa.test.advanced` or `jpa.test.jpql` look like good candidates; it does...

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

@glassfishrobot Commented Reported by mkarg

@glassfishrobot Commented mkarg said: I would really appreciate it if someone of the JPA spec team could at least comment on this more than two years old proposal. 

@glassfishrobot Commented @lukasj said: this make sense to me. Should check if there are other useful/commonly used hints to be defined by the spec.

@glassfishrobot Commented pbenedict said: For clarity's sake, EclipseLink's "read-only" hint regards how it manages the first-level cache during a query; it's not about a making the transaction read-only.

@glassfishrobot Commented mkarg said: A general "read-only" JPA property should simply allow the application programmer to tell JPA that the result of the query will never get updated by the...

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