One thing I think JPA is lacking is the ability to map read-only result classes,
without annotating them as @Entity and making the provider expect
table for them.
ConstructorResult is a pretty hacky way of getting there and loses some of the
benefits like lazy loading collections and in Hibernate's
If we can do that, it would be just awesome.
On Fri, Dec 2, 2016 at 7:10 PM, Steve Ebersole wrote:
> They will, and the spec group has had mentions of that happening and no
> response from the EG chair. We should offer a project on our Jira! ;)
>
>
> On Fri, Dec 2, 2016 at 11:06 AM Vlad Mihalce
They will, and the spec group has had mentions of that happening and no
response from the EG chair. We should offer a project on our Jira! ;)
On Fri, Dec 2, 2016 at 11:06 AM Vlad Mihalcea
wrote:
> That's a great idea. The only problem with the JPA EG is that there wasn't
> any response to emai
That's a great idea. The only problem with the JPA EG is that there wasn't
any response to emails in months. We could at least create a JIRA issue for
this. My only concern is that the JPA Jira and other resources are hosted
on java.net which will be deactivated on April next year.
Vlad
On Fri, D
On 2 December 2016 at 16:49, Steve Ebersole wrote:
> But on Java 6 there is the hack we used to use. Using Closeable instead and
> Java 8 recognizing that as well.
Right, I added that as comment on JPA_SPEC-77.
>
> On Fri, Dec 2, 2016 at 10:48 AM Steve Ebersole wrote:
>>
>> +1
>>
>> we should
But on Java 6 there is the hack we used to use. Using Closeable instead
and Java 8 recognizing that as well.
On Fri, Dec 2, 2016 at 10:48 AM Steve Ebersole wrote:
> +1
>
> we should start collecting a list. And voila:
> https://github.com/hibernate/hibernate-orm/wiki/Post-JPA-2.1-proposals-wor
+1
we should start collecting a list. And voila:
https://github.com/hibernate/hibernate-orm/wiki/Post-JPA-2.1-proposals-working-doc
:)
On Fri, Dec 2, 2016 at 10:31 AM Sanne Grinovero wrote:
> We updated several Hibernate APIs to allow using the
> try-with-resources pattern a while back,
> and
Following up on myself, I found references on the expert group and the issue:
- https://java.net/jira/browse/JPA_SPEC-77
It seems it's not being considered for JPA 2.2 as it would break
people on Java 6.
On 2 December 2016 at 16:26, Sanne Grinovero wrote:
> We updated several Hibernate APIs to
We updated several Hibernate APIs to allow using the
try-with-resources pattern a while back,
and I've been finding that quite handy.
Had to write some code using JPA's EntityManager these days; in
contrast it feels it's stuck somewhere between the stone age and the
dark ages to not be able to do
